google / google/CausalImpact

Rationale for explicit bsts parameters in `CausalImpact::ConstructModel` for StaticRegression

Open
#71 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
R
Stars
1.9k
Forks
264
PR merge metrics
No merged PRs in 30d

Description

Bit newer to the package (and just recently returning to R) so good chance this question has an easy answer that I haven't come across yet. I was curious on the rationale behind [setting explicit parameters](https://github.com/google/CausalImpact/blob/master/R/impact_model.R#L221-L229) for `expected.model.size`, `expected.r2`, and `prior.df` in the bsts.model.size and not enabling any means of optionally setting. I'd imagine that the appropriate number of covariates would vary significantly depending on the type of data, so surprised me that this was an unadjustable static value.

Obviously can go through the trouble of building a bsts model separately (and maybe that's more common than I'm realizing) but would be great to know if there's a reason behind the assumptions before trudging off to do that. Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.