mirror of
https://github.com/MillironX/nf-configs.git
synced 2024-11-21 16:16:04 +00:00
Updated iGenomes location
This commit is contained in:
parent
079258ebbb
commit
f793ffaace
2 changed files with 2 additions and 3 deletions
|
@ -7,7 +7,7 @@ params
|
|||
max_memory = 190.GB
|
||||
max_cpus = 40
|
||||
max_time = 240.h
|
||||
igenomes_base = "/projects/genomicsshare/igenomes"
|
||||
igenomes_base = "/projects/genomicsshare/AWS_iGenomes"
|
||||
}
|
||||
|
||||
singularity
|
||||
|
|
|
@ -32,5 +32,4 @@ module load graphviz/2.40.1
|
|||
|
||||
## Use of iGenomes
|
||||
|
||||
A local copy of the iGenomes resource with all commonly used genomes has been made available for all of Quest so you should be able to run the pipeline against any reference available in the `igenomes.config` specific to the nf-core pipeline.
|
||||
You can do this by simply using the `--genome <GENOME_ID>` parameter. While you can technically "stream" genomes from iGenomes directly using the pipeline, this is a substantial use of bandwidth and resources on both ends, and potentially poses reproducibility issues later on. Please use the local copies unless absolutely necessary, and save your custom genomes to your personal allocation where necessary.
|
||||
A local copy of the iGenomes resource with all commonly used genomes has been made available for all of Quest so you should be able to run the pipeline against any reference available in the `igenomes.config` specific to the nf-core pipeline. These files can be found at `/projects/genomicsshare/AWS_iGenomes`. You can do this by simply using the `--genome <GENOME_ID>` parameter. While you can technically "stream" genomes from iGenomes directly using the pipeline, this is a substantial use of bandwidth and resources on both ends, and potentially poses reproducibility issues later on. Please use the local copies unless absolutely necessary, and save your custom genomes to your personal allocation where necessary.
|
||||
|
|
Loading…
Reference in a new issue