Question: Bad Value For -Sequence With -Auto Defined
gravatar for morgan.e.mccall
3.2 years ago by
United States
morgan.e.mccall0 wrote:

I have been importing fasta files into galaxy then attempting to GetOrf on these files.  I have been receiving the same error message for 2 out 6 files and I am hoping you will be able to tell me what was wrong with my formatting of the file that prevented the system from getting the open reading frame.

Error: Unable to read sequence '/galaxy-repl/main/files/012/415/dataset_12415002.dat' Died: getorf terminated: Bad value for '-sequence' with -auto defined




Morgan McCall

galaxy • 713 views
ADD COMMENTlink modified 3.2 years ago by Jennifer Hillman Jackson25k • written 3.2 years ago by morgan.e.mccall0

Note: this is being examined in a bug report

ADD REPLYlink written 3.2 years ago by Jennifer Hillman Jackson25k
gravatar for Jennifer Hillman Jackson
3.2 years ago by
United States
Jennifer Hillman Jackson25k wrote:


From testing various inputs, it seems that this tool has a input line length upper limit. (Likely for technical reason, not a specific setting).

Doing either one of the following resulted in a successful run for your failures.

  • Wrap the fasta sequence with the tool FASTA Width formatter with a width between 40-80. 40 is less commonly used, I tend to use 60, but 80 is the default for most. This creates input that is in strict fasta format (a requirement implied by the tool help stating "sequence" input e.g fasta format, with more details in the tool documentation). For these reasons, it is the prefered solution.
  • Reduce the length of the sequence identifiers. Run Fasta-to-Tabular with the option "How many title characters to keep?". I set this at 20. Then converted back to fasta with Tabular-to-Fasta. Executing the tool with this input was successful. So, the tool is able to accept non-wrapped fasta data, but it appears that length is a factor for this to work. If you ever have a dataset that fails with the same original error after using this method, go ahead and wrap the lines, as the input line length was likely exceeded again, despite the identifier trimming.

Hope this helps! Jen, Galaxy team

ADD COMMENTlink modified 3.2 years ago • written 3.2 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 173 users visited in the last hour