2017-11-01 5:56 GMT+01:00 Peter Dunn <pdu...@usc.edu.au>: > Wow: Thanks again. You are going above and beyond Iñaki which I appreciate > greatly. > > But same error message appears, even after fixing (both the relerr, which I > had already attended to, and the lambda issue).
All I can say is that initialising both lambda and w (from CRAN version) solved the issue for me. As a matter of fact, I did see another message about uninitialised values, but the back trace was empty (no function names, I mean), which means that the problem is somewhere else. > I have since initialised *every* variable in the subroutine smallp (even the > *input* variables to some arbitrary value to try to work out what is causing > the issue) yet the error persists. There surely cannot be any uninitialized > variables now *every* var in the subroutine is explicitly initialised. > > That tells me that there is nothing I can do to remove the error. If > everything is initialised… > > Frustrated… And wasting so much time! If you set up a public repo (GitHub or similar) where everyone can see your current code base and changes made, it would be easier to help. It would be even easier if you check your changes using a public build system and share the results here. I don't know whether win-builder uses valgrind, but you can use r-hub (https://github.com/r-hub/rhub) by Gábor Csárdi. There is a function rhub::check_with_valgrind which requires no further explanation. Iñaki ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
