question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Nextflow: Grab workflow descriptions

See original GitHub issue

Feature Request

It would be great if Dockstore could auto-populate a few extra fields from Nextflow workflows which are sometimes available in the config metadata.

Desired behaviour

Description: manifest.description (example)

Author (in table view): manifest.author (example)

Note that Workflow Path: /nextflow.config is a little confusing, as the workflow is in the main.nf file (default filename - can be defined with workflow.mainScript), and it’s this that you execute, rather than the config file. I know I can change it manually, but if it’s pulled by default somewhere.

Apologies if these already happen, it could be that I’m simply being too impatient after clicking refresh on my GitHub repos 😀

Phil

┆Issue is synchronized with this Jira Bug ┆Issue Type: Bug ┆Fix Versions: Dockstore 1.6 ┆Sprint: Seabright Sprint 6 Ferry ┆Issue Number: DOCK-209

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
denis-yuencommented, Feb 8, 2019

We ended up calling out to Nextflow separately too (it wasn’t clear due to our lack of groovy expertise how to separate just what we needed and we didn’t want to include all of Nextflow in our classpath) May need to optimize later, but this should get us compatibility with descriptions, etc. from nf-core

Limitation: We can’t use Nextflow to aid us in detecting what files are useful from a repo (i.e. in CWL, we start with the “entry”/primary descriptor and spider out to figure out what files in the repo are relevant)

1reaction
denis-yuencommented, Jan 8, 2019

Oh cool, that at least gives us a good starting point. Thanks for the tip!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Creating a NextFlow workflow - Bioinformatics Workbook
Every nextflow workflow requires two main files. ... parameter, description ... This channel will grab the folder path and set it into a...
Read more >
Basic concepts — Nextflow 22.10.2 documentation
Basic concepts . Nextflow is a reactive workflow framework and a programming DSL that eases the writing of data-intensive computational pipelines.
Read more >
Examples — Nextflow 22.10.2 documentation
This example shows a pipeline that is made of two processes. The first process receives a FASTA formatted file and splits it into...
Read more >
Channels — Nextflow 22.10.2 documentation
Nextflow is based on the Dataflow programming model in which processes communicate through channels. A channel has two major properties: Sending a message...
Read more >
Processes — Nextflow 22.10.2 documentation
Labels are useful to organise workflow processes in separate groups which can be referenced in the configuration file to select and configure subset...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found