code-saturne / code-saturne/code_saturne
Bug with the Lagrangian module and restart on a different Mesh - CS 7.2-alpha revision fb85c8cdc
- Dominant language
- C++
- Stars
- 307
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have a problem when I try to do a restart with the Lagrangian module (and Vof) with a different mesh. I am using CS 7.2-alpha revision fb85c8cdc.
With the VoF module only, the restart on a different mesh works properly but when I add the Lagrangian module CS crashes.
During my tests, I tried to do a restart (iso mesh) by specifying a "different mesh" in the GUI while I keep the same mesh in MESH and I get the same bug:
** Information on the lagrangian computation
-------------------------------------
Read restart file for particle values
Start read
/home/yohann-ws2/Development/CS_MASTER/code_saturne/src/lagr/cs_lagr_restart.c:466: Fatal error.
Error reading main particle restart data.
Call stack:
1: 0x7fdfff83359d (libsaturne-7.2.so)
2: 0x7fdfff88304a (libsaturne-7.2.so)
3: 0x7fdfff81f68d (libsaturne-7.2.so)
4: 0x7fdffef2ff20 (libsaturne-7.2.so)
5: 0x7fdfffff2b81 (libcs_solver-7.2.so)
6: 0x7fdffeb450b3 <__libc_start_main+0xf3> (libc.so.6)
7: 0x557a23f4c12e <_start+0x2e> (cs_solver)
End of stack
and if I deactivate in the GUI the choice for "different mesh", it works fine.
Let me know if you need more info.
Cheers,
Yohann EUDE
Contributor guide
Research direction
Reproduce the restart with Lagrangian and VoF enabled, comparing a different mesh with the working same-mesh case. Start at src/lagr/cs_lagr_restart.c around line 466 and trace the particle restart read from cs_lagr_restart_read_particle_data. Done means the different-mesh restart completes without the fatal error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100