Table 3: Input Error Exception Messages
Input Error exceptions occur when the AutoRouter is missing information that users must provide such as placed nozzles, and accurate vicinity routing rules.
| Category | Message |
|---|---|
| Input Error | Invalid condition expression <expression> in <definition> vicinity routing rule <rule> |
| Input Error | Invalid level direction <key word> for nozzle <tag> on line <tag> from segment <expression> in vicinity routing rule <definition> |
| Input Error | Invalid routing direction <key word> for nozzle <tag> on line <tag> from segment <expression> in vicinity routing rule <definition> |
| Input Error | Invalid segment direction <key word> in segment <definition> of ~A vicinity routing rule <definition>; should be one of <key word list> |
| Input Error | Invalid segment distance <key word> in segment <definition> of <equipment tag> vicinity routing rule <definition>; should be an expression of one of <key word list> |
| Input Error | Invalid symbolic reference <key word> in expression <expression> when routing line <tag> at nozzle <tag> according to vicinity routing rule <rule> |
| Input Error | Invalid takeoff length <value> for nozzle <tag> on line <tag> from segment <definition> in vicinity routing rule <rule> |
| Input Error | The boundary has been placed at an offset equal to the bent design spacing for pipeway <tag> since the input location <value> puts it beyond this range |
| Input Error | The location description <value> for the boundary is inconsistent with the orientation of its pipeway <tag>. Taking the pipeway end as a default. |
| Input Error | The pipeline cannot be routed because at least one end is not located. |
| Input Error | The pipeline cannot be routed because at least one end of connected Pipeline <tag> is not located. |
| Input Error | The vicinity routing rule set must be a list. Instead it is <string> |
| Input Error | Unable to evaluate expression <expression> when routing line <tag> at nozzle <tag> according to vicinity routing rule <rule> due to error: <error message> |
| Input Error | Unable to read vicinity routing rule set due to an input parsing error. Perhaps there is a missing close parenthesis, a missing quotation mark, or an illegal character. The vicinity rule string is <rule> |
| Input Error | Unable to read vicinity routing rule set due to error <error message>. The string is <expression> |
| Input Error | Unable to read vicinity routing rule set for equipment <tag> due to parsing error. Please check your vicinity rules: <rule> |