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

Add DAPT tutorial #11664

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

Add DAPT tutorial #11664

wants to merge 11 commits into from

Conversation

jihyeonRyu
Copy link

@jihyeonRyu jihyeonRyu commented Dec 19, 2024

What does this PR do ?

Add a tutorial for DAPT training using ChipNeMo, provided as a step-by-step guide split into three stages, making it easy for users to follow along with interactive .ipynb notebooks.

Collection: [Note which collection this PR will affect]

Changelog

Added four .ipynb tutorial files under /tutorials/llm/llama-3/dapt to guide users through the DAPT training process.

  • Step 0: Create Dummy Data
  • Step 1: DAPT
  • Step 2: Alignment
  • Step 3: Domain Adapted Retrieval

Usage

You can follow the step-by-step tutorial by navigating to /tutorials/llm/llama-3/dapt and running the provided .ipynb notebooks.

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

  • [ O] Make sure you read and followed Contributor guidelines
  • [ O] Did you write any new necessary tests?
  • [ O] Did you add or update any necessary documentation?
  • [ X] Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • [O] Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

  • Related to # (issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants