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
Previously discussed in #23 specifically about fastq files.
Tripal Galaxy presents a form with allowed file types based on those specified in the Galaxy tool, however the type matching is too strict. For example, the Trimmomatic tool lists the following types as input:
fastqsanger
fastqsanger.gz
fastqillumina
fastqillumina.gz
fastqsolexa
fastqsolexa.gz
However, these are just the types, and not necessarily the extensions that these file types may have, such as fastq, fastq.gz, fq, fq.gz.
There are other file types as well that run into this error.
In the PR/Commit, for #23, there is a TODO item to allow site admins to define a list of filetype aliases (for lack of better term). This, in addition to a few preset examples of common filetype aliases, such as fastq, should be sufficient.
The text was updated successfully, but these errors were encountered:
It seems some tools do not report what file types they require in a way that Tripal Galaxy can interpret, and this alias functionality breaks. Inserting an "Input Dataset" tool before the actual processing tool (like hisat) is a workaround for this.
Previously discussed in #23 specifically about fastq files.
Tripal Galaxy presents a form with allowed file types based on those specified in the Galaxy tool, however the type matching is too strict. For example, the Trimmomatic tool lists the following types as input:
However, these are just the types, and not necessarily the extensions that these file types may have, such as fastq, fastq.gz, fq, fq.gz.
There are other file types as well that run into this error.
In the PR/Commit, for #23, there is a TODO item to allow site admins to define a list of filetype aliases (for lack of better term). This, in addition to a few preset examples of common filetype aliases, such as fastq, should be sufficient.
The text was updated successfully, but these errors were encountered: