Skip to content

docs: document orthogonal process resource labels (process_cpus_*/_mem_*/_time_*)#4212

Open
pinin4fjords wants to merge 4 commits into
mainfrom
docs/process-axis-labels
Open

docs: document orthogonal process resource labels (process_cpus_*/_mem_*/_time_*)#4212
pinin4fjords wants to merge 4 commits into
mainfrom
docs/process-axis-labels

Conversation

@pinin4fjords
Copy link
Copy Markdown
Member

@pinin4fjords pinin4fjords commented May 13, 2026

Summary

  • Make the axis-decomposed resource labels (process_cpus_*, process_mem_*, process_time_*) the preferred pattern in the modules spec and mark the bundled labels (process_low, process_medium, process_high) as legacy.
  • Update the user-facing config example on nextflow-for-your-system.md to show the axis labels alongside an explainer of the legacy scheme.
  • Refresh the resource-requirements snippet in contribute-existing-pipelines.md.
  • Add a new migration guide page (developing/migration-guides/process-axis-labels.md) with the legacy-to-axis mapping table, migration steps and a deprecation timeline.

Companion to the template change in nf-core/tools#4265 and the approved RFC at nf-core/proposals#139.

Test plan

  • npm run build (or equivalent local docs build) renders the four touched pages without errors.
  • Internal links between resource-requirements.md, nextflow-for-your-system.md and process-axis-labels.md resolve.
  • Spot-check formatting of the mapping and timeline tables in preview.

@netlify /docs/developing/migration-guides/process-axis-labels

Introduce the axis-decomposed labels (process_cpus_*, process_mem_*,
process_time_*) as the preferred scheme and mark the bundled labels
(process_low, process_medium, process_high) as legacy. Add a migration
guide for module authors, pipeline maintainers and site-config
maintainers.

Refs: nf-core/proposals#139
Refs: nf-core/tools#4265

[skip ci]
@netlify
Copy link
Copy Markdown

netlify Bot commented May 13, 2026

Deploy Preview for nf-core-main-site ready!

Name Link
🔨 Latest commit 1561469
🔍 Latest deploy log https://app.netlify.com/projects/nf-core-main-site/deploys/6a0595dd048a73000967c3ee
😎 Deploy Preview https://deploy-preview-4212--nf-core-main-site.netlify.app/docs/developing/migration-guides/process-axis-labels
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

pinin4fjords added a commit to pinin4fjords/proposals that referenced this pull request May 13, 2026
The /docs/contributing/migrating-resource-labels URL 404s until
nf-core/website#4212 is merged, so point reviewers at the draft PR
instead.

[skip ci]
Comment thread sites/docs/src/content/docs/contributing/migrating-resource-labels.md Outdated
Comment thread sites/docs/src/content/docs/contributing/migrating-resource-labels.md Outdated
pinin4fjords and others added 2 commits May 14, 2026 10:22
- Move migrating-resource-labels.md to developing/migration-guides/process-axis-labels.md.
- Tighten prose: drop redundant phrasing, merge module-author and pipeline-maintainer steps into a single section, sharpen the "Why migrate" bullets.
- Convert the two before/after migration examples to diff groovy blocks matching the strict-syntax migration guide's convention.
- Reformat the axis label table in resource-requirements.md so each tier is its own cell, with empty cells aligning the "single" tier on the CPU axis with the absent tier on memory/time.
- Update the two internal links (nextflow-for-your-system.md, resource-requirements.md) to the new migration-guide path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot deleted a comment from netlify Bot May 14, 2026
prettier wants table cells padded to the longest content + 2 spaces; the previous version had a few stray trailing spaces.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants