a74c645505a135d5c1e923afe477cdeb9c15bded markd Wed Jul 8 22:27:42 2020 -0700 added including multiple container directoies in genome dir path to gfServer diff --git src/hg/htdocs/goldenPath/help/hubQuickStartAssembly.html src/hg/htdocs/goldenPath/help/hubQuickStartAssembly.html index 772400a..140d7c3 100755 --- src/hg/htdocs/goldenPath/help/hubQuickStartAssembly.html +++ src/hg/htdocs/goldenPath/help/hubQuickStartAssembly.html @@ -106,37 +106,82 @@

Starting Blat for an Assembly Hub

From the location of yourAssembly.2bit file, http://yourURL/yourAssembly/yourAssembly.2bit, you can start two gfServers, specifying a port for the assembly hub to access amino acid sequence, 17777 -trans, or DNA sequence, 17779, in this example:

gfServer start localhost 17777 -trans -mask yourAssembly.2bit &
 gfServer start localhost 17779 -stepSize=5 yourAssembly.2bit &

Then you can edit the genomes.txt file of your assembly hub to include two lines in the stanza referring to yourAssembly, that would have matching port numbers:

-
transBlat yourLab.yourInstitution.edu 17777
-blat yourLab.yourInstitution.edu 17779 
+
+   transBlat yourLab.yourInstitution.edu 17777
+   blat yourLab.yourInstitution.edu 17779
+
+

+The assembly hub can be configured to talk to a dynamic BLAT server that loads +a pre-built index when started by an xinetd super-server. This +allows genomes to have a blat server without needing it to be resident in +memory at all times. +

+

+A dynamic BLAT server is specified with the dynamic argument to +the blat or transBlat specification, followed by +the gfServer dynamic root-relative directory contain the +2bit and gfidx files. The final genome +directory and base name of the data files must be the same as the +genome name. +

+For example: +

+   transBlat yourLab.yourInstitution.edu 4096 dynamic myGenome
+   blat yourLab.yourInstitution.edu 4096 dynamic myGenome
+
+

+

+for files store in the form: +

+    $rootdir/myGenome/myGenome.2bit
+    $rootdir/myGenome/myGenome.untrans.gfidx
+    $rootdir/myGenome/myGenome.trans.gfidx
+
+

+

-An addition argument of the string dynamic to the blat -or transBlat specification indicates that the BLAT server is dynamic and -started by xinetd. See gfServer documentation for the details -of configuring a dynamic BLAT server. +For for more deeply nest directory, for instance, for instance following the NCBI +convention: +

+   transBlat yourLab.yourInstitution.edu 4096 dynamic GCF/000/181/335/GCF_000181335.3
+   blat yourLab.yourInstitution.edu 4096 dynamic GCF/000/181/335/GCF_000181335.3
+
+

+

+will reference these genome files: +

+    $rootdir/GCF/000/181/335/GCF_000181335.3/GCF_000181335.3.2bit
+    $rootdir/GCF/000/181/335/GCF_000181335.3/GCF_000181335.3.untrans.gfidx
+    $rootdir/GCF/000/181/335/GCF_000181335.3/GCF_000181335.3.trans.gfidx
+
+

+ +See gfServer documentation for the details +of configuring a dynamic BLAT server and generating indexes. See an example genomes.txt with commented out lines here, and please note the uppercase "B" in transBlat. For more information, see the "Adding BLAT servers" section of the Assembly Hub Wiki. The Source Downloads page offers access to utilities with pre-compiled binaries such as gfServer found in a blat/ directory for your machine type here and further blat documentation here. Please note that because the -mask option in the above 17777 -trans gfServer option will mask all lower-case sequence from being matched, you may not wish to include it. See the above blat links and gfServer usage statement for more information.