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

--saveToys does not save POI value used for toy generation in limit tree #797

Open
adewit opened this issue Sep 30, 2022 · 1 comment
Open

Comments

@adewit
Copy link
Collaborator

adewit commented Sep 30, 2022

Behaviour should be, according to documentation:

If you include [the --saveToys] option, the `limit` TTree in the output will have an entry corresponding to the state of the POI used for the generation of the toy, with the value of **`quantileExpected`** set to **-2**.

But (at least when using --toysFrequentist) it appears to be saving the best-fit value of the POI after fitting to the toy data set.

See also https://cms-talk.web.cern.ch/t/parameter-values-in-toys-with-toysfrequentist-option/15578/2

@nucleosynthesis
Copy link
Contributor

This also seems to be happening without --toysFrequentist. The problem seems to be that (for example), when running with -M MultiDimFit, the branch for r is set (inside the MultiDimFit code ) after the fit to a toy is performed and so while the RooRealVar is correctly set to the value used to generate, this branch isn't.

Instead if you add the option --trackParameter r, the branch trackedParam_r will behave as expected - i.e the quantileExpected -2 branches will be the values used to generate the toy for the POI "r".

We should at least fix the explanation of the option to explain that the user should use the --trackedParameters option if they want to save the values used in the generation but it might be worth seeing if the behaviour can be fixed so that the branches created by MultiDimFit also reflect the same?

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

No branches or pull requests

2 participants