Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

llama 3.1 has correct max_seq_len for all versions #2203

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

akashc1
Copy link
Contributor

@akashc1 akashc1 commented Dec 23, 2024

Context

What is the purpose of this PR? Is it to

  • add a new feature
  • fix a bug
  • update tests and/or documentation
  • other (please add here)

Please link to any issues this PR addresses. #2202

Changelog

What are the changes made in this PR?

  • Ensure all llama 3.1 instantiations uses the correct max_seq_len the model was originally trained with based on the HF config

Test plan

Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.

  • run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
  • add unit tests for any new functionality
  • update docstrings for any new or updated methods or classes
  • run unit tests via pytest tests
  • run recipe tests via pytest tests -m integration_test
  • manually run any new or modified recipes with sufficient proof of correctness
  • include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example

  • I did not change any public API
  • I have added an example to docs or docstrings

Copy link

pytorch-bot bot commented Dec 23, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/2203

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 23, 2024
@felipemello1
Copy link
Contributor

felipemello1 commented Dec 24, 2024

thanks for the PR, do you mind updating the docstrings too, so they include the new arg? I think that for 405B the default is wrong, it should be 131k.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 23.85%. Comparing base (aa8f365) to head (d2f581c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2203   +/-   ##
=======================================
  Coverage   23.85%   23.85%           
=======================================
  Files         344      344           
  Lines       20658    20658           
=======================================
  Hits         4928     4928           
  Misses      15730    15730           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@RdoubleA
Copy link
Contributor

RdoubleA commented Jan 1, 2025

This seems inconsistent with our other builders, which do not specify a max seq len parameter. If you want to change the default max seq len for llama3_1 you should use the base builder llama3_1() instead of the 8b and 405b builders, as they're meant to expose minimal parameters and give all the defaults to get the correct model. But let us know if this is too prohibitive.

@akashc1
Copy link
Contributor Author

akashc1 commented Jan 6, 2025

@felipemello1 @RdoubleA thank you for the comments, can you please check the updated implementation? I set the correct default from the HF model config for Llama 3.1 models in the _model_builders file.

@akashc1 akashc1 changed the title lora llama 3.1 can accept specified max_seq_len llama 3.1 has correct max_seq_len for all versions Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants