[magiclevinho]

Dear Users,

I m using BlueCFD on windows. The interDyMFoam crashes randomly, and I don't know what could be the problem. I m running on 4 cores, parallel. If I run on 1 core, it does the same thing. Here is the error message I get:

Courant Number mean: 0.003091657 max: 0.9789671
Interface Courant Number mean: 0.0003166461 max: 0.2135742
deltaT = 0.0002311207
Time = 0.0114485

PIMPLE: iteration 1
AMI: Creating addressing and weights between 8065 source faces and 8065 target faces
AMI: Patch source sum(weights) min/max/average = 0.2486919, 2.427861, 1.007687
AMI: Patch target sum(weights) min/max/average = 0, 2.186797, 1.007601
Execution time for mesh.update() = 0.498 s
MULES: Solving for alpha.phase1
MULES: Solving for alpha.phase1
Phase-1 volume fraction = 0.551233  Min(alpha.phase1) = -2.887992e-009  Max(alpha.phase1) = 1.000159
MULES: Solving for alpha.phase1
MULES: Solving for alpha.phase1
Phase-1 volume fraction = 0.5512331  Min(alpha.phase1) = -2.608664e-009  Max(alpha.phase1) = 1.000147
[0] Generating stack trace...
[0]

Backtrace:
        ZN10StackTraceC1Ev [0x705c1465+0x25]
                 module: D:\PROGRA~2\BLUECF~1\ThirdParty-5.x\platforms\mingw_w64GccDPInt32\lib\libstack_trace.dll
        ZN4Foam5error10printStackERNS_7OstreamE [0x1021c88+0x218]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll
        ZN4Foam6sigFpe13sigFpeHandlerEi [0x1022af3+0x33]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll
        (No symbol) [0x405a1d]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        _C_specific_handler [0x7ffe4a866466+0x96]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        0_chkstk [0x7ffe4a87a07d+0x11d]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        RtlLookupFunctionEntry [0x7ffe4a7e9c58+0xab8]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        KiUserExceptionDispatcher [0x7ffe4a8790fe+0x2e]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        ZN4Foam6divideERNS_5FieldINS_6VectorIdEEEERKNS_5UListIS2_EERKNS_6TensorIdEE [0xff934b+0x84b]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll
        (No symbol) [0x444384]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        (No symbol) [0x440d86]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        (No symbol) [0x440ad5]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        (No symbol) [0x4a8535]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        (No symbol) [0x4013f7]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        (No symbol) [0x40152b]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\interDyMFoam.exe
        BaseThreadInitThunk [0x7ffe48672774+0x14]
                 module: C:\WINDOWS\System32\KERNEL32.DLL
        RtlUserThreadStart [0x7ffe4a840d51+0x21]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll

job aborted:
[ranks] message

[0] process exited without calling finalize

[1-3] terminated

---- error analysis -----

[0] on DESKTOP-93JM3T3
interDyMFoam ended prematurely and may have crashed. exit code 3

---- error analysis -----

Any Suggestions?

[wyldckat]

Quick answer and sorry for the late reply: The stack trace line that hints at the problem is this one:

ZN4Foam6sigFpe13sigFpeHandlerEi [0x1022af3+0x33]
                 module: D:\PROGRA~2\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll

Namely "ZN4Foam6sigFpe13sigFpeHandlerEi", where "sigFpe" can be seen in the name. This means that there was floating point exception: https://en.wikipedia.org/wiki/Signal_(IPC)#SIGFPE - usually a division by zero or some other calculation that required the result to be infinite or complex number.

I suspect that this happened due to this:

AMI: Patch target sum(weights) min/max/average = 0, 2.186797, 1.007601

If a weight is 0, this means that there is a face that is not in contact with another AMI interface. This means that you would have to use ACMI instead, which allows for unmatched surfaces, although the unmatched ones would then be automatically matched to a wall surface... although this doesn't work all that well, at least last time I heard/saw something about it.

[magiclevinho]

Thank You for your answer and time!