Personal tools
You are here: Home Forum Other... (new forum, problems, etc.) Can't see any post-processor results

Can't see any post-processor results

Up to Other... (new forum, problems, etc.)

Can't see any post-processor results

Posted by Luís Miranda at January 09. 2010
After I solve a problem using code Aster, 
the post processor doesn´t appear and I can't see any results,
even though I know the program has made calculations.

I have the following error, maybe the cause of my problem:
MEDouvrir.c [53] : Impossible d'accéder aux fichier :
MEDouvrir.c [54] : nom = "fort.80"
MEDouvrir.c [53] : Impossible d'accéder aux fichier :
MEDouvrir.c [54] : nom = "fort.80"

or: error during copying fort.80 - file doesn´t exist.

It is also said that astk server 1.71 version is different from astk client 1.6.2. 
I don´t if that might be causing my problem.

I would be very grateful if you could help me on this, because I need to be able to see the results.

Thanks in advance for any help.




Re: Can't see any post-processor results

Posted by Cacciatorino at January 09. 2010

Are you using Salome or Salome-Meca?

 

By the way, almost certainly there is an error in your comm file. Can you post a zip file containing the mesh (med format) and the comm file?

Re: Can't see any post-processor results

Posted by Luís Miranda at January 11. 2010

Here is the other one.

 

Attachments

Re: Can't see any post-processor results

Posted by Luís Miranda at January 11. 2010

I'm using Salome version 4.1.4.

I'll post two zips with very simple examples, from which I can't get the results.

 

Thank you

Attachments

Re: Can't see any post-processor results

Posted by Cacciatorino at January 13. 2010

Previously Luís Miranda wrote:

Here is the other one.

 

This test runs on my ws without any modifcation, just created an ASTK profile to run the test from astk gui.

Attachments

Re: Can't see any post-processor results

Posted by Cacciatorino at January 13. 2010

Previously Luís Miranda wrote:

I'm using Salome version 4.1.4.

I'll post two zips with very simple examples, from which I can't get the results.

 

Thank you

 

This test does not run due to this error:

 

<EXCEPTION> <MODELISA5_95>                                                                     !

vous avez utilise le mot cle orie_peau_2d alors que le probleme est 3d. utilisez orie_peau_3d

Re: Can't see any post-processor results

Posted by Cacciatorino at January 13. 2010

Previously Luís Miranda wrote:

I'm using Salome version 4.1.4.

I'll post two zips with very simple examples, from which I can't get the results.

 

Thank you

 

One more thing:

 

Aster complains about the fact that some groups have a too long name: grousp names longer than 8 characters are not allowed in Aster.

Re: Can't see any post-processor results

Posted by Cacciatorino at January 13. 2010

I attach the astk profile that I used and the message file about the diagnostic of Aster.

Re: Can't see any post-processor results

Posted by Cacciatorino at January 13. 2010

I attach the astk profile that I used and the message file about the diagnostic of Aster.

Attachments

Re: Can't see any post-processor results

Posted by Luís Miranda at January 13. 2010
Do you have this error in the dam example?
MEDouvrir.c [53] : Impossible d'accéder aux fichier :
MEDouvrir.c [54] : nom = "fort.80"
MEDouvrir.c [53] : Impossible d'accéder aux fichier :
MEDouvrir.c [54] : nom = "fort.80"

Because if you don't have, it may be the cause of my problem. Do you know how to fix it?

If you have it as well, I don't understand why I can't get the results because everything seems to be ok.


Re: Can't see any post-processor results

Posted by DAVID Gilles at January 13. 2010

Dear Luis,

Don't worry about this message, this is not an error in processing your results.

Here is the explanation from Vadim Sandler:

"The mentioned message is printed by MEDouvrir() function called from MED_Factory.cxx, GetVersionId() function that, in its turn, is called from the CrWrapper() function. Here MED_Factory tries to guess about the version of the MED file being opened.

The problem is that MED (as HDF-based file format) supports appending of the data to the existing MED file (to put several meshes and or fields to the same file). And MED wrapper cannot know for what reasons the file is being opened (i.e. should be re-written or it is opened for appending).

That's why actual file removal (if it already exists and user confirms its re-writing in the "Export to MED" dialog box) is done in the SMESH engine (SMESH_Mesh_i.cxx, PrepareForWriting() function).

Thus, if user needs to avoid mentioned warning message raised by med library, he/she needs just to build med library without diagnostic output (./configure --disable-mesgerr)."

Regards,
Gilles


Quick reply
URLs will be automatically hyperlinked. Basic HTML tags are OK.
Powered by Ploneboard
History
Activate by Luís Miranda on Jan 09, 2010 03:40 AM
Document Actions