-
Notifications
You must be signed in to change notification settings - Fork 9
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
Debugging TOL-10M dataset reproduction process #16
base: main
Are you sure you want to change the base?
Conversation
@thompsonmj please check the version I updated. My copy is still running on OSC, but it does seem to be working now. I also updated the directions in #14 to match these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set tag in folder name to match the version (release) of the data.
BTW is there a reason we're invoking the python interpreter through its path semi-hardcoded and into the conda environment, as opposed to simply activating the conda environment first (which presumably needs to be done anyway)? As an aside, conda environments can get quite big in terms of storage they take up, and it's therefore generally not a good idea to place them into one's home directory on a shared HPC. (Home directories on shared HPCs typically have quite a limited storage quota, and group or project directories is normally where a lot more storage is available or at least where it can be added on demand.) |
Co-authored-by: Elizabeth Campolongo <[email protected]>
… reproduce_tol10m
Co-authored-by: Elizabeth Campolongo <[email protected]>
@samuelstevens, this should work as described in updated directions in PR #14. If you encounter any issues or something seems off, please make suggestions there too. |
No description provided.