Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added Coreograph #49

Merged
merged 17 commits into from
Aug 12, 2024
Merged

added Coreograph #49

merged 17 commits into from
Aug 12, 2024

Conversation

RobJY
Copy link
Contributor

@RobJY RobJY commented Jul 25, 2024

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/mcmicro branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core 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).

@RobJY RobJY requested a review from jmuhlich July 25, 2024 21:24
Copy link

github-actions bot commented Jul 25, 2024

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 2d07fad

+| ✅ 177 tests passed       |+
#| ❔   1 tests were ignored |#
!| ❗  25 tests had warnings |!

❗ Test warnings:

  • nextflow_config - Config manifest.version should end in dev: 2.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: TODO nf-core:
  • pipeline_todos - TODO string in README.md: Include a figure that guides the user through the major workflow steps. Many nf-core
  • pipeline_todos - TODO string in README.md: Fill in short bullet-pointed list of the default steps in the pipeline
  • pipeline_todos - TODO string in README.md: Describe the minimum required steps to execute the pipeline, e.g. how to prepare samplesheets.
  • pipeline_todos - TODO string in README.md: update the following command to include all required parameters for a minimal example
  • pipeline_todos - TODO string in README.md: If applicable, make list of people who have also contributed
  • 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 README.md: Add bibliography of tools and data used in your pipeline
  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your preferred methods description, e.g. add publication citation for this pipeline
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required
  • pipeline_todos - TODO string in ci.yml: You can customise CI pipeline run tests as required
  • pipeline_todos - TODO string in main.nf: Optionally add in-text citation tools to this list.
  • pipeline_todos - TODO string in main.nf: Optionally add bibliographic entries to this list.
  • pipeline_todos - TODO string in main.nf: Only uncomment below if logic in toolCitationText/toolBibliographyText has been filled!
  • pipeline_todos - TODO string in output.md: Write this documentation describing your workflow's output
  • pipeline_todos - TODO string in usage.md: Add documentation about anything specific to running your pipeline. For general topics, please point to (and add to) the main nf-core website.
  • pipeline_todos - TODO string in test_full.config: Specify the paths to your full test data ( on nf-core/test-datasets or directly in repositories, e.g. SRA)
  • pipeline_todos - TODO string in test_full.config: Give any required params for the test so that command line flags are not needed
  • pipeline_todos - TODO string in base.config: Check the defaults for all processes
  • pipeline_todos - TODO string in base.config: Customise requirements for specific processes.
  • pipeline_todos - TODO string in test.config: Specify the paths to your test data on nf-core/test-datasets
  • pipeline_todos - TODO string in test.config: Give any required params for the test so that command line flags are not needed
  • schema_lint - Parameter input not found in schema

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.14.1
  • Run at 2024-08-05 18:48:37

Copy link
Member

@jmuhlich jmuhlich left a comment

Choose a reason for hiding this comment

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

I am still running the tests locally to verify the snapshots are stable, but here are some changes to work through in the meantime.

Also I found that on a 4-core machine the nf-test run failed as coreograph is tagged process_medium which requests 6 cores. Still working out the best way to address that.

assets/markers_1_coreograph.csv Outdated Show resolved Hide resolved
assets/samplesheet_1_row_sample_cycle_coreograph.csv Outdated Show resolved Hide resolved
conf/modules.config Outdated Show resolved Hide resolved
nextflow_schema.json Outdated Show resolved Hide resolved
tests/main.nf.test Show resolved Hide resolved
workflows/mcmicro.nf Show resolved Hide resolved
workflows/mcmicro.nf Outdated Show resolved Hide resolved
tests/main.nf.test Outdated Show resolved Hide resolved
conf/modules.config Outdated Show resolved Hide resolved
@RobJY
Copy link
Contributor Author

RobJY commented Aug 1, 2024

Hmm, my check for pixel_size when tma_dearray is true doesn't seem to be catching when I remove pixel_size from our test case. Looking into this now.

I ran a manual test and it seems to work correctly.
The error message when running with nf-test makes it look like it's getting further than the validation though. Please let me know if you think this is a problem.

@RobJY
Copy link
Contributor Author

RobJY commented Aug 1, 2024

Should I change the publish directory for the coreograph module to be output/tma_dearray/coreograph?

nextflow_schema.json Outdated Show resolved Hide resolved
subworkflows/local/utils_nfcore_mcmicro_pipeline/main.nf Outdated Show resolved Hide resolved
subworkflows/local/utils_nfcore_mcmicro_pipeline/main.nf Outdated Show resolved Hide resolved
@jmuhlich
Copy link
Member

jmuhlich commented Aug 5, 2024

Should I change the publish directory for the coreograph module to be output/tma_dearray/coreograph?

No, I think it should just be tma_dearray. Could you change it to that?

In general, I think the publish directories should only contain the tool name as a sub-directory when we support multiple simultaneous implementations for that tool or in downstream results (so just segmentation at the moment) but that's something we can adjust in another PR. I was unable to find any guidance on this in the nf-core documentation. Have you seen anything?

@RobJY
Copy link
Contributor Author

RobJY commented Aug 5, 2024

Yes, I'll make the change to tma_dearray.

That sounds like a good plan. I wasn't sure if we'd be adding other modules besides coreograph for performing dearray, but you're right, we can always change that in a later PR.

1 similar comment
@RobJY
Copy link
Contributor Author

RobJY commented Aug 5, 2024

Yes, I'll make the change to tma_dearray.

That sounds like a good plan. I wasn't sure if we'd be adding other modules besides coreograph for performing dearray, but you're right, we can always change that in a later PR.

@jmuhlich jmuhlich merged commit 48f7b23 into nf-core:dev Aug 12, 2024
4 checks passed
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