Two-way coupling code_saturne / code_aster

[Yvan Fournier]

Hello,

Your install seems OK.

Could you post the "run_solver" script from the execution directory (in RESU_COUPLING/<run_id>), to see how this script was generated ? If the file does not exist in the run directory, this may provide info in itself, so in this case, can you post the whole output of the run ?

Regards,

Yvan

[Oliveira77]

Hi Yvan,

Posted!

I thank your collaboration.

Flávio

[Oliveira77]

Hi Yvan,

Did you find the cause of the previous error? Is it an error in the setting of my test case?

Regards,

Flávio

[Yvan Fournier]

Hello Flávio,

Sorry, I did not have time yet to look at the issue. I'll try to check this by the middle of this week, and keep you informed.

Best regards,

Yvan

[Yvan Fournier]

Hello,

I did not find anything obviously wrong, so I am not sure about th cause of th error.

Could you post the whole case (hopefully this first test case is small) so I can try the same case on one of my installs, and see if I have the same issue ?

Regards,

Yvan

[Oliveira77]

Hi,

My case!

Regards,

Flávio

[Yvan Fournier]

Hello,

Just to tell you I downloaded you case, as well as SALOME_MECA 15.2 (please tell me iy you used another version), but have not had the time to run the tests yet.

I'll try to do this next week, and will keeep you informed. Sorry to keep you waiting, but as most of the works on Code_Saturne/Code_Aster coupling was done by people not working on this anymore, and part of the works was subcontracted, I have only very limited experience with this coupling (so can't give a quick answer based on errors already experienced), and the people who know this part better don't seem to visit this forum...

So Il'll need to find some tile to really try to run your case...

Regards,

Yvan

[Oliveira77]

Hi,

I'm using SALOME-MECA 2015.1 with Code_Saturne 4.0.4, but I have tested the case in SALOME-MECA 2014.2 with Code_Saturne 3.3.4 and the same error occurred.

I'll keep trying to get a solution to this problem and waiting for any information.

Regards,

Flávio

[Yvan Fournier]

Hello,

The coupling was not workable in versions prior to 4.0, so having an issue with older versions is expected, but I'll have to see if I reproduce your issue with SALOME_MECA 2015.2.

I'll keep you informed when I get to try it (hopefully within a few days)

Regards,

Yvan

[Yvan Fournier]

Hello Flavio,

I ran quick test on my side, and also have an error, but only for the FSI_ASTER component:

+++++++++++++++++++ start calculation +++++++++++++++++++
th. 140568750806784 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [620] : [GiveContainer] waiting 60 second steps container /Containers/dsp0677922/2258_FSI_ASTER_0x12e86f0
th. 140568759199488 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [620] : [GiveContainer] waiting 60 second steps container /Containers/dsp0677922/2258_FSI_MILIEU_0x12e89d0
th. 140568742414080 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [620] : [GiveContainer] waiting 60 second steps container /Containers/dsp0677922/2258_FSI_SATURNE_0x12e8d20
th. 140568750806784 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [432] : [GiveContainer] container /Containers/dsp0677922/2258_FSI_ASTER_0x12e86f0 launched
SalomeContainer launched : /Containers/dsp0677922/2258_FSI_ASTER_0x12e86f0 dsp0677922 2286
th. 140568759199488 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [432] : [GiveContainer] container /Containers/dsp0677922/2258_FSI_MILIEU_0x12e89d0 launched
SalomeContainer launched : /Containers/dsp0677922/2258_FSI_MILIEU_0x12e89d0 dsp0677922 2287
th. 140568742414080 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [432] : [GiveContainer] container /Containers/dsp0677922/2258_FSI_SATURNE_0x12e8d20 launched
SalomeContainer launched : /Containers/dsp0677922/2258_FSI_SATURNE_0x12e8d20 dsp0677922 2288
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
Problem in connectService: solid_service Component is probably not launched. Modify your YACS file
+++++++++++++++++++ end calculation +++++++++++++++++++

Applying the patch in file FSI.patch (by calling:

patch -p1 < FSI.patch

in the Code_Saturne source root directory, then reinstalling the code (or directly applying the change to the installed file <install_prefix>/lib/python-<version>/site-packages/code_saturne/cs_case_domain.py) allows reaching this stage, with a line similar to the following in the code_saturne.cfg file:

aster = /home/user_name/salome_meca/V2015.2/tools/Code_aster_stable-1240

Without this patch, I have complaints earlier.

With the patch, I get the eror messages above, and redirecting the output of as_run in the file aster_by_yacs (under RESU_COUPLING/ASTER), into another file, it seems Code_Aster has run, but has nothing to do (file attached).

At this stage, if I don't want to spend a week on this, I'll need to contact the people who last tested this (tested a few months ago, and I go patches, but I suspect they forget to provide some of the patches)... I may also test on one of our own cases they gave me, in case the issue is with the Code_Aster setup (which I suspect, given the "nothing" to do).

If you want to test first, I attach one of those cases, with some Code_Aster patches, and an additional Code_Saturne user subroutine (haven't checked yet where it fits).

Regards,

Yvan