uncertainty not reported

19 views
Skip to first unread message

Kale Letterman

unread,
Aug 4, 2022, 10:43:55 AM8/4/22
to lmfit-py
Hi!

I have read about uncertainties not being reported, usually this has to do with parameter being stuck at some point. However I have now fitted values with good initial guesses,  (that change I read that it could be a reason as to why it's not reporting either) (and no bounds). But I still get no uncertainties. My report looks like the following.
Backgroundc0: 6300.27980 (init = 7068.271)
 Backgroundc1: -147.640219 (init = -183.4653)
 Backgroundc2: 1.51282026 (init = 2.01155)
 Backgroundc3: -0.00492907 (init = -0.007027575)
 PV1_amplitude: 32151.4529 (init = 5206.7)
 PV1_center: 44.5278321 (init = 44.50349)
 PV1_sigma: 0.24791733 (init = 0.1)
 PV1_fraction: 0.54215771 (init = 0.5)
 PV1_fwhm: 0.49583465 == '2.0000000*PV1_sigma' PV1_height: 50270.4148 == '(((1-PV1_fraction)*PV1_amplitude)/max(1e-15, (PV1_sigma*sqrt(pi/log(2))))+(PV1_fraction*PV1_amplitude)/max(1e-15, (pi*PV1_sigma)))'
 PV2_amplitude: 4778.21955 (init = 299.6)
 PV2_center: 64.8255216 (init = 64.22238)
 PV2_sigma: 0.51332419 (init = 0.1)
 PV2_fraction: 1.00000000 (init = 0.5)
 PV2_fwhm: 1.02664838 == '2.0000000*PV2_sigma'
 PV2_height: 2962.95120 == '(((1-PV2_fraction)*PV2_amplitude)/max(1e-15, (PV2_sigma*sqrt(pi/log(2))))+(PV2_fraction*PV2_amplitude)/max(1e-15, (pi*PV2_sigma)))

Why I also ask is I get no warning? Usually this seems to be the case in your guys's example reports.
Thanks! And thank you for this great package :)


Matt Newville

unread,
Aug 4, 2022, 12:48:19 PM8/4/22
to lmfit-py
On Thu, Aug 4, 2022 at 9:43 AM Kale Letterman <kalel...@gmail.com> wrote:
Hi!

I have read about uncertainties not being reported, usually this has to do with parameter being stuck at some point.

... or getting to values (say, way outside the data range) so that other parameters have no effect on the fit.

 
However I have now fitted values with good initial guesses,  (that change I read that it could be a reason as to why it's not reporting either) (and no bounds). But I still get no uncertainties. My report looks like the following.
Backgroundc0: 6300.27980 (init = 7068.271)
 Backgroundc1: -147.640219 (init = -183.4653)
 Backgroundc2: 1.51282026 (init = 2.01155)
 Backgroundc3: -0.00492907 (init = -0.007027575)
 PV1_amplitude: 32151.4529 (init = 5206.7)
 PV1_center: 44.5278321 (init = 44.50349)
 PV1_sigma: 0.24791733 (init = 0.1)
 PV1_fraction: 0.54215771 (init = 0.5)
 PV1_fwhm: 0.49583465 == '2.0000000*PV1_sigma' PV1_height: 50270.4148 == '(((1-PV1_fraction)*PV1_amplitude)/max(1e-15, (PV1_sigma*sqrt(pi/log(2))))+(PV1_fraction*PV1_amplitude)/max(1e-15, (pi*PV1_sigma)))'
 PV2_amplitude: 4778.21955 (init = 299.6)
 PV2_center: 64.8255216 (init = 64.22238)
 PV2_sigma: 0.51332419 (init = 0.1)
 PV2_fraction: 1.00000000 (init = 0.5)
 PV2_fwhm: 1.02664838 == '2.0000000*PV2_sigma'
 PV2_height: 2962.95120 == '(((1-PV2_fraction)*PV2_amplitude)/max(1e-15, (PV2_sigma*sqrt(pi/log(2))))+(PV2_fraction*PV2_amplitude)/max(1e-15, (pi*PV2_sigma)))

Why I also ask is I get no warning? Usually this seems to be the case in your guys's example reports.

I don't know.  You did not post minimal working code or the fit report, so it is very hard to guess what might be going wrong.

Reply all
Reply to author
Forward
0 new messages