this is coming out of the build system for GGtools ... not easy to find as
the
problem seems to cause emission of megabytes of warnings
illuminaHumanv1CHR is deprecated as the data is better accessed from
another location. Please use an appropriate TxDb object or package for
this kind of d
On 09/21/2014 07:44 AM, Vincent Carey wrote:
this is coming out of the build system for GGtools ... not easy to find as
the
problem seems to cause emission of megabytes of warnings
illuminaHumanv1CHR is deprecated as the data is better accessed from
another location. Please use an appropri
On Sun, Sep 21, 2014 at 11:07 AM, Martin Morgan wrote:
> On 09/21/2014 07:44 AM, Vincent Carey wrote:
>
>> this is coming out of the build system for GGtools ... not easy to find as
>> the
>>
>> problem seems to cause emission of megabytes of warnings
>>
>>
>> illuminaHumanv1CHR is deprecated as
Hi Vince,
So if you wanted to do this manually, then the thing you would want to
do is to get a gene ID from the probe and to take that to a TranscriptDb
object (again: that is if you wanted to do it manually). Alternatively,
if you had an OrganismDb object then this association would be hand
Thanks for the clarification. Isn't there a way via active bindings to
preserve the
interfaces conferred by e.g., illuminaHumanv1CHRLOC, so that queries to the
object (no longer a Bimap) succeed with the endorsed metadata? the chipDb
packages would be revised to use a new protocol for these queri
Hi Vince,
You raise an important point that a common use of the chipDb objects
will become overly complicated with this change. Especially since chip
platforms should really have an implicit genome that they were designed
for from the get go. And since annotations packages are being build
rig
