code_saturne User's Forum

Hello,

I am running CS3.0 and Syrthes 4.01 on a Kubuntu 12.04 64bits machine, and would like to run a coupling calculation. I followed the tutorial "version 3.0 tutorial - Three 2D disks", and everything went OK up to the coupling calculation. When I launched the runcase_coupling script I have this error :
Coupling execution between:
o Code_Saturne [1 domain(s)];
o SYRTHES [1 domain(s)];


Code_Saturne is running
***********************

Version: 3.0.0
Path: /opt/Code_Saturne_3.0/Prod/code_saturne-3.0.0

Result directory:
/media/sdb1/CFD/3disks2D/RESU_COUPLING/20130712-0911


Single processor code_saturne simulation.
Single processor SYRTHES simulation.

SYRTHES4 home directory: /opt/syrthes4.0.1/arch/Linux_x86_64
MPI home directory: /opt/Code_Saturne_3.0/openmpi-1.6.3
Building the executable file syrthes..
ar: /opt/syrthes4.0.1/arch/Linux_x86_64/lib/libsyrthes_cfd.a: No such file or directory
make: *** [exe] Erreur 9

Error during the compilation stage
Traceback (most recent call last):
File "./runcase_coupling", line 151, in <module>
save_results=True)
File "/opt/Code_Saturne_3.0/Prod/code_saturne-3.0.0/lib/python2.7/site-packages/code_saturne/cs_case.py", line 1472, in run
mpi_environment)
File "/opt/Code_Saturne_3.0/Prod/code_saturne-3.0.0/lib/python2.7/site-packages/code_saturne/cs_case.py", line 1162, in prepare_data
d.prepare_data()
File "/opt/Code_Saturne_3.0/Prod/code_saturne-3.0.0/lib/python2.7/site-packages/code_saturne/cs_case_domain.py", line 1169, in prepare_data
retval = self.syrthes_case.prepare_run(exec_srcdir, compile_logname)
File "/opt/syrthes4.0.1/arch/Linux_x86_64/share/syrthes/syrthes.py", line 417, in prepare_run
destdir = self.exec_dir)
File "/opt/syrthes4.0.1/arch/Linux_x86_64/share/syrthes/syrthes.py", line 1338, in build_syrthes
shutil.move(os.path.abspath("syrthes"), exec_name)
File "/usr/lib/python2.7/shutil.py", line 299, in move
copy2(src, real_dst)
File "/usr/lib/python2.7/shutil.py", line 128, in copy2
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/media/sdb1/CFD/3disks2D/RESU_COUPLING/20130712-0911/solid/src/syrthes'

From what I understood, there is 2 errors,

• * one is the missing "libsyrthes_cfd.a", and I am not able to fix this. Is it a problem during configuration : an option I did forget ?

• * The other is the fact that it is not possible to find thedirectory : '/media/sdb1/CFD/3disks2D/RESU_COUPLING/20130712-0911/solid/src/syrthes'. But this should be generated during execution, no action should be done by myself, am I wrong ?

Is there someone who already faced this problem ?

Thanks for any help.

Hello,

Both errors are related:

- when you install Syrthes, in the Syrthes.ini file, you need to make sure you use/install both ple and syrthescfd (at the end of the ini file). If you have missed this, it would explain your first error.

- the second error is simple: since syrthescfd is not available, the syrthes executable is not compiled (or rather, linked).

Regards,

Yvan

Hello Yvan,

that's the thing : I did request for the installation of ple and syrthescfd. I did again the installation processus, and I missed something at the end of the terminal view :
make[1]: *** [/opt/syrthes4.0.1/build//cfd_couplage.o] Erreur 1
make[1]: quittant le répertoire « /opt/syrthes4.0.1/src/syrthes-kernel/src »
make: *** [syrthescfd] Erreur 2
function report

I enclosed the log file of syrthescfd.

OK, I found the problem, the path to the ple was wrong. thanks.

Hello,

Unfortunately if this problem is solved i faced another one. When I ran CS alone for this tutorial, no problem, but when I ran it for the coupling, CS stopped with the alarm :

/opt/Code_Saturne_3.0/installer/code_saturne-3.0.0/src/fvm/fvm_to_med.c:375: Erreur fatale.

MEDmeshCr() failed to create a new med_mesh.
Associated med_mesh name: "unlocated elements (centers)"
Associated writer name: "results"



Pile d'appels :
1: 0x7f036c8529bd <+0x689bd> (libsaturne.so.0)
2: 0x7f036c85451b <fvm_to_med_export_nodal+0x27b> (libsaturne.so.0)
3: 0x7f036c846edb <fvm_writer_export_nodal+0x3b> (libsaturne.so.0)
4: 0x7f036c8b69be <+0xcc9be> (libsaturne.so.0)
5: 0x7f036c8b91fa <cs_post_write_meshes+0x4a> (libsaturne.so.0)
6: 0x7f036c8dd015 <+0xf3015> (libsaturne.so.0)
7: 0x7f036c8debd3 <cs_syr4_coupling_init_mesh+0x63> (libsaturne.so.0)
8: 0x7f036c8dffda <geosyr_+0x2a> (libsaturne.so.0)
9: 0x7f036c88bf54 <cregeo_+0x24> (libsaturne.so.0)
10: 0x7f036c8600ad <caltri_+0x99> (libsaturne.so.0)
11: 0x7f036c8399e5 <cs_run+0xa35> (libsaturne.so.0)
12: 0x7f036c838eca <main+0x14a> (libsaturne.so.0)
13: 0x7f036c44c76d <__libc_start_main+0xed> (libc.so.6)
14: 0x400759 <> (cs_solver)
Fin de la pile

it seems that the conversion to med fails, while it ran when using CS alone. Any thing lse that I did wrong ?

I found this : http://code-saturne.org/forum/viewtopic ... 4&start=10

it seems that this is still the problem : I ran with ensight and this problem disappeared.