Skip to content

Trying to compare fit results in pyhf and trexfitter using same workspace

Notifications You must be signed in to change notification settings

efemberg11/pyhf-Trexfitter_problem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 

Repository files navigation

pyhf-Trexfitter_problem

Hi! I'm trying to compare fit results in pyhf and trexfitter using same workspace. Bestfit values have good compability, but errors have differences for both fit cases (asimov fit and data fit). Such differences was observed for pyhf (v. 0.5.4 and 0.7.0) vs trex fitter v4.15.

The workspace was generated by trexfitter using: trex-fitter nw clear.config "Regions=three_lep_presel_1jet"

To get pyhf results, run: pyhf_fit.py. To get trex fitter results, run: trex-fitter f clear.config "Regions=three_lep_presel_1jet"

In trexfitter's clear.config file, you can change FitBlind value to TRUE for asimov fit, or FALSE for data fit.

Maybe there are some parameters, which mismatching in pyhf or in trexfitter.

About

Trying to compare fit results in pyhf and trexfitter using same workspace

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages