Hi Joshua and Peter,
Thank you so much for your help. Yes, it's definitely my mistake in
mixing R and c++ function calls...
I think I can fix the problems now.
Thank you once again,
Wenchao
On 3/24/2018 7:31 PM, peter dalgaard wrote:
On 25 Mar 2018, at 00:42 , Wenchao Ma wrote:
arm
> On 25 Mar 2018, at 00:42 , Wenchao Ma wrote:
>
>arma::vec Pj = Calc_Pj(par = par, designMj = designMj, linkfunc =
> linkfunc, boundary = boundary, eps = eps);
I was never any good at C++, but that syntax looks like R code. Does C++ allow
tag=value argument specification? Aren't all the
On Sat, Mar 24, 2018 at 6:42 PM, Wenchao Ma wrote:
> Dear Duncan,
>
> Thank you. I really appreciate your help!
>
> Yes, the Fedora warning is self explanatory, but I'm still quite confused.
> Below are part of my Mstep.cpp file (both functions are in the same file).
> The fedora warned me that, a
Dear Duncan,
Thank you. I really appreciate your help!
Yes, the Fedora warning is self explanatory, but I'm still quite
confused. Below are part of my Mstep.cpp file (both functions are in the
same file). The fedora warned me that, among others,
Mstep.cpp:62:69: warning: explicitly assigning v
On 24/03/2018 9:28 AM, Wenchao Ma wrote:
Dear all,
I just submitted a package to CRAN. It went well on my computer and
winbuilder, but produced warning and error messages on some linux and
solaris systems, as shown here:
https://cran.r-project.org/web/checks/check_results_GDINA.html
Does anyone
Dear all,
I just submitted a package to CRAN. It went well on my computer and
winbuilder, but produced warning and error messages on some linux and
solaris systems, as shown here:
https://cran.r-project.org/web/checks/check_results_GDINA.html
Does anyone know what is going on here?
Thanks a
