Skip to content

Signal each class of posterior warning once - #416

Open
florence-bockting wants to merge 2 commits into
masterfrom
collect-posterior-warnings
Open

florence-bockting wants to merge 2 commits into
masterfrom
collect-posterior-warnings

Conversation

@florence-bockting

@florence-bockting florence-bockting commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Description

This PR is connected to stan-dev/posterior#470 where we introduced warning classes.
These can now be extracted and collected through the new .collect_warnings() function in loo.
This collector ensures that the same warning is printed only once (and not multiple times when e.g. running some posterior function in a loop).

This PR is related to Issue #353 (but it does not solve it entirely).

TODOs

  • test added
  • News item added

The PR was assisted by an LLM.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.69%. Comparing base (11415f5) to head (45a7c81).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #416      +/-   ##
==========================================
+ Coverage   92.65%   92.69%   +0.04%     
==========================================
  Files          31       31              
  Lines        3240     3258      +18     
==========================================
+ Hits         3002     3020      +18     
  Misses        238      238              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

This is how benchmark results would change (along with a 95% confidence interval in relative change) if 45a7c81 is merged into master:

  • ✔️loo_function: 1.59s -> 1.59s [-0.14%, +0.32%]
  • ✔️loo_matrix: 1.58s -> 1.58s [-0.88%, +0.39%]
    Further explanation regarding interpretation and methodology can be found in the documentation.

@florence-bockting
florence-bockting marked this pull request as ready for review November 2, 2026 11:27

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants