Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

The Offsets for Thresholded Regions feature is designed specifically for working with tiling array data. Captured data from tiling array probes should usually be shifted for display.  Since the probes are 25 base pairs long, but the x-coordinates given represent the starting coordinate, you should shift the threshold data so that it starts at 12 base pairs past the given beginning, and ends at 13 base pairs past the beginning.  This is the default placement of all graph threshold bars; if you are viewing typical tiling array data, IGB default is set to the correct parameters. If these offsets are not correct for the data you are analyzing, you should change them.

When you view non-tiling array data in IGB, you should adjust the offset to 0 (set Start to 0 and End to 1) to correctly align the threshold bars with their actual coordinates.

Control gaps

Experimental data can be noisy.  If you are looking for general trends and want to ignore small local variations, you can use the Max Gap and Min run settings. Slide the sliders to adjust, or enter values into the boxes for each parameter:

...

This track will be given a default label containing all of the relevant parameters, which you can later change if desired. An example name is

Wiki Markup"threshold, \ [60 to infinity\] offsets: (+12, \ +13), max_gap=20, min_run=30, graph: depth: HotI2T1"

The name of the new track will always start with 'threshold' and end with the name of the graph track that was used (in this case, the graph was a depth graph made from a .bam track called HotI2T1). The value '60 to infinity' shows that the threshold level was set to 60 and looked at > thresh. The offsets were NOT corrected as they should have been, and are set to the tiling array values. Finally, the max gap and min run values are recorded.