-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JBrowse2 tracks deconvolution #129
Comments
Since VEuPathDb is accessible now, can we do this via some kind of crawling @scottcain ? |
Contingent on our ability to query the db |
Can't this be done via the jbrowser API endpoint, the one that jbrowse
uses? Veupathdb staff told us how to do this...
…On Thu, Oct 10, 2024 at 6:14 PM Anton Nekrutenko ***@***.***> wrote:
Contingent on our ability to query the db
—
Reply to this email directly, view it on GitHub
<#129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACL4TP2SNIMJXYHEJGCHSTZ22RWDAVCNFSM6AAAAABPXATNM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVGUZTKMJQGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
We just discussed this with @scottcain |
Was the conclusion that it's possible using the API? (sorry I had a meeting at exactly the same time and duration as the BRC meeting today) |
@maximilianh it depends on what we want to do. Since these tracks' data are now static from VEuPathDB (that is, they aren't being actively curated, which would be a reason you might want to run the tracks from a database query), using the database to serve up JBrowse data is (in my opinion) a little obnoxious, when the alternative is something like tabix indexed GFF, BigBed or BigWig (along with associated metadata in all cases). Shifting to static files sitting in a bucket or web server somewhere would make implementing JBrowse 2 a lot easier (and presumably other genome browsers 😉), and is better for the community, since it makes getting a whole dataset for a given track a lot easier. The next question is, could we write a spider that crawled all of the JBrowse instances at VEuPathDB and extracts all of the data? Well, yes, I suppose we could, but it would be kind of an unfriendly thing to do. Rather, I think a reasonable approach is wait for a new hire in Sergei's group who knows this database pretty well and can (presumably) help us extract the track data and metadata from our instance of the database. |
Yes, I meant a spider. I don't know how unfriendly that would be, depends
on how fast the transfer is... but OK, if someone starts with Sergei, then
I guess there is an easier way. And yes, I convert everything to bigBed.
…On Thu, Oct 10, 2024 at 9:32 PM Scott Cain ***@***.***> wrote:
@maximilianh <https://github.com/maximilianh> it depends on what we want
to do. Since these tracks' data are now static from VEuPathDB (that is,
they aren't being actively curated, which would be a reason you might want
to run the tracks from a database query), using the database to serve up
JBrowse data is (in my opinion) a little obnoxious, when the alternative is
something like tabix indexed GFF, BigBed or BigWig (along with associated
metadata in all cases). Shifting to static files sitting in a bucket or web
server somewhere would make implementing JBrowse 2 a lot easier (and
presumably other genome browsers 😉), and is better for the community,
since it makes getting a whole dataset for a given track a lot easier.
The next question is, could we write a spider that crawled all of the
JBrowse instances at VEuPathDB and extracts all of the data? Well, yes, I
suppose we could, but it would be kind of an unfriendly thing to do.
Rather, I think a reasonable approach is wait for a new hire in Sergei's
group who knows this database pretty well and can (presumably) help us
extract the track data and metadata from our instance of the database.
—
Reply to this email directly, view it on GitHub
<#129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACL4TNJL7UK6ECFBJWBVH3Z23I47AVCNFSM6AAAAABPXATNM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVHA4DKOBTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for the quick reply!
On Thu, Oct 10, 2024 at 10:30 PM Maximilian Haeussler ***@***.***>
wrote:
… Yes, I meant a spider. I don't know how unfriendly that would be, depends
on how fast the transfer is... but OK, if someone starts with Sergei, then
I guess there is an easier way. And yes, I convert everything to bigBed.
On Thu, Oct 10, 2024 at 9:32 PM Scott Cain ***@***.***>
wrote:
> @maximilianh <https://github.com/maximilianh> it depends on what we want
> to do. Since these tracks' data are now static from VEuPathDB (that is,
> they aren't being actively curated, which would be a reason you might want
> to run the tracks from a database query), using the database to serve up
> JBrowse data is (in my opinion) a little obnoxious, when the alternative is
> something like tabix indexed GFF, BigBed or BigWig (along with associated
> metadata in all cases). Shifting to static files sitting in a bucket or web
> server somewhere would make implementing JBrowse 2 a lot easier (and
> presumably other genome browsers 😉), and is better for the community,
> since it makes getting a whole dataset for a given track a lot easier.
>
> The next question is, could we write a spider that crawled all of the
> JBrowse instances at VEuPathDB and extracts all of the data? Well, yes, I
> suppose we could, but it would be kind of an unfriendly thing to do.
> Rather, I think a reasonable approach is wait for a new hire in Sergei's
> group who knows this database pretty well and can (presumably) help us
> extract the track data and metadata from our instance of the database.
>
> —
> Reply to this email directly, view it on GitHub
> <#129 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AACL4TNJL7UK6ECFBJWBVH3Z23I47AVCNFSM6AAAAABPXATNM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVHA4DKOBTGU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
so that was fun lol.. first thoughts as i read this:
|
@d-callan these are solid questions. Here are my thoughts:
Perhaps, but I still think it would (likely) be cleaner to extract, format and config data coming directly from the database. And of course, such a spider doesn't actually exist except in my head.
Also fair--I can understand that as a design decision; on the other hand, I very much like having JBrowse backed by flatfiles, since it makes it easy for users who want to get a genome's worth of a particular data set much easier.
My philosophy can generally be stated as "if the data exists, let's get it in JBrowse" This can lead to a discoverability issue for assemblies with lots of data, but that's not a terrible problem to have, and tools are being developed to address it.
It is unclear to me if there is any real use for any of the other data in the database--when we got it, we were thinking VEuPathDB was going away for good. With it still existing, we can make better use of the website than trying to build something ourselves (in my opinion, that is).
I am reasonably sure that we got a bunch of binary files like bigwigs and bams, but I don't know that for sure (but I hope we did!) @jdavcs might know more |
Although, it just occurred to me that, since the JBrowse instance at VEuPathDB continues to exist, we could potentially proxy (to get around CORS issues) the paths where the data extraction tools are and just use their data directly. I will try experimenting with that today. |
@scottcain @d-callan We have roughly 11TB of flat files representing 13 DBs. I don't know what exactly we have, but here's a tiny sample:
|
More thoughts for @d-callan : what would be really cool would be a tool that, given the assembly we want it for, would extract the information needed from the database for what tracks are available and construct a config. There are a few details hidden in that one sentence, like
|
so if were serious about this.. id say that tool already exists. its at/ sort of is veupath. which means for us that tool is a spider.. no? ex: https://plasmodb.org/plasmo/service/jbrowse/tracks/pvivP01/trackList.json and follow it round. |
I cannot imagine that downloading the annotation would ever be a big
problem. The genome, all the annotations, are tiny, for a normal server.
We're talking a few kb per track at most. I wouldn't download with 100
parallel threads, just one thread is enough. And yes, jbrowse itself also
grabs an entire genome's worth of annotations when you zoom out.
…On Wed, Nov 20, 2024 at 7:50 AM Danielle Callan ***@***.***> wrote:
so if were serious about this.. id say that tool already exists. its at/
sort of is veupath. which means for us that tool is a spider.. no?
ex:
https://plasmodb.org/plasmo/service/jbrowse/tracks/pvivP01/trackList.json
and follow it round.
—
Reply to this email directly, view it on GitHub
<#129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACL4TJQ65FKBTW4XUQ2Z6L2BSVVBAVCNFSM6AAAAABPXATNM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBYHE2DOMZTGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
so some questions relating to this:
|
1. well, if we have no other meta data, what can we do?
2. the data will be shown on the UCSC browser, and to export to galaxy, the
ucsc data download button has a "send to Galaxy" option.
…On Mon, Dec 9, 2024 at 5:01 PM Danielle Callan ***@***.***> wrote:
so some questions relating to this:
1. How can we provide context for all these data? the dataset and
sample display names from veupath are unlikely to be inherently meaningful
to users.
2. For the experimental data, do we think ppl would want to play w it
in galaxy? say do something like find differentially expressed genes in an
rnaseq experiment, say? and if so, how can we facilitate that?
—
Reply to this email directly, view it on GitHub
<#129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACL4TMBXKDHEO3XGYHLBGL2EW5EVAVCNFSM6AAAAABPXATNM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRYGQ4TSNBTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
The text was updated successfully, but these errors were encountered: