Issues with Preporcessor

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
Debashis Basu

Issues with Preporcessor

Post by Debashis Basu »

Hello,

We are having a problem with Saturne. One of my colleagues is trying to use this.  We are thinking whether this is a version issue with Saturne.

----------------------------------------------------------------------------------------------------------------------------------------------- His message----------------------------------------This is the exact problem.
 
When running the preprocessor either through the SaturneGUI or the command line command check_mesh -m "filename" I receive and error message. The following are the exact error messages for each file format I have tired.  All of which, according to the manufacturers, is a supported type by Saturne 1.3.3.  However each of these file types processes normally on my laptop running Code_Saturne 2.0. Is this is a version issue ?. Any advice, would be appreciated.

1)  File type .med (produced in Salome)

Error in ECS execution
======================
ecs_pre.c:411: Fatal error.

File format "MED" support not available in this
installation (file "/home/lee/SATURNE-CODE/run-case/williamson/CYLINDER_TEST/MAILLAGE/cylinder.med").

Call stack
   1: 0x2b3a23228cad <bft_error+0x7d>                 (libbft.so.1)
   2: 0x413f05     <ecs_pre__type_format+0x385>     (ecs)
   3: 0x40e32c     <ecs_cmd__lit_arg+0x129c>        (ecs)
   4: 0x40f6dd     <main+0x1bd>                     (ecs)
   5: 0x37b701d994 <__libc_start_main+0xf4>         (libc.so.6)
   6: 0x408a69     ?                                (?)
End of stack

File type .unv (produced in Salome)
 
Error in ECS execution
======================

ecs_pre_ideas.c:1342: Fatal error.

Error reading line 85582 of file "/home/lee/SATURNE-CODE/run-case/williamson/CYLINDER_TEST/MAILLAGE/cylinder.unv".

Call stack
   1: 0x2b1f9c3d6cad <bft_error+0x7d>                 (libbft.so.1)
   2: 0x42d606     ?                                (?)
   3: 0x4306bf     <ecs_pre_ideas__lit_maillage+0x7ef> (ecs)
   4: 0x40f9ec     <main+0x4cc>                     (ecs)
   5: 0x37b701d994 <__libc_start_main+0xf4>         (libc.so.6)
   6: 0x408a69     ?                                (?)
End of stack

File type .msh (produced in Ansys or Gambit)

Error in ECS execution
======================
ecs_pre_gmsh.c:416: Fatal error.

Error reading a Gmsh mesh file:
at line 6252 of file "/home/lee/SATURNE-CODE/run-case/williamson/CYLINDER_TEST/MAILLAGE/Ansys_cylinder.msh".
The points definition was not found.

Call stack
   1: 0x2b8ff08d2cad <bft_error+0x7d>                 (libbft.so.1)
   2: 0x426469     <ecs_pre_gmsh__lit_maillage+0x15c9> (ecs)
   3: 0x40f9ec     <main+0x4cc>                     (ecs)
   4: 0x37b701d994 <__libc_start_main+0xf4>         (libc.so.6)
   5: 0x408a69     ?                                (?)
End of stack
 
 
Kindly advice. He was trying to simulate flow over a cylinder.
 
Thanks and Regards,
 
Debashis
 
Yvan Fournier

Re: Issues with Preporcessor

Post by Yvan Fournier »

Hello,

This is an installation issue: you need to configure/build Code_Saturne with MED file format support for it to be able to read MED files. If a MED library and headers are installed in standard directories (such as when using med and med-dev packages under Debian or Ubuntu), Code_Saturne will support them automatically.

I believe the install script handles MED support also, if it is configured correctly.

If you colleague already uses a SALOME install, there is no need to install MED again: he can point to the MED libraries already included with SALOME (for the Preprocessor's --with-med=<med_root> configure option).

For the other formats, things are stranger, as they do not need additional libraries. Were those files generated under Lnux or Windows ? If they were generated under windows, they should still be readable, but running "dos2unix" if available would be a precaution (especially with the older Code_Saturne 1.3). Otherwise, can you post the output of "head -100 cylinder.unv" for example ?

Another possibility is an install problem. What is the OS and compiler ? If all else fails, could your collegue try a clean reinstall ?

Best regards,
 
  Yvan
Debashis Basu

Re: Issues with Preporcessor

Post by Debashis Basu »

Thank You very much.

Regards,

Debashis
Alex Skillen

Re: Issues with Preporcessor

Post by Alex Skillen »

For gambit, you should export in neutral format (.neu file). Try solver -> generic.
Post Reply