-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in 'getParameterOrder' #791
Comments
Try re-installing glmmTMB (from source) after TMB. We're working on preventing this in the future. |
I will point out that you should have gotten a warning about "Package version inconsistency detected" when you loaded glmmTMB. Did you? |
Yes!! I saw the message right now. Thank you both for the rapid response. After re-installing glmmTMb from source it worked again. |
Hi all, Sorry to open this again, but I have a related issue, I think. When I try to simply see what's inside a saved model that I have run using glmmTMB, I got this message:
I tried this, but did not work unfortunately.
And I don't get this Any idea? Do you need more info? Thanks! |
@antigosa You might be able to run |
We should make sure this is documented appropriately ... |
Hello, Thanks, Error in .Call("getParameterOrder", data, parameters, reportenv, control, : |
OK, the usual questions:
I don't have many ideas beyond that, but it would be helpful if you can give the results of |
Thank you so much for your response. I appreciate it. I uninstalled R, RStudio, and Rtools and then reinstalled them as per the instructions at http://github.com/kaskr/adcomp/wiki/Download. Then I installed TMB and glmmTMB from source in that order. The error still persists from a clean R session (i.e., only TMB and glmmTMB loaded). The results of sessionInfo() from a clean R session are below. Thanks,
Matrix products: default locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
I should also mention that I am not trying to load a stored fit from an older session. Thanks, |
So far I haven't been able to reproduce this. Do you get this with any glmmTMB fit (e.g. library(glmmTMB)
data("sleepstudy", package = "lme4")
glmmTMB(Reaction ~ Days + (Days|Subject), sleepstudy) ) or is it only with a specific model? (Note that you might as well update now to glmmTMB 1.1.8, which just went up on CRAN, although I doubt it will make a difference ...) If it's with a specific model, can you create a reproducible example for us? |
Running the code you provided above worked without any problems. The issue I was having was related to the specific model demo that I was trying to run. I was able to get the model demo to run without any errors by replacing the .cpp file with another that was correctly specified. Thanks again for your assistance. |
OK, closing this, but if you can provide us a reproducible example that's causing a problem we can try to help diagnose (or, send it to |
I was able to correct the error by replacing the .cpp file and the model ran without error so there is no longer a need for diagnosis. It seems that maybe the .cpp file I was using had an error. Thanks again for your assistance. I appreciate it. |
Sorry to resurrect this issue but I have similar problems after updating to R 4.4.1.
This example is pre-existing code that was running without issues. (perhaps irrelevant: I also had to troubleshoot to make brms, cmdstanr and cmdstan to work together. In that case it was a matter of getting the cmdstan toolchain to use rtools44 instead of rtools42) |
Hi everyone,
After downloading the latest version of TMB package, I tried to re-run a code on glmmTMB that was working just fine until this morning, and I got this error:
'Error in .Call("getParameterOrder", data, parameters, new.env(), NULL, :
Incorrect number of arguments (4), expecting 3 for 'getParameterOrder'
If I use the same code for lme4 it works perfectly fine. Any idea on what is happening and what can I do to fix this?
If needed, I would have no problem sharing the code or anything else.
Thanks!
Julien
The text was updated successfully, but these errors were encountered: