Changes between Initial Version and Version 2 of Ticket #533


Ignore:
Timestamp:
Dec 10, 2013, 9:20:18 AM (10 years ago)
Author:
Nicklas Nordborg
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #533

    • Property Milestone Reggie v2.x → Reggie v2.15
    • Property Summary Add primary analysis section to Reggie → Add secondary analysis section to Reggie

  • Ticket #533 – Description

    initial v2  
    1 This is the master ticket for adding primary analysis registration functionality to Reggie. The primary analysis is the steps done from sequencing down to expression values have been generated, including demux and alignment against a reference genome.
     1This is the master ticket for adding secondary analysis registration functionality to Reggie. The secondary analysis is the steps done from sequencing down to expression values have been generated, including demux and alignment against a reference genome.
    22
    3 No details are available yet, but it is expected that this ticket is divided into sub-tickets.
     3Note! Primary analysis is the base calling performed by the Illumina software during the sequencing.
     4
     5The pipeline will be something like this. See the other tickets (to be created) for more information about each step:
     6
     7 1. Register sequencing as ended. Part of the "Library preparation wizards" section and done by someone in the lab.
     8
     9 2. Confirm sequencing as completed. First wizard in the "Secondary analysis wizards" section. Used to decide if the sequenced data is ok or not. If ok, continue with demuxing, otherwise flag pools for re-sequencing.
     10
     11 3. Start demux and merge. This wizard is starts the demux and merge operations.
     12
     13 4. Register demux and merge as ended. At the end we have one "!MergedSequences" item for each "Library" from the flow cells that was sequenced. A count of the number of reads for each library must be recorded and is used to determine if the library needs to be re-sequenced or not. FASTQ files for each library are stored on the server.
     14
     15 5. Start filtering and alignment. Bowtie and TopHat is used to first filter and then align against a pre-defined set of transcripts.
     16
     17 6. Register filtering and alignment as ended. At the end we have one "!AlignedSequences" item for each "Library" from the flow cells that was sequenced. BAM files for each library are stored on the server.
     18
     19 7. Start feature extraction. Cufflinks is used to calculate expression values.
     20
     21 8. Register feature extraction. At the end we have one "!RawBioAssay" item for each "Library" from the flow cells that was sequenced. FPKM files are uploaded to BASE and imported into the database.