Manage the visualization of large amounts of other people's [often messy] genomics data
A common question when reading an interesting paper is, “how does relate to my favorite gene locus?”. To address this question, usually we need to download the supplemental data, figure out what format it’s in, convert it to some other useful format, and visualize it alongside our own data.
hubward helps manage this process, lowering the effort required to track,
manage, organize, and upload many studies for cross-comparison in the UCSC
Data are organized into track hubs on the UCSC
Genome Browser, and the name
hubward indicates the direction in which data
are moved into these track hubs. It can also refer to a direction in other
The separate repository, hubward-studies, contains examples of prepared track hubs. Subsets of these can be combined into user-defined hubs, or can serve as examples for preparing other studies.
Documentation can be found at https://daler.github.io/hubward.
metadata.yamlconfig keeps track of the liftover history in the new
descriptionfield is empty or missing, fill in the contents of README as documentation.
Streamlining of the code and CLI. This causes some backward
metadata.yaml config files in version 0.1.0, in
particular, the “source” section is now required. There is now a defined schema
for the metadata and the grouping files so that future changes can be validated
and automatically fixed.