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
Copy file name to clipboardExpand all lines: README.md
+30-2Lines changed: 30 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,37 @@ See [model docs](docs/models.md) for information about available models.
21
21
22
22
Pipelines are run using nextflow. For a list of all available parameters, see [nextflow parameters](nextflow.config). Not all parameters will affect all pipeline workflows.
23
23
24
-
If you are running the pipeline on the HPC, you should submit the workflow as a job. You can use the example test as a starting template: [test-nextflow.sh](test-nextflow.sh).
24
+
You will need a batch file that lists the input files to process.
25
25
26
-
Input files should include the full path. An easy way to generate the list of inputs for `input_batch` is to run `find $(pwd) -name '*.avi' > video_batch.txt`.
26
+
An easy way to generate the list of inputs for `input_batch` is to run
27
+
`find $(pwd) -name '*.avi' > video_batch.txt`.
28
+
29
+
## Running on Sumner2 HPC (Slurm)
30
+
31
+
When running on the HPC (Sumner2),you should submit the workflow as a job. To make this
32
+
simple, we've provided a submission script that you can use to configure and submit
33
+
pipeline run.
34
+
35
+
The script is provided in the kumar-lab scripts module. To load the module, run:
36
+
```
37
+
module use --append /projects/kumar-lab/meta/modules
0 commit comments