How can you dynamically determine if an object "works" with an Analysis/environment type?

Adam R

In Ansys Mechanical scripting, is it possible to determine what objects types are "valid" in a specified analysis/environment type?

Through the Analysis object API, you can add any load/support, but that doesn't necessarily mean it's valid. For example, you can add a pressure object to a Modal analysis, but you won't be able to set the geometry location.

This mapping exists somewhere as the UI elements for a selected analysis change depending on the type.

For example, I've added a Pressure to a Modal through scripting, but this isn't possible through the UI.

Is it possible to check what is "valid" (according to the UI) in scripting?

Erik Kostson

Hi
The only way I have found is through the InternalObject State property, so it can not be guaranteed to work always (internal object).

Tried it also on a modal and static system and it gives 2 and 1 as a print out probably meaning that 1 is ok/defined and 2 is not fully defined.

All the best

Erik

model=ExtAPI.DataModel.Project.Model # refer to Model
analysis = model.Analyses[0] # change this
solution = analysis.Solution
forc=analysis.AddForce()
NS = ExtAPI.DataModel.GetObjectsByName('myfc')[0] # named sel.
forc.Location= NS
forc.Magnitude.Output.SetDiscreteValue(0, Quantity(1, "N"))
print(forc.InternalObject.State) # 1 for defined and 2 for undefined seems like