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

refactor preprocessing, one more time #494

Merged

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 - add to the software_versions process and a regex to scrape_software_versions.py
    • 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 lint .).
  • Ensure the test suite passes (nextflow run . -profile test,docker).
  • 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).

@maxulysse maxulysse changed the title refactor preprocessing, just one more time refactor preprocessing, one more time Mar 7, 2022
@maxulysse
Copy link
Member Author

reverted gatk4 spark containers to a version that was actually working

@FriederikeHanssen
Copy link
Contributor

reverted gatk4 spark containers to a version that was actually working

😢 I don't get why it doesn't work with the new one. Doesn't look like the base containers is changing. but great that you fixed it 🚀

@maxulysse
Copy link
Member Author

reverted gatk4 spark containers to a version that was actually working

cry I don't get why it doesn't work with the new one. Doesn't look like the base containers is changing. but great that you fixed it rocket

I'm as confused as you are

@@ -244,14 +244,12 @@ process {
withName: "BWA.*MEM" {
ext.args = { meta.status == 1 ? '-K 100000000 -M -B 3' : '-K 100000000 -M' }
ext.prefix = { params.split_fastq > 1 ? "${meta.id}".concat('.').concat(reads.get(0).name.findAll(/part_([0-9]+)?/).last()) : "" }
publishDir = [
enabled: false
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this the default? I think we discuss this in one of the previous PR'S?

Copy link
Member Author

Choose a reason for hiding this comment

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

Wasn't working properly actually

Copy link
Contributor

Choose a reason for hiding this comment

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

oh ok, so should be added back then to the other modules? Or is only BWA not working?

Copy link
Member Author

Choose a reason for hiding this comment

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

no idea, I'll need to do some more proper tests with that

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this solved?

Copy link
Member Author

Choose a reason for hiding this comment

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

oh, good point, I'll check this out

Copy link
Member Author

Choose a reason for hiding this comment

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

still not, I have no idea why I have the bam if I don't have this enabled: false here

workflows/sarek.nf Outdated Show resolved Hide resolved
@maxulysse maxulysse merged commit 915f18f into nf-core:dev Mar 15, 2022
@maxulysse maxulysse deleted the dev_refactor_harder_better_faster_stronger branch March 15, 2022 10:06
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