Closed spocks closed 1 year ago
You just need to run:
pSet <- updateObject(pSet)
And that will fix it.
Great, this solved the problem. How about implementing updateObject
internally before checking the slots? Do you think it will be too complected? Otherwise I would suggest to include a message " try running pSet <- updateObject(pSet)
" with the error message.
I am already updating the object automatically inside downloadPSet
. I can catch the error in the show
method and include the message though. I think that would be helpful.
Pull request with new message is open at #157
I also noticed that in PharmacoGx
I am only updating the object returned from the function. I have a fix that also resaves the object so any newly downloaded PSets shouldn't need to be updated.
Will open a PR for that once the CoreGx one is merged.
See bhklab/PharmacoGx#123 for PR fixing downloadPSet
Both of these fixes have been pushed to Bioconductor.
Look for CoreGx version 2.1.5 and PharmacoGx version 3.1.4 on Bioconductor (probably in the Friday build).
Best, Christopher Eeles Software Developer Haibe-Kains Lab | PM-Research University Health Network
Hi Team,
PharmacoGx
is giving error related to slot name and is breaking all the old code/pSet.Here is the session_info: