Messaging¶
Messaging commands are available only if Abaqus/CAE is run interactively using the GUI.
Other Classes¶
- class DataObject[源代码]¶
基类:
object
An instance of the DataObject object is passed to each callback.
The DataObject object has no methods. The members of a DataObject object depend on the type of the object. All DataObject instances have the following members, regardless of type:
备注
Member Details:
-
attempts : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the number of attempts made to reach equilibrium during this step.
-
clientHost : --is-rst--:py:class:`str` =
''
[源代码]¶ A String specifying the host name of the machine that is running the analysis.
-
clientName : --is-rst--:py:class:`str` =
''
[源代码]¶ A String specifying the name of the client that responded to the callback function. Possible values are BatchPre, Packager, Standard, Explicit, and Calculator.
-
dof : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the degree of freedom requested for monitoring the output.
-
equilibrium : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the number of equilibrium iterations made during this increment.
-
file : --is-rst--:py:class:`str` =
''
[源代码]¶ A String specifying the full path of the output database.
-
increment : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the increment of the analysis.
-
iterations : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the number of iterations in the step.
-
node : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the node number requested for monitoring output.
-
nset : --is-rst--:py:class:`str` =
''
[源代码]¶ A String specifying the node set specified for monitoring output.
- phase : --is-rst--:py:class:`~abaqus.UtilityAndView.SymbolicConstant.SymbolicConstant`[源代码]¶
A SymbolicConstant specifying the phase of the analysis. Possible values are BATCHPRE_PHASE, PACKAGER_PHASE, STANDARD_PHASE, EXPLICIT_PHASE, CALCULATOR_PHASE, and UNKNOWN_PHASE.
-
processId : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the process ID of the analysis product.
-
severe : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the number of severe discontinuity iterations completed during this increment.
-
step : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the current step number. Step number 1 corresponds to the first step.
-
stepId : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the ID of the step.
-
stepTime : --is-rst--:py:class:`float` | :py:obj:`None` =
None
[源代码]¶ A Float specifying the step time corresponding to the current increment.
-
threadId : --is-rst--:py:class:`int` | :py:obj:`None` =
None
[源代码]¶ An Int specifying the thread ID of the analysis product. Threads are used for parallel or multiprocessing; in most cases threadId is set to zero.
-
time : --is-rst--:py:class:`float` | :py:obj:`None` =
None
[源代码]¶ A Float specifying the total time corresponding to the monitor data.
-
timeIncrement : --is-rst--:py:class:`float` | :py:obj:`None` =
None
[源代码]¶ A Float specifying the time increment used in the current step.
-
attempts : --is-rst--:py:class:`int` | :py:obj:`None` =
- class MonitorMgr[源代码]¶
基类:
object
An instance of the MonitorMgr object is created when you import the abaqus module. No other instance of the MonitorMgr object is required. (This MonitorMgr object is not to be confused with the degree of freedom (DOF) monitor that is constructed from the Step object.)
备注
This object can be accessed by:
monitorManager
备注
Member Details:
-
addMessageCallback(jobName, messageType, callback, userData=
''
)[源代码]¶ This method specifies a callback function that will be called when the specified message is received from the analysis product. For more information, see An example of a callback function.
- 参数:¶
- jobName¶
A String specifying the name of the job to be monitored or the SymbolicConstant ANY_JOB.
- messageType¶
A SymbolicConstant specifying which message type will call this callback. Possible values are:
ABORTED
ANY_JOB
ANY_MESSAGE_TYPE
COMPLETED
END_STEP
ERROR
HEADING
HEALER_JOB
HEALER_TYPE
INTERRUPTED
ITERATION
JOB_ABORTED
JOB_COMPLETED
JOB_INTERRUPTED
JOB_SUBMITTED
MONITOR_DATA
ODB_FILE
ODB_FRAME
SIMULATION_ABORTED
SIMULATION_COMPLETED
SIMULATION_INTERRUPTED
SIMULATION_SUBMITTED
STARTED
STATUS
STEP
WARNING
- callback¶
A Python function to be called. The interface definition of the callback function is def onMessage(jobName, messageType, data, userData) jobName is a String. messageType is a SymbolicConstant with possible values as listed previously for the addMessageCallback method. data is a DataObject object. userData is the object passed as the userData argument to the addMessageCallback method.
- userData=
''
¶ Any Python object or None. This object is passed to the callback function.
- checkMonitorStatus()[源代码]¶
This method raises a MonitorError exception if the monitoring status is not ENABLED.
- 抛出:¶
MonitorError -- Status is not ENABLED
- removeMessageCallback(jobName, messageType, callback, userData)[源代码]¶
This method removes a callback function. You specify the callback function to remove using the same arguments you used to add the callback.
- 参数:¶
- jobName¶
A String specifying the name of the job to be monitored or the SymbolicConstant ANY_JOB.
- messageType¶
A SymbolicConstant specifying which message type will call this callback. Possible values are: - ABORTED - ANY_JOB - ANY_MESSAGE_TYPE - COMPLETED - END_STEP - ERROR - HEADING - HEALER_JOB - HEALER_TYPE - INTERRUPTED - ITERATION - JOB_ABORTED - JOB_COMPLETED - JOB_INTERRUPTED - JOB_SUBMITTED - MONITOR_DATA - ODB_FILE - ODB_FRAME - SIMULATION_ABORTED - SIMULATION_COMPLETED - SIMULATION_INTERRUPTED - SIMULATION_SUBMITTED - STARTED - STATUS - STEP - WARNING
- callback¶
A Python function to be called; it must be the same as the callback argument specified in the original call to addMessageCallback.
- userData¶
Any Python object or None; it must be the same as the userData argument specified in the original call to addMessageCallback.
-
addMessageCallback(jobName, messageType, callback, userData=