e6ad1f3c830ac6c46b539afb4c75d463ee323457 jnavarr5 Fri Oct 17 11:10:05 2025 -0700 Making changes from code review, refs #36505 diff --git src/hg/htdocs/inc/hgMyData.html src/hg/htdocs/inc/hgMyData.html index 5aa7d0beff9..7b7c5ff3af1 100755 --- src/hg/htdocs/inc/hgMyData.html +++ src/hg/htdocs/inc/hgMyData.html @@ -1,103 +1,102 @@
Upload your track hub files to UCSC and view your bigBed, bigWig, BAM, VCF, and other supported files -- no need to rely on third-party hosting services such as Dropbox, Google Drive, or AWS.
Each account is allocated 10 GB of storage. While we strive to maintain uninterrupted - access, please be sure to maintain your own backups. Data persistence over the long term + access, please maintain your own backups. Data persistence over the long term is not guaranteed. To request additional storage space, please contact us.
There are two primary ways to upload your files:
If a hub.txt file is not provided when uploading the data files, a hub.txt file is automatically generated. The generated hub.txt file is configured with the useOneFile trackDb setting, and as a result, each hub is limited to a single genome assembly.
Editing the generated hub.txt file is not yet supported. To customize the hub configuration or data display, replace the generated hub.txt file with your own version after uploading the data files.
By default, your most recently used genome assembly is selected after choosing which - files to upload. To use a different assembly, the - popular assemblies drop-down menu or the search - box can be used to select another genome assembly. + files to upload. Use the popular assemblies drop-down menu or the search + box to select another genome assembly.