null error margins crashes dftf

[gr5]

testing with v8.4.0

in menu do "view" "null error margins".

A dialog pops up. Do nothing and within about 10 seconds DFTF crashes and closes.

I tried loading a wavefront first and it seems to make no difference.

I'm curious if this happens for other people as well or if there's something weird with my settings. I haven't investigated much. Haven't tried running it debug mode or anything. Oh - I'll check the crash log:

[2026-08-09 12:46:50.766] [critical] CV error :(unsigned)i1 < (unsigned)size.p[1] in ../build_openCV/install/include/opencv2/core/mat.inl.hpp on line 1620
[2026-08-09 12:46:50.767] [critical] Unexpected issue. Stacktrace:
0# 0x00007FF625A224D8 in C:\Users\gr\DFTF840\DFTFringe.exe
1# 0x00007FF6258CA6D1 in C:\Users\gr\DFTF840\DFTFringe.exe
2# 0x00007FF6258CB2B9 in C:\Users\gr\DFTF840\DFTFringe.exe
3# 0x00007FFB0EAA6250 in C:\Users\gr\DFTF840\libopencv_core4120.dll
4# 0x00007FFB0EAA6442 in C:\Users\gr\DFTF840\libopencv_core4120.dll
5# 0x00007FF625A0A178 in C:\Users\gr\DFTF840\DFTFringe.exe
6# 0x00007FF6258F08D7 in C:\Users\gr\DFTF840\DFTFringe.exe

I'm happy to look into this myself in a week or so.

[githubdoe]

I'm still using my current open DFTFringe which has a list of recent figuring sessions that I find useful. So I don't want to close the current one or crash it.

Here is what that dialog does behind the scenes. It creates a Monti Carlo simulation. It randomly varies the mirror config diameter and ROC to see how the null would be changed. After doing that X number of times it then displays the standard deviation with the error margins displayed.

The user can specify the error delta to apply to the values to try. Perhaps those have gotten out of range for your current mirror config. I don't think it needs a wave front loaded but I forget.

[gr5]

But shouldn't it wait until I hit the button that says "compute simulation"? Anyway, I'm sure I can figure it out.

[githubdoe]

No it computes using default values when opened.

[githubdoe]

Mine works. So it probably is you setup with out of range settings. No wave front needed. Mine works without one as well. So it reveals some sort of init bug that probably needs some checking.