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

Add guidance text for methods/data #38

Open
simon-smart88 opened this issue May 7, 2024 · 9 comments
Open

Add guidance text for methods/data #38

simon-smart88 opened this issue May 7, 2024 · 9 comments

Comments

@simon-smart88
Copy link
Owner

Starting this to keep track of bits of guidance text that I can't write myself:

  • Why do we need an aggregation raster / does it do?
  • When would it be appropriate to use a uniform raster?
  • What is the mesh and why is it needed?
  • What the mesh settings change and when would you want to change them?
  • What is the difference between the model families and how should you decide which one to use?
  • What is the difference between the model link functions and how should you decide which one to use?
  • What is a spatial field and when should it be used / not used?
  • What are IID and when should it be used / not used?
  • What are priors and what difference will setting them make?
@simon-smart88
Copy link
Owner Author

  • Explanation of the options for predict_uncertainty

@timcdlucas
Copy link

Why do we need an aggregation raster / does it do?

We want to model on rates. 1 degree temperature increases the rate by 0.1 per person, not by 0.1.
In this sense it is working as an "offset" in a Poisson GLM.
It can also be though of as a weight but not sure if this is confusing

@simon-smart88
Copy link
Owner Author

aggregation is essentially weighting of the pixels in the model, but included in the model at fitting rather than just converting incidence to rate

@simon-smart88
Copy link
Owner Author

When would it be appropriate to use a uniform raster?

Each pixel could contribute to the response equally. e.g. average air pollution over the polygon - no way that you can know where in the polygon the sources are. Or average surveys which where completely random e.g. diversity of pollen in 10 cores taken at random

@timcdlucas
Copy link

What is the mesh and why is it needed?

https://sites.stat.washington.edu/peter/591/Lindgren.pdf (1.1. Continuous domain spatial Markov random fields
)

https://sites.google.com/a/r-inla.org/www/spde-book?authuser=0

SPDE is the keyword

@simon-smart88
Copy link
Owner Author

What is a spatial field and when should it be used / not used?

Spatial field is a completely flexible (non-parametric) 2D contributor to the linear predictor. It is a way of modeling missing covariates that are spatially structured. In other geospatial modelling tasks it is often used to model biased data collection e.g. due to oversampling.

Normally use it, only don't if you want to run faster or you know you have all the important covariates.

Continuous across the area and spatially structured c/f the IID effect on a polygon level.

@simon-smart88
Copy link
Owner Author

authoritative: https://link.springer.com/book/10.1007/978-0-387-48536-2

IID more likey due to be caused by data collection or that when outbreaks occur they spread rapidly leading to high values in a particular polygon but that doesn't necessarily mean the risk is much higher. Non-spatial implying that it makes no difference to the neighbouring polygons.

@simon-smart88
Copy link
Owner Author

@timcdlucas Just finishing off the last bits of this and wanted to check this is correct (for the Worldpop module).

Population counts can used to inform the model where population occurs inside the polygons. Areas with higher populations would be expected to have higher incidences of disease and so including this information helps to produce more accurate estimates of disease rates per person.

@timcdlucas
Copy link

"This can be considered as analogous to an offset in a Poisson regression."

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

2 participants