Cook, Malcolm
unread,Jul 1, 2015, 5:16:17 PM7/1/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Matthew Speir, Hiram Clawson, gen...@soe.ucsc.edu, Maximilian Haeussler
Matthew,
> Thank you for providing a link to your track hub. The issue is that you are
> defining a searchTrix file in your trackDb without defining a corresponding
> searchIndex. The searchTrix file is used to map free-text to IDs, which are
> then searched for in the searchIndex of the corresponding data file. Having a
> searchTrix file without the corresponding searchIndex will not do anything.
Aha! Now I see it was a uninformed mistake for me to simply my problem by trying to debug the searchTrix in the absence of a searchIndex.
(sounds of forehead slapping and murmurs of "doh" echo throughout the chambers)
So, while restoring my own "searchIndex name" in my trackdb.txt, I realize that before I had been placing it on the wrong stanzas! I had it put the searchIndex on all my bigWigs!
("doh"s are now joined by sotto voce whispers of "dumb twit"...)
So, I've fixed all that.
And, of course, I've remembered to re-enable my `-extraIndex=name` in my call to bedToBigBed
And, woo-hoo,
ELVIS IS IN THE GENOME
> We will expand the documentation to make this clearer.
Sounds good.
> We may also add
> something to hubCheck to report searchTrix entries without a matching
> searchIndex entry in the future.
And possibly to report
searchIndex on track types that don't take them.??
searchIndex referring to bed's that are not indexed ( you catch this during run-time now with a nice warning , but hubCheck could also screen on this)
Finally, I do note that my search for elvis is returning two hits to the same locus. This must be an error.
Thank you all so much for your assistance in sleuthing this.
Cheers,
~Malcolm