You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-i sff_file Provide the full path to your target sff file
119
+
-i input_file Provide the full path to your target input file
120
120
-o basefile Provide the full path to your results directory, plus the name you want to give your results
121
121
-c configfile Provide the full path to your configuration file. If none is provided, the program will look in the current working directory and then in ~/.config/4Pipe4rc (in this order) for one. If none is found the program will stop
122
122
-s [RUN_LIST] Specify the numbers corresponding to the pipeline steps that will be run. The string after -s must be given inside quotation marks, and numbers can be joined together or separated by any symbol. The numbers are the pipeline steps that should be run. This is an optional argument and it's omission will run all steps by default'. The numbers, from 1 to 9 represent the following steps:
@@ -130,17 +130,28 @@ optional arguments:
130
130
8 - SSR finder
131
131
9 - 7zip the report
132
132
133
+
-d 454/solexa Declare the type of data being used. Currentlly suported are 454 (454) and Illumina (solexa). Default is 454.
134
+
-p [True/False] Is the data paired end? True/False, default is False.
135
+
133
136
The idea here is that to resume an analysis that was interrupted for example after the assembling process you should issue -s '4,5,6,7,8,9' or -s '456789'. Note that some steps depend on the output of previous steps, so using some combinations can cause errors. The arguments can be given in any order.
134
137
```
135
138
136
139
--------------------------------------------
137
140
138
-
If you wish to run the entire pipeline, just issue something like
141
+
If you wish to run the entire pipeline on 454 data, just issue something like
0 commit comments