spatialreg icon indicating copy to clipboard operation
spatialreg copied to clipboard

change the way lag variables are detected in predict

Open rsbivand opened this issue 2 years ago • 4 comments

Handling of formula Durbin objects does not work, get to line 233 in R/predict.sarlm.R.

rsbivand avatar May 15 '23 17:05 rsbivand

Hi, I have this issue when using predict on a Durbin model with only some lagged variables. Assuming the problem isn't easy to fix, would there be any other way to generate forecasts with a model like this? Thanks.

dpr01 avatar Mar 06 '24 17:03 dpr01

Could you provide a reproducible example that matches your case?

rsbivand avatar Mar 07 '24 06:03 rsbivand

So after looking at it more carefully, I believe my error was actually being caused by a mismatch of structure between my original dataset and the predicting dataset. The message I had was:

"Error in predict.Sarlm(mod, dfp, listw = weights) : unknown mismatch. please report this bug In addition: Warning message: In colnames(Xs.not.lagged) != colnames(Xo) : longer object length is not a multiple of shorter object length"

I assumed the first error (which in the code you link to this issue) was the main problem but fixing the second warning appears to have made everything work. An example of what I'm doing:

library(tidyverse)
library(sf)
library(spdep)
library(spatialreg)

# Dataset
df <- st_read(system.file("shapes/boston_tracts.shp", package = "spData"))

# Spatial weights
centroids <- st_centroid(df)
neigh <- dnearneigh(centroids, d1 = 0, d2 = 30)
weights <- nb2listw(neigh, glist = lapply(nbdists(neigh, centroids), \(x) 1/(x^2)))

# Model
mod <- lagsarlm(log(MEDV) ~ CRIM + ZN + INDUS + CHAS + I(NOX^2) + I(RM^2) +
                  AGE + log(DIS) + log(RAD) + TAX + PTRATIO + B + log(LSTAT), 
                data = df,
                Durbin = ~ CRIM,
                listw = weights)
summary(mod)

# Predict
dfp <- df %>% 
  mutate(TAX = 0.5 * TAX)

predict(mod, dfp, listw = weights)

I think this works fine. But just to be clear, predict is aware that only CRIM is a spatially lagged variable in the model, as specified in lagsarlm, right? I think I may have misunderstood this issue.

dpr01 avatar Mar 07 '24 12:03 dpr01

Yes, predict only uses lag.CRIM, not other lagged X variables.

rsbivand avatar Mar 07 '24 20:03 rsbivand