Closed lkhilton closed 1 year ago
I think the designated data package is not working as efficiently as expected and this is another hidden issue that comes up and maybe to solve this the best approach is to roll back what we had before GAMBLR.data.
Is it just because the auto-loaded objects have a different name?
No this particular issues is because they are not having the @export and need to refer by GAMBLR.data:::
but I think the bigger problem with that package is that it is not giving us the outcome we were hoping for (dynamically using a particular version of the dataset) and in addition to that creates lots of hidden issues like this that need changes to the existing code base
We fixed this, didn't we, Kostia?
Yes, everyone just need to update their GAMBLR.data installation and load the package
Adam can you please confirm the fix works for you too if you update the package and call library(GAMBLR.data)
? We can close this issue then if the fix works for you.
With the migration of a bunch of data to
GAMBLR.data
, functions that call{genome_build}_ashm_regions
are now referencing a nonexistent object. Is the best solution to give the aSHM data inGAMBLR.data
an additional alias for backwards compatibility?