Good Afternoon Viren: I have experimented with all of your data sets here today and can see no errors in the handling of the tracks. In my previous email to you, I have indicated how to use the URL specification in the track line with the bed item name so you can avoid using the extra bedDetail items. You can use a simple 9 column bed track for this data. For example:
For example, this track line: track name=ISCA_Uncertain_2011-09-19 type="bed 9" description="ISCA Uncertain CNVs" db=hg19 visibility=3 itemRgb=On url="http://your.site.org/isca/ucsc/hg19/DetailsPages/$$.html"; With an item such as this: chr17 29033882 30326958 nssv582812 0 . 29033882 30326958 0,0,255 will construct the external link to nssv582812. Plus, you can achieve a much better response for your users if these tracks are bigBed types of data. --Hiram Patel, Viren wrote: > Hello. We have previously generated custom tracks for ISCA CNV data > (https://www.iscaconsortium.org/index.php/the-news/139-new-ucsc-tracks-now-available). > Recently the Genome Browser has started giving an "Invalid signed integer" > error when clicking on a CNV. We have not had any changes to the tracks and I > am wondering if something may have changed in the Genome Browser custom > tracks requirements. Please let me know what additional data you may need and > how I can troubleshoot this issue. Thanks. > > Viren Patel > www.iscaconsortium.org _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
