Hi Eric,
I'm glad this is now working for you!
I just wanted to include notes about the solution that you already found in case others search the mailing list archives in the future:
First, ensure that all hgcentral.dbDb.taxId values for your new species are valid NCBI Taxonomy IDs:
http://www.ncbi.nlm.nih.gov/taxonomyThe tree is generated from dbDb and the NCBI Taxonomy Database as described in kent/src/hg/makeDb/doc/dbDbTaxonomy.txt:
http://genome-source.cse.ucsc.edu/gitweb/?p=kent.git;a=blob_plain;f=src/hg/makeDb/doc/dbDbTaxonomy.txt;hb=HEADThe script kent/src/hg/utils/dbDbTaxonomy.pl is required. You'll need to do a couple things differently from the instructions in dbDbTaxonomy.txt:
use hgcentral instead of hgcentraltest
instead of overwriting ~/kent/src/hg/js/dbDbTaxonomy.js, create a new file in some directory that your CGIs can access.
Then add or change this setting in cgi-bin/hg.conf so that the tree is displayed using your custom file instead of our js/dbDbTaxonomy.js:
# Display phylogenetic tree in hgGateway (URL or path relative to cgi-bin)
hgGateway.dbDbTaxonomy=/path/to/custom/dbDbTaxonomy.js
Please respond to this list if you have further questions!
Thank you again for your inquiry and for using the UCSC Genome Browser. Please send new and follow-up questions to one of our UCSC Genome Browser mailing lists below:
* Subscribe: Email genome-annou...@soe.ucsc.edu
* Unsubscribe: Email genome-announ...@soe.ucsc.edu