Skip to content

Commit ecdd707

Browse files
committed
Updated docs to refer to gene-oracle repo
1 parent 8562963 commit ecdd707

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
This repository provides tools and instructions for running nextflow pipelines on a Kubernetes cluster. These scripts have been tested for the following pipelines:
44

55
- [SystemsGenetics/GEMmaker](https://github.com/SystemsGenetics/GEMmaker)
6-
- [SystemsGenetics/gene-oracle-nf](https://github.com/SystemsGenetics/gene-oracle-nf)
6+
- [SystemsGenetics/gene-oracle](https://github.com/SystemsGenetics/gene-oracle)
77
- [SystemsGenetics/KINC-nf](https://github.com/SystemsGenetics/KINC-nf)
88

99
(In Progress)

examples/gene-oracle.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ In this example you will use the [gene-oracle](https://github.com/SystemsGenetic
66

77
We will use the `make-input-data.py` script in the gene-oracle repo to generate a "fake GEM" and a list of gene sets for that GEM. Clone the gene-oracle repo to your local machine, and then run the script:
88
```bash
9-
python <gene-oracle-path>/scripts/make-input-data.py --n-samples 1000 --n-genes 20 --n-sets 50
9+
python <gene-oracle-path>/bin/make-input-data.py --n-samples 1000 --n-genes 20 --n-sets 50
1010
```
1111

1212
It is recommended that you create a separate directory for each pipeline that you use, so that the data and nextflow metadata for each pipeline are separate:
@@ -42,7 +42,7 @@ Before running the pipeline, you must transfer your input data from your local m
4242

4343
Then you can run the pipeline using nextflow's `kuberun` command:
4444
```bash
45-
nextflow kuberun systemsgenetics/gene-oracle-nf -v <pvc-name>
45+
nextflow kuberun systemsgenetics/gene-oracle -v <pvc-name>
4646
```
4747

4848
## Transfer Output Data

0 commit comments

Comments
 (0)