|
Hello, I need help with this track.. I am not able to get it to show up on Gbrowse.. and Im not sure what I need to change.. Hoping to get some idea.. J Hello, I know there are multiple posts about problems with individual wiggle track displays.. but I seem to be stuck in this as well.. I have the Conservation Score files from UCSC and I am trying to upload them on Gbrowse. The files look like this.. As you can see, not all positions have scores. Hence there are multiple places in the same file that have the “fixedStep chrom=Chr18 start=XXXXXX step=1” fixedStep chrom=Chr18 start=28760 step=1 0.000 0.000 0.000 0.001 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.001 0.001 0.003 0.010 0.015 0.020 0.023 0.026 0.028 0.029 0.029 0.030 0.029 fixedStep chrom=Chr18 start=31859 step=1 0.073 0.103 0.151 0.182 0.256 0.375 0.571 0.656 0.712 0.841 0.894 0.929 0.943 0.953 0.969 0.981 0.986 0.988 0.989 0.988 0.986 0.980 0.971 0.966 0.954 0.936 …. So I added the line only at the head of each file(irrespective of how many times it has the line fixedStep chrom=Chr18… repeated): track type=wiggle_0 name="fixedStep" description="fixedStep format" visibility=full autoScale=off viewLimits=0:1000 color=0,200,100 and then ran the wiggle2gff2.pl script. I get this line in the gff3 file: ##gff-version 3 Chr18 rgd Conservation 28760 87247357 . . . Name=fixedStep;Note=fixedStep%20format;wigfile=/rgd/gbrowse2/databases/Conscore/track_001.Chr18.1293125672.wib I use the bp_seqfeature_load.pl script to load these files into the DB. But then I get a blank track(first wiggle file). No errors either. Where am I going wrong? Am I supposed to add the line: “track type=wiggle_0 name="fixedStep" description="fixedStep format" visibility=full autoScale=off viewLimits=0:1000 color=0,200,100“ each time the line fixedStep chrom=Chr18.. repeats itself in the file? Here is the image:
And here is the configuration : [TEST_WIG] feature = Conservation glyph = wiggle_xyplot key = first wiggle file category = DETAILS:Annotated Variants Thanks, Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229 www.rgd.mcw.edu ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
Hello Pushkala
This is my suggestion. Try using variable step instead of fixed step. Like: track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" variableStep chrom=chr18 span=1 28760 1 28762 2 .... .... and so on. I'm not sure if we can use multiple headings in a wiggle file. That's a question I wanted to post. I generally create a wiggle file for each chromosome and give the path of the directory in the conf file. Karthik |
|
In reply to this post by pjayaraman
Hi Pushkala,
I'm not sure the GBrowse wiggle converter script supports multiple "fixedStep" lines in a single wiggle file. I've never seen that in a wiggle file before (though I admittedly have limited experience with them). If you trim those out but otherwise leave the file the same, does it work (though no doubt with screwed up coordinates)? Perhaps you'll need to split these into separate files. Scott On Tue, Dec 28, 2010 at 11:14 AM, Jayaraman, Pushkala <[hidden email]> wrote:
-- ------------------------------------------------------------------------ Scott Cain, Ph. D. scott at scottcain dot net GMOD Coordinator (http://gmod.org/) 216-392-3087 Ontario Institute for Cancer Research ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
In reply to this post by Karthik
I guessed that would be a problem.. the thing is that we do not have
information for all positions in the wiggle file.. hence the multiple headings.. So most wiggle files that Gbrowse is comfortable with use only one heading at the beginning of the file is it? Could I get an example WIG file from you? just to use as a model? Thanks, Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229 www.rgd.mcw.edu -----Original Message----- From: Karthik [mailto:[hidden email]] Sent: Tuesday, December 28, 2010 10:54 AM To: [hidden email] Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display Hello Pushkala This is my suggestion. Try using variable step instead of fixed step. Like: track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" variableStep chrom=chr18 span=1 28760 1 28762 2 .... .... and so on. I'm not sure if we can use multiple headings in a wiggle file. That's a question I wanted to post. I generally create a wiggle file for each chromosome and give the path of the directory in the conf file. Karthik -- View this message in context: http://generic-model-organism-system-database.450254.n5.nabble.com/FW-he lp-with-wiggle-track-display-tp3320404p3320440.html Sent from the gmod-gbrowse mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
If you use variable step, there is no need for multiple headings for the same chromosome, even if you don't have values for many positions.
For example, track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" variableStep chrom=chr18 span=1 1 4 2 5 35 1 36 2 ... ... The value for positions 1 and 2 are 4 and 5 respectively. The value for positions 3 - 34 are considered to be 0. So, you definitely do not need multiple headings for the same chromosome. I don't know if there is a way to represent multiple chromosomes in a single wiggle file. |
|
In reply to this post by Scott Cain
Thanks Scott, Ill try this.. there isn’t just two “fixedStep headings.. Each chromosome file has atleast 10-20 of those headings.. Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229 www.rgd.mcw.edu From: Scott Cain [mailto:[hidden email]] Hi Pushkala, On Tue, Dec 28, 2010 at 11:14 AM, Jayaraman, Pushkala <[hidden email]> wrote: Hello, I need help with this track.. I am not able to get it to show up on Gbrowse.. and Im not sure what I need to change.. Hoping to get some idea.. J Hello, I know there are multiple posts about problems with individual wiggle track displays.. but I seem to be stuck in this as well.. I have the Conservation Score files from UCSC and I am trying to upload them on Gbrowse. The files look like this.. As you can see, not all positions have scores. Hence there are multiple places in the same file that have the “fixedStep chrom=Chr18 start=XXXXXX step=1” fixedStep chrom=Chr18 start=28760 step=1 0.000 0.000 0.000 0.001 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.001 0.001 0.003 0.010 0.015 0.020 0.023 0.026 0.028 0.029 0.029 0.030 0.029 fixedStep chrom=Chr18 start=31859 step=1 0.073 0.103 0.151 0.182 0.256 0.375 0.571 0.656 0.712 0.841 0.894 0.929 0.943 0.953 0.969 0.981 0.986 0.988 0.989 0.988 0.986 0.980 0.971 0.966 0.954 0.936 …. So I added the line only at the head of each file(irrespective of how many times it has the line fixedStep chrom=Chr18… repeated): track type=wiggle_0 name="fixedStep" description="fixedStep format" visibility=full autoScale=off viewLimits=0:1000 color=0,200,100 and then ran the wiggle2gff2.pl script. I get this line in the gff3 file: ##gff-version 3 Chr18 rgd Conservation 28760 87247357 . . . Name=fixedStep;Note=fixedStep%20format;wigfile=/rgd/gbrowse2/databases/Conscore/track_001.Chr18.1293125672.wib I use the bp_seqfeature_load.pl script to load these files into the DB. But then I get a blank track(first wiggle file). No errors either. Where am I going wrong? Am I supposed to add the line: “track type=wiggle_0 name="fixedStep" description="fixedStep format" visibility=full autoScale=off viewLimits=0:1000 color=0,200,100“ each time the line fixedStep chrom=Chr18.. repeats itself in the file? Here is the image: And here is the configuration : [TEST_WIG] feature = Conservation glyph = wiggle_xyplot key = first wiggle file category = DETAILS:Annotated Variants Thanks, Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229
------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
In reply to this post by Karthik
Oh okay..
I forgot the coordinates before the scores.. I guess ill convert these in to Variable coordinates then.. :) Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229 www.rgd.mcw.edu -----Original Message----- From: Karthik [mailto:[hidden email]] Sent: Tuesday, December 28, 2010 11:15 AM To: [hidden email] Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display If you use variable step, there is no need for multiple headings for the same chromosome, even if you don't have values for many positions. For example, track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" variableStep chrom=chr18 span=1 1 4 2 5 35 1 36 2 ... ... The value for positions 1 and 2 are 4 and 5 respectively. The value for positions 3 - 34 are considered to be 0. So, you definitely do not need multiple headings for the same chromosome. I don't know if there is a way to represent multiple chromosomes in a single wiggle file. -- View this message in context: http://generic-model-organism-system-database.450254.n5.nabble.com/FW-he lp-with-wiggle-track-display-tp3320404p3320460.html Sent from the gmod-gbrowse mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
In reply to this post by Karthik
Hi,
You'll want to be careful with variableStep wig files. The wiggle glyph modules fail to interpolate values when they're not defined, leading to an artificial smoothing effect (it essentially keeps the previous known value) that you may not desire. I gave a more detailed explanation in a previous post, which you can find archived here http://generic-model-organism-system-database.450254.n5.nabble.com/wiggle-x yplot-smoothing-tp455999p456003.html The best solution is to either interpolate the data yourself and generate a fixedStep wig file, or switch to Lincoln's Bio::DB::BigWig adaptor. I personally found the BigWig format to be the best solution as it does not have these issues with variableStep wig files (confirmed with lots of personal experience), and that's what Lincoln seemed to advocate. As for the wiggle files themselves, there should only be one track line in the wig file, but you're allowed to have multiple definition lines (variableStep .... or fixedStep ....) lines. You may have multiple chromosomes per file. Tim -- Timothy J Parnell, PhD. Research Associate Howard Hughes Medical Institute Department of Oncology Huntsman Cancer Institute University of Utah Salt Lake City, UT 84112 On 12/28/10 10:14 AM, "Karthik" <[hidden email]> wrote: > >If you use variable step, there is no need for multiple headings for the >same >chromosome, even if you don't have values for many positions. >For example, > >track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" >variableStep chrom=chr18 span=1 >1 4 >2 5 >35 1 >36 2 >... >... > >The value for positions 1 and 2 are 4 and 5 respectively. The value for >positions 3 - 34 are considered to be 0. > >So, you definitely do not need multiple headings for the same chromosome. >I >don't know if there is a way to represent multiple chromosomes in a single >wiggle file. >-- >View this message in context: >http://generic-model-organism-system-database.450254.n5.nabble.com/FW-help >-with-wiggle-track-display-tp3320404p3320460.html >Sent from the gmod-gbrowse mailing list archive at Nabble.com. > >-------------------------------------------------------------------------- >---- >Learn how Oracle Real Application Clusters (RAC) One Node allows customers >to consolidate database storage, standardize their database environment, >and, >should the need arise, upgrade to a full multi-node Oracle RAC database >without downtime or disruption >http://p.sf.net/sfu/oracle-sfdevnl >_______________________________________________ >Gmod-gbrowse mailing list >[hidden email] >https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
Hello Dr. Parnell,
Could you give us an example of the usage of the Bio::DB::BigWig adaptor..? Currently we use the Bio::DB::Seqfeature::Store adaptor.. its not that flexible.. Thanks, Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email] Work: 414-955-2229 www.rgd.mcw.edu -----Original Message----- From: Timothy Parnell [mailto:[hidden email]] Sent: Tuesday, December 28, 2010 1:31 PM To: Karthik; [hidden email]; Jayaraman, Pushkala Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display Hi, You'll want to be careful with variableStep wig files. The wiggle glyph modules fail to interpolate values when they're not defined, leading to an artificial smoothing effect (it essentially keeps the previous known value) that you may not desire. I gave a more detailed explanation in a previous post, which you can find archived here http://generic-model-organism-system-database.450254.n5.nabble.com/wiggl e-x yplot-smoothing-tp455999p456003.html The best solution is to either interpolate the data yourself and generate a fixedStep wig file, or switch to Lincoln's Bio::DB::BigWig adaptor. I personally found the BigWig format to be the best solution as it does not have these issues with variableStep wig files (confirmed with lots of personal experience), and that's what Lincoln seemed to advocate. As for the wiggle files themselves, there should only be one track line in the wig file, but you're allowed to have multiple definition lines (variableStep .... or fixedStep ....) lines. You may have multiple chromosomes per file. Tim -- Timothy J Parnell, PhD. Research Associate Howard Hughes Medical Institute Department of Oncology Huntsman Cancer Institute University of Utah Salt Lake City, UT 84112 On 12/28/10 10:14 AM, "Karthik" <[hidden email]> wrote: > >If you use variable step, there is no need for multiple headings for the >same >chromosome, even if you don't have values for many positions. >For example, > >track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" >variableStep chrom=chr18 span=1 >1 4 >2 5 >35 1 >36 2 >... >... > >The value for positions 1 and 2 are 4 and 5 respectively. The value for >positions 3 - 34 are considered to be 0. > >So, you definitely do not need multiple headings for the same >I >don't know if there is a way to represent multiple chromosomes in a single >wiggle file. >-- >View this message in context: >http://generic-model-organism-system-database.450254.n5.nabble.com/FW-h elp >-with-wiggle-track-display-tp3320404p3320460.html >Sent from the gmod-gbrowse mailing list archive at Nabble.com. > >----------------------------------------------------------------------- --- >---- >Learn how Oracle Real Application Clusters (RAC) One Node allows customers >to consolidate database storage, standardize their database environment, >and, >should the need arise, upgrade to a full multi-node Oracle RAC database >without downtime or disruption >http://p.sf.net/sfu/oracle-sfdevnl >_______________________________________________ >Gmod-gbrowse mailing list >[hidden email] >https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
Hi Jayaraman,
Here is the track configuration [cry20:database] db_adaptor = Bio::DB::BigWig db_args = -bigwig /home/gb/gbrowse2/www/data/cry2-0hr.bw -fasta /home/gb/gbrowse2/www/data/ATH_TAIR9_genome.fa [CRY20hr] feature = summary database = cry20 glyph = wiggle_xyplot bgcolor = red height = 40 fgcolor = black min_score = 0 scale = left category = SRC key = cry2-mutant 0 hr
On 28 December 2010 20:56, Jayaraman, Pushkala <[hidden email]> wrote: Hello Dr. Parnell, ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
Hi Pushkala,
It looks like Vipin posted an appropriate example. That example used the wiggle_xyplot glyph with the summary feature, although I would also suggest trying the wiggle_whiskers glyph, which provides more information. The mean, stdev, min, and max are displayed as a box and whisker plot using color and line thickness. It gives a little more information when viewing large genomic segments. In GBrowse, the glyph type should be configurable by the end-user through the track configuration popup, although I find that to be buggy. Using the wiggle_whiskers glyph would be [input_nuc.100_134.sorted] database = input_nuc.100_134.sorted_db feature = summary glyph = wiggle_whiskers graph_type = boxes fgcolor = black height = 50 scale = left min_score = 0 max_score = 50 Also, the fasta option under the [xxx:database] stanza is optional. I generally don't see a need for it, unlike, say, the bam database. Tim From: Vipin TS <[hidden email]<mailto:[hidden email]>> Date: Tue, 28 Dec 2010 13:08:42 -0700 To: "Jayaraman, Pushkala" <[hidden email]<mailto:[hidden email]>> Cc: "[hidden email]<mailto:[hidden email]>" <[hidden email]<mailto:[hidden email]>> Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display Hi Jayaraman, Here is the track configuration [cry20:database] db_adaptor = Bio::DB::BigWig db_args = -bigwig /home/gb/gbrowse2/www/data/cry2-0hr.bw<http://cry2-0hr.bw> -fasta /home/gb/gbrowse2/www/data/ATH_TAIR9_genome.fa [CRY20hr] feature = summary database = cry20 glyph = wiggle_xyplot bgcolor = red height = 40 fgcolor = black min_score = 0 scale = left category = SRC key = cry2-mutant 0 hr regards, Vipin T S On 28 December 2010 20:56, Jayaraman, Pushkala <[hidden email]<mailto:[hidden email]>> wrote: Hello Dr. Parnell, Could you give us an example of the usage of the Bio::DB::BigWig adaptor..? Currently we use the Bio::DB::Seqfeature::Store adaptor.. its not that flexible.. Thanks, Pushkala Jayaraman Programmer/Analyst Rat Genome Database Human and Molecular Genetics Center Medical College of Wisconsin Email: [hidden email]<mailto:[hidden email]> Work: 414-955-2229 www.rgd.mcw.edu<http://www.rgd.mcw.edu> -----Original Message----- From: Timothy Parnell [mailto:[hidden email]<mailto:[hidden email]>] Sent: Tuesday, December 28, 2010 1:31 PM To: Karthik; [hidden email]<mailto:[hidden email]>; Jayaraman, Pushkala Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display Hi, You'll want to be careful with variableStep wig files. The wiggle glyph modules fail to interpolate values when they're not defined, leading to an artificial smoothing effect (it essentially keeps the previous known value) that you may not desire. I gave a more detailed explanation in a previous post, which you can find archived here http://generic-model-organism-system-database.450254.n5.nabble.com/wiggl e-x yplot-smoothing-tp455999p456003.html The best solution is to either interpolate the data yourself and generate a fixedStep wig file, or switch to Lincoln's Bio::DB::BigWig adaptor. I personally found the BigWig format to be the best solution as it does not have these issues with variableStep wig files (confirmed with lots of personal experience), and that's what Lincoln seemed to advocate. As for the wiggle files themselves, there should only be one track line in the wig file, but you're allowed to have multiple definition lines (variableStep .... or fixedStep ....) lines. You may have multiple chromosomes per file. Tim -- Timothy J Parnell, PhD. Research Associate Howard Hughes Medical Institute Department of Oncology Huntsman Cancer Institute University of Utah Salt Lake City, UT 84112 On 12/28/10 10:14 AM, "Karthik" <[hidden email]<mailto:[hidden email]>> wrote: > >If you use variable step, there is no need for multiple headings for the >same >chromosome, even if you don't have values for many positions. >For example, > >track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" >variableStep chrom=chr18 span=1 >1 4 >2 5 >35 1 >36 2 >... >... > >The value for positions 1 and 2 are 4 and 5 respectively. The value for >positions 3 - 34 are considered to be 0. > >So, you definitely do not need multiple headings for the same >I >don't know if there is a way to represent multiple chromosomes in a single >wiggle file. >-- >View this message in context: >http://generic-model-organism-system-database.450254.n5.nabble.com/FW-h elp >-with-wiggle-track-display-tp3320404p3320460.html >Sent from the gmod-gbrowse mailing list archive at Nabble.com. > >----------------------------------------------------------------------- --- >---- >Learn how Oracle Real Application Clusters (RAC) One Node allows customers >to consolidate database storage, standardize their database environment, >and, >should the need arise, upgrade to a full multi-node Oracle RAC database >without downtime or disruption >http://p.sf.net/sfu/oracle-sfdevnl >_______________________________________________ >Gmod-gbrowse mailing list >[hidden email]<mailto:[hidden email]> >https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email]<mailto:[hidden email]> https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
In reply to this post by pjayaraman
Yes, that's right. The bw file is binary file that is treated as a
separate database and is accessed through either the local file system or remotely through http or ftp. Think of it as a bam file, if that helps. The Bio::DB::BigWig, Bio::DB::Bam, and Bio::DB::SeqFeature::Store all share very similar APIs and behaviors in terms of segments and features. You can generate the bigwig file with utilities found at the UCSC website. Since you'll need to compile the Jim Kent's libraries in order to install Bio::DB::BigWig, you might as well also compile the utilities that come along with it, notably wigToBigWig. Lincoln has provided a wigToBigWig.pl script, but even he admits it's probably better to use Jim's utility (the latter may be deprecated). Also note that, to convert the wig to bigwig, you'll need to delete the track line. For whatever reason, wigToBigWig can't ignore that line. On 12/28/10 1:45 PM, "Jayaraman, Pushkala" <[hidden email]> wrote: >Hello, >I apologize for the multitude of emails about this.. I am not familiar >with the protocol for data generation used by the BigWig Adaptor.. and >hence trying to learn the string of getting this to work.. (or even the >simple wiggle track) >Did you guys use the protocol suggested here: >http://genome.ucsc.edu/goldenPath/help/bigWig.html > >Also, I notice that you guys do not load this into the DB but access it >from the filesystem.. >:) > >Is this the protocol to use? >Thanks, >Pushkala Jayaraman >Programmer/Analyst >Rat Genome Database >Human and Molecular Genetics Center >Medical College of Wisconsin >Email: [hidden email] >Work: 414-955-2229 >www.rgd.mcw.edu > > >-----Original Message----- >From: Timothy Parnell [mailto:[hidden email]] >Sent: Tuesday, December 28, 2010 2:30 PM >To: Vipin TS; Jayaraman, Pushkala >Cc: [hidden email] >Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display > >Hi Pushkala, >It looks like Vipin posted an appropriate example. That example used the >wiggle_xyplot glyph with the summary feature, although I would also >suggest trying the wiggle_whiskers glyph, which provides more >information. The mean, stdev, min, and max are displayed as a box and >whisker plot using color and line thickness. It gives a little more >information when viewing large genomic segments. In GBrowse, the glyph >type should be configurable by the end-user through the track >configuration popup, although I find that to be buggy. > >Using the wiggle_whiskers glyph would be > >[input_nuc.100_134.sorted] >database = input_nuc.100_134.sorted_db >feature = summary >glyph = wiggle_whiskers >graph_type = boxes >fgcolor = black >height = 50 >scale = left >min_score = 0 >max_score = 50 > >Also, the fasta option under the [xxx:database] stanza is optional. I >generally don't see a need for it, unlike, say, the bam database. > >Tim > > >From: Vipin TS <[hidden email]<mailto:[hidden email]>> >Date: Tue, 28 Dec 2010 13:08:42 -0700 >To: "Jayaraman, Pushkala" ><[hidden email]<mailto:[hidden email]>> >Cc: >"[hidden email]<mailto:[hidden email] >e.net>" ><[hidden email]<mailto:[hidden email] >e.net>> >Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display > >Hi Jayaraman, > >Here is the track configuration > > >[cry20:database] > >db_adaptor = Bio::DB::BigWig > >db_args = -bigwig >/home/gb/gbrowse2/www/data/cry2-0hr.bw<http://cry2-0hr.bw> > > -fasta /home/gb/gbrowse2/www/data/ATH_TAIR9_genome.fa > > > >[CRY20hr] > >feature = summary > >database = cry20 > >glyph = wiggle_xyplot > >bgcolor = red > >height = 40 > >fgcolor = black > >min_score = 0 > >scale = left > >category = SRC > >key = cry2-mutant 0 hr > > > >regards, Vipin T S > >On 28 December 2010 20:56, Jayaraman, Pushkala ><[hidden email]<mailto:[hidden email]>> wrote: >Hello Dr. Parnell, >Could you give us an example of the usage of the Bio::DB::BigWig >adaptor..? >Currently we use the Bio::DB::Seqfeature::Store adaptor.. its not that >flexible.. > >Thanks, >Pushkala Jayaraman >Programmer/Analyst >Rat Genome Database >Human and Molecular Genetics Center >Medical College of Wisconsin >Email: [hidden email]<mailto:[hidden email]> >Work: 414-955-2229 >www.rgd.mcw.edu<http://www.rgd.mcw.edu> > > >-----Original Message----- >From: Timothy Parnell >[mailto:[hidden email]<mailto:[hidden email] >>] >Sent: Tuesday, December 28, 2010 1:31 PM >To: Karthik; >[hidden email]<mailto:[hidden email] >.net>; Jayaraman, Pushkala >Subject: Re: [Gmod-gbrowse] FW: help with wiggle track display > >Hi, > >You'll want to be careful with variableStep wig files. The wiggle glyph >modules fail to interpolate values when they're not defined, leading to >an >artificial smoothing effect (it essentially keeps the previous known >value) that you may not desire. I gave a more detailed explanation in a >previous post, which you can find archived here > >http://generic-model-organism-system-database.450254.n5.nabble.com/wiggl >e-x >yplot-smoothing-tp455999p456003.html > > >The best solution is to either interpolate the data yourself and >generate >a fixedStep wig file, or switch to Lincoln's Bio::DB::BigWig adaptor. I >personally found the BigWig format to be the best solution as it does >not >have these issues with variableStep wig files (confirmed with lots of >personal experience), and that's what Lincoln seemed to advocate. > >As for the wiggle files themselves, there should only be one track line >in >the wig file, but you're allowed to have multiple definition lines >(variableStep .... or fixedStep ....) lines. You may have multiple >chromosomes per file. > >Tim > >-- > >Timothy J Parnell, PhD. >Research Associate >Howard Hughes Medical Institute >Department of Oncology >Huntsman Cancer Institute >University of Utah >Salt Lake City, UT 84112 > > > >On 12/28/10 10:14 AM, "Karthik" ><[hidden email]<mailto:[hidden email]>> wrote: > >> >>If you use variable step, there is no need for multiple headings for >the >>same >>chromosome, even if you don't have values for many positions. >>For example, >> >>track type=wiggle_0 name="XXX-chr18" description="XXX for chr18" >>variableStep chrom=chr18 span=1 >>1 4 >>2 5 >>35 1 >>36 2 >>... >>... >> >>The value for positions 1 and 2 are 4 and 5 respectively. The value for >>positions 3 - 34 are considered to be 0. >> >>So, you definitely do not need multiple headings for the same >chromosome. >>I >>don't know if there is a way to represent multiple chromosomes in a >single >>wiggle file. >>-- >>View this message in context: >>http://generic-model-organism-system-database.450254.n5.nabble.com/FW-h >elp >>-with-wiggle-track-display-tp3320404p3320460.html >>Sent from the gmod-gbrowse mailing list archive at Nabble.com. >> >>----------------------------------------------------------------------- >--- >>---- >>Learn how Oracle Real Application Clusters (RAC) One Node allows >customers >>to consolidate database storage, standardize their database >environment, >>and, >>should the need arise, upgrade to a full multi-node Oracle RAC database >>without downtime or disruption >>http://p.sf.net/sfu/oracle-sfdevnl >>_______________________________________________ >>Gmod-gbrowse mailing list >>[hidden email]<mailto:[hidden email] >e.net> >>https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse > > >------------------------------------------------------------------------ >------ >Learn how Oracle Real Application Clusters (RAC) One Node allows >customers >to consolidate database storage, standardize their database environment, >and, >should the need arise, upgrade to a full multi-node Oracle RAC database >without downtime or disruption >http://p.sf.net/sfu/oracle-sfdevnl >_______________________________________________ >Gmod-gbrowse mailing list >[hidden email]<mailto:[hidden email] >.net> >https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse > ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
|
Hello Timothy
The behavior you mentioned for variable step would be a serious problem for us, but I don't see that in my GBrowse. For positions with no value, I just don't get a point in my graph. Was this bug fixed in the latest Bio::Graphics ? Or can you recommend a way for me to spot the bug ? Thanks Karthik |
|
Hi Karthik,
I just checked again on my test machine; I had Bio::Graphics 2.15 and GBrowse 2.16 installed. I then upgraded to Bio::Graphics 2.18 and GBrowse 2.17 through CPAN. The behavior exists with both old and new versions. The behavior I am seeing is the skipping of values when using a wig file as source data, compared to data stored in either Bio:DB:SeqFeature:Store or Bio:DB:BigWig databases. To test this, I load the identical data in all three data formats (gff3, wig, and bw). The wig file is converted to a .wib file using wiggle2gff3.pl and the resulting GFF3 loaded into a B:DB:SF:Store database. The data is microarray data, with data points at varying positions along the chromosome, with a span of 1 bp (start = stop). The relevant track stanza info is below. [ma_db_rsc_chip] database = cerevisiae_test feature = RSC_ChIP_ypd_244k group_on = display_name glyph = xyplot graph_type = histogram key = DB MA RSC ypd data [ma_wig_rsc_chip] database = cerevisiae_test feature = RSC_ChIP_ypd_wig glyph = wiggle_xyplot graph_type = histogram key = Wig MA RSC ypd data [RSC_ChIP_ypd_244k_bigwig:database] db_adaptor = Bio::DB::BigWig db_args = -bigwig /Users/Shared/bigwig_data/RSC_ChIP_ypd_244k.bw [RSC_ChIP_ypd_bigwig] database = RSC_ChIP_ypd_244k_bigwig feature = summary glyph = wiggle_xyplot graph_type = histogram key = bigwig MA RSC ypd data I've attached two screenshots of the behavior, one using histogram and the other using points as the graph_type. It's harder to see with a line graph, but easiest to see with the points graph. With the wig source, there are points being dropped. Under the histogram and line graphs, this has the effect of simply extending the previous value. This can be easy to miss, depending on the data density, the noisiness of the data, and the size of the window. I've done some limited spelunking into the code and played with the respective modules outside of GBrowse in my own data collection scripts. It looks like Bio::Graphics::Wiggle returns an array of score values with the array length equal to the window size, for example 5 kb window would return an array of 5000 elements. Working with variableStep data, most of these values are undef. When the glyph is rendered for a 1000 pixel wide image, it has to grab every fifth value to plot the data across that 5 kb window. Hence, it grabs a lot of undef values, along with a few defined ones. That, at least, is my simplistic interpretation of what is going on. The B:D:SF:Store and B:DB:BW modules work in a fundamentally different manner, so this behavior isn't seen. They essentially only return the defined values. If you, or someone else, could confirm this behavior, that would be great, as it would mean I'm not imagining things. I haven't gone deep enough into the code to contribute a fix, though. Tim On 12/30/10 10:37 AM, "Karthik" <[hidden email]> wrote: > >Hello Timothy >The behavior you mentioned for variable step would be a serious problem >for >us, but I don't see that in my GBrowse. For positions with no value, I >just >don't get a point in my graph. >Was this bug fixed in the latest Bio::Graphics ? Or can you recommend a >way >for me to spot the bug ? > >Thanks >Karthik >-- >View this message in context: >http://generic-model-organism-system-database.450254.n5.nabble.com/FW-help >-with-wiggle-track-display-tp3320404p3322703.html >Sent from the gmod-gbrowse mailing list archive at Nabble.com. > >-------------------------------------------------------------------------- >---- >Learn how Oracle Real Application Clusters (RAC) One Node allows customers >to consolidate database storage, standardize their database environment, >and, >should the need arise, upgrade to a full multi-node Oracle RAC database >without downtime or disruption >http://p.sf.net/sfu/oracle-sfdevnl >_______________________________________________ >Gmod-gbrowse mailing list >[hidden email] >https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gmod-gbrowse mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gmod-gbrowse |
| Powered by Nabble | Edit this page |
