Open mattfidler opened 2 years ago
There are only 'skip'ped commits left to test. The first bad commit could be any of: 7cd313eeef91d9ea9269615d27834ec45e9d6cc6 a8acea8771475cb247e72095eb992b124784801a 425c4a25c072eb2137dfc6dafe7a1da8e5568107 b6c99cd93f72465120ca3a368b3e0f6d89586230 4d2a00bfd77ab5c6a4ad2ae99f3b59a695af3b76 8bdccd033d595fd1b7ad825580cffeb651d11357 a2336d7b44a704b9bfcc0078a7568990fb12b3d2 We cannot bisect more!
The 0.5
series seemed to run fine; The 0.6
/0.7
series wont compile with modern FORTRAN compilers..
Would it help to have an older docker container try it? If so, can you suggest the command to perform the bisection analysis?
I could spin up an old Ubuntu docker container with an older gfortran and do the bisection. I don't know the correct command to use for bisection analysis.
I tried a bisection already.
The problem is the older versions of rxode2
will not compile with the version of gfortran
that are available now. This means it happened some time around 0.6
or 0.7
, and does not solve for 0.9
and onward for this particular model.
Note the bisection is of released versions and comes from https://github.com/cran/RxODE
Some differences:
safeZero=FALSE
)R_pow
instead of pow
Some observations in the C code:
.
or .0
to ensure they are actually double values instead of integers. This can possibly cause problems in rxode2
mean_cd_water_flow =( water_in_CD - water_out_CD) / 2
Could cause the integer division issue in the old RxODE.
R_pow
instead of pow
-- changing to pow
did not fix it.2.0
and similar throughout did not change the results in the original RxODE
Originally posted by @mattfidler in https://github.com/nlmixr2/rxode2/discussions/227#discussioncomment-3256736_