where can I get test input files to verify code saturne?

[spiffly]

Greetings,

I just installed Code Saturne on our cluster for one of our users who has requested it. Where can I find a set of input files to run a test and verify the install succeeded?

Kind Regards,

edit:

*version 2.3.3 (the 2.3 release from the website)
*compile.log - I searched the entire code-saturn dir tree and there is no 'compile.log', only 'config.log', which I've attached. (I looked after running make && make install)
*preprocessor.log - again, I searched the entire tree for 'preprocessor.log', and there isn't one. Am I getting the filenames wrong here?
*input files - that's what I'm asking for:-)

[guingo]

Hi,

if I may anticipate the most likely upcoming question by Yvan or Jacques, I guess you will have to indicate the version of the code you refer to

(see here: http://code-saturne.org/forum/viewtopic.php?f=2&t=7)

Best regards
Mathieu

[spiffly]

Ah, sure. I'll edit my post above and provide all those details.

I suppose I hadn't included them because I figured the question is really a general one: Is there a suite of tests, or generic test files or something for validating any version of code saturne?

[spiffly]

I can also add that the User Guide for 2.3 says:

We assume in this section that the user has at his disposal the calculation data file (calculation set
up) or already prepared it following for instance the step-by-step guidance provided in Code Saturne
tutorial.

But I can't find this tutorial anywhere.

[Yvan Fournier]

Hello,

The config.log is in your build directory, but is important mainly if you detect a problem with your installation.

The tutorial test case data and meshes are somewhere in the "examples" directory. Meshes have a ".des" extension, and are read by an internal reader, so they won't test the installation of MED or CGNS support (for CGNS, you can find example meshes on the CGNS web site; just pick a 23D example).

To test the installation, I would mainly run

code_saturne compile -f -t

to check that user subroutines can be compiled and the code re-linked (you should see a link command at the end)

You can test the preprocessor by running it on a few meshes:

<install_prefix>/libexec/code_saturne/cs_preprocess --no-write <mesh>

and test the kernel is linked correctly:

<install_prefix>/libexec/code_saturne/cs_solver -h

If you are using MPI, you may also test:

mpiexec -n 2 <install_prefix>/libexec/code_saturne/cs_solver --log 0

with no other options; with no input, the code will fail, so you can remove the "error" file afterwords, but in the log output, you'll be able to check the the number of MPI processes is correct.

If you need a post-install stage (SYRTHES coupling or queuing system), then you need to setup a full case. The data from the tutorials needs to be placed in a true case structure (generated using "code_saturne create"), but tutorial data for 2.3 are not quite up to date (the ones for 3.0 either, but they will be commited to SVN very shortly).

The tutorial is installed with the code; run "code_saturne info" for more.

Regards,

Yvan

[spiffly]

Hi Yvan,

Thanks for your response.

The config.log is in your build directory, but is important mainly if you detect a problem with your installation.

Yes, I had found the config.log file. As you can see, I had attached it to my OP. My point was that the guidelines state to attach a 'compile.log' file, which I couldn't find.

The tutorial test case data and meshes are somewhere in the "examples" directory. Meshes have a ".des" extension, and are read by an internal reader, so they won't test the installation of MED or CGNS support (for CGNS, you can find example meshes on the CGNS web site; just pick a 23D example).

I found them in:

Code: Select all

installer/ncs-2.0.6/examples

To test the installation, I would mainly run

code_saturne compile -f -t

to check that user subroutines can be compiled and the code re-linked (you should see a link command at the end)

You can test the preprocessor by running it on a few meshes:

<install_prefix>/libexec/code_saturne/cs_preprocess --no-write <mesh>

compile seemed to work fine, but for cs_preprocess --no-write doesn't seem to exist. Ended up doing this, which worked:

Code: Select all

cs_preprocess -sc -m 1-simple_junction/mesh/downcomer.des

and test the kernel is linked correctly:

<install_prefix>/libexec/code_saturne/cs_solver -h

If you are using MPI, you may also test:

mpiexec -n 2 <install_prefix>/libexec/code_saturne/cs_solver --log 0

with no other options; with no input, the code will fail, so you can remove the "error" file afterwords, but in the log output, you'll be able to check the the number of MPI processes is correct.

hmm. I'm not seeing any text mentioning processes in the failure output, but I'm not sure I know what I'm looking for here.

The tutorial is installed with the code; run "code_saturne info" for more.

passing an 'info' arg to code_saturne doesn't seem to work:

Code: Select all

$ code_saturne info
Usage: code_saturne info [options]

Options:
  -h, --help            show this help message and exit
  -r <pdfreader>, --reader=<pdfreader>
                        define a pdf reader
  -g <guide>, --guide=<guide>
                        open a manual [refcard, user, theory, tutorial, developper]
  --version             print Code_Saturne version number

[Yvan Fournier]

Hello,

Are you sure you don't have an older version of the code installed somewhere ? The syntax for cs_preprocess that worked for you seems to be the one from version 2.0. The cs_preprocess for versions 2.3 and 3.0 are in libexec/code_saturne, so it is not in the PATH (hence, you need to use the absolute path).

For "code_saturne info", add "-g tutorial".

Regards,

Yvan

[spiffly]

ah, yes I was mixing up versions, and thanks for the clarification!