DRAP is composed by tree independent workflows: runDrap, runMeta and runAssessment.

This workflow is used to produce an assembly from one sample/tissue/development stage.
From the single-end reads (R1) or the paired-end reads (R1 and R2) of the sample it generate an assembly and a report.

Outputs:

  • The report contains the metrics of the sequences during all the step of the processing. OUT_FOLDER/report/DRAP_report.html
  • The assembly exists in several version. Each version comes from the same file with a contig filter on the FPKM. OUT_FOLDER/transcripts_fpkm_*.fa
  • Workflow end status:
    • If the workflow is correctly ended it exists a file OUT_FOLDER/00-ASSEMBLY_COMPLETE.
    • If the workflow has encountered an error it exists a file OUT_FOLDER/00-ERROR_AT_*_STEP (for more details see the log folder: OUT_FOLDER/err_log/*).

Execution:

Runtime statistics for runDrap on public datasets are available here.

This workflow is used to produce merge assemblies on several samples/tissues/development stages in one assembly without redundancy.

Outputs:

  • The report contains the metrics of the sequences during all the step of the processing. OUT_FOLDER/report/DRAP_report.html
  • The assembly exists in several version. Each version comes from the same file with a contig filter on the FPKM. OUT_FOLDER/transcripts_fpkm_*.fa
  • Workflow end status:
    • If the workflow is correctly ended it exists a file OUT_FOLDER/00-META-ASSEMBLY_COMPLETE.
    • If the workflow has encountered an error it exists a file OUT_FOLDER/00-ERROR_AT_*_STEP (for more details see the log folder: OUT_FOLDER/err_log/*).

This workflow is used to evaluate the quality of one assembly or compare several assemblies produced on the same dataset.
From one or more assembly (generated by DRAP or not) it generate a report.

Outputs: