code_saturne User's Forum

user bashrc file attached

Hello,

In you .bashrc file, simply add:

alias code_saturne-4='/opt/Saturne-4.0.5/code_saturne-4.0.5/arch/Linux_x86_64/bin/code_saturne'

for exampe (you can choose a shorter alias, such as cs4 if you want).

With this, you'll be abla to call Code_Saturne 4.0 with the "code_saturne-4" (or "cs4") command, while still calling the previous (version 3.0) with the default "code_saturne" command.

Regards,

Yvan

Hi Yvanne:

Thanks a ton. I can launch gui of code saturne. No testing has been performed yet. Because I have run into a stupid problem. I upgraded to ubuntu 14.04LTS thinking that upgrades unlike windows are safer in linux. The problem now is when I launch terminal it opens for a flash and then disappears. Doesn't matter how many times i open it; independent of location and method of opening. It is not minimized even. Once my internet connection slowed down and the terminal window froze and i read repeated error messages related to code aster even though I launched a plain terminal at the desktop.

I read so much online but unfortunately I cannot find a direction. I tried login into tty (xterm) but it goes into infinite login loops.

Any help to restore to full functionality?

Hello,

This might be du to the upgrade, but possibly (though I would expect warnings, not blocking errors) to a syntax error (for example missing quote) in your bashrc.

Try temporarily moving/renaming your .bashrc to see if the error persists.

Regards,

Yvan

Hi Yvanne

Yes after moving .bashrc, terminal is stable but i cannot laaunch any of the code saturne's. What should i modify ?

Regards

.bashrc is attached.

Regards

Hello,

Your alias syntax seems OK, but you can try removing different parts of the .bashrc (as a bisection), to see what causes the issue. Also, you may want to add a newline at the end of the file (not sure it is useful, but you can try)

At worse, instead of the "cs4" alias, you can always use the full path:

/opt/Saturne-4.0.5/code_saturne-4.0.5/arch/Linux_x86_64/bin/code_saturne

Regards,

Yvan

Hi Yvan:

I followed your advice and I figured out that removing the line : source /opt/caelinux/.bashrc-CAE makes the terminal stable but then i loose all short commands and aliases of all the CAE tools which are defined in .bashrc-CAE. Which means the terminal is not sourcing the bashrc-CAE but it is correctly reading the alias line of code saturne 4. For reference, the bashrc is attached in my last post.

Can you suggest some modifications? May also be useful for users like me upgrading Ubuntu on CAE Linux.

Best Regards

PS: I have attached the .bashrc-CAE file.

Hi Yvan

Sorry to question time and time again. I ran LES simulation on cs4 in order to see if it gets stuck in the same fashion as it did in version 3. But the solver didn't run and gave the following error.

/opt/Saturne-4.0.5/code_saturne-4.0.5/arch/Linux_x86_64/libexec/code_saturne/cs_solver: error while loading shared libraries: libmpi.so.0: cannot open shared object file: No such file or directory

I have also attached 'summary' and 'run solver' files.

Since the path to libmpi has been modified; I added :
export LD_LIBRARY_PATH="/usr/lib/openmpi/lib":$LD_LIBRARY_PATH
to both .bashrc and .profile and individually too and also logged out and logged in but the solver is not reading the open MPI path. What further can be done?

I also ran code_saturne 3.0 which has user subroutines and it gave error before anything saying that GNU fortran version has changed (can't read paramx) and something to do with Python 2.7 site packages. I believe this is all due to upgrade.

Should I try to fix things or re-install CAE Linux 2011?

I will be grateful.

Hello,

The "run_sover" scripr generated inside RESU/<run_id> should contain the correct LD_LIBRARY_PATH for MPI if needed. You can always try to add it there instead of in your .bashrc.

I would avoid forcing things in .bashrc (except for an alias), as this may explain why version 3.0 does not work anymore...

Di you do the upgrade to your system after installing version 4.0 ? In this case, simply try to re-run the installation on your new system. THe upgrade may have broken version 3.0, depending on which version comes "included" with the upgrade...

Regards,

Yvan