Mercurial > repos > kkonganti > cfsan_centriflaken

comparison 0.2.1/README.md @ 0:77494b0fa3c7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
"planemo upload"
author kkonganti
date Mon, 27 Jun 2022 15:55:37 -0400
parents
children 30191f39a957
comparison
equal deleted inserted replaced
-1:000000000000 0:77494b0fa3c7
1 # CPIPES (CFSAN PIPELINES)
2
3 ## The modular pipeline repository at CFSAN, FDA
4
5 **CPIPES** (CFSAN PIPELINES) is a collection of modular pipelines based on **NEXTFLOW**,
6 mostly for bioinformatics data analysis at **CFSAN, FDA.**
7
8 ---
9
10 ### **Pipelines**
11
12 ---
13 **CPIPES**:
14
15 1. `centriflaken` : [README](./readme/centriflaken.md).
16 2. `centriflaken_hy` : [README](./readme/centriflaken_hy.md).
17
18 #### Workflow Usage
19
20 Following is the example of how to run the `centriflaken` pipeline on the **CFSAN** raven cluster.
21
22 ```bash
23 module load cpipes/0.1.0-test
24
25 cpipes --pipeline centriflaken [options]
26 ```
27
28 Example:
29
30 ```bash
31 cd /hpc/scratch/$USER
32 mkdir nf-cpipes
33 cd nf-cpipes
34 cpipes \
35 --pipeline centriflaken \
36 --input /path/to/fastq_pass_dir \
37 --output /path/to/where/output/should/go \
38 --flye_nano_raw \
39 --user_email Firt.Last@fda.hhs.gov \
40 -profile raven
41 ```
42
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**
44 related logs, reports and trace files.
45
46 ### **PRE ALPHA**
47
48 ---
49 This modular structure and flow is still in rapid development and may change depending on assessment of various computational topics and other considerations.