NVIDIA-NeMo / NVIDIA-NeMo/Automodel
Migration NeMo 2.0 to Automodel
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 963
- Forks
- 318
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 143
Description
Is your feature request related to a problem? Please describe.
There's a few features added in https://github.com/NVIDIA-NeMo/NeMo/pull/13367 that we currently lack
Describe the solution you'd like
Port features from 13367 to automodel
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing NVIDIA-NeMo/NeMo pull request 13367 to identify the features that must be migrated, then inspect the corresponding Automodel implementation and entry points. The work is done when the identified features are available in Automodel and existing validation confirms they behave as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100