Update dashboard environment lock file#455
Merged
Merged
Conversation
This was referenced Jun 17, 2026
Contributor
|
I confirm that the new environment works well on MacOS. Note that I am getting this warning when downloading the model: However, I think that this is a minor issue, and could be fixed later, e.g. by updating the environment for training (and building a new Docker image to push to the NERSC registry). |
RemiLehe
approved these changes
Jun 18, 2026
Member
Author
Yes, I have been getting that warning for a long time, well before this PR. I agree we should update the ML training environment too. |
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
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.
Overview
Dashboard environment update extracted from #439.
Details
I recreated the environment lock file without changing the base file, so this only updates the existing packages:
I propose that we merge this first and then extract from #439 the addition of the AmSC Python client to the environment (base file and lock file) in a separate PR (#456), to keep things cleaner and easier to debug, revert, bisect, etc.