You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if saved model objects would remain valid when updating to new versions of TMB - see e.g. glmmTMB/glmmTMB#651 .
Solution idea:
Currently, a TMB model object contains functions (e.g. fn and gr) that explicitly .Call underlying cpp code. This design is highly sensitive to changes in the cpp API. The TMB R code might benefit from re-factoring all the .Call into separate R functions with a fixed R API.
The text was updated successfully, but these errors were encountered:
- Partly fixing #339: In theory objects generated and saved after this change should be more robust to C++ API changes (e.g. renaming a DLL registered routine shouldn't break the model object.)
- The change also makes it easier to use individual ADFun objects independent of the MakeADFun output.
Description:
It would be nice if saved model objects would remain valid when updating to new versions of TMB - see e.g. glmmTMB/glmmTMB#651 .
Solution idea:
Currently, a TMB model object contains functions (e.g.
fn
andgr
) that explicitly.Call
underlying cpp code. This design is highly sensitive to changes in the cpp API. The TMB R code might benefit from re-factoring all the.Call
into separate R functions with a fixed R API.The text was updated successfully, but these errors were encountered: