-
Notifications
You must be signed in to change notification settings - Fork 3
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
Query returns results outside query interval? #4
Comments
can you query the index using the command-line and see if it also returns these same results? if so, that will rule out the python bindings as the source of the issue. |
Did you sort your files before indexing? |
@ryanlayer Yes, the bed files are all lexicographically sorted before they were indexed. Example:
@brentp Querying the same index in the command line provides the exact same output |
You'll need to sort by chrom, then start. |
There is a sort_bed in the scripts directory that will sort a directory full of files.
… On Mar 2, 2018, at 6:53 AM, Brent Pedersen ***@***.***> wrote:
You'll need to sort by chrom, then start.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Using the sort_bed file on my own files seems to have solved to problem! Thanks, I really appreciate your support |
I am performing some queries on a index containing TAD intervals and I noticed sometimes the query returns 2 results where I only expect to see one (because I know all the intervals in the index are non overlapping). When checking the results, I noticed that sometimes they include a result that should not overlap with the query interval. For example:
returns:
The first results definitely does not overlap with the single query position and the second result also doe snot seem to overlap. The same is true for the other file in the index:
returns:
I am not sure if this is a bug or the fault lies in my index and/or indexed data or that I am just completely misinterpreting the results?
The text was updated successfully, but these errors were encountered: