Skip to content

Commit dfc546c

Browse files
author
Mitchell R. Vollger
committed
.
1 parent 5b141bd commit dfc546c

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/fire/run.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,11 @@ Then Snakemake installs all the additional requirements as conda envs in that di
3838

3939
If you wish to distribute jobs across a cluster you may need to install the appropriate [snakemake executor plugin](https://snakemake.github.io/snakemake-plugin-catalog/). The SLURM executor is included in the environment (`snakemake-executor-slurm`)
4040

41-
## Configuring
41+
## Configuring and inputs
4242

43-
See the [configuration README](https://github.com/fiberseq/FIRE/tree/main/config), the example [configuration file](https://github.com/fiberseq/FIRE/blob/main/config/config.yaml), and the example [manifest file](https://github.com/fiberseq/FIRE/blob/main/config/config.tbl) for configuration options.
43+
There are two main inputs for the FIRE workflow, a configuration file (e.g. `config.yaml`) and a manifest file (e.g. `manifest.tbl`). The configuration file contains parameters for running the workflow, a reference genome, as well as a path to the manifest file. The manifest file has two columns, the sample name (used to prefix the output files) and the path to the indexed Fiber-seq BAM (or CRAM) file for each sample.
44+
45+
For more details see the [configuration README](https://github.com/fiberseq/FIRE/tree/main/config), the example [configuration file](https://github.com/fiberseq/FIRE/blob/main/config/config.yaml), and the example [manifest file](https://github.com/fiberseq/FIRE/blob/main/config/config.tbl) for configuration options.
4446

4547
---
4648

0 commit comments

Comments
 (0)