LowerBound not constraining fitted value

Expected behavior

User applied upper and lower bounds to asymmetry value while fitting muon data in the MuonAnalysis interface and set lower bound to 0.0 or a small positive real number. Expected that asymmetry value would be >0.

Actual behavior

Negative value of parameter obtained even though lower bound implies a positive value is required.

Steps to reproduce the behavior

Please see above screenshot. We were able to get the same A0 value for the flat background for a variety of LowerBound values.

Platforms affected

3.11.2 Windows 10

P.S. Have sent Anthony Lim a link to this post.