dd638ed5172629e7904b8c18b54150005178ae4f kuhn Mon Nov 22 19:11:50 2021 -0800 removed contractions diff --git src/hg/htdocs/goldenPath/help/customTrackText.html src/hg/htdocs/goldenPath/help/customTrackText.html index 47d82e8..5981e97 100755 --- src/hg/htdocs/goldenPath/help/customTrackText.html +++ src/hg/htdocs/goldenPath/help/customTrackText.html @@ -766,31 +766,31 @@ in the internet browser's UCSC Genome Browser cookie and also never save them to the cookie. This means that that link will show the Genome Browser default settings such as track selections, custom tracks, and track hubs. Also: Any changes made by the user or other URL arguments will not affect the user's Genome Browser settings. E.g., if you add a track in this new window, and come back to the genome browser later, this track will appear NOT in the new window. This setting is useful if a website wants to link to the Genome Browser, wants to start with a "clean slate" but does not want any changes to affect other Genome Browser windows that are open or that the user may open later. - <a href="../../cgi-bin/hgTracks?db=hg19&incognito=1" target="_blank">example link</a> to show the default tracks and positions for hg19, in a new, clean session, that is completely independent from all other Genome Browser windows that the user has open or will open later. - Any changes made to this window won't be saved and are lost as soon as the window is closed. + Any changes made to this window will not be saved and are lost as soon as the window is closed. Compare this behavior to the setting <code>ignoreCookie=1</code> described above. (At the moment, there is no visual indicator in such a Genome Browser window that changes are not saved, but we could add one in the future, please contact us if you think this could be useful for you.) This variable is probably useful for most websites using our tool hgRenderTracks to show only the Browser's main image from a Javascript-driven website. </li> <li> <code>oligoMatch=pack&hgt.oligoMatch=<dnaSeq></code> - switch on the Short Match track and highlight a matching sequence - <a href="../../cgi-bin/hgTracks?db=hg19&position=chr9%3A136130563-136150630&oligoMatch=pack&hgt.oligoMatch=TATAWAR" target="_blank">example link</a> to highlight the TATAWAR motif in the ABO locus</li> @@ -977,31 +977,31 @@ special columns at the end of each line. Your track type entry should consist of two lines: the first to define the track type and the second to specify the URL. For example:</p> <pre><code>track type=<font color="000099">broadPeak</font> https://www.ncbi.nlm.nih.gov/geosuppl/...</code></pre> <p> <strong><em>Problem:</em></strong> I've gotten my annotation track to display, but now I can't make it go away! How do I remove an annotation track from my Genome Browser display?<br> <strong><em>Solution:</em></strong> To remove only one track, click the <em>Manage Custom Tracks</em> button and delete the desired track using the checkbox and Delete button. To quickly remove all of your custom tracks, reset the Genome Browser to its default settings by clicking the <em>Click here to reset</em> link on the Gateway page. Note that this reset will also remove any other customizations you have made to your Genome Browser display.</p> <p> <strong><em>Problem:</em></strong> I put my custom track files on Dropbox, Apple iCloud, Google Drive, Amazon Drive, Box.com, Microsoft OneDrive, or -another "online cloud backup" provider and they won't display in the browser. +another "online cloud backup" provider and they will not display in the browser. Why? <br> <em>OR</em><br> <strong><em>Problem:</em></strong> When I try to visualize my custom tracks in the Browser, I receive the error message "Byte-range request was ignored by server".<br> <strong><em>Solution:</em></strong> Backup providers used to work for hosting simple text-based custom tracks, but things have changed. For large custom track data sets, the use of indexed binary formats such as bigBed and bigWig is preferable and usually fail with backup providers. These formats provide much faster display performance because only the portion of the file needed to display the currently viewed region must be transferred to the Genome Browser server. This requires that they are stored on a real web server. And to allow this type of display, byte-range support must be enabled on the web server. No commercial online backup solution supports this, to our knowledge. To check if your server has byte-range requests enabled, issue the following command:</p>