Skip to content

Update and restructure docs for v1.0 release#83

Open
ochkalova wants to merge 18 commits into
1.0.0from
doc/limitations-scalability
Open

Update and restructure docs for v1.0 release#83
ochkalova wants to merge 18 commits into
1.0.0from
doc/limitations-scalability

Conversation

@ochkalova

@ochkalova ochkalova commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Documentation improvements:

  • Added a new "Scalability" section to README.md describing resource-intensive steps, recommendations for HPC usage, and ENA submission rate limits.
  • Added a new "Limitations" section to README.md outlining unsupported data types and scenarios for each pipeline mode, including details on co-assemblies, eukaryotic/viral bins, single-contig assemblies, and input format restrictions.
  • Made samplesheets section in README more slim to avoid major duplications with usage.md.
  • Updated methods.md document.
  • Added references to methods.md to usage.md.

Resolves #81

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/seqsubmit branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core pipelines lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@ochkalova ochkalova requested a review from KateSakharova July 8, 2026 14:02
@ochkalova ochkalova self-assigned this Jul 8, 2026
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

nf-core pipelines lint overall result: Passed ✅ ⚠️

Posted for pipeline commit bea141a

+| ✅ 252 tests passed       |+
#| ❔   8 tests were ignored |#
#| ❔   1 tests had warnings |#
!| ❗   4 tests had warnings |!
Details

❗ Test warnings:

  • nextflow_config - Config manifest.version should end in dev: 1.0.0
  • readme - README contains the placeholder zenodo.XXXXXXX. This should be replaced with the zenodo doi (after the first release).
  • pipeline_todos - TODO string in README.md: Add citation for pipeline after first release. Uncomment lines below and update Zenodo doi and badge at the top of this file.
  • pipeline_todos - TODO string in nextflow.config: Specify any additional parameters here

❔ Tests ignored:

  • files_exist - File is ignored: conf/igenomes.config
  • files_exist - File is ignored: conf/igenomes_ignored.config
  • nextflow_config - Config variable ignored: params.input
  • files_unchanged - File ignored due to lint config: .github/PULL_REQUEST_TEMPLATE.md
  • files_unchanged - File ignored due to lint config: assets/nf-core-seqsubmit_logo_light.png
  • files_unchanged - File ignored due to lint config: docs/images/nf-core-seqsubmit_logo_light.png
  • files_unchanged - File ignored due to lint config: docs/images/nf-core-seqsubmit_logo_dark.png
  • container_configs - container_configs

❔ Tests fixed:

✅ Tests passed:

Run details

  • nf-core/tools version 4.0.2
  • Run at 2026-07-10 15:28:07

@KateSakharova KateSakharova changed the base branch from dev to 1.0.0 July 9, 2026 15:42

@KateSakharova KateSakharova left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, Sonya!!! I have changed a base to 1.0.0 because I already have some changes there. We will merge it to dev after all fixes.

  1. We do not have READSUBMIT in methods.md. Do we have something to write about?
  2. We probably need to structure parts in alphabetic order: Assembly, Genome, Read
    or in submission order: Read, Assembly, Genome. I would say first one probably is quite universal ... and all docs should follow that order.

Comment thread README.md Outdated

#### `mags` and `bins` modes (`GENOMESUBMIT`)

- **Co-assemblies**: MAGs/bins generated from co-assemblies are not supported. The pipeline currently expects each MAG/bin to be derived from an assembly generated from a single run.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would point to your PR and say it is in development

Comment thread README.md Outdated

- **Co-assemblies**: MAGs/bins generated from co-assemblies are not supported. The pipeline currently expects each MAG/bin to be derived from an assembly generated from a single run.

- **Eukaryotic and viral bins/MAGs**: Submitting eukaryotic or viral genomes that require additional metadata generation is not supported. For such genomes tRNA and rRNA prediction, quality assessment (completeness/contamination estimation) and taxonomy assignment are not implemented. If all the required metadata (`completeness`, `contamination`, `stats_generation_software`, `RNA_presence` and `NCBI_lineage`) is already provided in the samplesheet, eukaryotic and viral bins/MAGs can still be submitted normally.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should link issues here? We kind of target to fix those

Comment thread README.md

- **Reads in non-FASTQ formats**: Only reads provided as FASTQ (`.fastq.gz`) can be submitted. Other formats (e.g. BAM) are not supported as input.

## Credits

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have a quite big readme and need a table of contents in the beggining of file (it was also one of James's suggestions)

@ochkalova ochkalova changed the title Add limitations and scalability sections to README Update and restructure docs Jul 10, 2026
@ochkalova ochkalova changed the title Update and restructure docs Update and restructure docs for v1.0 release Jul 10, 2026
@ochkalova ochkalova mentioned this pull request Jul 10, 2026
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.

Limitations section in README

2 participants