-
Notifications
You must be signed in to change notification settings - Fork 6
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
non #2
Comments
Hey, |
For that, you simply don't set the |
If you are asking what good values for window and step would be: that really depends on what you are looking for. step should be greater or equal to the bin size of your data. If you want to scan the whole genome, it should also not exceed half the window size. Within that range it really depends on your computational resources; the smaller the step, the more comparisons will be made, which increases the resolution of your scan. If your computational resources allow, you could start with a step of 100 kb, as in the example. |
Moved to a new issue thread. Will close, as the window size question seems answered. |
No description provided.
The text was updated successfully, but these errors were encountered: