mapdl code quits with MapdlExitedError inside python function - is there a problem with nested function

[imhsaq]

I have written a code that basically works, now I wanted to intercepts some errors with try/except. To avoid too much complexity of the code I had to shift some of the code snippets to functions.
The code worked already with putting mapdl-commands inside functions, but now I wanted to nest functions to still lower levels, the code exits with MapdlExitedError. I'm not aware of any mistake in the code, so I supposed, it could be a problem with nested function.

The structure is:

main:
mapdl.launch
mapdl commands for resume, set components, 
--> def fun1:
      try: creating and evaluating surfaces
      except: call fun2
     --> def fun2:
           check for MapdlExitedError 
           mapdl.launch()
           mapdl.resume(fpFileDb, 'db')
           call fun3
           --> def fun3:
                 the first mapdl-call inside this function throws a MapdlExitedError

I did a test:
If I put this first mapdl-call inside fun2 before calling fun3, this mapdl-call is executed and the next - now first - mapdl-call inside fun3 throws the error.
--> So it seems to work until fun2 with two levels of nesting.
And what is more: in the same code I do the launch and resume within main and then call fun3 from main, this works without any problem, so fun3 itself cannot be the problem.

Is there a known limit of nested function calls or some restricted functionality?

[germa89]

It is a bit difficult to follow your question. Can you post here a minimum working example of python code so I can try to replicate it??

[imhsaq]

250213_Excerpt_Script.txt
Yes, you are right, that was a bit confusing.
I did an excerpt of my script as attached, to show the nested calls.
In main I do calls to FUN__surAvgTemp and FUN__surAvgStress, Both do essentially the same, the one an averaging of temperature and the other of stresses respectively.
In their except-blocks they have a call to FUN__checkMapdlExitedError, where I try to reinitiate the state in case of error.
This function itself gets a call to FUN__setComponents and that's where the programme quits at the first mapdl-statement.
FUN__setComponents is not the problem, as it is called in main without problems.
What I did do: I replaced all calls of FUN__setComponents with the code itself and with thus reducing the nesting level of function calls, the programme continues working.
So my conclusion was that there is a restriction as to nesting functions.

My problems did not end with that, as you can see in my other post, as the way I do the catching of the error does not work either.
But I think it is better to attach the same code excerpt to my second post and elaborate on this in more detail there.

[germa89]

I did try your code and most of the parameters are not defined, for instance, the arguments of FUN__setComponents:

    mapdl.resume(fpFileDb, 'db')
    FUN__setComponents(cmBladeName, cmDiscName, matIdBlade, matIdBladeTbf, matIdDisc, matIdDiscTbf)
    mapdl.file(fpFileRth, 'rth')

Hence I cannot do any testing with that file.

I'm quite confident that PyMAPDL supports many levels of function nesting because we do have them already. Additionally, MAPDL is not aware of those functions (it just recibes the commands), hence I suspect your problem arise from an interaction between those commands, rather from the nesting itself.

To debug this, I will need the complete code. Please put the code in a python file and make sure you can replicate the same error by running python my_python_script.py.

[germa89]

Ok... Guessing a bit here since I do not have the actual code.

When PyMAPDL raises an MapdlExitedError it automatically sets mapdl.exited to return True. Hence any subsequent mapdl calls in the exception clause should raise MapdlExitedErrors. It should automatically closes MAPDL, but checking the code, that might be an actual bug. It should close it, but it doesn't.

Hence, any code you plan to execute in the exception clause, should be executed after you have started a new instance of MAPDL.

Now, why MAPDL exited... I dont know. I will really need the full code. If you are sure MAPDL is not exited, you could try to do something like:

except:
    mapdl._exited=False
    # mapdl calls

Also I would consider to be a bit more explicit on the type of exceptions you are trying to catch here, so you make sure you calling the right shots after it.

[imhsaq]

I will attach the code of the whole program, perhaps it will clarify a bit more, how I did catch the exceptions. However, it will not be executable, as it will need the corresponding input files, which I cannot provide.
_250317_postThermalStructural.txt
I tried to get the exact type of exception, but only succeeded in getting MapdlExitedError. I couldn't find explicit error messages in the online PyMAPDL pages. Where can I find more information about PyMAPDL errors?