(closes #3243) Unify NEMO parallelisation scripts#3443
Merged
Conversation
…ation' into single_nemo_script
Collaborator
Author
|
@LonelyCat124 This is ready for another look, we had a first review some time ago in #3244 and there was open comments there. |
Collaborator
Author
|
@LonelyCat124 Removing 9ee8eb6 has worked here, so this is ready to review again. |
LonelyCat124
requested changes
May 28, 2026
Collaborator
There was a problem hiding this comment.
@sergisiso I think this is almost ready - have a few comments about the new README to fix up.
Collaborator
Author
|
@LonelyCat124 This is ready for another review |
LonelyCat124
approved these changes
Jun 1, 2026
LonelyCat124
left a comment
LonelyCat124
left a comment
Collaborator
There was a problem hiding this comment.
changes look good to me now, happy to merge.
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
2 participants
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 is the continuation of #3244 , I started a new PR because I shared the branch associated with the previous PR with multiple people that may be using them and modifying may break their workflows.
The PR aims to: