Open m3hdad opened 6 months ago
Revisting this @m3hdad just now made me think: do you think this should be solved here or upstream in AMPLify itself?
What do yout think? One hand we can 'fix it' in the pipeline, but 'manual' modification of the input/output files isn't a great idea for a pipeline.
If you agree, could you make an issue on the AMPlify repo, and maybe we can see how fast they are in solving it?
Description of the bug
AMPLIFY_PREDICT fails on some protein sequences. The issue is discussed on slack here. Two input sequences for which AMPLIFY_PREDICT fails/passes are available on Slack.
Pyrodigal and Prodigal were tested as annotation tools. AMPlify v.2.0.0 tested which failed on similar sequences.
Removing stop codon before running AMPlify solves the issue.
.command.err
on AMPLIFY_PREDICT:Command used and terminal output
No response
Relevant files
No response
System information
No response