NVIDIA-NeMo / NVIDIA-NeMo/Automodel

Guidance on adapting a fine-tuning recipe into a pretraining recipe

Open
#1,746 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community-request enhancement waiting-on-customer
Dominant language
Python
Stars
963
Forks
318
Avg merge
3d 20h
Merged PRs (30d)
143

Description

Hi NeMo AutoModel team,

Thanks a lot for this excellent repository. I think the project is very well designed, and the provided recipes are very useful.

I noticed that there are already many fine-tuning recipes in the repo, while the number of pretraining recipes seems relatively limited. My impression is that fine-tuning and pretraining recipes may share a lot of common structure, so I am wondering how to properly adapt a fine-tuning recipe into a pretraining recipe.

Could you please share some suggestions on what parts should typically be changed?

For instance, I assume the modifications may involve things like:

  • training data format and pipeline
  • objective / loss configuration
  • optimizer and scheduler
  • model initialization
  • masking / packing strategy

I would really appreciate any guidance, recommendations, or pointers to relevant examples.

Thank you very much for your time and for maintaining this great repo.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by comparing the repository's existing fine-tuning and pretraining recipes, focusing on the data pipeline, objective or loss, optimizer and scheduler, model initialization, and masking or packing strategy. Done would be documented guidance or a relevant pretraining example.

Written by the indexing model from the issue text.

Assessment

Tech stack
huggingface, python, pytorch
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.