INQUIRE the RST file behaviour

[germa89]

Hi all,

I find the behavior of the INQUIRE a bit weird regarding querying the RST file.

If you have an newly MAPDL instance and you dont issue anything just:

>>> from ansys.mapdl.core import launch_mapdl
>>> mapdl = launch_mapdl()
>>> mapdl.inquire("", "rstfile")
''
>>> mapdl.inquire("", "rstext")
''

That is ok, but then:

>>> mapdl.post1()
>>> mapdl.inquire("", "rstfile")
'file'
>>> mapdl.inquire("", "rstext")
'rst'

However no file has been generated.

So, it seems that while we are in no processor (after mapdl.finish()) the inquire will return None.

But once we have entered in a processor, it will return something.

If we go back to no-processor:

>>> mapdl.finish()
>>> mapdl.inquire("", "rstfile")
'file'
>>> mapdl.inquire("", "rstext")
'rst'

We keep obtaining file and rst. I guess those variables are not initialized until we enter in post1.
In fact, it does not work with /SOLU:

>>> mapdl.clear()
>>> mapdl.inquire("", "RSText")
''
>>> mapdl.inquire("", "RSTFILE")
''
>>> mapdl.slashsolu()
>>> mapdl.inquire("", "RSTFILE")
''
>>> mapdl.inquire("", "RSText")
''

Nor with /post26:

>>> mapdl.inquire("", "RSText")
''
>>> mapdl.inquire("", "RSTFILE")
''
>>> mapdl.post26()
>>> mapdl.inquire("", "RSTFILE")
''
>>> mapdl.inquire("", "RSText")
''

So I wonder if this is consistent enough.

We could force (anytime we use mapdl.inquire("", "RSTFILE") to go into /post1 to obtain the right values.

In that case, mapdl.inquire("", "RSTFILE") will never return None, but I think this is more consistent.

[germa89]

mmhh... I think this is trivial..... I'm going to implement the proposed changes (never return None, by always going into post1 to do the inquire).

Leaving this for possible feedback and future tracks.