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

Mapping can be removed #12

Open
DLBPointon opened this issue Nov 6, 2024 · 1 comment
Open

Mapping can be removed #12

DLBPointon opened this issue Nov 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@DLBPointon
Copy link
Collaborator

Description of the bug

Mapping is resource-intensive and generates a lot of unnecessary data that BTK doesn't need. This adds a significant amount of time to the total run time.

Instead, the mapping should be removed from EAR and we allow the BTK to run its own mapping which only requires coverage information, not indels and CIGAR data.

Command used and terminal output

No response

Relevant files

No response

System information

No response

@DLBPointon DLBPointon added the bug Something isn't working label Nov 6, 2024
@yumisims
Copy link

yumisims commented Nov 6, 2024

BTK can take aligned bam/cram or unaligned bam/cram, but in principle, giving an aligned one will save time to process BTK. The solution of mapping for EAR can be either: convert read fasta to unmapped bam/cram, but when running BTK should change the "align = true" in nextflow.config (https://github.com/sanger-tol/blobtoolkit/blob/dev/nextflow.config). solution B, using cram_filter to chunk the container as in readmapping : https://github.com/sanger-tol/readmapping/blob/dev/subworkflows/local/align_pacbio.nf, but will first convert fasta to cram (also in readmapping ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants