Refactor/improvedgpu: Fixing a bug so that now the user can specify GPU training #23
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
…the accelerator and number of devices can be specified. Also changed the metrics_utils calculations to put the metric equations onto whatever device the data is on.
…y not implemented for subspace methods but that is on the list
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.
Passing the argument
training_modificationstotrain.train_and_save_modelallows the user to use GPU/MPS to train their models, and also to choose the number of devices.The argument is a dictionary with the keys
acceleratoranddevices.This is not implemented for subspace methods yet.