goodwright / clipseq

The primary analysis pipeline for CLIP samples.
MIT License
1 stars 4 forks source link

CLIP Analysis

Full documentation here, salient usage details summarised below.

Cross-linking and immunoprecipitation followed by sequencing (CLIP) has allowed high resolution studies of RNA binding protein (RBP)-RNA interactions at transcriptomic scale.

This pipeline enables analysis of various forms of single-end CLIP data including variants of iCLIP (eg. irCLIP, iCLIP2, iiCLIP) and eCLIP (note that we have achieved comparable results using this pipeline to study reformatted paired-end eCLIP also). The pipeline currently doesn't support mutation calling and therefore might not be suitable for PAR-CLIP analysis, but we plan to include this at a future date.

This DSL2 CLIP-Seq pipeline is written and maintained by Goodwright in collaboration with Ule lab and the developers of the DSL1 nf-core/clipseq pipeline.

Quick-start

To test the pipeline, use the associated config file and run it with the profiles test and the container engine you wish to use eg. docker. For example:

nextflow run main.nf -profile test,docker

Full dataset testing of 9 iCLIP samples can also be run using profile test_full. A test can also be run that skips all preparing of annotations/indexes using profile test_no_prep_genome.

Input

If you require all reference files (eg. genomic indexes, filtered and segmented gtf...) to be generated the minimal input is:

group replicate fastq_1 fastq_2
TDP43_1 1 s3://nf-core-awsmegatests/clipseq/input_data/fastq/ERR1530360.fastq.gz

If you are providing all reference files then the following additional files must be provided (note these are all produced by the prepare_clipseq subworkflow automatically if they are not provided to the pipeline):

Output

When the full pipeline is run, output is organised into 6 folders:

Authors and contact

This DSL2 CLIP-Seq pipeline is written and maintained by Goodwright in collaboration with Ule lab and the developers of the DSL1 nf-core/clipseq pipeline. To raise any issues or comments with the pipeline you can (in order of preference):