CS5 & Salome_meca installation issues

All questions about installation
Forum rules
Please read the forum usage recommendations before posting.
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

CS5 & Salome_meca installation issues

Post by Paul Brss »

Hello everyone,

I'm currently trying to set CS5 and Salome_meca (last stable version) in order to realize some FSI simulations.
1) The command "code_saturne create -s stud -c fluid --aster solid" works and creates all the features. CS5 and salome_meca both work when stand-alone.

2)I changed the scrip for the file cs_case.py as indicated in another post on this forum with the indications given by "0001-Update-script-generation.....".

3) I try the launch the FSI case given by Yvan Fournier externecylindresconcentriques. The calculation starts but fails directly. The error I get looks like this (I attached a .zip files with all the necessary files)

Code: Select all

Proc state : FAILED
Elapsed time after execution: 21290 ms
Execution has ended in error
<error node= proc state= FAILED>
<error node= inter_service state= ERROR>
Problem in connectService: solid_service Component is probably not launched. Modify your YACS file
</error>
<error node= fluid_service state= ERROR>

</error>
<error node= solid_service state= ERROR>
Error while trying to create a new component: component 'FSI_ASTER' is not installed or it's a wrong name
SALOME_Container::create_component_instance failed
</error>
</error>
shutdown SALOME container: /Containers/turbulentchbg/32313_FSI_MILIEU_0x20abcc0
shutdown SALOME container: /Containers/turbulentchbg/32313_FSI_SATURNE_0x20abf70
shutdown SALOME container: /Containers/turbulentchbg/32313_FSI_ASTER_0x1df9420
Error raised when executing command: driver -e fsi_yacs_scheme.xml
ERROR:salomeContext:SystemExit 1 in method _runSession.

I didn't manage to solve the problem related to FSI_ASTER. I don't know if it's a cause or a consequence. Does anyone solved this problem ?

Regards,
Paul
Attachments
20180427-0951.zip
Results files from crashed simulation
(64.47 KiB) Downloaded 276 times
0001-Update-script-generation-for-coupling-with-current-v.patch(1).txt
Update script for cs_case.py
(989 Bytes) Downloaded 273 times
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: CS5 & Salome_meca installation issues

Post by Yvan Fournier »

Hello,

I think Salome also places some useful log files in the /tmp directory...

Not sure wether this is an install issue or a missng update in the code_aster comm file (a special command is needed to load the module now, but the "init_compo" at the beginning of your comm script seems to be good).

Did you check this thread, viewtopic.php?f=2&t=2213&hilit=aster&start=20, especially the one about the CXXFLAGS aspect, which may be required or not depending on how recent is your compiler ?

Regards,

Yvan
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

Re: CS5 & Salome_meca installation issues

Post by Paul Brss »

Hi Yvan,

So I made the coupling between Saturne and Aster work. It took me some times but I'll now run some more tests.

Just to inform you what was my last problem, which was unexpected: the coupling procedure was not working when the "number of iterations for the fluid initialization" (NALINF) in the ALE module was not set at 0.
Do you know if it is normal or if it is a problem coming from my installation ?

Another small problem, the coupling procedure does not seem to stop properly:

Code: Select all

YACS Exception during execute
Execution problem: probably an error in input arguments of service 'inter_run' from component 'FSI_MILIEU'
Problem in disconnect(CORBA::SystemException) uses port: DTCALC
Problem in disconnect(CORBA::SystemException) provides port: ICV
Problem in disconnect(CORBA::SystemException) provides port: DONGEO
Problem in disconnect(CORBA::SystemException) uses port: DTCALC
Problem in disconnect(CORBA::SystemException) uses port: EPSILO
Problem in disconnect(CORBA::SystemException) uses port: EPSILO
Problem in disconnect(CORBA::SystemException) uses port: TTINIT
Problem in disconnect(CORBA::SystemException) uses port: TTINIT
Problem in disconnect(CORBA::SystemException) uses port: PDTREF
Problem in disconnect(CORBA::SystemException) uses port: PDTREF
Problem in disconnect(CORBA::SystemException) uses port: DEPSAT
Problem in disconnect(CORBA::SystemException) uses port: FORAST
Problem in disconnect(CORBA::SystemException) uses port: NBPDTM
Problem in disconnect(CORBA::SystemException) uses port: NBPDTM
Problem in disconnect(CORBA::SystemException) uses port: NBSSIT
Problem in disconnect(CORBA::SystemException) uses port: NBSSIT
Problem in disconnect(CORBA::SystemException) uses port: ISYNCP
Problem in disconnect(CORBA::SystemException) uses port: NTCHRO
Problem in disconnect(CORBA::SystemException) uses port: ICVEXT
Problem in disconnect(CORBA::SystemException) uses port: ICVAST
Problem in disconnect(CORBA::SystemException) uses port: NB_DYN
Problem in disconnect(CORBA::SystemException) uses port: NB_FOR
+++++++++++++++++++  end calculation  +++++++++++++++++++
Proc state : ACTIVATED
Elapsed time after execution: 413480 ms
Execution has ended in error

