-
Notifications
You must be signed in to change notification settings - Fork 0
Data
This pages describes how to load snippets into HiPiler and extract the location of snippets. It also explains how to load HiPiler in a Jupyter notebook.
HiPiler's configuration is specified in JSON and consists of two main parts: one for the snippet location and display and another one for HiGlass. The snippet configuration is stored under fgm
and HiGlass is configured under hgl
.
This is an example for the snippet configuration:
{
"fgm": {
"fragmentsServer": "//34.199.119.21/api/v1/",
"fragmentsPrecision": 2,
"fragmentsDims": 22,
"fragments": [
["chrom1", "start1", "end1", "strand1", "chrom2", "start2", "end2", "strand2", "dataset", "zoomOutLevel", "size", "distance-to-diagonal", "noise", "_groupA", , "_groupB"],
["22", 17395000, 17400000, "coding", "22", 17535000, 17540000, "coding", "CQMd6V_cRw6iCI_-Unl3PQ", 3, 25000000, 135000, 0.21559968240959723, 1, 1],
["22", 17400000, 17410000, "coding", "22", 17980000, 17990000, "coding", "CQMd6V_cRw6iCI_-Unl3PQ", 3, 100000000, 570000, 0.19905589933149648, 1, 4],
["22", 17650000, 17655000, "coding", "22", 17980000, 17985000, "coding", "CQMd6V_cRw6iCI_-Unl3PQ", 3, 25000000, 325000, 0.14815256212601854, 3, 2],
...
]
},
...
}
The parameters are defined as follows:
- fragmentsServer: URL to a HiGlass server or HiPiler server
- fragmentsPrecision: Float precision of the raw matrix snippets to be returned by the server
- fragmentsDims: Pixel dimension of the matrix snippets to be returned by the server. Since HiPiler currently only supports squared snippets only one dimension is needed.
- fragments: BEDPE-like table of snippet locations. For details see below.
Like a simple spreadsheet, the first row of the BEDPE-like location table contains the header. The following columns are required by HiPiler. Examples are in brackets
- chrom1 [str, e.g.: 'chr1']
- start1 [int, e.g.: 0]
- end1 [int, e.g.: 0]
- strand1 [str, e.g.: 'coding' or else]
- chrom2 (like
chrom1
) - start2 (like
start1
) - end2 (like
end1
) - strand2 (like
stand1
) - dataset [str, e.g.: 'CQMd6V_cRw6iCI_-Unl3PQ']
- zoomOutLevel [int, e.g.: 0]
The dataset
is the UUID of the Hi-C map where the locations should be extracted. zoomOutLevel
at which zoom level the snippets should be extracted, where 0 means maximally zoomed it.
Additionally, an unlimited number of extra columns can be appended to load categorical and ordinal attributes for exploration. Ordinal attributes just need to specified by a unique name, e.g., size, distance-to-diagonal, and noise. They appear as measure for arrangement of snippets in HiPiler. Categorical attributes need must be prefixed with an underscore (_), e.g., _groupA and _groupB. They appear as grouping options in HiPiler.
The local neighborhood (i.e., the Hi-C map) of snippets are shown in HiGlass. The configuration of HiGlass in HiPiler is unrestricted except that one should only configure one row of primary matrices and avoid vertical arrangement of multiple matrices as the vertical space is needed for the detail matrices. For instructions on how to configure HiGlass please visit its wiki.
A set of example / demo configurations are available here.
There are two options to load a configuration:
- Drag and drop JSON onto the browser window of HiPiler.
- Go to the home page and click on Select a config.
Coming soon
Coming soon