Fix memory limitation and subject/case globbing on slurm script #407
Conversation
This file contains 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
dkuegler
force-pushed
the
fix/slurm/memory-limits
branch
from
0673b2f
to
f45bfea
Compare
fix globbing, so globbing does happen if subjects/cases are read fix number of cpus per surf task (--hint=nomultithread makes sure hyperthreads are automatically allocated)
dkuegler
force-pushed
the
fix/slurm/memory-limits
branch
from
f45bfea
to
9bebc7b
Compare
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.
Adjust memory limits to fail less often
fix globbing, so globbing does happen if subjects/cases are read
confirmation for known bad OASIS cases is running
This specifically is caused by very inconsistent memory usage of mris_sample_parc, which runs into memory limitations for 14GB of memory.