I'm working on nlmixr2targets, and I find that in some scenarios, I consistently get different model digest values (digest::digest(rxuiObject) differs between R sessions for rxUi objects that are created the same way). I think that this relates to creating digests of the environments or temporary files.
That said, the rxuiObject$md5 value remains consistent between R sessions.
Would it be reasonable to create a digest.rxUi method that would return the object$md5 value or can you think of a reason that should not be done?
And related to that, would it make sense to create a digest.nlmixr2FitCore method that would do the same thing?
Would there be any other object types that should have a digest method created?
Should this live in the specific packages (rxode2::digest.rxUi, nlmixr2est::digest.nlmixr2FitCore) or within nlmixr2targets?
billdenney
commented
3 months ago
I'm working on
nlmixr2targets, and I find that in some scenarios, I consistently get different model digest values (digest::digest(rxuiObject)differs between R sessions for rxUi objects that are created the same way). I think that this relates to creatingdigests of the environments or temporary files.That said, the
rxuiObject$md5value remains consistent between R sessions.digest.rxUimethod that would return theobject$md5value or can you think of a reason that should not be done?digest.nlmixr2FitCoremethod that would do the same thing?digestmethod created?rxode2::digest.rxUi,nlmixr2est::digest.nlmixr2FitCore) or withinnlmixr2targets?