Mercurial > repos > kkonganti > cfsan_centriflaken
annotate 0.2.1/README.md @ 12:b55b48954b95
"planemo upload"
| author | kkonganti |
|---|---|
| date | Tue, 28 Jun 2022 13:06:08 -0400 |
| parents | 77494b0fa3c7 |
| children | 30191f39a957 |
| rev | line source |
|---|---|
| kkonganti@0 | 1 # CPIPES (CFSAN PIPELINES) |
| kkonganti@0 | 2 |
| kkonganti@0 | 3 ## The modular pipeline repository at CFSAN, FDA |
| kkonganti@0 | 4 |
| kkonganti@0 | 5 **CPIPES** (CFSAN PIPELINES) is a collection of modular pipelines based on **NEXTFLOW**, |
| kkonganti@0 | 6 mostly for bioinformatics data analysis at **CFSAN, FDA.** |
| kkonganti@0 | 7 |
| kkonganti@0 | 8 --- |
| kkonganti@0 | 9 |
| kkonganti@0 | 10 ### **Pipelines** |
| kkonganti@0 | 11 |
| kkonganti@0 | 12 --- |
| kkonganti@0 | 13 **CPIPES**: |
| kkonganti@0 | 14 |
| kkonganti@0 | 15 1. `centriflaken` : [README](./readme/centriflaken.md). |
| kkonganti@0 | 16 2. `centriflaken_hy` : [README](./readme/centriflaken_hy.md). |
| kkonganti@0 | 17 |
| kkonganti@0 | 18 #### Workflow Usage |
| kkonganti@0 | 19 |
| kkonganti@0 | 20 Following is the example of how to run the `centriflaken` pipeline on the **CFSAN** raven cluster. |
| kkonganti@0 | 21 |
| kkonganti@0 | 22 ```bash |
| kkonganti@0 | 23 module load cpipes/0.1.0-test |
| kkonganti@0 | 24 |
| kkonganti@0 | 25 cpipes --pipeline centriflaken [options] |
| kkonganti@0 | 26 ``` |
| kkonganti@0 | 27 |
| kkonganti@0 | 28 Example: |
| kkonganti@0 | 29 |
| kkonganti@0 | 30 ```bash |
| kkonganti@0 | 31 cd /hpc/scratch/$USER |
| kkonganti@0 | 32 mkdir nf-cpipes |
| kkonganti@0 | 33 cd nf-cpipes |
| kkonganti@0 | 34 cpipes \ |
| kkonganti@0 | 35 --pipeline centriflaken \ |
| kkonganti@0 | 36 --input /path/to/fastq_pass_dir \ |
| kkonganti@0 | 37 --output /path/to/where/output/should/go \ |
| kkonganti@0 | 38 --flye_nano_raw \ |
| kkonganti@0 | 39 --user_email Firt.Last@fda.hhs.gov \ |
| kkonganti@0 | 40 -profile raven |
| kkonganti@0 | 41 ``` |
| kkonganti@0 | 42 |
| kkonganti@0 | 43 The above command would run the pipeline and store the output wherever the author of the workflow decided it to be and the **NEXTFLOW** reports are always stored in the current working directory from where `cpipes` is run. For example, for the above command, a directory called `CPIPES-centriflaken` would hold all the **NEXTFLOW** |
| kkonganti@0 | 44 related logs, reports and trace files. |
| kkonganti@0 | 45 |
| kkonganti@0 | 46 ### **PRE ALPHA** |
| kkonganti@0 | 47 |
| kkonganti@0 | 48 --- |
| kkonganti@0 | 49 This modular structure and flow is still in rapid development and may change depending on assessment of various computational topics and other considerations. |