198c9b8daecc44fbda6a6494c566c723920f030a lrnassar Wed Mar 11 18:25:21 2026 -0700 Fixing a few hundred clear typos with the help of Claude. Some are less important in code comments, but majority of them are in user-facing places. I manually approved 60%+ of the changes and didn't see any that were an incorrect suggestion, at worst it was potentially uncessesary, like a code comment having cant instead of can't. No RM. diff --git src/hg/htdocs/goldenPath/help/bigChain.html src/hg/htdocs/goldenPath/help/bigChain.html index d1fba62c819..87d767735c4 100755 --- src/hg/htdocs/goldenPath/help/bigChain.html +++ src/hg/htdocs/goldenPath/help/bigChain.html @@ -1,25 +1,25 @@

bigChain Track Format

-The bigChain format describes a pairwise alignment that allow gaps in both sequences simultaneously, +The bigChain format describes a pairwise alignment that allows gaps in both sequences simultaneously, just as chain files do; however, bigChain files are compressed and indexed as bigBeds. Chain files are converted to bigChain files using the program bedToBigBed, run with the -as option to pull in a special autoSql (.as) file that defines the fields of the bigChain.

The bigChain files are in an indexed binary format. The main advantage of this format is that only those portions of the file needed to display a particular region are transferred to the Genome Browser server. Because of this, bigChain files have considerably faster display performance than regular chain files when working with large data sets. The bigChain file remains on your local web-accessible server (http, https or ftp), not on the UCSC server, and only the portion needed for the currently displayed chromosomal position is locally cached as a "sparse file". If you do not have access to a web-accessible server and need hosting space for your bigChain files, please see the Hosting section of the Track Hub Help documentation.

@@ -159,31 +159,31 @@ computer (Step 1 in Creating a bigChain track, above).

Save the autoSql files bigChain.as and bigLink.as to your computer (Step 2, above).

Download the bedToBigBed and chainToBigChain utilities (Step 3, above).

Save the hg38.chrom.sizes text file to your computer. This file contains the chrom.sizes for the human hg38 assembly (Step 4, above).

Run the utilities in Steps 5-7, above, to create the bigChain and bigLink output files.

- Place the newly created bigChain (bigChain.bb) and and bigLink + Place the newly created bigChain (bigChain.bb) and bigLink (bigChain.link.bb) files on a web-accessible server (Step 8).

Construct a track line that points to the bigChain file (Step 9, above).

Create the custom track on the human assembly hg38 (Dec. 2013), and view it in the Genome Browser (Step 10, above).

Sharing your data with others

If you would like to share your bigChain data track with a colleague, learn how to create a URL by looking at Example 6 on this page.

Extracting data from the bigChain format

@@ -194,21 +194,21 @@

bigBedToBed — converts a bigBed file to ASCII BED format.
bigBedSummary — extracts summary information from a bigBed file.
bigBedInfo — prints out information about a bigBed file.

As with all UCSC Genome Browser programs, simply type the program name (with no parameters) at the command line to view the usage statement.

Troubleshooting

If you encounter an error when you run the bedToBigBed program, check your input -file for data coordinates that extend past the the end of the chromosome. If these are present, run +file for data coordinates that extend past the end of the chromosome. If these are present, run the bedClip program (available here) to remove the problematic row(s) in your input file before running the bedToBigBed program.