Hi Congmao, I replied to your inquiry about this last week. Maybe it got buried in your inbox. Here are the two messages I sent you last week.... (the fix should appear in the next couple of days now.)
------------------------------------- Hi Congmao, thanks for bringing this to our attention. This does seem to be a bug. It could be that the values of min and max are just switched on screen, but at this time, I cannot be certain. We will investigate this further and make any needed fixes as soon as possible. - Greg Roe UCSC Genome Browser ========================== Thanks again for letting us know about this issue. One of our developers has fixed it already on our test machine, so the fix should be out soon. I believe the issue was just that the min and max values were switched in the display. -Greg ========================== On 1/7/11 10:41 PM, springwang wrote: > Hi, mary! > Is it someting wrong about the "Minimum span" and "maximum span" in the > Mapability track? Why "Minimum span" is larger than "maximum span"? > Thanks! > Congmao > > Example: > Position: chr2:233,338,058-233,338,219 > Total Bases in view: 162 > Statistics on: 59 items covering 162 bases (100.00% coverage) > Average item spans 2.75 bases. Minimum span 22 maximum span 1 > Average value 0.391596 min 0.0625 max 1 standard deviation 0.304196 > > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
