nlmixr2/rxode2 user functions to modify code

This month I will talk about a new type of user function. Previously, I spoke of user functions that you can use in your code to extend the functionality of rxode2 and nlmixr2. Recently we released the ability for certain functions to generate code. I will go over examples that could be helpful to extend rxode2 ui models: An example that allows arguments to be named inside of the rxode2 ui models (though classic models still do not allow this).

nlmixr2/rxode2 mu referencing 3.0/4.0

This month, I will talk about about a new iteration of mu-referencing in nlmixr2, which I call mu3 and mu4. What is mu referencing in nlmixr2 – Review from another post From the last blog post about mu-referencing, I will give a brief overview of mu-referencing and what mu-2 referencing is and how it is expanded a bit more. mu-referencing is combining a fixed effect, random effect and possibly a covariate in the form:

babelmixr2 and PopED

New babelmixr2 integrates PopED. I am excited to announce today a new version of babelmixr2 has been released that streamlines creating fast, efficient PopED databases for optimal design. With the babelmixr2 package you can: Import your NONMEM model to rxode2/nlmixr2 format using nonmem2rx Import your Monolix model to rxode2/nlmixr2 using monolix2rx Use your existing nlmixr2 model or create your own rxode2/nlmixr2 model With it in the nlmixr2 format, you can then quickly do optimal design

monolix2rx

monolix2rx has been released on CRAN. I am excited to announce that as part of the nlmixr2 3.0 series of releases, you now have a way to import a Monolix model into rxode2/nlmixr2. This is similar to how you can import the output of nonmem into a rxode2 model with nonmem2rx. I am also in the process of releasing a bug-fix revision now. Key notes in importing models to rxode2 and nlmixr2 There are a few things to note in any conversion from monolix to rxode2 and nlmixr2:

nlmixr2 3.0

nlmixr2 3.0 is here nlmixr2 3.0 has been released and most of the related packages in the nlmixr2 ecosystem have been updated as well. Since there were a few non-backward compatible changes and breaking changes, the version has been bumped from 2 to 3. Most code will run the same, but because of the breaking change, we changed the major version. The big changes are: Non abi binary linkages between every package.