Errors, Warnings and Other Messages
Contents
Introduction to AnyBody's Message System
In AnyBody version 2.0, a new system for sending output messages to the user
was introduced. This system provides each messages an id, the Message
Id, which can be used as reference for finding further information. Most
"messages" contains two messages a short and an extended. The shorter is
the one that is send to the user during the execution of operations in AnyBody,
whereas the extended one is intended to provide more information to the user
who is not familiar with the particular issue. Both short and extended version
of all messages are found in this manual ordered according to their
Message Id.
Short messages are typically displayed to AnyBody's Report
View in the bottom of the frame of the GUI application or send to
stdout from the console application. The begining of the message shows the
Message Id. In the GUI application, double-clicking the Message Id will open a
dialog box with the extended message. Issues associated with special views of
GUI application, such as Model View and Chart Views, will typically be
displayed in these view.
The new message system also includes new logging facilities. As in previous
version, the Report View simply displays the contents of AnyBody main output
log file. The location of this file has now moved from the AnyBody
installation directory to a user specific Application Data directory (e.g.
C:\Documents and Settings\<UserName>\Application Data\AnyBody
Technology\AnyBody.2.x.x). The log file is now named AnyBody.output.log or
AnyBody.XX.output.log, where XX is a number allowing for multiple sessions
of AnyBody running at the same time with their own log file. Additionally,
the new message system introduces a new log file, called AnyBody.full.log or
AnyBody.XX.full.log. This is a socalled full log file, that contains the same
as the ordinary log plus occasionally additional information. This additional
information in the full log is deemed less important for typical
operations in AnyBody and is in this way filtered out of the normal infomation
view; however, in problematic case, the additional information may be
valuable to solve a given problem.
All messages are catagorized into severity groups that defines how the
system treats the given situation.
| Severity Level |
Output |
Operation |
Description |
| Notice |
Standard output* |
Continues |
Not used in AnyBody, version 2.0. |
| Warning |
Full log only |
Continues |
A warning that is typically not important for your work unless you are having
particular problems. |
| Important Warning |
Standard output* |
Continues |
An impotant issue that allows you to continue but requires your
attention. |
| Error |
Standard output* |
Continues, but operation will fail |
An issue that enforces the system to stop the given operation eventually, but
it may continue beyond the point of the problem. |
| Fatal Error |
Standard output* |
Stops |
An issue that enforces the system to stop the given operation at once. |
| Fatal System Error |
Standard output* |
Stops** |
A fatal errror has occured which is not properly handled by the system and
may therefore lead to unpredictable results. |
*"Standard output" means the Report View (and thereby AnyBody.output.log), or
a particular View in the GUI application, as well as the full log for
AnyBody's GUI application. For the console application, it is
simply outputing to the command prompt evironment.
**Such errors may crash the system eventually and in any case restarting
AnyBody is recommened.
All messages belong to a group, socalled message groups, depending on the
module that handles the particular type of message. A group is defined as
covering a certain topic and the groups are ordered hiarcially allowing general
groups to consist of one or more subgroups in multiple levels. Each groups
is given a short name (acronym) consiting of typically three letters. Both
message and group ids are assembled of these acronyms, i.e., the
particular group acronym preceeded with its supergroup's id. Message ids
have an addtional numeric identifier that defined its positon in its group.
Messages Groups
| Group name |
Description |
| SYS |
Messages sent from basic system functions. |
| SCR |
Messages sent from the AnyScript kernel. |
| SCR.SCN |
Messages from the AnyScript file scanner. This includes for instance basic syntax error. |
| SCR.PRS |
Messages from the AnyScript parser. |
| SCR.EXP |
AnyScript Expression messages. This message group covers basic issues related to mathematical expression. |
| SCR.EXP.FUN |
Particular expression messages related to AnyScript functions (i.e. objects derived from AnyFunction). |
| OBJ |
Messages send from classes the AnyScript class structure, which are not considered to be fundamental classes. Such classes are all derived from AnyFolder. |
| OBJ.FILE |
Messages send from AnyFile objects. |
| OBJ.CHT |
Messages send from the AnyChart module. |
| OBJ.DES |
Messages from classes in the design module of AnyBody, which means that they are related to AnyDesStudy, either by derivation or usage. |
| OBJ.MCH |
Messages from classes in the mechanical modules of AnyBody. These classes are derived from AnyMechStudy or AnyMechObject. |
| OBJ.MCH.KIN |
Kinematically related messages from mechanical modules. |
| OBJ.MCH.DYN |
Dynamically (kinetically) related messages from mechanical modules. |
| OBJ.MCH.MUS |
Messages from mechanical modules that are particularly related to musculoskeletal modeling. |
| OBJ.MATH |
Messages from basic mathematical/numerical routines. |
| OBJ.LIB |
Messages from routines in external libraries. |
| OBJ.LIB.OOS |
Messages from the OOSol library. |
| SET |
Messages regarding settings. |
| SET.STY |
Messages regarding style settings. |
Messages Descriptions
SYS1
(Fatal error)
ERROR(SYS1) : 'Module Name' : Unknown error
'Optional additional message'
An unknown error is an error that is not handled properly by the system or by the module indicated in the message. In other words, this is not supposed to happen. If an unknown error do occur, it could mean that data in memory has been corrupted and unpredictable behavior could be the result. Therefore, it may be necessary to restart AnyBody after such an error. Please contact AnyBody Technology in case of any reproducable Uknown error.
SCR.SCN1
(Fatal error)
ERROR(SCR.SCN1) : Cannot open file : 'FileName'
The file may not exist, your access permission may be limitted, or it may be locked by another operation or application (sharing violation).
SCR.SCN2
(Fatal error)
ERROR(SCR.SCN2) : Include file loop : 'FileName'
A series of nested include statements return to the same file. This results in an infinite loop during the scanning of the files. The include file that closes the loop is indicated in the message.
SCR.SCN3
(Fatal error)
ERROR(SCR.SCN3) : Syntax error in include statement
Sorry - there is no detailed description or explanation related to this message.
SCR.SCN4
(Fatal error)
ERROR(SCR.SCN4) : 'TokenString' : Value out of range
Sorry - there is no detailed description or explanation related to this message.
SCR.SCN5
(Fatal error)
ERROR(SCR.SCN5) : Documentation Comment error : 'Additional error description'
Documentation Comments are a special kind of AnyScript source code comments. Apart from being a comment, in the sense that the text is not compiled by the AnyScript parser, a Documentation Comment is intended to contain the script writer's "documentation" of a specific object in the model.It is, therefore, treated differently than normal source comments during loading the model.
The Documentation Comment will be associated and stored with an object and it must therefore be written in the code either right before or after the particular object. Space in the form of empty lines are not accepted. The Documentation Comments can be made in front of an object by
1) /// ... instead of // ...
2) /** ... */ instead of /* ... */
And after an object by
3) ///< ... instead of // ...
4) /**< ... */ instead of /* ... */
Combinations of 1 and 2, respectively 3 and 4, are allowed if no linespace is dividing the individual blocks.
Multiple comments, for instance before and after an object or comments attached to multiple initializations of folder, are also allowed.In all such cases, the comments are internally assembled to one Documentation Comment.
SCR.PRS1
(Fatal error)
ERROR(SCR.PRS1) : 'FileName(LineNo)' : 'TokenString' : Object already declared at :
'FileName(LineNo)' : 'TokenString'
Only one object with a given name can exist within a given scope. In this case, either two objects have the same name or the same objects is declared twice.
SCR.PRS2
(Fatal error)
ERROR(SCR.PRS2) : 'FileName(LineNo)' : 'TokenString' : Object already auto declared by owner : 'ObjectName'
Only one object with a given name can exist within a given scope. In this case, an object with the same name as a predefined object was declared.
SCR.PRS3
(Fatal error)
ERROR(SCR.PRS3) : 'FileName(LineNo)' : 'TokenString' : Object already globally declared : 'ObjectName'
THIS ERROR MESSAGE IS NOT USED BY THE SYSTEM AFTER VERSION 1.3.
SCR.PRS4
(Fatal error)
ERROR(SCR.PRS4) : 'FileName(LineNo)' : 'TokenString' : Name lookup points out of 'Main'
An relative object name (e.g. used to initialize a reference) is targeting an object outside the scope Main.
SCR.PRS5
(Fatal error)
ERROR(SCR.PRS5) : 'FileName(LineNo)' : 'TokenString' : Objects of class 'ClassName' cannot be created because it is an abstract class
Abstract classes do not contain full functionality and therefore objects hereof the cannot be created. Abstract classes merely serve to provide a common base for derived classes. Abstract classes can be used as references. Try to find the class that really provide the functionality, you are looking for and use this instead. Or maybe you intended this to be a reference to an 'ClassName' object.
SCR.PRS6
(Fatal error)
ERROR(SCR.PRS6) : 'FileName(LineNo)' : 'TokenString' : Class name expected
This error arise when making a declaration of an objects using a wrong class name. Typically, this is due to spelling mistake. Notice that the syntax highligting will indicate when the class name is know to the parser. Only creatable and abstract classes are known to the parser, but there do exist some certain "hidden" classes that are not know and these cannot be used anywhere in AnyScript as class names.
SCR.PRS7
(Fatal error)
ERROR(SCR.PRS7) : 'FileName(LineNo)' : 'TokenString' : Circular dependency in expression
The expression leads to a circular reference, which basically means together with other expression dependecies this value comes to depend on itself. This is not allowed by the AnyScript expression handler.
SCR.PRS8
(Fatal error)
ERROR(SCR.PRS8) : 'FileName(LineNo)' : 'TokenString' : Circular declaration
Object constructed from inside itself.
THIS MESSAGE IN NOT USED IN VERSION 2.0 AND LATER.
SCR.PRS9
(Fatal error)
ERROR(SCR.PRS9) : 'FileName(LineNo)' : 'TokenString' : Unresolved object
An unresolved object is an object name for which a matching object in the AnyScript data structure was be found.
This could for instance be due to a typing mistake in the object name or a reference to an object that was deleted from the model.
Notice that mistake could be in any part of a long name, i.e., a name pointing through several scopes, even though only the last part of the name is included in the message.
SCR.PRS10
(Fatal error)
ERROR(SCR.PRS10) : 'FileName(LineNo)' : 'TokenString' : Initialization denied
This error implies that the model script contains a explicit initialization of an AnyValue with restricted access. Initialization of the particular value is not alowed. Typically, it is a computational value that the model uses to store result and as such it value is controlled completely by the system.
SCR.PRS11
(Fatal error)
ERROR(SCR.PRS11) : 'FileName(LineNo)' : 'TokenString' unexpected
This is general error that occurs when the basic syntactical principles of AnyScript are not followed and no other, more particular, error is detected.
Unexpected 'end of file' (EOF) is a special case, in which the end of a file is reached before expected. This happens when start and end scope delimiters do not match pairwise, so that the end of the file is reached, while still in a scope opened in the particular file.
SCR.PRS12
(Fatal error)
ERROR(SCR.PRS12) : 'FileName(LineNo)' : 'TokenString' when 'TokenString' was expected
This error arise in very particular cases, where AnyScript requires a special token, for instance the first object in a main-file must be Main.
SCR.PRS13
(Fatal error)
ERROR(SCR.PRS13) : 'FileName(LineNo)' : 'TokenString' : Reserved identifier used for object name
Sorry - there is no detailed description or explanation related to this message.
SCR.PRS14
(Fatal error)
ERROR(SCR.PRS14) : 'FileName(LineNo)' : 'TokenString' : Expression assignments are not allowed for AnyFolder objects
Sorry - there is no detailed description or explanation related to this message.
SCR.PRS15
(Fatal error)
ERROR(SCR.PRS15) : 'FileName(LineNo)' : 'TokenString' : Folder assignments are not allowed for AnyValue object
Sorry - there is no detailed description or explanation related to this message.
SCR.PRS16
(Fatal error)
ERROR(SCR.PRS16) : 'FileName(LineNo)' : 'TokenString' : Reference to non-folder object. 'ObjectName' is of class 'ClassName'
References can only be made to AnyFolder objects or derived. AnyValue objects must be linked by expressions if possible.
SCR.PRS17
(Error)
ERROR(SCR.PRS17) : 'FileName(LineNo)' : 'TokenString' : Reference of class 'ClassName' cannot refer to an object of class 'ClassName'
A reference must be of the same class as the target object. This implies that any base class of the target object is also accepted as reference class.
SCR.PRS18
(Fatal error)
ERROR(SCR.PRS18) : 'FileName(LineNo)' : 'TokenString' : Non-folder reference object declaration
References can only be made for folder-objects (derived from AnyFolder), not value-objects (derived from AnyValue). This error may arise when a value-class is used as reference class.
SCR.PRS19
(Fatal error)
ERROR(SCR.PRS19) : 'FileName(LineNo)' : 'TokenString' : Folder identifier used in expression
Folders cannot be part of a mathematical expression.
SCR.PRS20
(Fatal error)
ERROR(SCR.PRS20) : 'FileName(LineNo)' : 'TokenString' : Illegal assignment:
'TokenString' already assigned at : 'FileName(LineNo)'
Values can only be assigned once in order to avoid unclear situations, because the is no well-defined cronological sequence of the statements in AnyScript.
SCR.PRS21
(Fatal error)
ERROR(SCR.PRS21) : 'FileName(LineNo)' : 'TokenString' : Illegal use of a global object
Names of global objects are resctricted keywords.
SCR.PRS22
(Fatal error)
ERROR(SCR.PRS22) : 'FileName(LineNo)' : 'TokenString' : Circular reference
The reference declaration leads to a cyclic dependency, which basically means that the reference is pointing to a target that contains itself. This is not allowed by the AnyScript Reference Linker, because it will cause infinite loops traversing the Model Tree in later operations.
SCR.PRS23
(Fatal error)
ERROR(SCR.PRS23) : 'FileName(LineNo)' : 'TokenString' : Expression assignments are not allowed in declarations of AnyFolder objects
Folder objects cannot be assigned with an expression. In this particular case, the error occur during in the declaration of the object. Maybe a reference operator is missing if you wanted to make a reference to another objects. Possible syntax:
<folder_class_name> &<reference_name> = <object_name (complete or relative)>;
<folder_class_name> <object_name> = { ... };
where the former is a reference declaration and assignment and the latter is a folder declaration and assignment.
SCR.PRS24
(Fatal error)
ERROR(SCR.PRS24) : 'FileName(LineNo)' : 'TokenString' : Folder assignments are not allowed in declarations of AnyValue object
Value objects cannot be assigned with folder scope, {}. In this particular case, the error occur during in the declaration of the value object. Maybe you class name specifier is wrong. Possible syntax:
<value_class_name> <object_name> = <expression>;
<folder_class_name> <object_name> = { ... };
where the former is a value declaration and assignment and the latter is a folder declaration and assignment.
SCR.EXP1
(Fatal error)
ERROR(SCR.EXP1) : 'FileName(LineNo)' : 'TokenString' : Illegal operation for given argument types : 'List of 'ValueType''
Sorry - there is no detailed description or explanation related to this message.
SCR.EXP2
(Fatal error)
ERROR(SCR.EXP2) : 'FileName(LineNo)' : 'TokenString' : Illegal type conversion from 'ClassName' to 'ClassName' : 'additional message'
Some operations contain type conversions. This message is send if such conversions require additional attention. This can for instance be because the implicit type conversion in not recommendable. The optional part of the message will explain the actual need of attention.
SCR.EXP3
(Fatal error)
ERROR(SCR.EXP3) : 'FileName(LineNo)' : 'TokenString' : Index ['integer'] out of range for 'ValueType'
Remember that indicies in [] of AnyScript data structures are zero based, i.e., the first element has index zero.
SCR.EXP4
(Fatal error)
ERROR(SCR.EXP4) : 'FileName(LineNo)' : 'TokenString' : Division by zero
Sorry - there is no detailed description or explanation related to this message.
SCR.EXP5
(Fatal error)
ERROR(SCR.EXP5) : 'FileName(LineNo)' : 'TokenString' : Illegal use of AnyInt. State value 'integer' is out of range of valid states while converting to 'ClassName'. Allowed values : 'state-list'
An AnyEnum can hold a fixed number of named states as value. Each of these have a corresponding integer from zero to the number of states minus one. These integer values can also be used in assignments of AnyEnums, but values outside the valid range causes this error.
SCR.EXP6
(Fatal error)
ERROR(SCR.EXP6) : 'FileName(LineNo)' : 'TokenString' : Illegal state value ('state-name') in assignment of 'ClassName'. Allowed values : 'state-list'
Sorry - there is no detailed description or explanation related to this message.
SCR.EXP7
(Fatal error)
ERROR(SCR.EXP7) : 'FileName(LineNo)' : 'TokenString' : Unresolved function
A function with the given name was not found.
SCR.EXP8
(Fatal error)
ERROR(SCR.EXP8) : 'FileName(LineNo)' : 'TokenString' : Illegal function argument list 'TokenString'('List of 'ValueType'').
Supported function use :
'list of functions'
Sorry - there is no detailed description or explanation related to this message.
SCR.EXP9
(Fatal error)
ERROR(SCR.EXP9) : 'FileName(LineNo)' : 'TokenString' : AnyFunction object expected
Sorry - there is no detailed description or explanation related to this message.
SCR.EXP10
(Fatal error)
ERROR(SCR.EXP10) : 'FileName(LineNo)' : 'TokenString' : Expression evaluation failed at moment 'EvaluationMoment' :
'FileName(LineNo)' : 'ObjectName' : argument will not be ready for evaluation until moment 'EvaluationMoment'
All values in AnyBody are assigned to specific Evaluation Moments that specify when the values are evaluated. All the Evaluation Moments together define a kind of time line of execution of the model from the early model loading steps to steps in running operations (AnyOperation). This error indicates that an AnyScript value has been assigned with an expression containing other symbolic variables of a later Evaluation Moment. This is not allowed because the dependent value, in this case, would be updated before the inputs, i.e., with "old" values.
SCR.EXP.FUN1
(Fatal error)
ERROR(SCR.EXP.FUN1) : 'FileName(LineNo)' : Wrong dimensionality or dimensions of function argument number 'integer'. Expected dimensions : 'ValueType'
An argument of a particular call to the function has unacceptable dimensions or dimensionality. For further details please refer to the documentation about the particular function. The function is of the type 'ClassName'.
OBJ1
(Fatal error)
ERROR(OBJ1) : 'ObjectName' : 'Error message' : incomplete C++ coded error
This message is a general "object error" in which the full message text is varying from case to case and no further explanation is available here.
Some of these messages are actually messages that has not yet been converted to AnyBody's new message format with their own message ID and with additional explanations. We appologize for these cases.
OBJ2
(Fatal error)
ERROR(OBJ2) : 'ObjectName' : Obligatory initilization of member 'ClassName' 'ObjectName' is missing
The object referred to in the error message requires initialization. It is a predefined member object and without this initialization the model cannot behave properly; loading the model is therefore terminated. To avoid this error make proper initialization, for instance in the object's construction scope indicated by the file reference in the error message.
OBJ3
(Fatal error)
ERROR(OBJ3) : 'ObjectName' : Member expectations are not satisfied :
'Expectation information'
Some classes (folders only) may require certain objects to be declared inside them. For instance a drawing object may need one or more reference frames to attach the drawing to. This error occurs, if such "member expectation" are not satisfied.
Notice that these expected members often could be made as AnyScript references to already existing objects, that have been declared in other parts of the model.
OBJ4
(Fatal error)
ERROR(OBJ4) : 'ObjectName' : Wrong owner class for 'ClassName'. Accepted owner(s): 'list of accepted owners'
This error occurs in objects that requires a specific owner class, if this demand is not satisfied. To avoid this error, consider the folder in which you have declared 'ObjectName', it may be misplaced.
OBJ5
(Fatal error)
ERROR(OBJ5) : 'ObjectName' : Numerical value of 'ObjectName' is out of range : 'Allowed Range'
A value is outside the allowed range. This is typically a fatal error, but it may be send with lower severity. An additional message may indicate any actions taken to avoid severe problems, e.g. auotmatical adjustment of values.The 'Allowed Range' is specified by:
Closed bounded interval limits: [min..max]
Open bounded interval limits: ]min..max[
Unbounded upper limit: ]min..max[
Unbounded lower limit: ]-Inf..max]
OBJ6
(Fatal error)
ERROR(OBJ6) : 'ObjectName' : Numerical value of 'ObjectName' is out of range : 'Allowed Range'
A value is outside the allowed range. This is typically a fatal error, but it may be send with lower severity. An additional message may indicate any actions taken to avoid severe problems, e.g. auotmatical adjustment of values.The 'Allowed Range' is specified by:
Closed bounded interval limits: [min..max]
Open bounded interval limits: ]min..max[
Unbounded upper limit: ]min..max[
Unbounded lower limit: ]-Inf..max]
OBJ7
(Important warning)
WARNING(OBJ7) : 'ObjectName' : Initialization without effect : 'additional explanation'
This message implies that a redundant initialization has taken place. The 'additional explanation' will explain the reason in the particular case. In rare cases, this message is an error-indicator, but typically it is just a warning.
OBJ.FILE1
(Fatal error)
ERROR(OBJ.FILE1) : 'ObjectName' : Problem with file : 'FileName' : 'Additional explanation'
This message is send by AnyFile objects. This is a basic, generic message that can cover many different issues depending on the actual type of file and the situation. An 'additional explanation' will typically accompany the basic part of the message, explaining the particular issue. The file references may for text files include a reference to the line number of the error (if applicable).
OBJ.CHT1
(Fatal error)
ERROR(OBJ.CHT1) : 'ObjectName' : Invalid serie selection : 'Additional message with reason'
This error is caused by a selection made while defining a data serie for a chart object (AnyChart). This can either happen while loading a model with an AnyChart object declared in the AnyScript code, or while making serie selections in the AnyChart View that uses an AnyChart object as a component.
Look to the last part of the message for the reason in the particular case.
OBJ.DES1
(Fatal error)
ERROR(OBJ.DES1) : 'ObjectName' : Wrong initialization of 'ClassName' linking to value 'ObjectName' :
'additional message'
An AnyVarRef can only be equal to a single, independent, scalar quantity. The reason is that a AnyVarRef also function as a link in the opposite direction of the normal initialization, i.e., an AnyVarRef can (during runtime) transfer values from itself to the AnyValue object it is linked to (its dependency) This is only possible if there is a one-to-one correspondence and the evaluation moments of left and right-hand side match completely. The dependency is typically created by an AnyScript initialization of the AnyVarRef with the depedency given by the left-hand side of the expression. but it can also be created internally, e.g. by an owner object of the AnyVarRef.
Typical errors:
- The right-hand side is an expression of multiple other AnyValues.
- The right-hand side is an AnyValue with multiple elements (without proper indicies to refer to a particular element).
- The right-hand side Evaluation Moment does not match the left-hand side .
(This could cause unpredictable overwriting of values after they are updated by the AnyVarRef object and it is therefore not allowed.)
Please see the reference page on the AnyVarRef class for further details.
OBJ.DES2
(Fatal error)
ERROR(OBJ.DES2) : 'ObjectName' : Optimization failed : 'additional message'
When this error arise, the optimization process has broken down before convergence. This is typically due to some sort of numerical issue and the particular reason is therefore problem and solver dependent. It could be the optimization problem that does not behave well, or the solver or solver settings not being well-suited for the problem.
OBJ.DES3
(Fatal error)
ERROR(OBJ.DES3) : 'ObjectName' : Design initialization issue
This message accompanies issues occuring while manipulating design values, i.e., the values of design variable. This can for instance be while loading design values from (or saving to) external files
OBJ.MCH.KIN1
(Fatal error)
ERROR(OBJ.MCH.KIN1) : 'ObjectName' : Model is kinematically indeterminate : 'additional message'
This error may arise during the kinematical analysis a kinematically indeterminate system. This implies that the model has fewer independent kinematic constraints than degrees of freedom.
OBJ.MCH.KIN2
(Fatal error)
ERROR(OBJ.MCH.KIN2) : 'ObjectName' : Model is kinematically over-constrained : 'additional message'
This error may arise during the kinematical analysis of a kinematically over-constrained system. This implies that the model has more independent kinematical constraints than degrees of freedom and therefore not all constraints can be satisfied.
This message may also be send as a warning, when there are excessive kinematical constraints in the model, but the additional constraints are dependent, so that the independent set of constraints is solvable. The excessive dependent constraints are referred to as redundant kinematical constraints.
This kinematic solver may not always be numerically able to distinguish between redundant and unsolvable constraints Therefore, it is advisable to avoid excessive constraints whenever possible.
OBJ.MCH.KIN3
(Fatal error)
ERROR(OBJ.MCH.KIN3) : 'ObjectName' : Kinematic analysis failed in time step 'integer'
This error may arise when the kinematical analysis fails to complete. This implies that the kinematic constraints does not have a solution or simply that the solution was not be found with under the given numerical circumstances.
In the latter case, more appropiate settings of the kinematic solver may allow for a solution.Additionally, a better choice of initial positions will improve the solver ability to solve the constraints.
OBJ.MCH.KIN4
(Fatal error)
ERROR(OBJ.MCH.KIN4) : 'ObjectName' : Failed to resolve kinematic constraints : final kin. error : 'number'
This error may arise when the kinematical analysis fails to complete. This implies that the kinematic constraints does not have a solution or simply that the solution was not be found with under the given numerical circumstances.
In the latter case, more appropiate settings of the kinematic solver may allow for a solution.Additionally, a better choice of initial positions will improve the solver ability to solve the constraints.
OBJ.MCH.KIN5
(Warning)
WARNING(OBJ.MCH.KIN5) : 'ObjectName' : Failed to consistently set approximate positions this kinematic measure : 'additional message'
"Approximate positions" are a set of values of the kinematic measure, which are numerically close to real/current value. They function to determine the real values uniquely in kinematic measures that may have multiple value, for instance angular values that repeat for each 2 time Pi. They are continously updated during a kinematic analysis so that they always a close to the current value and in the begining of a kinematic analysis all constraints (hereunder drivers) will suggest approximate values to the measures they are applied to. This warning indicates that the update of "approximate positions" has not been carried out completely.
"Approximate positions" may be pushed back through measure organizers (AnyKinMeasureOrg or derived) to the measures that the organizer uses. However, for some types of measure organizers it is not mathematically meaningful to do this and in such cases this warning will be send. AnyKinMeasureLinComb is an example of such a measure organizer. While the "approximate position" of the output an AnyKinMeasureLinComb may be known, it is not meaningful to convert this back into vales for the input measures (except in special cases). The update of the "approximate position" will then fail in the intial step of a kinematic analysis in cases where the AnyKinMeasureLinComb (or similar measure organizer) is driven/constrained.
Typically, this warning can be disregarded, but in some very special cases this issue may be the cause of kinematic problems. For instance, if angular measures with initial values larger than 2*Pi are used in measure organizers without the capability of setting apprimate positions.
OBJ.MCH.KIN6
(Important warning)
WARNING(OBJ.MCH.KIN6) : 'ObjectName' : Close to singular position : 'additional message'
A singular position is a position where one or more singularities occur in the mathematical description of the motion.Being close to such positions may cause the kinematic analysis or the computation of derived quatities to become inaccurate or in worst case fail. The "additional message" may give further details about the concrete nature of the problem.
The object sending this message will typically filter multiple occurances, so that the message is send only once during an analysis, even though the problem occurs several times independently. It is thereby expected and a advisable to deal with the first occurance of the problem before any continuation of the analysis.
OBJ.MCH.KIN7
(Important warning)
WARNING(OBJ.MCH.KIN7) : 'ObjectName' : Penetration : 'additional message'
This warning indicates that a unwanted penetration has occured. The "additional message" will give details on the particular reason.
The object sending this message will typically filter multiple occurances, so that the message is send only once during an analysis, even though the problem occurs several times independently. It is thereby expected and a advisable to deal with the first occurance of the problem before any continuation of the analysis.
OBJ.MCH.KIN8
(Fatal error)
ERROR(OBJ.MCH.KIN8) : 'ObjectName' : Incorrect number of elements in driver specification vector, it must be the same as the number of coordinates in the kinematic measure, i.e. in 'Pos'.
This message is send from AnyKinEqDriver objects, when the dimensionality of driver specifications does not match the number of coordinates to be driven. It is for instance send from AnyKinEqSimpleDriver objects when wrong number of elements is specified for 'Pos', 'Vel' , or 'Acc'.
OBJ.MCH.DYN1
(Fatal error)
ERROR(OBJ.MCH.DYN1) : 'ObjectName' : Model is kinetically indeterminate : 'additional message'
This error implies that the model contains fewer unknown forces than equations and it is therefore not solvable.
The additional message may provide further information about the particular problem.
OBJ.MCH.DYN2
(Important warning)
WARNING(OBJ.MCH.DYN2) : 'ObjectName' : Model contains redundant constraint reactions : 'list-of-redundant-reactions'
This message is send when the model contains reactions which are not uniquely defined. In other words, the reaction forces are not independent.
This happens when there are more reaction forces the degrees of freedom in the system, but it does also happen if two similar reactions are defined or if two subsets of reaction forces span the same space.
This message may be handled as an error as well as a warning, that allows you to continue, if possible. In any case it is however recommended to stop and make sure the system is properly defined. Generally, it is not advisable to work with systems containing redundant constraints, because they may lead to indeterminacies depending on the system and the solver. The solver will typically try to select a subset of reactions to edal with, negleting the rest and this choice may be rather arbitrary
The message may be accompanied by a list of the reaction forces that is neglected by the solver. This does not mean that these are the actual cause of the error, but the error is related to the function they have and othes reactions with similar functions.
OBJ.MCH.MUS1
(Important warning)
WARNING(OBJ.MCH.MUS1) : 'ObjectName' : The muscles in the model are not loaded due to kinetically over-constrained mechanical system.
This message is send when the model contains the same number of (or more) independent reaction forces than degrees of freedom. This implies that these reaction forces carries all directions of the applied load, and thus the muscles will not be loaded at all.
This is typically an error in the model, though it from a mathematical point is a acceptable situation, but with a trivial solution. The solution (if consideredas an error) is to remove reaction forces or to switch off their force carrying capability. This implies to open for the loads in the associated degrees of freedom to be carried by the muscles.
For more information on how to switch off existing reaction forces, please refer to the AnyScript class AnyReacForce and its use class AnyKinEq and derived classes.
OBJ.MCH.MUS2
(Important warning)
WARNING(OBJ.MCH.MUS2) : 'ObjectName' : Muscle without strength : 'additional message'
This warning indicates that a muscle has lost it strength, for instance because it has been strected beyond its for producing range. This may indeed be intensionally and it is as such no error. The "additional message" provides more information about the reason in the particular case.
This error is handled by the muscle so that it is send only once during a simulation analysis. This implies that the issue may occur several times independently of each other without additional notice. It may be advisable to inspect the strength variation of the particular muscle in the output of the analysis.
OBJ.MATH1
(Fatal error)
ERROR(OBJ.MATH1) : 'ObjectName' : Convergence failed : 'additional message'
A numerical routine failed to converge. The "additional message" may provide more detail about the particular reason.
OBJ.MATH2
(Fatal error)
ERROR(OBJ.MATH2) : 'ObjectName' : Solver setting error : 'additional message'
Settings specified for the referred solver object are not functional. The "additional message" may provide more detail about the particular reason.
OBJ.LIB.OOS1
(Fatal error)
ERROR(OBJ.LIB.OOS1) : 'ObjectName' : Unexpected exception in the library OOSol :
OOSol exception : 'exception description'.
A routine in the OOSol library failed unexpectedly. The "exception description" may provide more detail about the particular reason.
Such failures can be and is most typically due to wrong input to the library routines. This implies that the error could be in the calling AnyObject, either its body or its parameters.
OOSol functionality is for instance used in AnyKinSPLine, whch is part of muscle wrapping functionality. This type of error, if send from a muscle object, can therefore indicate that the muscle wrapping setup is poor; for instance too few wrapping points on curve compared to the surface curvatures.
SET.STY1
(Error)
ERROR(SET.STY1) : 'ObjectName' : RGB value is out of range : 'Description of current values'
AnyRGB is a three component vector aimed at holding RGB (color) value. These value are restricted to the range from zero to one. Violation of this restriction will result in the this (non-fatal) error as well as an automatic modification of the value to obey the restriction.
SET.STY2
(Fatal error)
ERROR(SET.STY2) : 'ObjectName' : RGB value structure has wrong dimensions
AnyRGBs is a struture of three component vectors aimed at holding RGB (color) value, i.e., an array of three-vectors, a matrix of three-vectors, or any-dimensional tensor of three-vectors. If the structure is initialized so that it does not consist of such three component vectors, this error message will be send.
Message Index
SYS (message group)
SYS1SCR (message group)
SCR.SCN (message group)
SCR.SCN1SCR.SCN2SCR.SCN3SCR.SCN4SCR.SCN5SCR.PRS (message group)
SCR.PRS1SCR.PRS2SCR.PRS3SCR.PRS4SCR.PRS5SCR.PRS6SCR.PRS7SCR.PRS8SCR.PRS9SCR.PRS10SCR.PRS11SCR.PRS12SCR.PRS13SCR.PRS14SCR.PRS15SCR.PRS16SCR.PRS17SCR.PRS18SCR.PRS19SCR.PRS20SCR.PRS21SCR.PRS22SCR.PRS23SCR.PRS24SCR.EXP (message group)
SCR.EXP1SCR.EXP2SCR.EXP3SCR.EXP4SCR.EXP5SCR.EXP6SCR.EXP7SCR.EXP8SCR.EXP9SCR.EXP10SCR.EXP.FUN (message group)
SCR.EXP.FUN1OBJ (message group)
OBJ1OBJ2OBJ3OBJ4OBJ5OBJ6OBJ7OBJ.FILE (message group)
OBJ.FILE1OBJ.CHT (message group)
OBJ.CHT1OBJ.DES (message group)
OBJ.DES1OBJ.DES2OBJ.DES3OBJ.MCH (message group)
OBJ.MCH.KIN (message group)
OBJ.MCH.KIN1OBJ.MCH.KIN2OBJ.MCH.KIN3OBJ.MCH.KIN4OBJ.MCH.KIN5OBJ.MCH.KIN6OBJ.MCH.KIN7OBJ.MCH.KIN8OBJ.MCH.DYN (message group)
OBJ.MCH.DYN1OBJ.MCH.DYN2OBJ.MCH.MUS (message group)
OBJ.MCH.MUS1OBJ.MCH.MUS2OBJ.MATH (message group)
OBJ.MATH1OBJ.MATH2OBJ.LIB (message group)
OBJ.LIB.OOS (message group)
OBJ.LIB.OOS1SET (message group)
SET.STY (message group)
SET.STY1SET.STY2
