fix: set POI for limit calculations via dedicated pyhf API #364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#348 added the possibility to specify a custom POI via a kwarg in
fit.limit
. This was done by settingmodel.config.poi_name
andmodel.config.poi_index
directly, which is no longer possible after scikit-hep/pyhf#1972 (see scikit-hep/pyhf#1984). scikit-hep/pyhf#1985 adds support forNone
POI values inmodel.config.set_poi
, which allows that API to be used instead. This PR switches to this dedicated API to support temporarily changing the POI, which requires an update of the minimumpyhf
version to0.7.0rc4
.