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
The --consensus parameter was an experimental parameter added after publishing isONclust. It has not been tested well and I would simply suggest not to use it in isONclust.
If you are looking for clustering + consensus forming + barcode removal and some more, you may try NGSpeciesID which is based on isONclust clustering method but adds some features on top of the clustering.
Finally, you should probably not call the --consensus if you are clustering transcript data because the consensus step will not take into account exon differences between transcripts. It is possible you can achieve some level of transcript level consensus forming with NGSpeciesID by setting --aligned_threshold and --mapped_threshold very high (like 0.95) but this is not the intended use of NGSpeciesID and can produce a fairly suboptimal result (depending on the nature of your data).
...and as for the actual runtime error I don't know. As you mention, if you are able to run spoa without error on the instance reported in the error message ('spoa', '/tmp/tmp_12sh3ko/reads_tmp.fq', '-l', '0', '-r', '0', '-g', '-2') it is strange.
I would have expected that this instance would be the command throwing the error.
Hi
I am running isONclust in a Conda environment and the spoa and medaka modules are loaded before the run.
Here is my commands:
the run failed in the consesus step when running spoa with the following kill signal.
I can see
/tmp/tmp_12sh3ko/reads_tmp.fq
and can run spoa on the reads_tmp.fq directly.Any suggestions what's wrong?
Thanks
Magdy
The text was updated successfully, but these errors were encountered: