Home Mold

nextflow-summary-to-galaxy-data-flow

Translate a Nextflow summary into a Galaxy data-flow design brief.

Mold health

ok
  • Source layout

    Every file beside index.md is one the mold kind declares.

  • Axis fields

    source-specific fields are coherent.

  • Eval plan

    Abstract oracle: the properties any cast of this Mold must satisfy.

    eval.md declares properties and check type.

    eval.md ↗
  • Scenarios

    Concrete cases bound to fixtures, run against the eval properties.

    scenarios.md declares cases bound to fixtures.

    scenarios.md ↗
  • Typed refs

    14 typed references; 0 resolver issues.

  • On-demand triggers

    All on-demand references describe triggers.

  • Evidence checks

    Hypothesis references include verification.

axis
source-specific
source
nextflow
name
nextflow-summary-to-galaxy-data-flow
contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Research open-requirements-ledger

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Inherit open entries rather than re-deriving them, close the ones this brief's wiring and collection decisions settle, and append data-flow obligations the channel topology leaves open — an operator with no Galaxy collection recipe, a value channel with no Galaxy carrier, a join whose key Galaxy can't reconstruct.
Verify
Promote after a worked run shows entries this Mold appends or resolves are consumed downstream without re-derivation.
Pattern galaxy-conditionals-patterns

Workflow-construction idiom. Copied verbatim.

Purpose
Ground conditional-branch and optional-step choices in curated, corpus-observed Galaxy when/pick_value patterns.
Trigger
When data-flow translation needs optional steps, gating on non-empty results, routing between alternative outputs, or transform-or-pass-through branches.
Pattern galaxy-interval-patterns

Workflow-construction idiom. Copied verbatim.

Purpose
Ground genomic-interval operation choices in curated, corpus-observed Galaxy interval recipes.
Trigger
When the workflow operates on genomic intervals (BED/GFF/VCF coordinate features) and data-flow translation needs overlap, merge, coverage, windowing, masking, or set-algebra steps.
Research galaxy-sample-sheet-collections

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Preserve per-row metadata on the data-flow side: keep sample_sheet column_definitions wired through identifier-keyed steps instead of dropping into parallel parameter inputs, and re-attach metadata after map-over steps that lose it.
Trigger
When the upstream interface brief carries a sample_sheet[:paired|:paired_or_unpaired|:record] input, or when the Nextflow summary shows tuple(meta, path...) channel shape originating from samplesheetToList or splitCsv(header: true).
Research nextflow-reference-data-classification

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Cross-check source-side reference-data classifications before deciding how reference assets and optional rebuild branches flow through the Galaxy data-flow draft.
Trigger
When the reference-data or interface brief is silent, low-confidence, or conflicts with source evidence for iGenomes-derived params, coordinated bundles, compute-if-missing branches, multi-DB pick-lists, or cohort-specific assets.
Research nextflow-to-galaxy-reference-data-mapping

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Decide how reference assets and their indexes flow through the Galaxy data-flow draft (preserving dbkey through map-overs, deferring index-building to wrappers vs surfacing as workflow steps).
Trigger
When the upstream interface brief carries reference-data inputs (FASTA, fai, dict, indexes, known sites, intervals, PoN) or when the source pipeline's compute-if-missing branches imply rebuild semantics the data flow has to honor.
Research nextflow-conditional-to-galaxy-subworkflow-when

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Decide between subworkflow `when:` and inline tool-step `when:` for each source conditional, and pick the right output fan-in primitive (`pick_value` vs twin-cascade) so the data-flow brief carries a coherent conditional disposition forward.
Trigger
When the Nextflow summary's `workflow.conditionals[]` is non-empty, or when subworkflow boundaries in the source align with parameter-driven branches (step, aligner, wes, tools, skip_*, use_*).

Cast artifacts

How to install →

Artifact handoffs

/ pipeline contract

Produces

Consumes

nextflow-summary-to-galaxy-data-flow

Read a Nextflow summary plus the preceding Galaxy interface brief and emit a reviewable Markdown data-flow brief. Capture abstract operations, collection map/reduce choices, shape-changing placeholder transformations, Galaxy tool needs, confidence, and open questions.

The output is not gxformat2 and should not resolve exact Tool Shed tools. Nor does it rule them out. Recording that a step’s tool does not exist, will not be found, or must be authored is the same adjudication made negative, and it belongs to advance-galaxy-draft-step, which owns routing. Say what each step needs a tool to do; let discovery report what exists. Justify step granularity from the source’s own structure — subworkflow boundaries, the ratio of plumbing to scientific work. A guess about tool availability is not a justification.

Incoming References (27)