Description of the modifications
This is a grammatic or documentation issue. Since mechdpf exists in Mechanical, there are name conventions used in Mechanical that differentiate from what dpf uses and that is causing confusion.
The problem is scale in dpf.
In Mechanical, we have a drop down button in the results tab above to scale results. That will increase the scaling in the images generated for the various results. That capability pre-exists pydpf.
If you try to scale a result in mechdpf using the scale operator, I am guessing the numerical value is scaled, but the visualized result is not scaled.
The expectation of users is that a scaling function in mechanical will change the graphic result scaling. And no matter what the dev teams want to believe, the customers have a right to expect that a description/word used in the same interface (mechanical) has the same meaning and function.
Neither is right or wrong, scaling can be interpreted both ways. But if you read some of the 'solutions' on the dev forum, you will understand that users have the mechanical definiton in mind and are perplexed when the mechdpf result does not scale when using a scale operator.
It is up to one team or another to decide how to differentiate this, but the confusion will remain, along with customer frustration, if the difference is not clear.
Useful links and references
Just look for the questions regarding scaling in the dev forum to see the confusion.
Description of the modifications
This is a grammatic or documentation issue. Since mechdpf exists in Mechanical, there are name conventions used in Mechanical that differentiate from what dpf uses and that is causing confusion.
The problem is scale in dpf.
In Mechanical, we have a drop down button in the results tab above to scale results. That will increase the scaling in the images generated for the various results. That capability pre-exists pydpf.
If you try to scale a result in mechdpf using the scale operator, I am guessing the numerical value is scaled, but the visualized result is not scaled.
The expectation of users is that a scaling function in mechanical will change the graphic result scaling. And no matter what the dev teams want to believe, the customers have a right to expect that a description/word used in the same interface (mechanical) has the same meaning and function.
Neither is right or wrong, scaling can be interpreted both ways. But if you read some of the 'solutions' on the dev forum, you will understand that users have the mechanical definiton in mind and are perplexed when the mechdpf result does not scale when using a scale operator.
It is up to one team or another to decide how to differentiate this, but the confusion will remain, along with customer frustration, if the difference is not clear.
Useful links and references
Just look for the questions regarding scaling in the dev forum to see the confusion.