You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I recently ran a lot of toys for a very large model and had a hard time debugging, as some nuisance parameters hit the parameter bounds for some of the toys.
It would be great if a warning could be added in that case. What do you think?
Where do you forsee the error being raised? Would it be as part of optimization (which scipy's fortran routines have a warning for that I added a long time ago; but minuit really doesn't) or do you imagine this being done after the fit is done and we're checking all returned fitted parameter values (for non-fixed parameters) to see if any of them are matching the upper or lower bounds of those parameters?
harder to do it as part of the fit, mostly because scipy and minuit are entirely different and trying to add a check while doing optimization will slow down the optimization at each stage. It should be somewhat straightforward to add a way to check the bounds are hit. Given you provided an example, then we have a good way to test that we catch it.
Summary
Hey,
I recently ran a lot of toys for a very large model and had a hard time debugging, as some nuisance parameters hit the parameter bounds for some of the toys.
It would be great if a warning could be added in that case. What do you think?
Additional Information
A simple example:
Code of Conduct
The text was updated successfully, but these errors were encountered: