- Overview
- nf-core Launch via API/SDK
- nf-core Launch via Web Walkthrough
- 1. Navigate to the nf-core launcher card.
- 2. Launcher Tabs
- 3. Go to the Review & Submit
Overview
nf-core provides a collection of open source pipelines and workflows. This workflow can be launched via API/SDK or via Web Walkthrough.
nf-core Launch via API/SDK
You can launch nf-core workflows programmatically using the Form Bio CLI/SDK tool to call the Form Bio API.
- Upload any relevant input data/files
- For transferring large files or transferring from Cloud Providers like AWS S3, Azure, Box use the Form Data Transfer Service
# Upload files to Form Bio project
$ formbio storage cp -r ./local-files/sequences formbio://${org}/${project}- Create input parameters for a given nf-core workflow as a JSON params list
- You can use nf-core Launch pipeline to create JSON parameters.
- Note: any input files should be of the URI scheme:
formbio://${project}/${org}/${filepath} - You then can launch a workflow via the API using the Form Bio CLI/SDK:
- See docs on how to use the Form Bio CLI/SDK to run workflows via the API
For example, to launch nf-core/bamtofastq workflow:
Another example to launch nf-core/taxprofiler using formbio input files:
🔔 WATCH OUT for special characters!
Specific characters in parameter values can cause errors. In the nf-core ampliseq workflow, using the "=" symbol within the data_ref_taxonomy parameter's value e.g., coidb=221216 could crash the workflow.
- 👍 Replacing the
=character with itsUnicodeequivalence - 🙀 Put the below in a shell script and run it
nf-core Launch via Web Walkthrough
1. Navigate to the nf-core launcher card.
- Find nf-core workflow via:
- Inside Workflows, start scrolling down the category, click nf-core to display it
- Search bar in the top right corner once click Launch
2. Launcher Tabs
3 to-do before running an nf-core workflow
- Workflow name
- Search for the desired nf-core workflow. nf-core workflow repository supports a variety of workflows available on nf-co.re.
b. Workflow version
- Search for workflow version of selected workflow repository
c. Parameters JSON
- Step 1: To determine required parameters, go to the documentation of selected workflow and version in the link as shown below.
- Step 2: Check desired/required Parameters
Navigate to the Parameters tab to see list of parameters required for the JSON input.
- Compulsory are parameters with required on the right side. These are needed for the workflow to run.
- Others are optional depending on your specific needs.
- outdir does not need be defined since Form Bio platform handles it automatically .
- Step 3: For each desired/required parameter, assign value to it a put the parameters in JSON format
{
"input": "formbio://form-bio-customer-support/onboarding-project/rnaseq_nfcore/rnaseq_nf_core/samplesheet_test.csv",
"fasta": "formbio://form-bio-customer-support/onboarding-project/rnaseq_nfcore/rnaseq_nf_core/genome.fasta",
"gtf": "formbio://form-bio-customer-support/onboarding-project/rnaseq_nfcore/rnaseq_nf_core/genes_with_empty_tid.gtf.gz"
}- Add the created JSON to Parameters JSON on the platform
🚧 Note:
- Any file or directory paths should point to its
formbio://path - Within a file, any path should be formatted as described below:
- The platform can handle different types of data paths, including those from public datasets (S3 buckets) and web addresses (HTTP).
- If your data is already uploaded onto the platform, paths must be in Google Cloud Storage format.
📖 To generate the GCS format path
🤏 Go to Data → Find desired input files → Click three-dots → Select Copy Download URL
👍 This generates a download URL:
- 👉 Replace
https://storage.googleapis.com/withgs:// - 👉 Remove whatever comes after the first ?
🙀 The final result should be:
gs://formbio-production-26a68935-d9a6-4b3e-9b89-43dacfbf5e32/DNAseq/cancergenomics/SRR15663418_T1_1.fastq.gz💯 Parameters JSON can be created using nf-core website
- You can use nf-co.re Launch to map which fields to populate in the JSON input field for this workflow.
- For rnaseq https://nf-co.re/rnaseq/3.14.0 → Click on Launch version <latest> (here it’s 3.14.0) to see which JSON fields to populate into JSON format
red asterisk marks those required which must be filled. Note: outdir must be omitted in the final result.outdir and add the generated JSON to Parameters JSON3. Go to the Review & Submit
- ✍️ Add a run name
- ✅ Check all input again
- 😃 Click Run Workflow to execute