millironx/nf-configs
1
0
Fork 0
mirror of https://github.com/MillironX/nf-configs.git synced 2024-11-25 17:29:55 +00:00
Code Issues Releases Packages Activity

Merge pull request #151 from jfy133/master

Browse source 
Add additional custom nf-core/eager params for SHH profile
This commit is contained in:
James A. Fellows Yates 2020-05-07 09:25:02 +02:00 committed by GitHub
commit 38e9e54932
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
conf/pipeline/eager/shh.config
View file

@ -17,3 +17,8 @@ process {
queue = { task.memory > 756.GB ? 'supercruncher' : 'long' } queue = { task.memory > 756.GB ? 'supercruncher' : 'long' }
} }
} }
params {
bwaalnn = 0.01
bwaalnl = 32
}

1
docs/pipeline/eager/shh.md
View file

@ -15,3 +15,4 @@ Example: `nextflow run nf-core/eager -profile shh`
Specific configurations for shh has been made for eager. Specific configurations for shh has been made for eager.
* If running with the MALT module turned on, the MALT process by default will be sent to the long queue with a resource requirement minimum of 725GB and 64 cores. If this fails, the process will be tried once more only and sent to the supercruncher queue. The module will not retry after this, and pipeline will fail. * If running with the MALT module turned on, the MALT process by default will be sent to the long queue with a resource requirement minimum of 725GB and 64 cores. If this fails, the process will be tried once more only and sent to the supercruncher queue. The module will not retry after this, and pipeline will fail.
* Modifies the bwa aln `-n` parameter to 0.01, rather than typical default of 0.04, and `-l` to 32 (rather than 1024) to syncronise the (unpublished) parameter with EAGER1 and typical/expected usage within the department.