id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc 717,Auto-confirmation service,Nicklas Nordborg,Nicklas Nordborg,"For the secondary analysis we should implement an auto-confirmation service. This should monitor the progress of secondary analysis jobs and if the outcome is successful and within a required set of parameters the result should automatically be confirmed and the next step be started. The demux step is always started manually and it should be possible to select if the auto-confirmation should be enabled or not (can we use the `AutoProcessing` annotation?) Results that doesn't pass the auto-confirmation rules should be left for manual confirmation. If the operator decides to confirm and continue it should once again be possible to enable auto-confirmation (eg. all secondary analysis wizards should have this feature). Besides the implicit rule that the job must finish successfully, the following rules should apply: Rules for the demux step: * No `DemuxWarnings` on the sequencing run items * All libraries must get `PT_READS` > 10M * All libraries must have valid `FragmentSizeAvg` and `FragmentSizeStdev` values Rules for the align step: * `ALIGNED_PAIRS` >= 5M (confirm and continue) * `ALIGNED_PAIRS` >= 1M (confirm, flag RNA and continue) * `ALIGNED_PAIRS` < 1M (confirm, flag RNA and stop) Rules for the Cufflinks step: * No extra rules. ",task,closed,critical,Reggie v3.0,net.sf.basedb.reggie,fixed,,