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
Thank you for the wonderful tool! I was testing this out earlier this week and ran into an issue as follows:
INFO [job extract_protein] /tmp/48sbgcsb$ samtools
faidx
--output
output.fasta
--region-file
/tmp/qkhr8fv0/stgf37b22d0-9409-4aeb-ab28-6ba52a517ec7/proteins1.txt
/tmp/qkhr8fv0/stgf94fefbd-b6be-49c5-8ce9-50df72640298/proteins.fasta
samtools: /d/Apps/Miniconda/bin/../lib/libtinfow.so.6: no version information available (required by samtools)
samtools: /d/Apps/Miniconda/bin/../lib/libncursesw.so.6: no version information available (required by samtools)
samtools: /d/Apps/Miniconda/bin/../lib/libncursesw.so.6: no version information available (required by samtools)
[W::fai_get_val] Reference W2RFS7 not found in FASTA file, returning empty sequence
[faidx] Failed to fetch sequence in W2RFS7
WARNING [job extract_protein] exited with status: 1
WARNING [job extract_protein] completed permanentFail
WARNING [step extract_protein] completed permanentFail
INFO [workflow extract_region_pairs] completed permanentFail
ERROR Workflow cannot make any more progress.
WARNING Final process status is permanentFail
Traceback (most recent call last):
File "/d/Apps/Miniconda/bin/lukasa.py", line 71, in
workflow_output_str = subprocess.check_output(cwl_commandline)
File "/d/Apps/Miniconda/lib/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/d/Apps/Miniconda/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['cwltool', '--no-container', '/d/Apps/Miniconda/share/lukasa/lukasa.cwl', '/tmp/tmp7njg_qgc']' returned non-zero exit status 1.
This is an excerpt from the log. I also extracted the sequences for this particular protein when I ran metaeuk separately, which didn't fail.
Thanks for the report @harish0201. I think I know where the problem is coming from - it parses the sequence header to extract MetaEuk alignment information.
I am currently quite actively developing the tool so I will try and fix this bug in a future release.
Hi!
Thank you for the wonderful tool! I was testing this out earlier this week and ran into an issue as follows:
This is an excerpt from the log. I also extracted the sequences for this particular protein when I ran metaeuk separately, which didn't fail.
Here they are:
The codon sequences:
I'm not sure where the issue is, because it stops here randomly. I can send the protein and contig fasta if needed.
The text was updated successfully, but these errors were encountered: