File tree Expand file tree Collapse file tree 1 file changed +11
-7
lines changed Expand file tree Collapse file tree 1 file changed +11
-7
lines changed Original file line number Diff line number Diff line change @@ -168,8 +168,12 @@ rm -fR sample_noHQ.vcz
168
168
```
169
169
170
170
``` {code-cell}
171
- vcf2zarr encode sample.icf -s sample_noHQ.schema.json sample_noHQ.vcz
171
+ vcf2zarr encode sample.icf -Qs sample_noHQ.schema.json sample_noHQ.vcz
172
172
```
173
+ :::{tip}
174
+ Use the `` -Q/--no-progress `` flag to suppress progress bars.
175
+ :::
176
+
173
177
We can then `` inspect `` to see that there is no `` call_HQ `` array in the output:
174
178
175
179
``` {code-cell}
@@ -210,7 +214,7 @@ Let's go through the example above using the distributed commands. First, we
210
214
rm -fR sample-dist.icf
211
215
```
212
216
``` {code-cell}
213
- vcf2zarr dexplode-init sample.vcf.gz sample-dist.icf 5
217
+ vcf2zarr dexplode-init sample.vcf.gz sample-dist.icf -Q 5
214
218
```
215
219
216
220
Here we asked `` dexplode-init `` to set up an ICF store in which the data
@@ -227,9 +231,9 @@ granularity). You should be careful to use this value in your scripts
227
231
Once `` dexplode-init `` is done and we know how many partitions we have,
228
232
we need to call `` dexplode-partition `` this number of times.
229
233
230
- <!-- ```{code-cell} -->
231
- <!-- vcf2zarr dexplode-partition sample-dist.icf 0 -->
232
- <!-- vcf2zarr dexplode-partition sample-dist.icf 1 -->
233
- <!-- vcf2zarr dexplode-partition sample-dist.icf 2 -->
234
- <!-- ``` -->
234
+ ``` {code-cell}
235
+ vcf2zarr dexplode-partition sample-dist.icf 0
236
+ vcf2zarr dexplode-partition sample-dist.icf 1
237
+ vcf2zarr dexplode-partition sample-dist.icf 2
238
+ ```
235
239
You can’t perform that action at this time.
0 commit comments