One of the things that I changed in the last release was steady state. Once I created the nonmem2rx package, I searched for NONMEM control streams that we could test the import from, especially those with attached data. I ran across nmtests that uses NONMEM to test against mrgsolve and how it behaves. During that test I noticed that rxode2 did not follow the convention of NONMEM in lagged steady state doses.
nlmixr2 2.1.0 was released 9 Jan 2024 which requires the newest (and recently released) engine packages nlmixr2est 2.2.0 (released 12 Dec 2023) and rxode2 2.0.10 (released 13 Dec 2023). I will be blogging about a few new features but want to mention a few now: More flexible mu referencing User defined functions can now be used with nlmixr2 and rxode2 Event handling changes Many new estimation methods for population only fitting The truncated changelog for these packages are below:
rxode2 2.0.9 has been released, and rxode2 2.0.10 will be released soon! I want to personally thank all those who have submitted issues, and helped with the development. Without the support rxode2 wouldn’t be the tool it is today. This is the first CRAN-visible release since rxode2 2.0.7 and I would like to highlight a few new interesting features: ‘rxode2’ can now have more flexible model functions The key features are:
mrgsolve vs rxode2 One of the most common questions I get is, “What are the differences between mrgsolve (1) and rxode2?”. The most common reasons for this question are: I really don’t know what tool to use, what are the advantages of each? I really like one of the tools (either mrgsolve or rxode2) and I want to let my colleagues know how nice my favorite tool is. I am not really the best person to answer this question since I am most familiar with rxode2 and can’t answer all the questions about mrgsolve.
RxODE vs rxode2 Since rxode2 came out recently, I am getting many questions about what is the difference between rxode2 and RxODE. I think the biggest reason for the question is – is this update going to break all the nice things I already do with RxODE? Or maybe why should I bother to change? I feel the same way when I have big changes in things I use. For me, I love the ability to pipe and change data with the tidyverse, and similar tools, but hate when they change things that affect my code.