Skip to content
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

Torch downgrade removed from W3D3 (NeuromatchAcademy#905) #934

Merged

Conversation

colleenjg
Copy link
Contributor

This commit fixes issue #905. torch 2.0 introduced an out of memory bug in the tutorial, which was addressed with commit ed8f9f2 by downgrading to torch 1.11. The pytorch bug was fixed in torch 2.1 through commit fff4a9. Since Google Colab now comes with torch 2.1 installed by default, the downgrade is no longer needed.

I also changed the supervised learning performance reported in table from 98.67% to 98.70%. Unlike the other methods (VAE, SimCLR, etc.), the supervised result has never been perfectly identical on each run. It varies a little bit around 98.70% (from 98.67% to 98.73%, when I've run it). To avoid confusion for users, the first time this result is reported, it is now reported with a ~ (i.e., as ~98.70%) to signal to users that their result may differ slightly from it.

This commit fixes issue NeuromatchAcademy#905. `torch 2.0` introduced an out of memory bug in the tutorial, which was addressed with commit ed8f9f2 by downgrading to `torch 1.11`. The pytorch bug was fixed in `torch 2.1` through commit [fff4a9](pytorch/pytorch@fff4a9d). Since Google Colab now comes with `torch 2.1` installed by default, the out of memory bug no longer occurs when running the notebook without the pytorch downgrade.

I also changed the supervised learning performance reported in table from `98.67%` to `98.70%`. Unlike the other methods (VAE, SimCLR, etc.), the supervised result has never been perfectly identical on each run. It varies a little bit around `98.70%` (from `98.67%` to `98.73%`, when I've run it). To avoid confusion for users, the first time this result is reported, I now report it with a `~` (i.e., as `~98.70%`) to signal to users that their result may differ slightly from the one reported.
@colleenjg colleenjg changed the title Torch downgrade removed Torch downgrade removed from W3D3 (NeuromatchAcademy#905) Oct 23, 2023
@colleenjg
Copy link
Contributor Author

Tagging @spirosChv to let you know about this PR reversing the torch downgrade you implemented a few months ago to fix a new memory bug that showed up in W3D3. :)

TL;DR: torch on Google Colab has now been updated to 2.1. From my tests, this fixes the memory bug you found (as planned!), and so torch no longer needs to be downgraded.

@spirosChv spirosChv merged commit 4ae1d83 into NeuromatchAcademy:main Oct 25, 2023
@spirosChv
Copy link
Collaborator

Fixes this #905

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants