code_saturne User's Forum

Hello Yvan, I didn't include the patches, but I did use solid mesh in aster format and made some modifications in calc_ifs_dnl_ops.py. Now, in my current test, the usvima isn't call in begin of the each time step. It's call only in the ALE initialization (listing file). Do you know fix it? Regards, ...

Hello Yvan, I finally solved a fluid-structure interaction problem using the code_saturne/code_aster coupling (I am very satisfied with this progress), but the results obtained show a relative error of at least 33% in relation to the results of the literature. I'm trying to implement a variable mesh...

Hi Yvan,

I would like to have these cases. Any contribution is welcome!

Thank you!

Flávio

Hello Yvan, I got a new advance in coupling problem. Checking the log files (in the /tmp directory), I observed that the same problem ("GFORTRAN_1.4' not found") appears in the log of the FSI_SATURNE. Then I added the command "export LD_PRELOAD=$LD_PRELOAD:/usr/lib/x86_64-linux-gnu/li...

Hello all! I know that the ALE module can be used with internal and external coupling in FSI analisys. My doubt is how to use the ALE module in external coupling without to use the yacs schemas generated by code_saturne? This is possible? In an old topic, I found a python script for simulation of th...

Hello Yvan, I changed the cs_case_domain.py file, as indicates the FSI.patch.txt, however, the same error occurred again: Code_Saturne is running *********************** Version: 4.0 Path: /home/flavio/saturne/4.0.4 Result directory: /home/flavio/FSI_Auto/TESTE01/RESU_COUPLING/20160606-1745 Single p...

Hello Yvan,

I'll make the changes and I'll test a case in the next days. I'll post any progress!

Thank you!

Flávio

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

Hi,

My case!

Regards,

Flávio

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