Conversation
Uses cnn-hpc4wc's remove-committed-mnist branch, which downloads MNIST data on first run instead of committing it to the repo.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Dear Oli,
We would like to hereby submit our project for the course HPC4WC, as requested via PR.
During our developement we had downloaded the MNIST data into our repo. In order not to spam/bloat your repo, we rewrote the code to download the data on first use. Due to our accounts no longer allowing for slurm jobs on alps (see message on Slack, we haven't heard back so we will submit now because the deadline is tomorrow), we were only able to test this on the login node (which requires activating a uenv and venv, see readme).
Should it not run as a slurm job (which only requires running "make all"), we can also upload the original version with the data downloaded which definitely runs. I hope this compromise of convenience and certainty is also in your best interest, otherwise let us know.
Although the report (in report folder) and the repo should be able to explain usage, our thoughts and results, we are always glad to clarify in case there are questions.
Best,
Ari, Matteo, Nicola