Allow variable memory for motioncorr via slurm #225
Merged
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.
Unexpectly large raw data files cause the motion correction service to crash when going to slurm, and there was no way of adjusting that memory request. This adds a memory option to the motion correction service inputs.
Also, this creates a common Dockerfile for Relion, to act as a base for motion correction and class selection and speed up image creation.
The memory aspects will need revisiting in future if the microscopes get large cameras.