bbabbd5d2566d47d923d51dbe350634783455999 mspeir Sun Oct 26 12:14:52 2025 -0700 change soe to gi, refs #35031 diff --git src/hg/htdocs/goldenPath/help/bigGenePred.html src/hg/htdocs/goldenPath/help/bigGenePred.html index 98a6290522f..603afa3a5f2 100755 --- src/hg/htdocs/goldenPath/help/bigGenePred.html +++ src/hg/htdocs/goldenPath/help/bigGenePred.html @@ -85,41 +85,41 @@
Step 1.
Format your pre-bigGenePred file. The first 12 fields of pre-bigGenePred files are described by the
BED file format. Your file must
also contain the 8 extra fields described in the autoSql file definition
shown above: name2, cdsStartStat, cdsEndStat, exonFrames, type, geneName, geneName2,
geneType. For example, you can use this bed12+8 input file,
bigGenePred.txt. Your pre-bigGenePred file must be sorted
first on the chrom field, and secondarily on the chromStart field. You
can use the UNIX sort command to do this:
sort -k1,1 -k2,2n unsorted.bed > input.bed
Step 2.
Download the bedToBigBed program from the
-binary utilities directory.
Step 3.
Download the chrom.sizes file for your assembly from
-our downloads page (click on "Full
+our downloads page (click on "Full
data set" for your organism). For example, the hg38.chrom.sizes file for the hg38
database is located at
-http://hgdownload.soe.ucsc.edu/goldenPath/hg38/bigZips/hg38.chrom.sizes.
+http://hgdownload.gi.ucsc.edu/goldenPath/hg38/bigZips/hg38.chrom.sizes.
Alternatively, you can use the fetchChromSizes script from the
-utilities directory.
+utilities directory.
Step 4.
Create the bigGenePred file from your pre-bigGenePred file using the bedToBigBed
utility command:
bedToBigBed -as=bigGenePred.as -type=bed12+8 bigGenePred.txt chrom.sizes myBigGenePred.bb
Step 5. Move the newly created bigGenePred file (myBigGenePred.bb) to a web-accessible http, https, or ftp location. See hosting section if necessary.
Step 6. Construct a custom track using a single track line. Any of the track attributes will be available for use on bigBed tracks. The basic version of the track line will look something like this:
@@ -196,80 +196,80 @@ page to view an example of bigGenePred amino acid display at the beginning of the SIRT1 gene on chromosome 10.
In this example, you will create your own bigGenePred file from an existing pre-bigGenePred input file, a bed12+8 file.
bedToBigBed
+ Download the bedToBigBed
utility (Step 2, in the Creating a bigGenePred section above).bedToBigBed utility to create the bigGenePred output file (step 4,
above):
bedToBigBed -type=bed12+8 -tab -as=bigGenePred.as bigGenePred.txt hg38.chrom.sizes bigGenePred.bbIn this example, you will convert a GTF file to bigGenePred using command line utilities.
You will need gtfToGenePred, genePredTobigGenePred,
and bedToBigBed. If you would like to convert a GFF file to bigGenePred, you will use
gff3ToGenePred in place of the gtfToGenePred. You can download utilities from the
-utilities directory.
wget command. Skip this step if you already have a GTF
or GFF file.
wget http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredExample4.gtfgtfToGenePred command.
gtfToGenePred -genePredExt bigGenePredExample4.gtf example4.genePred
If you are converting a GFF file, use the gff3ToGenePred command.
gff3ToGenePred yourFile.gff example4.genePred genePredToBigGenePred example4.genePred bigGenePredEx4.txtwget https://genome.ucsc.edu/goldenPath/help/examples/bigGenePred.as
bedToBigBed -type=bed12+8 -tab -as=bigGenePred.as bigGenePredEx4.txt http://hgdownload.soe.ucsc.edu/goldenPath/hg38/bigZips/hg38.chrom.sizes bigGenePredEx4.bbbedToBigBed -type=bed12+8 -tab -as=bigGenePred.as bigGenePredEx4.txt http://hgdownload.gi.ucsc.edu/goldenPath/hg38/bigZips/hg38.chrom.sizes bigGenePredEx4.bb
http://genome.ucsc.edu/cgi-bin/hgTracks?db=hg38&position=chr19:44905790-44909388&hgct_customText=track%20type=bigGenePred%20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredEx4.bbYou can also add your data in the custom track management page. This allows you to set position, configuration options, and write a more complete desciption. If you want to see codons, you can right click, then click configure codon view or set this options using
baseColorDefault=genomicCodons as is done below.
browser position chr19:44905790-44909388
track type=bigGenePred baseColorDefault=genomicCodons name="bigGenePred Example Four" description="Ex4:BigGenePred Made from GTF" visibility=pack bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredEx4.bb
Once you are done, you should have a track on the Genome Browser like the one below.
If you would like to share your bigGenePred data track with a colleague, learn how to create a URL link to your data by looking at Example #6 on the custom track help page.
Because the bigGenePred files are an extension of bigBed files, which are indexed binary files, it can be difficult to extract data from them. UCSC has developed the following programs to assist in working with bigBed formats, available from the -binary utilities directory.
+binary utilities directory.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.
If you encounter an error when you run the bedToBigBed program, check your input
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
+(available here) to remove the problematic
row(s) before running the bedToBigBed program.