Closed mattfidler closed 3 months ago
Why would that not be an error? It seems like an unintentional issue with a dataset that should be corrected.
It has always been a warning. I don't like breaking changes. It is already there, I just didn't see it in my particular use case
I saw it in my fit, though.
You can see with rxSolve()
no warnings are suppressed, though with nlmixr2(...,est="rxSolve")
warnings are suppressed. (note I added it at the beginning of issue).
Created on 2024-07-22 with reprex v2.1.0