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

RE: IsONclust on ONY; spot died with <Signals.SIGILL: 4>. #21

Open
Malabady opened this issue Mar 9, 2022 · 2 comments
Open

RE: IsONclust on ONY; spot died with <Signals.SIGILL: 4>. #21

Malabady opened this issue Mar 9, 2022 · 2 comments

Comments

@Malabady
Copy link

Malabady commented Mar 9, 2022

Hi
I am running isONclust in a Conda environment and the spoa and medaka modules are loaded before the run.

Here is my commands:

ml Miniconda3/4.10.3
source activate isonclust
ml spoa/4.0.0-GCC-8.3.0
ml minimap2/2.22-GCC-8.3.0
ml medaka/1.5.0

isONclust --ont --use_old_sorted_file --fastq ./isONclust-out2/sorted.fastq  --outfolder isONclust-out2 --consensus  --t 24

the run failed in the consesus step when running spoa with the following kill signal.

Traceback (most recent call last):
  File "/home/malabady/.conda/envs/isonclust/bin/isONclust", line 263, in <module>
    main(args)
  File "/home/malabady/.conda/envs/isonclust/bin/isONclust", line 127, in main
    center = consensus.run_spoa(reads_path.name, os.path.join(work_dir,"spoa_tmp.fa"), "spoa")
  File "/home/malabady/.conda/envs/isonclust/lib/python3.10/site-packages/modules/consensus.py", line 89, in run_spoa
    subprocess.check_call([ spoa_path, reads, "-l", "0", "-r", "0", "-g", "-2"], stdout=output_file, stderr=null)
  File "/home/malabady/.conda/envs/isonclust/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['spoa', '/tmp/tmp_12sh3ko/reads_tmp.fq', '-l', '0', '-r', '0', '-g', '-2']' died with <Signals.SIGILL: 4>.

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

@ksahlin
Copy link
Owner

ksahlin commented Mar 10, 2022

Hi @Malabady,

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).

Best.
K

@ksahlin
Copy link
Owner

ksahlin commented Mar 10, 2022

...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.

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

No branches or pull requests

2 participants