gcv icon indicating copy to clipboard operation
gcv copied to clipboard

need to think of a better way to determine track boundaries in pan-view

Open adf-ncgr opened this issue 6 years ago • 2 comments

currently, the pan-view uses the old strategy from basic view whereby every track extent is determined exclusively by "num neighbors"; when some tracks have internal gene PAVs (as is typically the case) this creates "ragged" track alignment edges. This can give the false impression that tracks are lacking the genes on the edges when in fact they simply fell outside the num neighbors bounds. One approach, though perhaps not the most "performant" would be to do a two-pass track definition. In the first pass, we would determine a gene family set using the num neighbors approach across all the given gene foci. Then, after this gene family set had been established, we could requery for tracks, using essentially (if not exactly) the same method that is used for the search view track retrieval (ie for the sought tracks, not the query track). If it weren't for federated mode, this could probably be accomplished in one server request, but as it stands it seems like it will have to be two. Other ideas welcome...

adf-ncgr avatar Oct 13 '17 02:10 adf-ncgr