UNV mesh in Code_Saturne 2.0.0-rc1
Posted: Wed Mar 06, 2013 2:39 pm
Hi everyone,
I currently face a problem with an "old" version of Code_Saturne : 2.0.0-rc1. I try to use an UNV mesh but the preprocessor (ECS) fails to load it.
Maybe there is a trick to solve this issue. My UNV file is generated with SALOME (I tried version 5.1.5 and version 6.6.0).
Here is my mesh quality criteria checks :
Another question : Is it possible to use a more recent preprocessor ? What is the newest preprocessor version that is compatible with CS 2.0.0-rc1 ?
Thanks for any clue or workaround, you may give to me.
Best regards,
Quentin
I currently face a problem with an "old" version of Code_Saturne : 2.0.0-rc1. I try to use an UNV mesh but the preprocessor (ECS) fails to load it.
Maybe there is a trick to solve this issue. My UNV file is generated with SALOME (I tried version 5.1.5 and version 6.6.0).
Here is my mesh quality criteria checks :
Code: Select all
/opt/saturne/cs-2.0-beta2/bin/cs_preprocess --in ecs_cmd -m
/work/Etude_Box/MESH/box_unvS5.unv --ensight --case check_mesh
.------------------------------.
| |
| Code_Saturne Preprocessor |
| |
`------------------------------'
ECS version 2.0.0-rc1 (Thu 13 May 2010 05:08:41 PM CEST)
CGNS 2.5.4 file format support
MED 2.3.6 (HDF5 1.6.9) file format support
Reading of compressed files ('.gz') with Zlib 1.2.3.3
Case configuration
------------------
Date : Wed 06 Mar 2013 02:12:46 PM CET
System : Linux 2.6.32-45-generic
Machine : samantha
Processor : Quad-Core AMD Opteron(tm) Processor 2376
Memory : 16468396
User : quentin (Quentin BEY)
Directory : /work/Etude_Box/CAS_UNV/RESU
Case name : check_mesh
Mesh file : /work/Etude_Box/MESH/box_unvS5.unv
Reading mesh from file in I-deas universal format
----------------------
Mesh file: /work/Etude_Box/MESH/box_unvS5.unv
Number of vertices : 8
SIGSEGV signal (access to forbidden memory area) intercepted !
Call stack
1: 0x42cb0b (cs_preprocess)
2: 0x40e9a8 (cs_preprocess)
3: 0x409f40 (cs_preprocess)
4: 0x7fd14cb18c4d (libc.so.6)
5: 0x4041a9 (cs_preprocess)
End of stack
Thanks for any clue or workaround, you may give to me.
Best regards,
Quentin