-
Notifications
You must be signed in to change notification settings - Fork 37
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
number of samples for cross-validation #85
Comments
Neither of those is an error. A characteristic feature of errors is that the message starts with word Both are informative messages. The first implies that you had an old model fitted with an earlier version (earlier than 3.0-9) of Hmsc which had two unused columns in the The second tells that one of the updaters will not be used for your model because you had a spatial method which is not supported by that updater (GammaEta). |
sorry about that, I meant warning. Thanks for the explanation. |
See issue #86 that touches the same problem. |
@FabianRoger |
Thanks! This answers my question. |
Hi,
I am trying to evaluate the model fit by two-fold cross-validation using the
computePredictedValues
function. However, I am confused by what I should specify for the sampling. I looked in both the documentation and the book but didn't find an explanation of how the models are fitted to each fold. Sorry if I missed it!The
computePredictedValues
has the parametersstart
,thin
, andmcmcStep
, each of which defaults to1
. Does that mean the model would be fitted with a single iteration? This seems implausible? Or do I need to specify the sampling to match the sampling form the model fitting?For the model I fitted I used the following parameters:
nChains = 10
samples = 200
thin = 200
transient = 0.5*thin*samples
Sorry if I miss the obvious.
ps: I also get the error
(I set the updater to FALSE as it was suggested to me this would speed up the mcmc sampling significantly. I didn't get an error during the initial model fitting)
Is that anything to worry about?
Thank you for your help!
The text was updated successfully, but these errors were encountered: