@@ -123,57 +123,57 @@ terminal, so you can see what snakemake is about to perform. Next, the test data
123123is moved to the input directory underneath the new test run directory. Then the
124124entirety of processing can start.::
125125
126- # After constructing the config file and having reference files
127- # (i.e. sampleinfo). You can check the samples associated with the run.
128-
126+ # If conda is not in your path ...
127+
128+ source ${HOME}/miniconda3/etc/profile.d/conda.sh
129+
130+ # Activate iguide environment
131+
132+ conda activate iguide
133+
134+ # After constructing the config file and having reference files (i.e. sampleinfo)
135+ # You can check the samples associated with the run.
136+
129137 iguide list_samples configs/simulation.config.yml
130138
131139 # Create test analysis directory
132- # (The simulation configuration file is used by default and does not need to
133- # be specified)
134-
140+
135141 iguide setup configs/simulation.config.yml
136142
137143 # Process a simulation dataset
138144
139145 iguide run configs/simulation.config.yml -- -np
140146 iguide run configs/simulation.config.yml -- --latency-wait 30
141- zcat analysis/simulation/output/unique_sites.simulation.csv.gz
142147
143- # Processing will complete with a report , but if additional analyses are
144- # required, you can reevaluate the 'incorp_sites' object . Multiple objects
145- # can be evaluated together, just include the run files.
148+ # Processing will complete with several reports , but if additional analyses are required,
149+ # you can re-evaluate a run by its config file . Multiple runs can be evaluated together,
150+ # just include multiple config files.
146151
147- iguide eval analysis /simulation/output/incorp_sites.simulation.rds \
152+ iguide eval configs /simulation.config.yml \
148153 -o analysis/simulation/output/iguide.eval.simulation.test.rds \
149154 -s sampleInfo/simulation.supp.csv
150155
151156 # After evaluation, generate a report in a different format than standard.
152- # Additionally the evaluation and report generation step can be combined using
153- # config file(s) as inputs for the 'report' subcommand. For PDF output, you'll
154- # need to verify that your system has the correct latex-based software
155- # support, such as 'texlive'.
157+ # Additionally the evaluation and report generation step can be combined using
158+ # config file(s) as inputs for the 'report' subcommand (using the -c flag instead of -e).
156159
157160 iguide report -e analysis/simulation/output/iguide.eval.simulation.test.rds \
158161 -o analysis/simulation/reports/report.simulation.pdf \
159162 -s sampleInfo/simulation.supp.csv \
160163 -t pdf
161164
162- # If you are looking for a quick and consise report of the output, use the
163- # 'summary' subcommand with input of either a config file(s) or a single
164- # evaluation file, generated by the 'eval' subcommand.
165-
166- iguide summary -e analysis/simulation/output/iguide.eval.simulation.test.rds
167-
168- # When you are all finished and ready to archive / remove excess files, a
169- # minimal configuration can be achived with the 'clean' subcommand.
165+ # When you are all finished and ready to archive / remove excess files, a minimal configuration
166+ # can be achieved with the 'clean' subcommand.
170167
171168 iguide clean configs/simulation.config.yml
172169
173170 # Or you realized you messed up all the input and need to restart
174171
175172 iguide clean configs/simulation.config.yml --remove_proj
176173
174+ # Deactivate the environment
175+
176+ conda deactivate
177177
178178Uninstall
179179---------
0 commit comments