mapdl.get() gives an empty string if we have mapdl.nopr() issued before mapdl.get()

The below mapdl.get() command should get the number of result sets in the rst file. In the below command deck, Anzset_python is correctly printed (float).

mapdl.post1()
mapdl.file(fname="Simple_Cantilever",ext="rst")
mapdl.set(1, 1)
#mapdl.nopr()
Anzset_python = mapdl.get(par="Anzset_mapdl", entity="ACTIVE", entnum="", item1="set", it1num="nset")
print('Number of sets: Python Variable -->', Anzset_python)

Number of sets: Python Variable --> 1.0

However, when I activate the mapdl.nopr() command, Anzet_python gives an empty string. Is this a bug?

mapdl.post1()
mapdl.file(fname="Simple_Cantilever",ext="rst")
mapdl.set(1, 1)
mapdl.nopr()
Anzset_python = mapdl.get(par="Anzset_mapdl", entity="ACTIVE", entnum="", item1="set", it1num="nset")
print('Number of sets: Python Variable -->', Anzset_python)

Number of sets: Python Variable --> 

[akaszynski]

What about Query? Is it also likely to be deprecated?

The Query methods are unlikely to be deprecated in the near future as they perform several valuable, but we’re going to fix the documentation to use mapdl.queries instead of from ansys.mapdl.core import Query.

Agree in regards to using get_value rather than get. @jgd10, can you refactor this?

[akaszynski]

The legacy method get relies on printing an output and then parsing the text and will likely be deprecated (or moved) as we work to expose more features using modern, direct methods. The get_value method does this as it directly requests the data from the server, thus avoiding writing any intermediate text.

In the meantime, I’d do the following:

• Use get_value rather than get unless you need to store the parameter within MAPDL and grab it at the same time.
• @germa89, make /NOPR a unsupported when issued from mapdl.nopr and run() (really, just capture the request at run). We can allow it to be run from _run just in case we need to issue it temporarily, but I think that you’re right, there overlap already with mute.