Skip to content

Commit

Permalink
Add a NEWS.md entry for stan-dev#319 (currently only partly resolved).
Browse files Browse the repository at this point in the history
  • Loading branch information
fweber144 committed Mar 28, 2023
1 parent 5445d21 commit a65074c
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions NEWS.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ If you read this from a place other than <https://mc-stan.org/projpred/news/inde
* Although bad practice (in general), a reference model lacking an intercept can now be used within **projpred**. However, it will always be projected onto submodels which *include* an intercept. The reason is that even if the true intercept in the reference model is zero, this does not need to hold for the submodels. An informational message mentioning the projection onto intercept-including submodels is thrown when **projpred** encounters a reference model lacking an intercept. (GitHub: #96, #391)
* In case of non-predictor arguments of `s()` or `t2()`, **projpred** now throws an error. (This had already been documented before, but a suitable error message was missing.) (GitHub: #393, based on #156 and #269)
* L1 search now throws a warning if an interaction term is selected before all involved main effects have been selected. (GitHub: #395)
* Documented that in multilevel (group-level) terms, function calls on the right-hand side of the `|` character (e.g., `(1 | gr(group_variable))`, which is possible in **brms**) are currently not allowed in **projpred**. A corresponding error message has also been added. (GitHub: #319)
* Due to internal refactoring:

+ `project()`'s output elements `submodl` and `weights` have been renamed to `outdmin` and `wdraws_prj`, respectively.
Expand Down

0 comments on commit a65074c

Please sign in to comment.