This Nextflow Workflow was created to run data-to-model challenges.
In order to use this workflow, you must already have completed the following steps:
- Created a Synapse project shared with challenge participants.
- Created an evaluation queue within the Synapse project.
- One or more Docker containers must have already been submitted to your evaluation queue.
- Created a submission view that at least includes the
id
,status
columns. - Added the input data for evaluating submissions to a folder within your Synapse project.
The workflow takes several inputs. They are:
view_id
(required): The Synapse ID for your submission view.input_id
(required): The Synapse ID for the folder holding the testing data for submissions.cpus
(optional): Number of CPUs to dedicate to theRUN_DOCKER
process i.e. the challenge executions. Defaults to4
memory
(optional): Amount of memory to dedicate to theRUN_DOCKER
process i.e. the challenge executions. Defaults to16.GB
The Default parameter values for view_id
and input_id
currently point to a Synapse project that only DPE members have access to. Unless you have access to the DPE-Testing
Synapse project, you will not be able to test this workflow using the default values. Additionally, this workflow expects a secret called SYNAPSE_AUTH_TOKEN
(a Synapse Authentication Token). This secret should be configured in your local copy of Nextflow for local runs, or as a workspace secret in your Nextflow Tower workspace.
Run the workflow locally:
nextflow run main.nf --view_id "<your_view_id>" --input_id "<your_input_id>"
The workflow comes with two preconfigured profiles
for memory and CPU allocation. The local
profile is equivilent to the default (cpus
= 4
; memory
= 16.GB
) this is intended to be used for runs on local machines with the adequate resources. The tower
profile dedicates double the resources (cpus
= 8
; memory
= 32.GB
) and can be used when running the workflow on Nextflow Tower for improved performance.