Bhagwat,
> Aditya [aditya.bhag...@mpi-bn.mpg.de]
> Sent: Wednesday, September 18, 2019 1:57 PM
> To: Michael Lawrence
> Cc: bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] read_bed()
>
> Hi Michael,
>
> That's a software design dilemma I've encountered a few times.
>
] on behalf of Bhagwat,
Aditya [aditya.bhag...@mpi-bn.mpg.de]
Sent: Wednesday, September 18, 2019 1:57 PM
To: Michael Lawrence
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
Hi Michael,
That's a software design dilemma I've encountered a few times.
One approach is to keep
-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
I'm not sure if a function called read_bed() should be plotting or
printing. Is your BED file a known BED variant, i.e., maybe there is a
better name for the file type than "bed"?
On Wed, Sep 18, 2019 at 3:17 AM Bhagwat, Adit
-bn.mpg.de]
> Sent: Wednesday, September 18, 2019 11:31 AM
> To: Michael Lawrence
> Cc: bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] read_bed()
>
> (Typo corrected to avoid confusion)
>
> Michael,
>
> rtracklayer::import.bed() indeed works perfectly for me, so I a
-bn.mpg.de]
Sent: Wednesday, September 18, 2019 11:31 AM
To: Michael Lawrence
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
(Typo corrected to avoid confusion)
Michael,
rtracklayer::import.bed() indeed works perfectly for me, so I am dropping
multicrispr::read_bed().
In order
tember 18, 2019 8:35 AM
To: Michael Lawrence
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
Thank you Michael :-)
Aditya
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 8:49 PM
To: Bhagwat, Aditya
Cc: M
nce
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
Thank you Michael :-)
Aditya
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 8:49 PM
To: Bhagwat, Aditya
Cc: Michael Lawrence; bioc-devel@r-project.org
S
Thank you Michael :-)
Aditya
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 8:49 PM
To: Bhagwat, Aditya
Cc: Michael Lawrence; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
I think you probably made
data.table::fread is
> doing the job, so I will stick to that .
>
> Thank you for all feedback,
>
> Cheers,
>
> Aditya
>
>
> ________
> From: Bioc-devel [bioc-devel-boun...@r-project.org] on behalf of Bhagwat,
> Aditya [aditya.bha
Aditya [aditya.bhag...@mpi-bn.mpg.de]
Sent: Tuesday, September 17, 2019 2:48 PM
To: Michael Lawrence
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
Oh :-) - Thankyou for explaining!
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: T
Oh :-) - Thankyou for explaining!
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 2:40 PM
To: Bhagwat, Aditya
Cc: Michael Lawrence; Shepherd, Lori; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
Having
nd whether to mix the two).
>
> Aditya
>
>
> From: Michael Lawrence [lawrence.mich...@gene.com]
> Sent: Tuesday, September 17, 2019 2:23 PM
> To: Bhagwat, Aditya
> Cc: Michael Lawrence; Shepherd, Lori; bioc-devel@r-project.org
> Subject: Re: [Bioc
: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 2:23 PM
To: Bhagwat, Aditya
Cc: Michael Lawrence; Shepherd, Lori; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
The generic documentation does not mention it, but see ?import.bed.
It's similar to colClasses
e.com]
> Sent: Tuesday, September 17, 2019 2:05 PM
> To: Bhagwat, Aditya
> Cc: Michael Lawrence; Shepherd, Lori; bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] read_bed()
>
> It breaks it because it's not standard BED; however, using the
> extraCols= argument should work i
From: Michael Lawrence [lawrence.mich...@gene.com]
Sent: Tuesday, September 17, 2019 2:05 PM
To: Bhagwat, Aditya
Cc: Michael Lawrence; Shepherd, Lori; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
It breaks it because it's not standard BED; however
, Aditya
> Cc: Shepherd, Lori; bioc-devel@r-project.org
> Subject: Re: [Bioc-devel] read_bed()
>
> I don't see an attachment, nor can I find the multicrispr package
> anywhere. The "addressed soon" was referring to the BEDX+Y formats,
> which was addressed many year
...@gene.com]
Sent: Tuesday, September 17, 2019 1:41 PM
To: Bhagwat, Aditya
Cc: Shepherd, Lori; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] read_bed()
I don't see an attachment, nor can I find the multicrispr package
anywhere. The "addressed soon" was referring to the BEDX+Y form
>
> Buffalo, New York 14263
>
> ____
> From: Bioc-devel on behalf of Bhagwat,
> Aditya
> Sent: Tuesday, September 17, 2019 6:58 AM
> To: bioc-devel@r-project.org
> Subject: [Bioc-devel] read_bed()
>
> Dear bioc-devel,
>
> I had tw
s & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel on behalf of Bhagwat,
Aditya
Sent: Tuesday, September 17, 2019 6:58 AM
To: bioc-devel@r-project.org
Subject: [Bioc-devel] read_bed()
Dear bioc-devel,
I had two f
Aditya
Sent: Tuesday, September 17, 2019 6:58 AM
To: bioc-devel@r-project.org
Subject: [Bioc-devel] read_bed()
Dear bioc-devel,
I had two feedback requests regarding the function read_bed().
1) Did I overlook, and therefore, re-invent existing functionality?
2) If not, would `read_bed` b
rk 14263
From: Bioc-devel on behalf of Bhagwat,
Aditya
Sent: Tuesday, September 17, 2019 6:58 AM
To: bioc-devel@r-project.org
Subject: [Bioc-devel] read_bed()
Dear bioc-devel,
I had two feedback requests regarding the function read_bed().
1) Did I
Dear bioc-devel,
I had two feedback requests regarding the function read_bed().
1) Did I overlook, and therefore, re-invent existing functionality?
2) If not, would `read_bed` be suited for existence in a more foundational
package, e.g. `GenomicRanges`, given the rather basal nature of this
22 matches
Mail list logo
