Thanks Marc, this is good to know. We need to have the hg38 objects ready
for general use -- there
is nothing custom about using the same build as NHGRI. I wouldn't say
there's a huge rush but
there is a need for both a solution and a policy that addresses the
management of an environment
where a
Hi Vince,
The current Homo.sapiens package/object contains a reference to an hg19
TranscriptDb object (which makes it specific to hg19). But you can
easily make a custom Homo.sapiens object of your own that points to a
custom TranscriptDb object. Making a custom OrganismDbi object is easy
t
I confirmed that the rtracklayer liftOver will work with the appropriate
chain. the
remap utility seems to have some more configurability. might be worth a
look.
What I need to do promptly is put the proper seqinfo on result of
makeCurrentGwascat
so that folks are not led astray. We also need g
I just noticed that the addresses for NHGRI GWAS catalog distribution
are relative to GRCh38. Is there a plan for using Homo.sapiens with
selection of build? It may not be uncommon for someone to want to
work with different builds.
What would be useful for me at this time is a simple way to get
