Alexander Held

A few more ideas that might be out of scope for this implementation: - optional return of the mu values and obs/exp CLs would be convenient for visualizations, e.g. with...

Sorry for the possible confusion about `staterror_Signal_region` vs `staterror_SR`, that was just because I copied this from an example and then forgot to change it in one instance. I edited...

As far as I remember, yes #994 allows for this too. I opened this issue because I think it makes sense to have it in the `model.config.par_slice` API directly instead...

I think the strings for channel/sample may possibly be allowed to begin with a number too, but not sure there. For modifiers I believe numbers cause issues, but I don't...

related: https://github.com/scikit-hep/pyhf/issues/179#issuecomment-1073751988

Hi, for basic MLE fits a "POI" is not different from any other normalization factor, so this should already work at the moment. For things like parameter rankings where the...

> If you have a HistFactory XML+ROOT workspace that has multiple POIs declared, I would be interested in seeing it. @kratsg I have one here: `/afs/cern.ch/user/a/alheld/public/pyhf_multi_POI` ```xml Signal_norm Bg_norm ```...

Some thoughts from my perspective: - Breaking the schema to use a list of strings for the POI instead of a space-separated string of POI names seems like a good...

> Do we match the weird behavior in ROOT or try to do better? Then we get into situations where workspaces in HiFa JSON are not translateable into ROOT XML...

I tried out a roundtrip from JSON with a POI called `Signal norm`. Conversion to xml is fine, and xml back to JSON recovers the original spec. A problem only...