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
If amino acids are used as a mistake for the input, the program could stop.
Current Behavior
Instead, the program runs and then output empty files without erroring out.
Steps to Reproduce (for bugs)
Using metaeuk with protein sequences on accident.
MetaEuk Output (for bugs)
No bugs
Context
This is a very low priority feature but think it could save some headaches with minimal effort on the devs. I have metaeuk set up in quite a few pipelines. I use the same genome identifiers but with assemblies I use .fa and proteins I use .faa. During testing, I accidentally gave metaeuk protein files but thought there was something else going on since it was running without error. I downgraded a few versions then realized it was the input file I was using.
Your Environment
Linux
metaeuk 7.bba0d80=pl5321h6a68c12_0
The text was updated successfully, but these errors were encountered:
Expected Behavior
If amino acids are used as a mistake for the input, the program could stop.
Current Behavior
Instead, the program runs and then output empty files without erroring out.
Steps to Reproduce (for bugs)
Using metaeuk with protein sequences on accident.
MetaEuk Output (for bugs)
No bugs
Context
This is a very low priority feature but think it could save some headaches with minimal effort on the devs. I have metaeuk set up in quite a few pipelines. I use the same genome identifiers but with assemblies I use .fa and proteins I use .faa. During testing, I accidentally gave metaeuk protein files but thought there was something else going on since it was running without error. I downgraded a few versions then realized it was the input file I was using.
Your Environment
Linux
metaeuk 7.bba0d80=pl5321h6a68c12_0
The text was updated successfully, but these errors were encountered: