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
Currently, we use the SRA format for FASTQ headers which prefix the SRR run accession to the original string from the sequencer. This format is not compatible with ArrayExpress and local sources and will pose a problem if we try to generalize batch information extraction for arbitrary FASTQs and not just GEO series.
The solution is to add the --origfmt flag to fastq-dump so that the original header will be used instead.
This might require some adjustment in how Gemma parses the batch information.
The text was updated successfully, but these errors were encountered:
Currently, we use the SRA format for FASTQ headers which prefix the SRR run accession to the original string from the sequencer. This format is not compatible with ArrayExpress and local sources and will pose a problem if we try to generalize batch information extraction for arbitrary FASTQs and not just GEO series.
The solution is to add the
--origfmt
flag tofastq-dump
so that the original header will be used instead.This might require some adjustment in how Gemma parses the batch information.
The text was updated successfully, but these errors were encountered: