Skip to content
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

predicted values with INLA #50

Open
arives opened this issue Jun 17, 2020 · 4 comments
Open

predicted values with INLA #50

arives opened this issue Jun 17, 2020 · 4 comments

Comments

@arives
Copy link
Collaborator

arives commented Jun 17, 2020

Russell,

While updating rr2, I found that the bayes=T version of pglmm returns the "nearest_node" predicted values even when the "tip_rm" option is used. Is there a structural reason for this? For R2_pred, the "tip_rm" option makes more sense.

Thanks, Tony

@daijiang
Copy link
Owner

@rdinnager
Copy link
Collaborator

Thanks Daijiang for the reminder. Looks like I chose to ignore the gaussian.pred option. I think it was because I didn't really know what those two options meant (still not sure), I just wanted to get it working, and planned to come back to it later. But then I forgot to. Could you explain briefly what tip_rm means? Or point to somewhere where it is explained? If it requires predicting with new data, my implementation currently can't do this, but I have been meaning to update it so that it can.

@daijiang
Copy link
Owner

Russell, tip_rm means removing a record (sort of like remove a tip species from a phylogeny) and then using the remaining data to predict the value. nearest_node means after removing the record, make prediction for the most common ancestor instead of itself. @arives probably can correct me and explain better here.

@arives
Copy link
Collaborator Author

arives commented Jun 19, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants