-
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
Predictions by prepareGradient
do not match spatial latent factor
#204
Comments
This looks very odd to me, but unfortunately no informed guess so far regarding where this discrepancy can originate from. I cannot rule this possibility out, but this does not look just like the effect of whether the nonlinear transformation from EtaLambda to Normal_CDF(Const+EtaLambda) is made before/after the averaging over the posterior. |
Hi @gtikhonov Thanks for your response. Is the information below helpful? I won't be able to share the model file itself since it's nearly 100 MB. Model summary:
Code:
Do you have suggestions about how to tell if the geodesic coordinates are getting confused by the GPP? Thanks, |
Hello,
I'm trying to use
prepareGradient
to make spatial predictions across a low-resolution raster of near-global extent.This could be my own misunderstanding of the principles behind
prepareGradient
, but I noticed that the predictions made usingprepareGradient
do not match the spatial distribution of the posterior mean of the (one and only) spatial latent factor in my single-species Hmsc model fitted using the GPP algorithm.Figure 1. The posterior mean spatial latent factor, mean(Eta) * mean(Lambda).
Figure 2. Predictions made by running
predict
on a gradient made usingprepareGradient
with a raster of constant values, so that only the spatial latent factor should be driving variation across pixels. (Though not relevant to the issue, the cyan points are those where this species' presence has been recorded.)Note that even though the posterior mean spatial latent factor displays low values in Canada (Fig 1), predictions made on pixels located in Canada are unusually high (Fig 2).
Is this expected behavior? Do you have ideas about what could be causing the discrepancy?
Thanks,
Clara
The text was updated successfully, but these errors were encountered: