CodeAster 9.4 in CAELinux2009

Hello,

First of all I would like to thank the admin for all the work he has put into publishing CAELinux2009 in Ubuntu 8.04 64 bit especially with OpenMP support for multi-core CPUs. This a trail I have been trying to traverse for a long time, but had not quite succeeded at it. Thank you very, very much!

So, having cleanly installed it on a hard drive of quad-core Intel PC with 4GB RAM I tried a problem I had run previously on STA9.3 on this same hardware. I also updated it with all the currently available updates (i.e. "sudo aptitude safe-upgrade"). But CAELinux2009's CodeAster 9.4 gives errors such as:

1. ENDED F_(ERROR) in the ASJOB status window of ASTK

2. A partial error log (Error.zip) is attached in my next message:

The results file (fort.80) is copied as *res.med and a cursory look using Salome 4.1.4 post processing seems okay.

Why am I getting an abnormal end to the run? Has anybody else encountered this problem? Thank you for any feedback or suggestions. Since the mesh is proprietary as also some of the analysis, I can possibly post a similar comm file, but not the mesh.

Regards
JMB<br /><br />Post edited by: JMB, at: 2009/07/08 05:47

The Error.zip showing a portion of the error log is attached...

JMB

Hi JMB,
I found problems too when I tried to run old case on the new caelinux. I did't understand if it was a permission problem, or simply the problem is that the path to the asteru executable is different so the old case does not find the new executable. The shortest solution was to create a new case with the old comm file and mesh, and it worked. It was a work of a few minutes.

Please note that I have my analisys files on a separate partition that I didn't format during the installation of the new caelinux, even if I corrected the permission with chown and chmod.

Hello Alessendro,

Thank you for your reply and for sharing your experience. I will try your suggestion and post my findings.

Regards,
JMB

PS: I tried your suggestion of re-creating the *.astk file, and re-submitting the problem, but that does not make the error go away. The analysis does seem to complete and a *.res.med file is produced.<br /><br />Post edited by: JMB, at: 2009/07/08 23:28

[Solved]

This is due to a bug in 9.4, which I am told has been fixed in CodeAster 10.0. The workaround is to remove the FORMAT_HDF of the FIN command.

JMB