Performing single profiling using the following command
zipstrain utilities profile-single
--bed-file genomes_bed_file.bed
--bam-file sample.bam
--stb-file mapping.stb
--null-model null_model.parquet
--num-chunks 24
--max-concurrency 4
--output-dir sample_profile
results in the profile parquet file named as such: sample_profile.parquet, whereas performing batch profiling using the following command
zipstrain profile
--input-table bams.csv
--stb-file reference_genomes.stb
--null-model null_model.parquet
--gene-range-table profiling_assets/gene_range_table.tsv
--bed-file profiling_assets/genomes_bed_file.bed
--genome-length-file profiling_assets/genome_lengths.parquet
--run-dir out_profile
results in the profile parquet file named as such: sample.bam.parquet.
Performing single profiling using the following command
zipstrain utilities profile-single
--bed-file genomes_bed_file.bed
--bam-file sample.bam
--stb-file mapping.stb
--null-model null_model.parquet
--num-chunks 24
--max-concurrency 4
--output-dir sample_profile
results in the profile parquet file named as such: sample_profile.parquet, whereas performing batch profiling using the following command
zipstrain profile
--input-table bams.csv
--stb-file reference_genomes.stb
--null-model null_model.parquet
--gene-range-table profiling_assets/gene_range_table.tsv
--bed-file profiling_assets/genomes_bed_file.bed
--genome-length-file profiling_assets/genome_lengths.parquet
--run-dir out_profile
results in the profile parquet file named as such: sample.bam.parquet.