Bug Fix: Convert tensors to scalars for plotting compatibility #909
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
utsavrai
changed the title
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.
Convert Tensor Outputs to Scalars Before Storing in Results
Description:
This commit adjusts the train function to explicitly convert loss and accuracy metrics from PyTorch tensors to Python scalars. This change is implemented right after obtaining the results from
train_stepandtest_stepfunctions. If the metric is a tensor, it is converted to a float using the .item() method, ensuring it is not a tensor residing on the GPU. This prevents TypeError issues when attempting to convert CUDA tensors to NumPy arrays during plotting. The change simplifies downstream data handling and visualization, making our code more robust and easier to maintain.