src/utils/userApps/bigBedWigs.txt 1.3

Index: src/utils/userApps/bigBedWigs.txt
===================================================================
RCS file: /projects/compbio/cvsroot/kent/src/utils/userApps/bigBedWigs.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -b -B -U 4 -r1.2 -r1.3
--- src/utils/userApps/bigBedWigs.txt	30 Mar 2009 17:37:01 -0000	1.2
+++ src/utils/userApps/bigBedWigs.txt	2 Apr 2009 23:38:25 -0000	1.3
@@ -1,5 +1,20 @@
 
+INTRODUCTION:  Where is this bigWig and bigBed system useful ?
+
+    Your wiggle data or bed track files are too large to load as
+    custom tracks in the normal custom track submission system.
+    This system will convert your very large file into a much larger
+    file which can be used without transferring it to the genome browser.
+    Place this special file on your WEB server or FTP server and supply
+    a URL to it for your custom track submission.  Rather than trying
+    to transfer the entire file, only small parts of it will transfer
+    as you view the track in the genome browser.  The small parts transferred
+    will accumulate at UCSC as a cache for later reuse without any
+    additional transfer.
+
+========================================================================
+
 BIGWIG - BigWig files store continuous data that is displayed as a graph
 in the Genome Browser, much as wig files do.  BigWig files in fact are
 created initially from wig files, using the program wigToBigWig.  The
 resulting bigWig files are in an indexed binary format.  The main
@@ -19,8 +34,9 @@
 	wigToBigWig input.wig.gz chrom.sizes myBigWig.bw
     if your input.wig.gz file has 'track' and 'browser' lines:
 	zcat input.wig.gz | egrep -v "^track|^browser" \
 	    wigToBigWig stdin chrom.sizes myBigWig.bw
+    make sure you do not have more than one track of data in your input file.
 5) Move the output bigWig file to a http, https, or ftp site.
 6) Create a custom track with just the track line.
 	This will look something like:
        track type=bigWig name="My Big Wig" description="A Graph of Cool Data from My Lab" dataUrl=http://myorg.edu/mylab/myBigWig.bw
@@ -54,8 +70,9 @@
        bedToBigBed input.bed.gz chrom.sizes myBigBed.bb
     if your input.bed.gz file has 'track' and 'browser' lines:
 	zcat input.bed.gz | egrep -v "^track|^browser" \
 	    bedToBigBed stdin chrom.sizes myBigWig.bb
+    make sure you do not have more than one track of data in your input file.
 5) Move the output bigBed file to a http, https, or ftp site.
 6) Create a custom track with just the track line.
 	This will look something like:
        track type=bigBed name="My Big Bed" description="Cool Genome Annotations from My Lab" dataUrl=http://myorg.edu/mylab/myBigBed.bb