NeMo 2.0 SFT PEFT notebooks
State: closed | Pull request: yes
Labels: name: audio

# What does this PR do ?

NeMo 2.0 SFT PEFT notebook

**Collection**: [Note which collection this PR will affect]

# Changelog 
- Add specific line by line info of high level changes in this PR.

# Usage
* You can potentially add a usage example below

```python
# Add a code snippet demonstrating how to use this 
```

# 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**:
- [ ] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] Did you write any new necessary tests?
- [ ] Did you add or update any necessary documentation?
- [ ] 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
- [ ] 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](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to # (issue)


This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or update or this will be closed in 7 days.

<!-- pylint-output-strict-mode-false -->

beep boop 🤖: 🙏 The following files have warnings. In case you are familiar with these, please try helping us to improve the code base.

---

Your code was analyzed with PyLint. The following annotations have been identified:

```
************* Module nemo.collections.llm.api
nemo/collections/llm/api.py:68:0: C0301: Line too long (135/119) (line-too-long)
nemo/collections/llm/api.py:224:0: C0301: Line too long (135/119) (line-too-long)
nemo/collections/llm/api.py:355:0: C0301: Line too long (121/119) (line-too-long)
nemo/collections/llm/api.py:256:0: C0116: Missing function or method docstring (missing-function-docstring)
nemo/collections/llm/api.py:316:0: C0116: Missing function or method docstring (missing-function-docstring)
nemo/collections/llm/api.py:328:0: C0116: Missing function or method docstring (missing-function-docstring)
nemo/collections/llm/api.py:490:0: C0116: Missing function or method docstring (missing-function-docstring)

-----------------------------------
Your code has been rated at 9.72/10
```

---

Thank you for improving NeMo's documentation!

Please create a README outside these notebooks, with pre-requisites and requirements, instructions to pull the container, and launch the notebook

Please remove any (advanced) configurations that are not needed for a successful run with the data, especially if defaults work well. These add cognitive load to the end user, who may - 
* don't know or have the patience or time to understand each configuration
* feel they don't know how to configure this even if they understand what it means

We should just link to the API reference and config documentation when it's available. 

Example: Do we need to show "store_optimizer_states" in a beginner notebook?

![image](https://github.com/user-attachments/assets/6f5d0c02-7f6a-422f-8f82-bb5578a1d218)

Thanks!

> Please remove any (advanced) configurations that are not needed for a successful run with the data, especially if defaults work well. These add cognitive load to the end user, who may -
> 
> * don't know or have the patience or time to understand each configuration
> * feel they don't know how to configure this even if they understand what it means
> 
> We should just link to the API reference and config documentation when it's available.
> 
> Example: Do we need to show "store_optimizer_states" in a beginner notebook?
> 
> ![image](https://private-user-images.githubusercontent.com/20920371/387381500-6f5d0c02-7f6a-422f-8f82-bb5578a1d218.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzIwNDA1ODksIm5iZiI6MTczMjA0MDI4OSwicGF0aCI6Ii8yMDkyMDM3MS8zODczODE1MDAtNmY1ZDBjMDItN2Y2YS00MjJmLThmODItYmI1NTc4YTFkMjE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTE5VDE4MTgwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTIwZTE3MGI5ZDZlMDhiMDA1NWU1YzZlYzZjYmM2MWE2ZWU2ZTg2NzZkZDg1M2MwZWU0OTQ1NDBiNDA0NTFlY2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.AUULtYB5lxQT8XZY-sSbfaZ4AgmIW_iiZf0tYdu-mE8)
> 
> Thanks!

Just changed it to the same simple for as in the trainer. Kept only TP param.