Hello again, Thank you for clarifying the situation - very helpful for us. This turns out to be a known issue that we have a correction for.
See "Known Issues" at this link: http://genomewiki.ucsc.edu/index.php/Wiggle The short answer is that this is a data compression/decompression problem. Using the table browser to get "data points" from your custom track reveals this note: # This data has been compressed with a minor loss in resolution. # (Worst case: 373.531) The new-and-improved wiggle description page provides more info. http://genome.ucsc.edu/goldenPath/help/wiggle.html We suggest using the new file format "bedgraph" instead: http://genome.ucsc.edu/goldenPath/help/bedgraph.html Please review and try the new data format and let us know if this corrects the display of your data, Thank you for your patience, Jennifer Atif Shahab wrote: > Hi Jennifer, > > I thought "auto-scale data to view" scales the min/max range of view > based on the values in the display range. Changing it to 'user > vertical range settings' would mean that the vertical range would no > longer dynamically change and will be fixed independent of the values > in the display range. > > If this understanding is correct then the expected behaviour should be > that in the range of chr1:162,872,114-162,872,154 the values should > auto scale with max 198 to min 4; however it is not happening and the > browser shows the value to be 2 which is in fact the minimum of the > dataset and is not even in the display range. > > - atif >>> tinfo/genome _______________________________________________ Genome maillist - [email protected] http://www.soe.ucsc.edu/mailman/listinfo/genome
