About mapdl.slashsolu and mapdl.solution

[germa89]

We have currently mapdl.slashsolu which in my opinion is an important command (it is used everywhere), but the "slash" part is reaally bothering me (probably I'm not the only one).

Current implementation

Currently mapdl.solution return an object which provides some information about the solution for example, number of substeps, maximum number of DOF, etc.

You can check the code here

Implementation

To compatibilise this, we could just implement the __call__ submethod, this __call__ method will call mapdl.slashsolu().

class Solution:
    def __call__(self):
        return self._mapdl.slashsolu()

Do you think it is a good idea?

Pinging @ansys/pymapdl-developers @ansys/pymapdl-collaborators @ansys/pymapdl-maintainers

[mcMunich]

General comment from the APDL side: /SOLU is just used to go into the Solution processor. In a typical APDL script you don't expect any information to be returned for the /PREP7, /SOLU... So the mapdl.solution is a clear improvement. But to keep old APDLers happy, it would be nice to also have slashsolu (and then just go into the solution processor).
My vote would be for both to do the same thing with one returning information.

[germa89]

Thank you for the feedback.

Both:

mapdl.solution()
# and
mapdl.slashsolu()

will return the same "Enter in solution processor" message.

[mikerife]

Hi @germa89 as long as we don't get rid of 'slashsolu' I really like the concept. And I agree with everything @mcMunich said!

[germa89]

The mapdl.slashsolu will still be available.