Thanks Vince, understood about the Core's focus right now.
I think this is something that Leo and I can fix among ourselves for the
time being.
Looking forward, as you brought up, if we were to refresh recount or
produce a recount4 (discussed) we'd certainly consider additional coverage
formats.
drew E.
Subject: Re: [Bioc-devel] Remote BigWig file access
thanks
On Thu, May 23, 2024 at 5:36 PM Chris Wilks (gmail)
wrote:
> Thanks Vince, understood about the Core's focus right now.
>
> I think this is something that Leo and I can fix among ourselves for the
> time being.
>
thanks
On Thu, May 23, 2024 at 5:36 PM Chris Wilks (gmail)
wrote:
> Thanks Vince, understood about the Core's focus right now.
>
> I think this is something that Leo and I can fix among ourselves for the
> time being.
>
> Looking forward, as you brought up, if we were to refresh recount or
> pr
Really glad to see this discussion moving forward. I would say that the
core is wrangling with some
even lower-level technical concerns right now, so I can't jump in just
now. I just want to raise the question
of whether bigWig files are a technologically sound format to continue
investing in for
Thanks for sharing Leo, this does interest me, especially since so much is
built on BigWig access via rtracklayer at least in the recount2 ecosystem.
As you alluded to, Megadepth currently supports remote access of BigWigs
(and BAMs) over HTTPS on all platforms (Linux, MacOS, and Windows),
getting
