--
---
You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/AM9PR02MB692920EBE39FE7782443CAEEB1B49%40AM9PR02MB6929.eurprd02.prod.outlook.com.
Hello Udi,
Upon some investigation, you should be able to use csi indexes. Could you try to add the VCF file to your hub on your GBiB as a custom track (http://genome.ucsc.edu/cgi-bin/hgCustom) as such (note the bigDataIndex setting):
track type=vcfTabix name="vcfCSI" bigDataUrl=PATH/TO/VCF.GZ bigDataIndex=PATH/TO/VCF.GZ.CSI
Below is a working example on hg38 for reference:
track type=vcfTabix name="vcfCSI" bigDataUrl=https://hgwdev.gi.ucsc.edu/~lrnassar/ExampleCustomTracks/bamExample/NA12877.vcf.gz bigDataIndex=https://hgwdev.gi.ucsc.edu/~lrnassar/ExampleCustomTracks/bamExample/NA12877.vcf.gz.csi
Let us know if that works for you. If so, the same setting could be used to load the track as part of the hub.
Another option would also be to convert the VCF file to a bigBed (http://genome.ucsc.edu/FAQ/FAQformat.html#format1.5) to display the data. We have done this for some internal VCF tracks, such as dbSNP and gnomAD. Below is a link to the table schema for gnomAD as an example:
You would need to reformat the file to at least have three required fields:
chrom
chromStart
chromEnd
You could then add any number of additional fields to the file which would be displayed in the track description page. It is worth noting that this would also allow you to use some settings available to bigBeds such as filters, mouseOvers, coloring, etc. I'll link to some more resources below:
http://genome.ucsc.edu/goldenPath/help/hgTrackHubHelp.html
http://genome.ucsc.edu/goldenPath/help/trackDb/trackDbHub.html
If you decide to employ this approach and require any assistance or have any further questions let us know.
I hope this is helpful. Please include gen...@soe.ucsc.edu in any replies to ensure visibility by the team. All messages sent to that address are archived on our public forum. If your question includes sensitive information, you may send it instead to genom...@soe.ucsc.edu.
Lou Nassar
UCSC Genomics Institute
Hi, Udi.
Glad to hear you were able to at least go the bigBed route. Let us know when you try the VCF with the csi index.
Regarding your issues with the bigBed file, there are a few suggestions. It can be hard to diagnose these problems without having access to the file itself.
Our first suggestion would be to try and rebuild the file but instead of type=3+4, use type=5+2. In essence your 4th and 5th field are standard BED fields, name (in this case arbitrary dots) and score. The reason for this is that very small BED files (BED 3 and BED 4) can sometimes have some unexpected interactions.
For labelFields, in the syntax:
The labelFields represents the display setting, the text inside the carrots (<>) represent the required settings, with the exception of anything inside brackets ([]) which is optional. In this case that means you need to designate at least one field name, but can optionally pass others.
For a working example, you can take a look at the transMapV5 track on hg38: https://genome.ucsc.edu/cgi-bin/hgTrackUi?db=hg38&c=chrX&g=transMapEnsemblV5
You will see a long list of available labels:
Label: common name organism abbreviation source database ...
And these are designated with the following trackDb setting:
Note that these are the names of the fields in the file schema:
If you are still having issues with display or data, could you send us a snippet of the raw data, as well as all commands and trackDb settings you are using?
I hope this is helpful. Please include gen...@soe.ucsc.edu in any replies to ensure visibility by the team. All messages sent to that address are archived on our public forum. If your question includes sensitive information, you may send it instead to genom...@soe.ucsc.edu.
Lou Nassar
UCSC Genomics Institute
Hello Udi,
Thanks for your patience in this reply.
Additional information can be added to an item description page using the bedDetail format, described here:
With this format, you can include up to two extra columns, in addition to the standard 4-12 columns, for extra information like a URL or description text. This should allow you to visualize it in your assembly hub in the bedDetail format or by converting to bigBed.
To convert it to bigBed binary format, you will want to use an autoSQL(.as) file that matches your number of columns. You may need to create a custom Table Schema if your file format does not have a pre-made file type name. If so, you can merge pieces of the bigBed12 and the bedDetail columns to create your custom schema.
https://github.com/ucscGenomeBrowser/kent/blob/master/src/hg/lib/bed12Source.as
https://github.com/ucscGenomeBrowser/kent/blob/master/src/hg/lib/bedDetail.as
I hope this was helpful. If you have any more questions, please reply-all to gen...@soe.ucsc.edu. All messages sent to that address are publicly archived. If your question includes sensitive data, please reply-all to genom...@soe.ucsc.edu.
All the best,
Daniel Schmelter
UCSC Genome Browser
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/AM9PR02MB6929B67E13F72CAEEB733710B1829%40AM9PR02MB6929.eurprd02.prod.outlook.com.