Closed AakaashRao closed 2 weeks ago
Hi @AakaashRao! Thanks for pointing this out.
The goal here is to make sure that we take proper leads and lags to compute first differences within each unit. In your case you are fine with taking differences between a Monday and a Friday, right? Then your solution makes sense.
I think the error message is informative, it tells the user what the code is doing with the time dimension. What additional information in the error message would have helped? Maybe suggesting to relabel the time variable?
Closed due to inactivity. Feel free to reopen if you want to discuss more @AakaashRao
@santiagohermo , sorry for the delay! You're right -- this reflected a misunderstanding on my part and the error message is plenty informative as it is. Thanks for the great work on this package!
Thanks @AakaashRao!
I run into the following uninformative error message when running EventStudy on a dataset that contains gaps in the time variable for all
idvar
values.My specific case is using calendar date as the time variable for a dataset lacking weekend observations. The values passed to
timevar
therefore look likec(1,2,3,4,5,8,9,10,11,12,15, ...)
.I solved the issue by re-generating the numeric date variable without gaps:
It might be helpful to add a more informative error message in case others have the same use case?