Mechanical Solution
This container holds Solution data for an instance of ANSYS Mechanical.
Opens the Mechanical editor and attaches geometry.
Optional Arguments
To edit the solution component with default optional parameter values.
solution.Edit()
Or by specifying optional parameter values:
solution.Edit(Interactive=True)
Exit the Mechanical editor
Optional Arguments
Exports the results(*.db, *.rth, *.rmg, and *.rst) files to given DirectoryPath.
Required Arguments
This query is used to obtain the ComponentSettingsForRsmDpUpdate object for Journaling and Scripting
This query is used to obtain the ExpertProperties object for Journaling and Scripting
Query to return the reference to the container's MechanicalSystemType data entity.
Return
A reference to the requested MechanicalSystemType data entity.
Query to return the data reference to the modal options for solution to model
Return
A reference to the requested data entity.
Required Arguments
Query to return the reference to the container's MechanicalSystemType data entity.
Return
A reference to the requested MechanicalSystemType data entity.
Query to return the data reference to the static options for solution to model
Return
A reference to the requested data entity.
Required Arguments
Returns a DataReference to the Solution Settings object for this container
Return
The Data Entity containing settings for this component.
Query to return the data reference to the static options for solution to model
Return
A reference to the requested data entity.
Required Arguments
Executes a JScript or python command in the Mechanical editor.
If the Mechanical editor is not open, then the editor's GUI will not be available, causing some commands to fail. In this case, consider calling the container's Edit method to open the editor before using SendCommand.
Furthermore, if the Mechanical editor is not open, SendCommand will start the editor without the GUI, issue the specified command, and then close the editor. For multiple SendCommands, this may degrade performance.
Required Arguments
Optional Arguments
To execute some arbitrary command (in this case, causing a dialog box to appear) in the Mechanical editor:
model.SendCommand(Command="WBScript.Out(\"My Text\",true);" )
To run a JScript file already saved to disk using Run Macro from Mechanical:
setup.SendCommand(Command="WB.AppletList.Applet(\"DSApplet\").App.Script.doToolsRunMacro(\"C:\\\\macro.js\")")
Extended Component settings when solved as part of design point update via RSM Currently used for Addins with solvers that would like to take advantage of SMP
The general property that defines the user-visible name of an entity. This property is defined for all data entities but is used only in those entities that present a label in the user interface.
The number of processes that the RSM-based design point update should not exceed during execution.
A boolean flag indicating whether or not to restrict the solver to using SMP, instead of distributed parallel
Indicates whether to limit the number of processes for parallel execution.
ModalUpdateOptionsForCdbTransfer
The general property that defines the user-visible name of an entity. This property is defined for all data entities but is used only in those entities that present a label in the user interface.
Should we process the element components for the system
RBDUpdateOptionsForMechdbTransfer
The general property that defines the user-visible name of an entity. This property is defined for all data entities but is used only in those entities that present a label in the user interface.
Should we process the element components for the system
Mechanical specific simulation solution settings entity used for Journaling and Scripting. Not based on the common Infrastructure.Rsm.Queries entity.
The general property that defines the user-visible name of an entity. This property is defined for all data entities but is used only in those entities that present a label in the user interface.
StaticUpdateOptionsForCdbTransfer
The general property that defines the user-visible name of an entity. This property is defined for all data entities but is used only in those entities that present a label in the user interface.
Should we process the element components for the system