Problem on edit the boundary_conditions.f90

Forums code_saturne usage
1

Dear experts,

When I did the tutorial: full domain, I need to use the file cs_user_boundary_conditions.f90 in case2 of full domain. After updating the Fortan file cs_user_boundary_conditions.f90, I run the calculation. But the case stopped with the error like that:

gfortran -I /home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne -I /home/xutingting/code_saturne/arch/Ubuntu_3.3.1/include/code_saturne -x f95-cpp-input -Wall -pedantic-errors -std=f2003 -O -c /home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90

I don’t know what is the problem and I hope to ask experts here to help me.

From: Research Engineer in R&D center, EDF China

2

Hello,

Do you have a compile.log file ?

Please read the Forum usage recommendations to check for the list of files you should send so we can try to determine the issue.

Regards,

Yvan

3

This is the content of compile.log.

/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:389.5:

dt , &
1
Warning: Unused dummy argument ‘dt’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:388.9:

icodcl , itrifb , itypfb , izfppp , &
1
Warning: Unused dummy argument ‘icodcl’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:388.18:

icodcl , itrifb , itypfb , izfppp , &
1
Warning: Unused dummy argument ‘itrifb’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:388.27:

icodcl , itrifb , itypfb , izfppp , &
1
Warning: Unused dummy argument ‘itypfb’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:388.36:

icodcl , itrifb , itypfb , izfppp , &
1
Warning: Unused dummy argument ‘izfppp’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:387.17:

( nvar , nscal , &
1
Warning: Unused dummy argument ‘nscal’ at (1)
/home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90:387.7:

( nvar , nscal , &
1
Warning: Unused dummy argument ‘nvar’ at (1)
gfortran -I /home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne -I /home/xutingting/code_saturne/arch/Ubuntu_3.3.1/include/code_saturne -x f95-cpp-input -Wall -pedantic-errors -std=f2003 -O -c /home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/src_saturne/cs_user_boundary_conditions.f90
gcc -o /home/xutingting/EDF-CFD/TUTORIAL/full_domain/case1/RESU/20140923-1835/cs_solver cs_user_boundary_conditions.o -L/home/xutingting/code_saturne/arch/Ubuntu_3.3.1/lib -L/home/xutingting/salome/salome_7.4.0/cgnslib-3.1.3/lib -L/home/xutingting/salome/salome_7.4.0/med-3.0.7/lib -L/home/xutingting/salome/salome_7.4.0/hdf5-1.8.10/lib -L/home/xutingting/salome/salome_7.4.0/scotch-5.1.11/lib -O -Wl,-export-dynamic -lsaturne -lple -lcgns -lmedC -lhdf5 -lscotch -lm -lmpi -lxml2 -lblas -lz -ldl -L/usr/lib/gcc/x86_64-linux-gnu/4.8 -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../.. -lgfortran -lm -lquadmath -Wl,-rpath -Wl,:/home/xutingting/code_saturne/arch/Ubuntu_3.3.1/lib:/home/xutingting/salome/salome_7.4.0/cgnslib-3.1.3/lib:/home/xutingting/salome/salome_7.4.0/med-3.0.7/lib:/home/xutingting/salome/salome_7.4.0/hdf5-1.8.10/lib:/home/xutingting/salome/salome_7.4.0/scotch-5.1.11/lib

compile.log (3.14 KB)

4

Hello,

It seems your compilation is actually OK, so the problem must come later. Do you have a cs_solver an/or run_solver.sh file in your running (RESU/<date_time>) directory ? Do you have other error messages, perhaps in the terminal from which you ran the code ?

Regards,

Yvan