The first 5 fields of the interact format are the same as the first 5 fields of the standard -BED format. +BED format. See a graphical depiction +below of the columns.
When creating bigInteract files, we encourage you to customize the title and field descriptions of the prototype autoSql schema to better describe your data. Customizing this file will make your data more easily interpreted by users, who will see the field descriptions when accessing the track data from the Table Browser, when viewing items on the Genome Browser details pages (via the "view table schema" link), and (for users who download files), from the -as option of the bigBedInfo tool.
As an example, if the dataset represents SNP/gene interactions, replace 'sourceName' and related fields with 'snpName', etc, and 'targetName' and related fields with 'geneName', etc., editing the field descriptions to reflect the changes you make. For non-directional data such as ChIA-PET, one could use 'region1' and 'region2'.
@@ -155,31 +156,32 @@ chr3 64623042 64636663 . 800 4 . 0 chr3 64623042 64625153 . . chr3 64632961 64636663 . .
After the file loads in the Genome Browser, you should see four interactions displayed on chromosome 3. Two of the interactions have both interacting regions in the browser view, and two have a single region. One of these interacts across chromosomes (with a region on chromosome 20), and the other with a region outside of the browser window (indicated by rectangular connector). -The darkness of the interaction indicates the strength of the interaction. +The darkness of the interaction indicates the strength of the interaction. Also see the graphical +representation of each column of this example data below.
In this example, you will create a bigInteract track out of an existing bigInteract format file,
located on the UCSC Genome Browser http server. This file contains data for the hg19 assembly.
This example also contains the interactUp=true setting to flip the arcs of the interact display.
To create a custom track using this file:
track exampleInteractTrack
type bigInteract
visibility full
shortLabel exInteract
longLabel Example interact track
spectrum on
scoreMin 175
maxHeightPixels 300:150:20
bigDataUrl interactExample4.inter.bb
+This graphic represents the data in Example #2 with boxes around +columns of data, separately illustrated as individual custom tracks in the lower image.
+
++The interact file format has 18 fields where the first 5 fields +(column 1 box) are standard BED +format fields, which define the span of the interaction to be viewed on a chromosome. In the +below image see the representation of column 1 and how it spans the length of each arc. Next, there +are 3 fields for value, exp, and color before two sets of 5 fields that specify +the coordinates, name, and strand of the source (column 2 box) +and target (column 3 box) data, defining the endpoints of +each interact arc. In the below image the column 2 box represents the left foot of each arc +while the column 3 box represents the right foot of each arc. The second row of the example +data denotes an interaction to another chromosome, chr20, and thus is not represented by an arc.
+
+
If you would like to share your interact/bigInteract data track with a colleague, learn how to create a URL by looking at Example 6 on this page.
Because bigInteract files are an extension of bigBed files, which are indexed binary files, it can be difficult to extract data from them. UCSC has developed the following programs to assist in working with bigBed formats, available from the binary utilities directory.
bigBedToBed — converts a bigBed file to ASCII BED format.bigBedSummary — extracts summary information from a bigBed file.bigBedInfo — prints out information about a bigBed file. Use the -as option to see the file field descriptions.-As with all UCSC Genome Browser programs, simply type the program name (with no parameters) at the +As with all UCSC Genome Browser programs, one can type the program name (with no parameters) at the command line to view the usage statement.
If you encounter an error when you run the bedToBigBed program, check your input
file for data coordinates that extend past the end of the chromosome. If these are present, run
the bedClip program
(available here) to remove the problematic
row(s) in your input file before running the bedToBigBed program.