Unhandeled exception when using get_value to retrieve 'twsi' values. about pymapdl HOT 6 CLOSED

I see the error:

 *** WARNING ***                         CP =      17.192   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 *** WARNING ***                         CP =      17.192   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 *** WARNING ***                         CP =      17.193   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 *** WARNING ***                         CP =      17.193   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 *** WARNING ***                         CP =      17.193   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 *** WARNING ***                         CP =      17.193   TIME= 11:37:20
 Material for this node can not be determined.  No failure criteria      
 calculations done at this node in POST1.                                

 ************************************************************************
 The number of ERROR and WARNING messages exceeds 20.                    
 Additional messages suppressed.  See ( /local/simulation/file.err )     
 for suppressed messages.                                                
 ************************************************************************

 *GET  __TEMP__  FROM  NODE      9  ITEM=S    TWSI  VALUE=  225.000000

but surprisingly the value is correct 225.00.

I am not sure how to get rid of the warnings without silence them forever.

from pymapdl.

@mikerife @koubaa

I have a question regarding design:

If my model is clear (no nodes defined), the following query (get maximum define node ID):

mapdl.get_value("node", 0, "num", "maxd")

should:
a) Return 0.0?
b) Raise a No nodes defined error?

It should be noticed that MAPDL prints already a NOTE message:

There are no NODES defined

from pymapdl.

@mikerife @koubaa

I have a question regarding design:

If my model is clear (no nodes defined), the following query (get maximum define node ID):

mapdl.get_value("node", 0, "num", "maxd")

should: a) Return 0.0? b) Raise a No nodes defined error?

It should be noticed that MAPDL prints already a NOTE message:

There are no NODES defined

I would prefer that 0.0 be returned but also keep the Note message.

from pymapdl.

How to keep the note message? We currently dont store any.

There are about 3 type of messages in MAPDL (error, warning and note), which we have, quite relaxed, related them to:

But as I said, this relationship is not enforced 1-to-1. Because MAPDL behaviour on Error is not very standarized. Some errors make MAPDL to exit, sometimes, it just keep going. Some errors are very redundant.

I feel I should probably enforce the following:

But I think it could make PyMAPDL very verbose.

Other option could be trying to parse everything from MAPDL and create a sort of message queue. We can raise errors from there, and let the user check this queue for the rest of the messages.
But, MAPDL messages are not super standardised (sometimes you don't know when the error message ends).

from pymapdl.

@germa89
Adding a "FCTYP,ADD,TWSI" to the input file is the...more correct approach and does away with the issue. Sorry I missed that yesterday. Thing to watch out for is FCTYP is a post processing command while FC can be used in either /prep7 or /post1. I prefer to keep commands together that act together, if possible, so I redid the script and moved the FC to post processing and now the script runs as expected.
MIke

from pymapdl.

Let's keep approach A.

But definitely, this question about the messsages will keep popping up in the future.

from pymapdl.