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

minimap2 overlap parameters #64

Open
rcgsmith opened this issue Oct 22, 2024 · 0 comments
Open

minimap2 overlap parameters #64

rcgsmith opened this issue Oct 22, 2024 · 0 comments

Comments

@rcgsmith
Copy link

Dear herro authors,

For my particular use case I find that the minimap2 all-v-all overlap stage results in a large fraction of input reads being discarded before the inference stage (2828 reads in overlap input, 620 represented in overlap alignment output).

Please can I ask how the ava overlap parameters have been chosen in the create_batched_alignments.sh script?:

minimap2 -K8g -cx ava-ont -k25 -w17 -e200 -r150 -m2500 -z200 -f0.005 --dual=yes

I am using herro for error correction across reads from a small fraction of the human genome (~400kbp locus) which is known to contain a large segmental duplication. The low number of herro output reads resulting from loss at the overlap stage, means that there are some regions in the locus with extremely low coverage. Although I can adapt the minimap2 parameters to improve this (in particular, allowing k, w, and f to take default -X ava-ont values), I would like to understand whether this would be a bad idea for herro inference stage.

Any insights gratefully received, thank you.

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

No branches or pull requests

1 participant