Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constant increase in threads with comma separated list of input files and --parallel parameter #138

Closed
FelixKrueger opened this issue Oct 20, 2017 · 1 comment
Assignees
Labels

Comments

@FelixKrueger
Copy link
Owner

We have been made aware that the specifying a comma separated list of input files in conjunction with the parameter --parallel [cores] seems to lead to a continuous rise of spawned Bismark threads. This would be unintended and prone to fail at some point.

A sample command line with the 3 times the same simulated Yeast FastQ files (with different names for clarity) looks like this:

bismark --genome /bi/scratch/Genomes/Yeast/Saccharomyces_cerevisiae/SGD1/ -1 R1.fastq,simulated_1.fastq,ZZZ_R1.fastq -2 R2.fastq,simulated_2.fastq,ZZZ_R2.fastq --multicore 4
@FelixKrueger FelixKrueger self-assigned this Oct 20, 2017
@FelixKrueger
Copy link
Owner Author

It turned out that for this we only had to properly exit all child processes once the mapping and merging had finished so that they do not also continue to process read pairs 2, 3 and so on...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant