glm.cluster reliant on/generates NULL wgt__ value

[alexanderrobitzsch]

glm.cluster reliant on/generates NULL wgt__ value

[alexanderrobitzsch]

I agree that overwriting wgt__ produces an error. I just did not see an alternative simple method to get the lm formula evaluation running inside the function.

[b-johns]

I have been having the same issue as the original poster when calling lm.cluster and glm.cluster within a larger function. Is the best strategy for now to set wgt__ <- NULL just before calling the larger function, as he suggested? Or will this cause other problems that I'm not foreseeing?

[ahoundetoungan]

@b-johns , adding wgt__ <- NULL before calling the function is a good solution if you do not use weight in glm.cluster. In this case, weight argument in glm.cluster is NULL and corresponds to what has been created before calling the function. If you use weight in glm.cluster, the best way is to add wgt__ <<- weight before glm.cluster, where weight is the vector of weights plugged into the function glm.cluster. Here is an example.

f <- function(...){
....
wgt__ <<- wghts
mTP <- glm.cluster(formula = y ~ X, cluster = 'IDClass', weights = wghts, data = data)
....
}

The line wgt__ <<- wghtsP creates wgt__ in the global environment because of the assignment approach <<-. This makes sure that the weight wgt__ created is the one used in the function glm.cluster. If there are no weights, wgt__ <<- wghtsP can be replaced with wgt__ <<- NULL.