Bug located in MPCOPY and other commands which has unused field about pymapdl HOT 5 OPEN

The /post26 command ADD and QUOT still have problems due to multiple blank fields on the command. Also if the data is complex then QUOT using the NAME field returns machine zeros for complex variables.

from pymapdl.

Interesting... it seems to work for me:

>>> mapdl.mat(1)
>>> mapdl.mp("SONC", 1, 1500)  # sonc in m/s
>>> mapdl.mp("DENS", 1, 1000)  # Density in kg/m3
>>> mapdl.mpcopy(1, 2)

COPY MATERIAL        1  DENS  TO MATERIAL        2

 COPY MATERIAL        1  SONC  TO MATERIAL        2

The /post26 command ADD and QUOT still have problems due to multiple blank fields on the command. Also if the data is complex then QUOT using the NAME field returns machine zeros for complex variables.

I will need an example for testing and debugging this.

from pymapdl.

There is an unused/beta field in MPCOPY. So the command should really be mapdl.mpcopy('', 1, 2)

from pymapdl.

For reference: #3026 (comment)

GitHub

What should we do with the undocumented arguments (``--``) ? · ansys pymapdl · Discussion #3026

Given this APDL command: MPCOPY,--,matf,matt where: -- is an "unused" field or, in pythonic terms, an undocumented argument. This undocumented argument can serve different purposes: Maybe it is a d...

from pymapdl.

This issue is locked until #3026 gets closure.

GitHub

What should we do with the undocumented arguments (``--``) ? · ansys pymapdl · Discussion #3026

Given this APDL command: MPCOPY,--,matf,matt where: -- is an "unused" field or, in pythonic terms, an undocumented argument. This undocumented argument can serve different purposes: Maybe it is a d...

from pymapdl.