You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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...
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:
The text was updated successfully, but these errors were encountered: