Re: [Bioc-devel] Bioc-devel Digest, Vol 145, Issue 60

2016-04-20 Thread Aedin Culhane
Hi Vince Agreed, I agree fData is over-simplification. But if data have an associated "annotation", the feature annotation associated with it should be available. I was recently trying to map between one of the hugene st1.0 and primeview arrays. The first has multiple .db packages (including

Re: [Bioc-devel] Bioc-devel Digest, Vol 145, Issue 60

2016-04-20 Thread Vincent Carey
I am in favor of simplifying the binding of useful metadata to our genome-wide objects. Before we automate this I think we should define a widely applicable procedure for this task ... and see how it works in examples from the ExperimentData library and ExperimentHub. Using fData for ExpressionSe

Re: [Bioc-devel] Bioc-devel Digest, Vol 145, Issue 60

2016-04-20 Thread Aedin Culhane
Hi Using select/mapIDs to annotate probe IDs is an additional step that confuses many. May I suggest we automatically populate fData with minimal annotation (ProbeID, entrez ID, symbol) if a known platform is detected. We record the version and parameters (eg mapIDs multi=first) used to cre

Re: [Bioc-devel] System Requirements for imported packages

2016-04-20 Thread Kasper Daniel Hansen
What Martin is hinting at, is that if you end up depending on a package which is really hard to install, your users indirectly will suffer. And that should be a consideration when you choose to depend on another package. I have certainly had situations where I have tried to avoid depending on pac

Re: [Bioc-devel] System Requirements for imported packages

2016-04-20 Thread Martin Morgan
On 04/20/2016 12:14 PM, Zach Skidmore wrote: Hi All, I'm curious what the preferred method is for dealing with System Requirements originating from an imported package. For example, if I had a package that imported `biomaRt` which itself imports `XML` which has the SystemRequirement `libxml2`

[Bioc-devel] System Requirements for imported packages

2016-04-20 Thread Zach Skidmore
Hi All, I'm curious what the preferred method is for dealing with System Requirements originating from an imported package. For example, if I had a package that imported `biomaRt` which itself imports `XML` which has the SystemRequirement `libxml2` how is that dealt with? Are package installe

Re: [Bioc-devel] Vignettes and package size

2016-04-20 Thread Kasper Daniel Hansen
Also, if your issue is the size (and not runtime) of the vignette files, chances are that this could be fixed. Whatever you produce manually as pdf, you should be able to get using the build system. Do you have code somewhere (Github? elsewhere?). Kasper On Wed, Apr 20, 2016 at 9:19 AM, Martin

Re: [Bioc-devel] Vignettes and package size

2016-04-20 Thread Martin Morgan
On 04/20/2016 01:22 AM, Samuel Wieczorek wrote: Hi I am the developper of the packages DAPAR and Prostar. Each of these packages contains two vignettes : a user manual and an tutorial. As these documents contain screen shots, I have to join the images (png files) in the packages in addition of