-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
35 changed files
with
1,460 additions
and
118 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,3 +7,5 @@ testing/ | |
testing* | ||
*.pyc | ||
.nf-test/ | ||
tests/test_data/ | ||
.nf-test.log |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,12 @@ | ||
Nov-20 17:46:16.940 [main] INFO com.askimed.nf.test.App - nf-test 0.8.1 | ||
Nov-20 17:46:16.960 [main] INFO com.askimed.nf.test.App - Arguments: [init] | ||
Jan-16 10:10:49.572 [main] INFO com.askimed.nf.test.App - nf-test 0.8.2 | ||
Jan-16 10:10:49.580 [main] INFO com.askimed.nf.test.App - Arguments: [test, tests/modules/local/gridss/gridss/main.nf.test] | ||
Jan-16 10:10:49.580 [main] INFO com.askimed.nf.test.commands.RunTestsCommand - Load config from file /Users/diders01/projects/jabba_prod/nf-jabba/nf-test.config... | ||
Jan-16 10:10:49.758 [main] INFO com.askimed.nf.test.commands.RunTestsCommand - Detected 1 test files. | ||
Jan-16 10:10:49.827 [main] INFO com.askimed.nf.test.config.FileStaging - Create symlink '/Users/diders01/projects/jabba_prod/nf-jabba/.nf-test/tests/1a4fc5dc640a75b58bcf88f15a9b2cb6/meta/bin' --> '/Users/diders01/projects/jabba_prod/nf-jabba/bin' | ||
Jan-16 10:10:49.828 [main] INFO com.askimed.nf.test.config.FileStaging - Create symlink '/Users/diders01/projects/jabba_prod/nf-jabba/.nf-test/tests/1a4fc5dc640a75b58bcf88f15a9b2cb6/meta/lib' --> '/Users/diders01/projects/jabba_prod/nf-jabba/lib' | ||
Jan-16 10:10:49.828 [main] INFO com.askimed.nf.test.config.FileStaging - Create symlink '/Users/diders01/projects/jabba_prod/nf-jabba/.nf-test/tests/1a4fc5dc640a75b58bcf88f15a9b2cb6/meta/assets' --> '/Users/diders01/projects/jabba_prod/nf-jabba/assets' | ||
Jan-16 10:10:49.828 [main] DEBUG com.askimed.nf.test.core.AbstractTest - Stage 1 user provided files... | ||
Jan-16 10:10:49.828 [main] INFO com.askimed.nf.test.config.FileStaging - Create symlink '/Users/diders01/projects/jabba_prod/nf-jabba/.nf-test/tests/1a4fc5dc640a75b58bcf88f15a9b2cb6/meta/tests/test_data/' --> '/Users/diders01/projects/jabba_prod/nf-jabba/tests/test_data' | ||
Jan-16 10:10:49.830 [main] INFO com.askimed.nf.test.core.TestExecutionEngine - Started test plan | ||
Jan-16 10:10:49.830 [main] INFO com.askimed.nf.test.core.TestExecutionEngine - Running testsuite 'Test Process GRIDSS_GRIDSS' from file '/Users/diders01/projects/jabba_prod/nf-jabba/tests/modules/local/gridss/gridss/main.nf.test'. | ||
Jan-16 10:10:49.830 [main] INFO com.askimed.nf.test.core.TestExecutionEngine - Run test '1a4fc5dc: Should run GRIDSS without failures'. type: com.askimed.nf.test.lang.process.ProcessTest |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Refactor | ||
## Questions: | ||
- Do we expect to have more than one tool per step (e.g gridss and svaba): No | ||
- Is there redundancy/dependency in the package parameters. Can parameters be | ||
organized into a dependency tree or otherwise hardcoded because they never | ||
change?: Yes, need to investigate. | ||
- Do we care about alignment? Should the pipeline be able to start at | ||
alignment? No. | ||
|
||
## To Do | ||
- Refactor output channel attribute extraction (21) | ||
- Swich from steps conditionals to cases (8) | ||
- Switch from tools to nodes (13) | ||
- Remove alignment step (3) | ||
- Refactor repetitive declarations (1) | ||
|
||
## Outline | ||
- Swtich from the "step" based conditionals to something more declarative (e.g | ||
cases). Having the program run a block of code by checking if the starting | ||
step is included in a list of steps is enormously cumbersome, cases should | ||
make things more parsimoinous and readable. | ||
- Tools-in-step paradigm could be replaced with ungrouped nodes. | ||
- Use functions for repetitive declarations/imports and hold their required | ||
variables in arrays/maps. | ||
- Clean up output channel attribute extraction. Currently very repetitive, | ||
could be replaced with functions. | ||
- Cut down on the number of default parameters in the config (possibly at the | ||
package level). Packages/processes/workflows shouldn't have so many | ||
parameters (see: JaBbA as the worst offendor), it indicates either | ||
overparameterization or a dependency tree in the parameter space. | ||
- Add *_create_csv methods for remaining tools to generate samplesheets to | ||
start from those tools | ||
- Move parameter specification from nextflow.config to module specific config, | ||
then import them into nextflow config. This keeps the process and its parameter | ||
configuration tightly coupled--but loses a central interface for modifying | ||
all the defaults in one place, which is useful if changing one default would | ||
affect defaults in a different parameter. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
|
||
params { | ||
config_profile_name = 'mskilab-org NYU BigPurple Cluster Profile' | ||
config_profile_description = """ | ||
mskilab-org NYU School of Medicine BigPurple cluster profile to run nf-JaBbA. | ||
!!Make sure to load both singularity/3.1 and squashfs-tools/4.3 before running nf-JaBbA with this profile!! | ||
Ideal to make work folder on scratch as it generates whole lot of temporary files to run the pipeline | ||
Make sure to submit the run as an SBATCH job since we don't own our own node at NYU yet!! | ||
""".stripIndent() | ||
config_profile_contact = "Tanubrata Dey ([email protected])" | ||
config_profile_url = "https://www.mskilab.org/" | ||
|
||
// Resources | ||
max_memory = 700.GB | ||
max_cpus = 256 | ||
max_time = 10.d | ||
} | ||
process { | ||
|
||
// default SLURM node config | ||
beforeScript = """ | ||
module load singularity/3.9.8 | ||
module load squashfs-tools/4.3 | ||
""" | ||
.stripIndent() | ||
|
||
executor='slurm' | ||
|
||
// memory errors which should be retried. otherwise error out | ||
errorStrategy = { task.exitStatus in ((130..145) + 104) ? 'retry' : 'finish' } | ||
maxRetries = 3 | ||
maxErrors = '-1' | ||
|
||
} | ||
executor { | ||
name = 'slurm' | ||
queueSize = 500 | ||
submitRateLimit = '10 sec' | ||
} | ||
singularity { | ||
enabled = true | ||
autoMounts = true | ||
cacheDir = "/gpfs/data/imielinskilab/singularity_files/nextflow_singularity_cache" | ||
} | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.