id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc 1299,Import of FASTQ files from external lab,Nicklas Nordborg,Nicklas Nordborg,"This is related to #1295 and is the second step after importing information about the specimen. The import in #1295 should create all items from the specimen down to ~~!MergedBioAssay~~ !DemuxedSquences. The !DemuxedSquences will be different and only represent a single library instead of an entire flow cell. See [6215]. It will probably be a good idea to use the pattern with an item list to control the flow of items between #1295 and this import. It is expected that the FASTQ files have not been processed after the demux except for adapter trimming that has replaced reads with N instead of removing reads from the FASTQ files. The import functionality need to make those FASTQ files ""compatible"" with the FASTQ files we get from the regular demux wizard. This means we have to replicate the following steps: * Bowtie to estimate the fragment size and standard deviation * Trimmomatic step 1 to remove the N reads. This is an alternate version of step 1 in the regular demux and will allow is to get values for the PF_READS and ADAPTER_READS annotations * Trimmomatic step 2 to remove low-quality reads. This is exactly the same as the second step in the regular demux wizard. Auto-confirmation should be supported and continue with the regular secondary analysis workflow (eg. the Legacy pipeline and Hisat alignment). The same checks (for individual items) that are used in the regular demux wizard should be made. A manual confirmation wizard is also needed with options for accepting, retrying the import or flagging the RNA.",task,closed,major,Reggie v4.32,net.sf.basedb.reggie,fixed,,