[sparta-users] Grid2Paraview issues

[Nnaemeka A. <nna...@en...>]

Hi

I'm back with an noticed issue somewhere in the workflow regarding the post processing of flowfield (grid) data.

Everything works fine in the 20Jan2025 release of SPARTA, however upon migrating to the 24Sep2025 release, I'm unable to run grid2paraview.py successfully... (Note, surf2paraview.py ran fine)

Here's what the terminal output looked like after running the same runcase in 20Jan2025:

Processing  36  grid chunk(s).
Completed grid chunk number:  15
Completed grid chunk number:  12
Completed grid chunk number:  20
Completed grid chunk number:  17
Completed grid chunk number:  14
Completed grid chunk number:  23
Completed grid chunk number:  18
Completed grid chunk number:  22
Completed grid chunk number:  19
Completed grid chunk number:  21
Completed grid chunk number:  13
Completed grid chunk number:  16

However if I run the case in 24Sep2025 (i.e. same input file, same geometry, same collision parameter file, etc. same paraview download (5.7.0) so the same pvpython file, but different SPARTA release), then the terminal hangs after this warning is printed:

Processing  36  grid chunk(s).
/home/engs2351/paraview/ParaView-5.7.0/lib/python3.7/multiprocessing/semaphore_tracker.py:55: UserWarning: semaphore_tracker: process died unexpectedly, relaunching.  Some semaphores might leak.
  warnings.warn('semaphore_tracker: process died unexpectedly, '
^C

And nothing happens until I press Ctrl+C to abort the task, after which the following errors are printed

Loguru caught a signal: SIGINT

Loguru caught a signal: SIGINT
Stack trace:
27            0x401f7d ../../../paraview/ParaView-5.7.0/bin/pvpython() [0x401f7d]
26      0x78acab42a28b __libc_start_main + 139
25      0x78acab42a1ca /lib/x86_64-linux-gnu/libc.so.6(+0x2a1ca) [0x78acab42a1ca]
24            0x4024b4 ../../../paraview/ParaView-5.7.0/bin/pvpython() [0x4024b4]
23      0x78aca8208b24 vtkPythonInterpreter::PyMain(int, char**) + 756
22      0x78aca0fd7af3 Py_Main + 35
21      0x78aca0fd78a7 /home/engs2351/paraview/ParaView-5.7.0/bin/../lib/libpython3.7m.so.1.0(+0x1d78a7) [0x78aca0fd78a7]
20      0x78aca0fb5815 PyRun_SimpleFileExFlags + 229
19      0x78aca0fb56a2 PyRun_FileExFlags + 178
18      0x78aca0f81b5b PyEval_EvalCode + 27
17      0x78aca0f81b2e PyEval_EvalCodeEx + 62
16      0x78aca0f819fc _PyEval_EvalCodeWithName + 2780
15      0x78aca0e71fec _PyEval_EvalFrameDefault + 35116
14      0x78aca0e68610 /home/engs2351/paraview/ParaView-5.7.0/bin/../lib/libpython3.7m.so.1.0(+0x68610) [0x78aca0e68610]
13      0x78aca0e71fec _PyEval_EvalFrameDefault + 35116
12      0x78aca0e98286 _PyFunction_FastCallKeywords + 166
11      0x78aca0f819fc _PyEval_EvalCodeWithName + 2780
10      0x78aca0e71fec _PyEval_EvalFrameDefault + 35116
9       0x78aca0e98286 _PyFunction_FastCallKeywords + 166
8       0x78aca0f819fc _PyEval_EvalCodeWithName + 2780
7       0x78aca0e7138b _PyEval_EvalFrameDefault + 31947
6       0x78aca0ea0ea9 _PyMethodDescr_FastCallKeywords + 73
5       0x78aca0e98783 _PyMethodDef_RawFastCallKeywords + 755
4       0x78aca1010d0a /home/engs2351/paraview/ParaView-5.7.0/bin/../lib/libpython3.7m.so.1.0(+0x210d0a) [0x78aca1010d0a]
3       0x78aca0fc18d8 PyThread_acquire_lock_timed + 488
2       0x78acab4a4fb8 /lib/x86_64-linux-gnu/libc.so.6(+0xa4fb8) [0x78acab4a4fb8]
1       0x78acab498d71 /lib/x86_64-linux-gnu/libc.so.6(+0x98d71) [0x78acab498d71]
0       0x78acab445330 /lib/x86_64-linux-gnu/libc.so.6(+0x45330) [0x78acab445330]
(  74.682s) [main thread     ]

I have tried running the data from the 20Jan2025 run case with the grid2paraview.py from 24Sep2025 release and it still didn't work, so it's not an issue with the data output of the 24Sept2025... it's an issue with the grid2paraview.py specifically of the 24Sep2025 release...

I will have also logged this on the github.

Looking forward to a solution!

Many thanks!
Nnaemeka