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 fastq_bwa_mem_samblaster #5582

Closed
wants to merge 2 commits into from

Conversation

GallVp
Copy link
Member

@GallVp GallVp commented May 9, 2024

PR checklist

Closes #4909

  • Added fastq_bwa_mem_samblaster
  • 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 module conventions in the contribution docs
  • If necessary, include test data in your PR.
  • Remove all TODO statements.
  • Emit the versions.yml file.
  • Follow the naming conventions.
  • Follow the parameters requirements.
  • Follow the input/output options guidelines.
  • Add a resource label
  • Use BioConda and BioContainers if possible to fulfil software requirements.
  • Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
    • For modules:
      • nf-core modules test <MODULE> --profile docker
      • nf-core modules test <MODULE> --profile singularity
      • nf-core modules test <MODULE> --profile conda
    • For subworkflows:
      • nf-core subworkflows test <SUBWORKFLOW> --profile docker
      • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
      • nf-core subworkflows test <SUBWORKFLOW> --profile conda

@GallVp GallVp requested a review from a team as a code owner May 9, 2024 21:32
@GallVp GallVp requested review from adamrtalbot and removed request for a team May 9, 2024 21:32
@SPPearce
Copy link
Contributor

Do you know if samblaster works on CRAM files?

@GallVp
Copy link
Member Author

GallVp commented Jul 29, 2024

Do you know if samblaster works on CRAM files?

According to this the developer has no plans to support CRAM for now: GregoryFaust/samblaster#25 (comment)

Copy link
Contributor

@SPPearce SPPearce left a comment

Choose a reason for hiding this comment

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

Can we swap to the . notation that the other subworkflows generally use?

@@ -0,0 +1,11 @@
process {
withName: BWA_MEM {
ext.prefix = { "${meta.id}.on.${meta.ref_id}.bwa.mem" }
Copy link
Contributor

Choose a reason for hiding this comment

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

Why these prefixes?

Copy link
Member Author

Choose a reason for hiding this comment

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

Although these prefixes are not necessary here but in a pipeline they are as fastqs from each sample are mapped to each reference.

@GallVp
Copy link
Member Author

GallVp commented Aug 27, 2024

Can we swap to the . notation that the other subworkflows generally use?

Thank you for the review.

Do you mean swapping | with .? Yes, I have no objection to that other than that I prefer | as it is visually more explicit compared to a small .

@GallVp GallVp force-pushed the fastq_bwa_mem_samblaster branch from 8b53fe0 to dca715d Compare August 27, 2024 21:38
@GallVp
Copy link
Member Author

GallVp commented Nov 24, 2024

Closing this as it has not gained any interest from any other pipeline. If someone comes looking for this or something similar, please find it here: https://github.com/GallVp/nxf-components/blob/c30c8320078c68e14e41516ec6eaaca5f084ef38/subworkflows/gallvp/fastq_bwa_mem_samblaster/main.nf#L5

@GallVp GallVp closed this Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: No status
Development

Successfully merging this pull request may close these issues.

new subworkflow: FASTQ_BWA_MEM_SAMBLASTER
2 participants