-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Clarify staterror modifier specification #1856
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1856 +/- ##
=======================================
Coverage 98.16% 98.16%
=======================================
Files 68 68
Lines 4315 4315
Branches 725 725
=======================================
Hits 4236 4236
Misses 46 46
Partials 33 33
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Thanks for the PR @Moelf. We'll try to get to it before the end of the weekend. As you didn't make a GitHub Issue for this can you give a full summary in the PR body and then also finish off the rest of the CONTRIBUTING guidelines (hint: adding yourself to contributors. 😉)? |
I think the
So I think the table is not wrong. |
Note to myself for when I review this tomorrow: Relevant RTD build section is here: https://pyhf--1856.org.readthedocs.build/en/1856/likelihood.html#mc-statistical-uncertainty-staterror |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukasheinrich @kratsg while I think we should maybe discuss more the notational consistency across the docs I don't think that this needs to hold up Jerry's PR. So if we get approvals from both of you then I this LGTM for now.
d5a214f
to
24a8d4c
Compare
clarify and fix typo for `Staterror` modifier
for more information, see https://pre-commit.ci
@kratsg @lukasheinrich if this can get reviewed today by one (ideally both) of you then I think we can merge this. |
Thanks for your PR @Moelf! |
clarify and fix typo for
Staterror
modifier.Description
The
\delta
parameter is the absolute error in each bin due to MC Stat at +/- 1 sigma. Thus, the\sigma
of the Gaussian constraint term should have\delta / nominal
value not the other way around.And by play around with the
logpdf()
output, I'm convinced that the input in JSON is\delta
rather than\delta^2
(https://scikit-hep.org/pyhf/intro.html#id25)Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: