v 2.1.0 sur ubuntu 12.04 : f90 functions don't work

[laurence wallian]

hello,

My OS is ubuntu 12.04,so it was very easy to install code_saturne.

all was OK, but when I try to use fortran functions, it seems not to take them into account :
I have put the files as recommanded (DATA : *.xml SRC : *.f90), and the compilation is OK, excepted some warnings related to unused variables.

Code: Select all

                      code_saturne is running
                      ***********************
 Version: 2.1.0
 Path:    /usr
 Result directory:
   /home/...RESU/20120926-1410

 Working directory (to be periodically cleaned):
   /home/...

 Single processor code_saturne simulation.
 ****************************************
  Compiling user subroutines and linking
 ****************************************
 ****************************
  Preparing calculation data
 ****************************
 ***************************
  Preprocessing calculation
 ***************************
 **********************
  Starting calculation
 **********************
 ****************************
  Saving calculation results
 ****************************

I try a very simple case with usclim.f90, to force Vy=10m/s on the boundary entree :

Code: Select all

call getfbr('1 or BC_1 or inlet or entree', nlelt, lstelt)
do ilelt = 1, nlelt
  ifac = lstelt(ilelt)
  iel = ifabor(ifac)
  itypfb(ifac) = ientre
  rcodcl(ifac,iu,1) = 0.0d0
  rcodcl(ifac,iv,1) = 10.0d0
  rcodcl(ifac,iw,1) = 0.0d0
enddo

but vitesse used by the calcul is always the vitesse defined in the DATA/*.xml file !

Is there something to add to force the code to use the fortran functions ?

As I've seen, one has just to add files other than fortran functions in directory DATA, (for exemple ASCII files used by fortran files), and in the code_saturne guide, the fortran files seems to have the priority on xml files !

thank you for your help

[Yvan Fournier]

Hello,

We have encountered this problem before, but only using a packaged version on Ubuntu (I even ran detailed tests on an Ubuntu machine switching between a packaged version of the library and a manually-built version, changing only the library, and this activated/deactivated the bug).

So this definitely looks like a "package" bug, not a problem in your use of the code itself...

The problem occurred on 2.0, but I had not seen it on 2.1 before. In any case, even though it is slightly more complicated, I would recommend installing version 2.2 or 2.3 either manually or with our install script from this web site, as this should solve the issue. We should also notify the debian or ubuntu maintainers of this bug in the packaging...

Best regards.

Yvan

[laurence wallian]

thank you for all your answers.

I've just followed your advices : I've installed the 2.3.2 release, and it seems to work !

Just for info., it seems better to use the *.tar.gz file (http://code-saturne.org/cms/download/2.3) instead of the *.zip file, since the last is viewed like a windows file, and some characters are not recognized (link if it was necessary to do an dos2unix command!)

I've also precised not to use cgns, in order to avoid errors... : in summary, I've launched the followings commands

Code: Select all

apt-get install pyqt4-dev-tools
tar xvfz code_saturne-2.3.2.tar.gz
cd code_saturne-2.3.2
./configure --prefix=/usr/local/code_saturne-2.3.2 --without-cgns
make
make install
chmod a+rX -R /usr/local/code_saturne-2.3.2
chmod a+x /usr/local/code_saturne-2.3.2/share/code_saturne/SaturneGUI

thank you again for your help

Best regards.

Laurence