Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@maxulysse
Copy link
Member

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/sarek 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).

@nf-core-bot
Copy link
Member

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

@famosab
Copy link
Contributor

famosab commented Mar 14, 2025

I think this looks good but I am not an expert on anything related to GHA haha

@famosab
Copy link
Contributor

famosab commented Mar 14, 2025

Do we also need to extend the nf-test.config to include gpu settings (similar to modules repo) or does nextflow do this automatically?

@famosab
Copy link
Contributor

famosab commented Mar 14, 2025

Something like this in the nextflow config

gpu {
        process {
            withLabel: process_gpu {
                ext.use_gpu = true
            }
        }
        docker.runOptions = '-u $(id -u):$(id -g) --gpus all'
        apptainer.runOptions = '--nv'
        singularity.runOptions = '--nv'
    }

@famosab
Copy link
Contributor

famosab commented Mar 14, 2025

or a test profile for gpus

@maxulysse
Copy link
Member Author

Possibly, I think that can be included in the parabricks PR.
I did just have a go at the GHA

Comment on lines -614 to -615
"test.md.cram.stats:md5,f181d98f08ad94c3926ac149a87d834b",
"test.recal.cram.stats:md5,18346c938c7b1bfaf9ac9413fdba90d8"
Copy link
Contributor

Choose a reason for hiding this comment

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

what happened to the checksums?

Copy link
Member Author

Choose a reason for hiding this comment

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

Famke removed some cram.stats, because they were unstable, so I removed them all

@maxulysse maxulysse merged commit e8009c4 into nf-core:dev Mar 24, 2025
26 checks passed
@maxulysse maxulysse deleted the GPUS branch April 25, 2025 08:05
@maxulysse maxulysse restored the GPUS branch April 25, 2025 08:05
@edmundmiller edmundmiller linked an issue May 12, 2025 that may be closed by this pull request
5 tasks
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.

Sarek goes GPU - parabricks integration

4 participants