Changing sample CLI design; Refactor devices; Trying out quantization #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd may get more in the future)
…ging into the config file every time.
… quantization works; fix a bug on gradient_checkpointing along with use_cache
# Conflicts: # aria/data/datasets.py # aria/data/jsonl_zst.py # aria/run.py # tests/test_data.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aria.run sampleso that I don't have to type in binary name and midi filename every time..cuda(). If cuda not available it will just use CPU in the CLI, but thegreedy_samplefunction will always take an extra paramter regarding which device to put tensors.~- [ ] testing out torch 2.0 quantization features. Working on CPU but cuda still has problems...... ~