Skip to content

migrate nf4 to configs #1857

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

Merged
merged 65 commits into from
Mar 12, 2025
Merged

migrate nf4 to configs #1857

merged 65 commits into from
Mar 12, 2025

Conversation

vkuzo
Copy link
Contributor

@vkuzo vkuzo commented Mar 7, 2025

Summary:

  1. migrate nf4 to configs
  2. create a separate, temporary, workflow file for nf4 to get around
    circular import errors. A future person should properly make nf4 a
    workflow in torchao's dir structure, but that is out of scope for
    this PR.

Note that this technically breaks "BC", but nf4 isn't an official API so there isn't really BC. This does not break the torchtune integration.

Test Plan:

pytest test/dtypes/test_nf4.py

Reviewers:

Subscribers:

Tasks:

Tags:

vkuzo added 8 commits March 7, 2025 06:48
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@vkuzo
Copy link
Contributor Author

vkuzo commented Mar 7, 2025

Copy link

pytorch-bot bot commented Mar 7, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/1857

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 Mar 7, 2025
vkuzo added a commit that referenced this pull request Mar 7, 2025
Summary:

1. migrate nf4 to configs
2. create a separate, temporary, workflow file for nf4 to get around
   circular import errors. A future person should properly make nf4 a
   workflow in torchao's dir structure, but that is out of scope for
   this PR.

Test Plan:

```
pytest test/dtypes/test_nf4.py
```

Reviewers:

Subscribers:

Tasks:

Tags:

ghstack-source-id: 160d039
ghstack-comment-id: 2707042209
Pull Request resolved: #1857
@vkuzo vkuzo added the topic: not user facing Use this tag if you don't want this PR to show up in release notes label Mar 7, 2025
vkuzo added 5 commits March 7, 2025 09:51
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
vkuzo added a commit that referenced this pull request Mar 7, 2025
Summary:

1. migrate nf4 to configs
2. create a separate, temporary, workflow file for nf4 to get around
   circular import errors. A future person should properly make nf4 a
   workflow in torchao's dir structure, but that is out of scope for
   this PR.

Test Plan:

```
pytest test/dtypes/test_nf4.py
```

Reviewers:

Subscribers:

Tasks:

Tags:

ghstack-source-id: f9960e5
ghstack-comment-id: 2707042209
Pull Request resolved: #1857
vkuzo added 3 commits March 7, 2025 10:42
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
vkuzo added 14 commits March 8, 2025 12:16
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
vkuzo added 3 commits March 10, 2025 15:47
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
vkuzo added 2 commits March 10, 2025 16:04
[ghstack-poisoned]
[ghstack-poisoned]
vkuzo added 6 commits March 12, 2025 10:17
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@vkuzo vkuzo changed the base branch from gh/vkuzo/60/head to main March 12, 2025 20:57
@vkuzo vkuzo merged commit ac411bf into main Mar 12, 2025
3 checks passed
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. topic: not user facing Use this tag if you don't want this PR to show up in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants