track uniqueCompositeTrackName
compositeTrack on
...
track uniqueNameWithoutSpaces
parent uniqueCompositeTrackName on
...
track newUniqueNameWithoutSpaces
parent uniqueCompositeTrackName off
A composite track groups together related tracks, usually but not necessarily of a similar type, that you
want to display together (referred to as "subtracks"). If you want to organize tracks into
a hierarchy and there is a single level of grouping, use a composite. For example, you could group
together called variants or ChIP-seq peaks with their underlying BAM reads or sequencing coverage. The
compositeTrack on line defines the parent track that will be later
referenced as parent uniqueCompositeTrackName off in each subtrack's
-stanza. Either "on" or "off" can be used to set a subtrack to be displayed or not
+stanza. Either "on" or "off" can be used to set a subtrack to be displayed or not
displayed by default. Composite tracks can be broken apart further to group very similar tracks with
the trackDb use of subGroups and
views, not demonstrated here. Read
all about composite
tracks here. See an
example trackDb.txt.
track uniqueSuperTrackName
superTrack on show
...
@@ -171,31 +171,31 @@
For example, you could have a composite with RNA-seq results and a composite with ChIP-Seq results grouped
together into a supertrack describing a cell line.
Supertracks contain composite tracks or container multiWigs, but not vice
versa. The superTrack on show line allows for this track to be later
referenced as parent uniqueSuperTrackName in each of the children
subtracks (note how it is only required for direct children, and not for subtracks contained in a
composite inside the supertrack -more below). The "show" is optional and sets the supertrack to
display by default. It may help to think of the original declaring supertrack stanza as a light switch
that by default is off, and can be flipped on by adding show.
All tracks that claim membership to the supertrack can then set their
own visibilities in lower stanzas by declaring settings such as by having
the parent line and a separate visibility dense line.
If no visibility setting is defined for a track,
the default setting of hide is assigned. This can cause confusion if one
-mistakenly tries to set visibilities only at the top parent supertack stanza and
+mistakenly tries to set visibilities only at the top parent supertrack stanza and
leaves out visibility declarations for all children.
Also do not confuse the parent line with how it is used in composites. For example,
in supertracks DO NOT try something like parent uniqueSuperTrackName [off/on][off/on] will only work with composite tracks.
In the above nested example you do see track uniqueNameWithoutSpaces with a
setting line specific only to the fact it is a child of a composite,
parent uniqueCompositeTrackNameInSuperTrack on. The parent
-of the child composite track is in turn is a child to a supertrack declared by
+of the child composite track is in turn a child to a supertrack declared by
parent uniqueSuperTrackName.
Read all about
supertracks here. See an
example trackDb.txt.