Allow users to define memory usage in 'samtools sort' #362
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 PR makes the following changes:
CPU/juicer.sh
andCPU/mega_from_bams_diploid.sh
, users can define memory per thread insamtools sort
using--mem
, for example,--mem 8G
samtools sort
is calculated based on the preexisting resource requestsWith the ability to increase the memory per thread setting, it will reduce the number of temporary files produced during sorting. With large dataset, users can set a larger value to prevent the "Too many open files" error from happening (e.g. #343), as the default used by
samtools sort
is only 768M per thread.