Skip to content

Add fuzzy checking for continuous means#79

Open
zmbc wants to merge 12 commits intomainfrom
fuzzy_check_continuous_values
Open

Add fuzzy checking for continuous means#79
zmbc wants to merge 12 commits intomainfrom
fuzzy_check_continuous_values

Conversation

@zmbc
Copy link
Contributor

@zmbc zmbc commented Sep 9, 2025

Add fuzzy checking for continuous means

Description

Changes and notes

Added and documented fuzzy checks for means of continuous values.

Testing

Note: Tests are currently failing! I need some help figuring out how to test this, aside from in-situ in the MNCNH V&V.

@zmbc zmbc added the enhancement New feature or request label Sep 9, 2025
@zmbc
Copy link
Contributor Author

zmbc commented Sep 9, 2025

@albrja or @patricktnast any possibility you could help me add tests for this?


When a target 95% UI is specified instead of a single target value,
we use a `normal inverse-gamma distribution <https://en.wikipedia.org/wiki/Beta_distribution>`_ that has approximately that UI
on the mean (if the variance parameter is marginalized out) and the same :math:`IG(2, s_{ref}^2)` prior on
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IG or \Gamma^{-1}? Better to be consistent, and I would recommend switching all to \text{InverseGamma} as the most clear option.

specifically :math:`N\text{-}\Gamma^{-1}(0, 10^{-3}, 2, s_{ref}^2)`
where :math:`N\text{-}\Gamma^{-1}` refers to `the normal-inverse-gamma distribution <https://en.wikipedia.org/wiki/Normal-inverse-gamma_distribution>`_
and :math:`s_{ref}` is set to the target mean or the midpoint of the UI.
In fact, rather than specifying :math:`10^{-3}` for the :math:`\lambda` parameter,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found this confusing; maybe use a variable instead of 10^{-3} above, and then define it below.

@zmbc
Copy link
Contributor Author

zmbc commented Sep 10, 2025

Note: while this is marked "ready for review" because I'd like review from researchers on the documentation, engineers should likely not review this yet -- no tests yet!

Base automatically changed from docs to main September 16, 2025 18:29
- We calculate how likely your data is under each scenario, and compare them. If your data is much more likely under the bug/issue scenario, we flag it.

For more details, see:
https://vivarium-research.readthedocs.io/en/latest/model_design/vivarium_features/automated_v_and_v/index.html#proportions-and-rates
Copy link
Contributor

@patricktnast patricktnast Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these links have moved (to here?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes!

@zmbc
Copy link
Contributor Author

zmbc commented Oct 31, 2025

As a general status update on this, I think I should be able to find a better mathematical formulation that will not require the user to make such an accurate guess about the variance parameter; I could not find a version of the current formulation that passed tests for a variety of misses on this parameter.

I hope to get back to this!

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments