Atmospheric fow model/SIGSEGV signal (forbidden memory area access) intercepted!

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
ximeng
Posts: 23
Joined: Sun Jan 22, 2023 3:28 pm

Atmospheric fow model/SIGSEGV signal (forbidden memory area access) intercepted!

Post by ximeng »

Dear all,

I wonder if there are some detailed tutorials for the atmospheric flow model/ urban building flow cases?

I use code_saturne v7.2.0 in WSL(WSL 1) ubuntu 20.04. I got some problems when I use the atmospheric flow model for a large-scale city model. The mesh for the urban building group is generated by STAR CCM+ with .ccm file format, which is supported by the code_saturne. Since the building groups' geometry is too much complex, the mesh quality is bad, but the same mesh has been tested well for OpenFOAM before. I use the atmospheric flow model to introduce the ABL (atmospheric boundary layer). I fill in the 'idealized large scale meteorological data' in the GUI, without giving the meteo file in the DATA folder.(I am a fresher and don't know if it is okay? And if the longitude and latitude of the domain center are the coordinate, x & y axis of domain center ).

And When I run calculations, it shows errors like: 'SIGSEGV signal (forbidden memory area access) intercepted!'. Some relevant files are attached. Could you please help me with this? Please let me know if you need other information. Very appreciate!!

Best regards.

error's file:
SIGSEGV signal (forbidden memory area access) intercepted!

Call stack:
1: 0x7f0a728dbbde <+0x4a8bde> (cs_solver)
2: 0x7f0a728ddd43 <+0x4aad43> (cs_solver)
3: 0x7f0a728bdf89 <+0x48af89> (cs_solver)
4: 0x7f0a72608dd8 <+0x1d5dd8> (cs_solver)
5: 0x7f0a725231a3 <+0xf01a3> (cs_solver)
6: 0x7f0a7243e6db <+0xb6db> (cs_solver)
7: 0x7f0a7243df0a <+0xaf0a> (cs_solver)
8: 0x7f0a71354083 <__libc_start_main+0xf3> (libc.so.6)
9: 0x7f0a7243df7e <+0xaf7e> (cs_solver)
End of stack
Attachments
run_solver.log
(15.74 KiB) Downloaded 51 times
preprocessor.log
(6 KiB) Downloaded 47 times
ximeng
Posts: 23
Joined: Sun Jan 22, 2023 3:28 pm

Re: Atmospheric fow model/SIGSEGV signal (forbidden memory area access) intercepted!

Post by ximeng »

Dear all,

The problem above might be caused by the mesh conversion from STAR CCM+ to code_saturne. I made some changes to the name of the selection criteria in the boundary regions definition part, and then it could be successful when just doing Mesh processing only execution mode. But when I do the standard computation(same errors with standard Eulerian single phase or Atmospheric Flow models), it still crashed at the same error but should be different reasons, which could be seen in the attachments.

Do you have any suggestions for this? Sincerely thanks!

Best regards,
Ximeng
Attachments
setup.log
(27.61 KiB) Downloaded 47 times
run_solver.log
(17.3 KiB) Downloaded 48 times
preprocessor.log
(6 KiB) Downloaded 45 times
ximeng
Posts: 23
Joined: Sun Jan 22, 2023 3:28 pm

Re: Atmospheric fow model/SIGSEGV signal (forbidden memory area access) intercepted!

Post by ximeng »

Error file:

SIGSEGV signal (forbidden memory area access) intercepted!

Call stack:
1: 0x7f9b4d4c88f1 <+0x3168f1> (cs_solver)
2: 0x7f9b4d4cd2e9 <+0x31b2e9> (cs_solver)
3: 0x7f9b4d4d054e <+0x31e54e> (cs_solver)
4: 0x7f9b4d20714b <+0x5514b> (cs_solver)
5: 0x7f9b4d6275ab <+0x4755ab> (cs_solver)
6: 0x7f9b4d2bdb72 <+0x10bb72> (cs_solver)
7: 0x7f9b4d1bd720 <+0xb720> (cs_solver)
8: 0x7f9b4d1bcf0a <+0xaf0a> (cs_solver)
9: 0x7f9b4c0d4083 <__libc_start_main+0xf3> (libc.so.6)
10: 0x7f9b4d1bcf7e <+0xaf7e> (cs_solver)
End of stack

application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
SimBu
Posts: 30
Joined: Tue Sep 13, 2022 4:13 pm

Re: Atmospheric fow model/SIGSEGV signal (forbidden memory area access) intercepted!

Post by SimBu »

I am definitly not an expert of Code Saturne, neither in linux authorization. Firstly, reading the setup.log, it seems that you did not defined all your boundaries :

Code: Select all

  Boundary:   top
    type:     undefined
    zone id:  4

  Boundary:   wall_e
    type:     undefined
    zone id:  5

  Boundary:   wall_w
    type:     undefined
    zone id:  6
Then when I get these kind of errors it's sometimes when I run on another computer that doesn't have access to where the case is set up (e.g. running on a VM while having files somewhere else). That is probably not the solution but maybe...
Post Reply