048b2becc526e0ec8ef7d4a172543349e72d2020 mspeir Mon Jan 27 10:00:50 2025 -0800 adding pointers to net construction example in GenomeWiki, refs #26358 diff --git src/hg/htdocs/FAQ/FAQtracks.html src/hg/htdocs/FAQ/FAQtracks.html index 8602f018684..f0b01a38956 100755 --- src/hg/htdocs/FAQ/FAQtracks.html +++ src/hg/htdocs/FAQ/FAQtracks.html @@ -20,30 +20,31 @@
Return to FAQ Table of Contents
There are different reasons why the Genome Browser tracks display can become slow. Below is a list of common scenarios alongside potential solutions. The most common reason involves the configuration settings that are saved as users interact with the Genome Browser, such as track visibilities and custom data. This can be solved by a reset of all your current Genome Browser session information although it is important to note that this will reset all settings including filters, track order and remove all custom data. To do @@ -483,16 +484,28 @@ ... track subTrack_1_NameIncomposite parent compositeTrackNameInSuperTrack on ... track subTrack_2_NameIncomposite parent compositeTrackNameInSuperTrack off
Key Differences:
For more information about superTracks and composite tracks, refer to the Organizing Track Hubs into Groupings help page.
+ + ++In short, nets are constructed to be single-coverage on the target assembly. +Nets are constructed from whole or parts of chains based on score. More details +can be found in this +net construction example in our wiki. + +