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

Window and K-mer size #19

Open
HTaekOppa opened this issue Apr 23, 2019 · 1 comment
Open

Window and K-mer size #19

HTaekOppa opened this issue Apr 23, 2019 · 1 comment

Comments

@HTaekOppa
Copy link

Hi MashMap,

Hope this email finds you well.

Just wondering is it possible to indicate a specific window size? Or, is it automatically calculated based on segment length?

From the "mashmap -h", I can see the -k (kmer), -s (seg length) and --pi (percent identity) can be modified but not the "Window Size".

I am trying to calculate the percentage of each 2Mb region (I assume this part would be "Window Size") covered by a query sequence of at least 1,000bp (I assume this part would be "seg length) and 95% identity (I assume this part would be "percent identity").

Looking forward to your reply!

Cheers,

Taek

@cjain7
Copy link
Contributor

cjain7 commented May 13, 2019

Just wondering is it possible to indicate a specific window size? Or, is it automatically calculated based on segment length?

Yes it is automatically computed.

Your interpretation of seg length and percent identity is correct, but window-size is a parameter for kmer sampling, it shouldn't be changed for your application. The way minimizer-based k-mer sampling works is that we pick minimum k-mer within a window; this helps towards better speed and memory-usage of the algorithm. So you can specify your ref. and query, and seg length of 1000 bp, I think it should work out.

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

2 participants