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

Error using --add-orf-stop #88

Closed
berkelem opened this issue Mar 4, 2024 · 5 comments
Closed

Error using --add-orf-stop #88

berkelem opened this issue Mar 4, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@berkelem
Copy link

berkelem commented Mar 4, 2024

Hi, I am encountering an error when I add the --add-orf-stop option to a metaeuk easy-predict run.

Here's my command:

metaeuk easy-predict --threads 12 GCA_000192795.1_Vavr_culi_floridensis_V1_genomic.fna busco_downloads/lineages/fungi_odb10/refseq_db.faa test_output.fna tmp/ --max-intron 60000 --max-seq-len 70000 --min-exon-aa 15 --max-overlap 15 --min-intron 5 --overlap 1 --add-orf-stop -s 4.5

This works fine without the --add-orf-stop option, but once I add it in I get

ERROR: strand is MINUS but the contig coordinates are positive. Soemthing is wrong.

The relevant line in the code base is https://github.com/soedinglab/metaeuk/blob/master/src/exonpredictor/unitesetstofasta.cpp#L61

Might this be a bug?

@elileka
Copy link
Member

elileka commented Apr 16, 2024

Hi,

Hmm. Thank you, this needs checking...

Thank you

@elileka elileka added the bug Something isn't working label Apr 16, 2024
@elileka
Copy link
Member

elileka commented Apr 16, 2024

Hi,

I was able to reproduce your problem. The parameter you set is an MMseqs2 parameter, which should be blocked from MetaEuk because it messes it up. But I think you can actually get the info you need about stop codons by setting the MetaEuk param instead:
--write-frag-coords 1.

Thank you for reporting this!

Best,
Eli

@elileka
Copy link
Member

elileka commented Apr 19, 2024

The MMseqs2 parameter was blocked in the latest commit (6643). Please use --write-frag-coords 1 for information about stop codon positions.

@elileka elileka closed this as completed Apr 19, 2024
@berkelem
Copy link
Author

Thanks!

@elileka
Copy link
Member

elileka commented Apr 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants