Skip to content

Commit b752fe4

Browse files
committed
Fix notebook links to reference pages
1 parent 7ebd9ef commit b752fe4

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

‎docs/notebooks/processed-data-downloading.ipynb‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@
4444
"2. produce a PEP-compatible sample table, `PROJECT_NAME_sample_processed.csv` and `PROJECT_NAME_series_processed.csv`, in your metadata folder.\n",
4545
"3. produce a PEP-compatible project configuration file, `PROJECT_NAME_sample_processed.yaml` and `PROJECT_NAME_series_processed.yaml`, in your metadata folder.\n",
4646
"\n",
47-
"Complete details about geofetch outputs is cataloged in the [metadata outputs reference](metadata_output.md)."
47+
"Complete details about geofetch outputs is cataloged in the [metadata outputs reference](../metadata-output.md)."
4848
]
4949
},
5050
{

‎docs/notebooks/raw-data-downloading.ipynb‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@
173173
"2. produce a PEP-compatible sample table, `PROJECT_NAME_annotation.csv`, in your metadata folder.\n",
174174
"3. produce a PEP-compatible project configuration file, `PROJECT_NAME_config.yaml`, in your metadata folder.\n",
175175
"\n",
176-
"Complete details about geofetch outputs is cataloged in the [metadata outputs reference](../metadata_output.md)."
176+
"Complete details about geofetch outputs is cataloged in the [metadata outputs reference](../metadata-output.md)."
177177
]
178178
},
179179
{
@@ -485,14 +485,14 @@
485485
"\n",
486486
"## Selecting samples to download.\n",
487487
"\n",
488-
"By default, `geofetch` downloads all the data for one accession of interest. If you need more fine-grained control, either because you have multiple accessions or you need a subset of samples within them, you can use the [file-based sample specification](file-specification.md).\n",
488+
"By default, `geofetch` downloads all the data for one accession of interest. If you need more fine-grained control, either because you have multiple accessions or you need a subset of samples within them, you can use the [file-based sample specification](../file-specification.md).\n",
489489
"\n",
490490
"\n",
491491
"## Tips\n",
492492
"\n",
493493
"* Set an environment variable for `$SRABAM` (where `.bam` files will live), and `geofetch` will check to see if you have an already-converted bamfile there before issuing the command to download the `sra` file. In this way, you can delete old `sra` files after conversion and not have to worry about re-downloading them. \n",
494494
"\n",
495-
"* The config template uses an environment variable `$SRARAW` for where `.sra` files will live. If you set this variable to the same place you instructed `sratoolkit` to download `sra` files, you won't have to tweak the config file. For more information refer to the [`sratools` page](howto-location.md).\n",
495+
"* The config template uses an environment variable `$SRARAW` for where `.sra` files will live. If you set this variable to the same place you instructed `sratoolkit` to download `sra` files, you won't have to tweak the config file. For more information refer to the [`sratools` page](../howto-location.md).\n",
496496
"\n",
497497
"You can find a complete example of [using `geofetch` for RNA-seq data](https://github.com/databio/example-projects/tree/master/rna-seq). \n"
498498
]

0 commit comments

Comments
 (0)