CTDAS functionality #67
Open
Conversation
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
Merging remote to local
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.
This git commit adds CTDAS functionality into the processing chain.
I had to mildly modify some bits of the core code to make them work on Santis and (compared to other jobs) this doesn't run everything as separate SLURM jobs but runs mostly on the front node. For example, I'm running the ERA-5 data requests on the front node, because after making a request we're just waiting for an hour (or two!) before the result is ready to be downloaded, which is not something you want to submit to the supercomputer. The changes I made shouldn't break any of the existing cases.
We discussed this case won't be part of the test case, so it's up to Empa to maintain this processing chain case.