shutdown SALOME container: /Containers/turbulentchbg/22876_FSI_SATURNE_0x28f61f0
shutdown SALOME container: /Containers/turbulentchbg/22876_FSI_ASTER_0x28f5c20
Error raised when executing command: driver -e fsi_yacs_scheme.xml
ERROR:salomeContext:SystemExit 1 in method _runSession.

 ****************************
  Saving calculation results
 ****************************
Is there a way to avoid this message ?

Regards,

Paul
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: CS5 & Salome_meca installation issues

Post by Yvan Fournier »

Hello,

Good news.

Not sure about the NALINF option, but I suspect that it works in uncoupled ALE cases but not on coupled cases, which have received less testing. A workaround would be to use a calculation restart.

I have the same error message ("dirty finalization") as you have, so you can consider this "normal". It is ugly, but probably won't be fixed: we are currently collaborating with an inter in another organization to set up a Code_Saturne/code_aster using other (MPI-based) libraries, and if this is successful, we hope to have a better, simpler, cleaner coupling by the end of this year. So hopefully, the current, messy coupling will be "kept alive" only as long as we don't have something better ;-)

Best regards,

Yvan
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

Re: CS5 & Salome_meca installation issues

Post by Paul Brss »

Hi Yvan,

So the guy in charge of the cluster has made some update in the software. And.... I have this error:

Code: Select all

th. 140190191470400 - Trace /home/A21173/smeca/yamm_build/V2017_0_2_build/V2017_public/modules/src/KERNEL/src/NamingService/SALOME_NamingService.cxx [1446] : CORBA::SystemException: unable to contact the naming service
Elapsed time before load: 109 ms
The imported file has errors
LogRecord: parser:FATAL:Unknown OutStreamPort Type: CALCIUM_double for node: inter_service port name: DTCALC (fsi_yacs_scheme.xml:46)

Error raised when executing command: driver -e fsi_yacs_scheme.xml
ERROR:salomeContext:SystemExit 1 in method _runSession.


I saw in this old topic that (viewtopic.php?f=2&t=2213&hilit=aster&start=20) this command should work:

Code: Select all

    CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0
I tried this with the configure command:

Code: Select all

../../code_saturne-5.0.8/configure --prefix=/mnt/data/Paul/cs8/code_saturne/prod/ --with-salome=/opt/salome-meca/V2017.0.2 --with-hdf5=salome --with-cgns=salome --with-med=salome  CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0
And it did not work so I guess that I haven't done the right thing. Can you guide me a little bit more ?

Thank you !

Paul
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: CS5 & Salome_meca installation issues

Post by Yvan Fournier »

Hello,

The "CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0" option is used to solve some link problems when Salome_MECA has been generated with an older version of gcc/g++ than the one you are using.

This error seems different, and I have never seen it before... It seems that your version of YACS does not include CALCIUM support, or does not recognize some of its syntax (the error message appears on the first "CALCIUM" type message). Could you also send me the config.log for Code_Saturne, to see if an error on this support was detected ?

Also, some builds of Salome_Meca seem to be usable, so this may depend on the build you have. Is it a "public" build or an "EDF" build ?

Best regards,

Yvan
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

Re: CS5 & Salome_meca installation issues

Post by Paul Brss »

Hi Yvan,

It is very strange because it was working...

Thanks for your help. Here my "config.log" files.

Regards,

Paul
Attachments
config.log
(276.74 KiB) Downloaded 250 times
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: CS5 & Salome_meca installation issues

Post by Yvan Fournier »

Hello,

The "Calcium" support seems to have been detected normally.

To check if th file was somehow corrupted, could you try importing the fsi_yacs_scheme.xml from you failed executon directory under the YACS module using the Salome_MECA GUI and tell me if you have an error. You may also post the file here to check if it is different from the reference file.

Best regards,

Yvan
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

Re: CS5 & Salome_meca installation issues

Post by Paul Brss »

Hi Yvan,

So I imported the fsi_yacs_scheme.xml with succes in the salome's GUI.

I also checked with the this files: https://github.com/code-saturne/code_sa ... scheme.xml
I think there is no difference with mine.

Do you have any idea ?

Regards,

Paul
Attachments
fsi_yacs_scheme.xml
(17.72 KiB) Downloaded 247 times
Paul Brss
Posts: 32
Joined: Mon Dec 04, 2017 3:00 pm

Re: CS5 & Salome_meca installation issues

Post by Paul Brss »

Hi (again) Yvan,

So I have finally found what was my problem. I made some cleaning in the /tmp directory some days ago by deleting the *_FSI_ASTER_*.log, *_FSI_SATURNE_*.log and *_FSI_MILIEU_*.log. But I did not delete this salome files:

- .omniORB_PortManager.cfg
- .omniORB_PortManager.lock
- .omniORB_<username>_<hostname>_<port>.cfg
- .omniORB_<username>_last.cfg


Yet, I still don't know why exactly it was blocking the simulation to run. Any guess ?

Regards,

Paul
Post Reply