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/FAQ/FAQblat.html src/hg/htdocs/FAQ/FAQblat.html index 705593db630..c9f5fd74f9a 100755 --- src/hg/htdocs/FAQ/FAQblat.html +++ src/hg/htdocs/FAQ/FAQblat.html @@ -106,31 +106,31 @@ if your sequence is less than 30 bp. You can work around this minimum length limitation by adding more flanking sequence to your query to make the query unique enough. If this is not possible, the only alternative is to download the executables of BLAT and the .2bit file of a genome to your own machine and use BLAT on the command line. See <a href="#blat3">Downloading BLAT source and documentation</a> for more information. When using the command line version of BLAT, you can set the repMatch option to a large value to try to improve finding matches in repetitive regions and do not use one of the default 11.ooc repeat masking files.</p> <a name="blat1c"></a> <h2>BLAT or In-Silico PCR finds multiple matches such as chr_alt or chr_fix even though only one is expected</h2> <h6>I am seeing two or more matches in the genome although there should only be one. What are these extra matches?</h6> <p> This usually occurs on the newer genome assemblies, such as hg38, when you search a sequence that -has an "alternate" or "fix" sequence. To improve the quality of the these +has an "alternate" or "fix" sequence. To improve the quality of these assemblies, curators have added multiple versions of some important loci, e.g. the MHC regions. They also add fix sequences to resolve errors without changing the reference. See our <a target="_blank" href="https://genome-blog.gi.ucsc.edu/blog/patches/">patches blog post</a> for more information.</p> <p> When you blat or isPCR a sequence which matches a chromosome location that also has a fix or alt sequence, you will see a match on the reference chromosome (e.g. "chr1") and another match on the patch sequence (e.g. chr1_KN196472v1_fix). In most cases it is safe to ignore the patch hit, as a human genome will not contain both the reference and alternate sequence at the same time. For more information on the specific kinds of patch sequences see our <a target="_blank" href="FAQdownloads#downloadAlt">FAQ entry</a> on the topic.</p> <a name="blat2"></a> <h2>BLAT usage restrictions</h2> <h6>I received a warning from your Blat server informing me that I had exceeded the server use @@ -431,42 +431,42 @@ #For linux rsync -a rsync://hgdownload.gi.ucsc.edu/genome/admin/exe/linux.x86_64/blat/ ./ #For MacOS rsync -a rsync://hgdownload.gi.ucsc.edu/genome/admin/exe/macOSX.x86_64/blat/ ./ chmod +x gfServer gfClient blat </pre> <p> Next, download the appropriate .2bit genome (hg19 in this example), and run the gfServer utility with the web Blat parameters, designating the local machine and port 1234:</p> <pre> wget http://hgdownload.gi.ucsc.edu/goldenPath/hg19/bigZips/hg19.2bit ./gfServer start 127.0.0.1 1234 -stepSize=5 hg19.2bit </pre> <p> -After a few moments, the gfServer will initialize and be ready to recieve queries. In order +After a few moments, the gfServer will initialize and be ready to receive queries. In order to approximate web Blat, we will use the gfClient with the following parameters, designating our input and output files.</p> <pre> ./gfClient -minScore=20 -minIdentity=0 127.0.0.1 1234 . input.fa out.psl </pre> <p>The output file <code>out.psl</code> should have results very similar to web-based Blat.</p> <a name="blat12"></a> <h2>Standalone or gfServer/gfClient result start positions off by one</h2> <h6>My standalone Blat results or gfServer/gfClient Blat results have a start -position that is one less that what I see on web Blat results</h6> +position that is one less than what I see on web Blat results</h6> <p> This is due to how we store internal coordinates in the Genome Browser. The default Blat <strong>Output type</strong> of <strong>hyperlink</strong> shows results in our internal coordinate data structure. These internal coordinates have a zero-based start and a one-based end. See the following <a target="_blank" href="/FAQ/FAQtracks#tracks1" >FAQ entry</a> for more information.</p> <p> If the <strong>Output type</strong> is changed to <strong>psl</strong> on web Blat, the same zero-based half open coordinate results will be seen as the standalone Blat and gfServer/gfClient procedures.</p> <a name="blat13"></a> <h2>Protein-translated BLAT having different results</h2> <p> Protein-translated BLAT (protein or translated RNA queries) uses the standard vertebrate