Opened 10 months ago
Closed 10 months ago
#1562 closed task (fixed)
Implement a wizard or procedure for registering FASTQ files for WGS
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | Reggie v4.52 |
Component: | net.sf.basedb.reggie | Keywords: | |
Cc: |
Description (last modified by )
We are sending samples to an external lab for WGS. When we receive the FASTQ files with the result we need a simple procedure or wizard that is NOT including several manual steps and batch imports from Excel files.
Right now we have aliquots from DNA (normal and tumor) and we need to create items and annotations:
- Library items
- Pipeline
- ExternalOperator
- MergedSequences items
- Pipeline
- DataFilesFolder
- READS
- FASTQ file items
- FlowCellID
- FlowCellType
- LaneNumber
- READS
- ReadLength
- SequencingRunNumber
- SerialNumber
Most information can be extracted from the FASTQ files. We are not sure if the FASTQ files have merged data from different sequencing runs. In that case we may want to split them per flow cell and lane so that they are compatible with existing data.
UPDATE It is better to make this procedure a bit more like the FASTQ import from the RNAseq side. This means that there is a first wizard that will read information from a CSV-file (provided by the external operator) that we use to create child Library and DemuxedSequences items. Then there is a second wizard that processes the FASTQ files and put them in the right place and create the MergedSequences item. Automatica processing and failures can be handled just as we are used to from the RNAseq pipeline (eg. delete the MergedSequences item). So we also need:
- DemuxedSequences items
- Pipeline
- DataFilesFolder
- RawFASTQ
Change History (25)
comment:1 by , 10 months ago
comment:18 by , 10 months ago
Description: | modified (diff) |
---|
comment:25 by , 10 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
In 7533: