Loads / Boundary Conditions Legend Ordering

Hello,

I am exporting various data from Ansys Mechanical in order to automatically generate reports. One part of this to export a screenshot including all of the loads and boundary conditions, then write details on each. I have no issue taking the screenshot and accessing the data on each load and boundary condition information, but the order shown on the legend does not always align with the order in the tree. So, I currently can't predict which load/boundary condition has which label.

Is there a way to read the legend to determine which boundary condition has which label? What's interesting is that on my machine, the labels are always in tree-order (which is my current implementation) but for my colleague, they aren't always in that order.

Thank you,

Justin

Find more posts tagged with

Mechanical

scripting

Accepted answers

All comments

AlexGh

Hi Justin!

What's interesting is that on my machine, the labels are always in tree-order (which is my current implementation) but for my colleague, they aren't always in that order.

Perhaps your colleague added the loads in a different order (for example, weight first and then gravity)? The placement of the labels depends on the position of the object in the project tree.

AlexGh

You can create your own labels in the graphics area. Check out this link:
https://discuss.ansys.com/discussion/1454/how-do-i-create-an-annotation-using-act

JustinF

@AlexGh said:
Hi Justin!

What's interesting is that on my machine, the labels are always in tree-order (which is my current implementation) but for my colleague, they aren't always in that order.

Perhaps your colleague added the loads in a different order (for example, weight first and then gravity)? The placement of the labels depends on the position of the object in the project tree.

Hi,

On my machine, the placement of the labels matches the position of the object in the project tree, as you say. I thought this was always the case (and if it were, I have no problem). But on his machine, that's not true: the labels are in a different order for some reason. Could this be a bug on his installation and it should typically be OK to assume the labels match the tree position?

Thank you,

Justin