Skip to content
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

Full likelihoods #5

Merged
merged 2 commits into from Jan 12, 2022
Merged

Full likelihoods #5

merged 2 commits into from Jan 12, 2022

Conversation

jackaraz
Copy link
Member

Description of the Change:
add the ability to include CRs and VRs in the full likelihoods.

Benefits:

  • In general, ATLAS analyses are designed such that the signal contamination of CRs is max 10%. So recasting only the SRs but not the CRs/VRs is a good approximation in most cases (as long as the signal hypothesis is not very different from the one the analysis has been designed for).
  • Some analyses do a combined fit to signal and control regions; others don't. If they do, removing the CRs altogether is wrong. If they don't, it makes no difference whether or not the CRs are kept.

New options:
Option introduced in the .info file of the analysis e.g.

  <pyhf id="RegionC">
    <name>atlas_susy_2018_31_SRC.json</name>
    <regions>
      <channel name="CRtt_cuts"> </channel>
      <channel name="SR_metsigST">
      SRC_22
      SRC_24
      SRC_26
      SRC_28
      </channel>
      <channel name="VRzAlt_cuts" is_included="True"> </channel>
      <channel name="CRz_cuts" is_included="True"> </channel>
      <channel name="VRtt_cuts"> </channel>
      <channel name="VRz_cuts"> </channel>
    </regions>
  </pyhf>

If there is no data present in the channel code will look for the is_included tag, which can be "True", "yes", "1". If true, the channel will be included in the likelihood calculation; if not, it will be removed. If is_included is not present, and the channel does not have any data, it will be removed by default.

nonetype can not be added to a string -> convert to str first
Option introduced in the `.info` file of the analysis e.g.
```
  <pyhf id="RegionC">
    <name>atlas_susy_2018_31_SRC.json</name>
    <regions>
      <channel name="CRtt_cuts"> </channel>
      <channel name="SR_metsigST">
      SRC_22
      SRC_24
      SRC_26
      SRC_28
      </channel>
      <channel name="VRzAlt_cuts" is_included="True"> </channel>
      <channel name="CRz_cuts" is_included="True"> </channel>
      <channel name="VRtt_cuts"> </channel>
      <channel name="VRz_cuts"> </channel>
    </regions>
  </pyhf>
```
If there is no data present in the channel code will look for `is_included`
tag which can be "True", "yes", "1". If true the channel will be included
in the likelihood calculation if not it will be removed. If `is_included`
is not present and channel does not have any data, it will be removed by
default.
@jackaraz jackaraz requested a review from BFuks January 12, 2022 10:34
@jackaraz jackaraz added ⚙️enhancement New feature or request PAD Public Analysis Database labels Jan 12, 2022
@BFuks BFuks merged commit 6180b04 into main Jan 12, 2022
@jackaraz jackaraz deleted the full_likelihoods branch January 12, 2022 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚙️enhancement New feature or request PAD Public Analysis Database
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants