Table 7: Pipeway Exception Messages
Any time a pipeway is undersized, a pipeline routes on a level other than the one that is preferred/required, or the pipeway network is flawed, a Pipeway exception is generated.
| Category | Message |
|---|---|
| Pipeway | Can't find a starting point on pipeway <tag>, default to <centerline coordinates> |
| Pipeway | Can't find an ending point on pipeway <tag>, default to <centerline coordinates> |
| Pipeway | Pipeline <tag> routed on level <tag> of Pipeway <tag>, but that level does not have enough space for it. |
| Pipeway | Pipeline cannot be routed because there is not a path through the pipeway network between the start and end pipeways (<tag>, <tag>). |
| Pipeway | Pipeline is routed off preferred Level <tag> in Section <tag> of Pipeway <tag> at elevation <value> |
| Pipeway | Pipeline is routed off required Level <tag> in Section <tag> of Pipeway <tag> at elevation <value> |
| Pipeway | Pipeline is routed on level <tag> of Pipeway <tag> because there is no level named <tag> on this pipeway. |
| Pipeway | Pipeway <tag> has these overflowing levels: <capacity report> |
| Pipeway | Pipeway <tag> was last saved with <value> berthing level(s), now it has <value> level(s). Will put the existing named level(s) above level <tag> on the new top level. |
| Pipeway | Pipeway network cycle detected between <tag> and <tag>, removing that sequencing constraint and proceeding with pipeway routing. Please check your network. |
| Pipeway | The width required for the lines on pipeway <tag>, berthing level <tag> is <size>, which exceeds the space available (<size>). |
| Pipeway | There are <value> berthing level(s) in pipeway <tag>, but only <value> level name(s) were specified. Will use the default level name(s) for the unspecified level(s). |
| Pipeway | This pipeline does not yet have a route on Pipeway <tag>. |
| Pipeway | Unable to compute on-pipeway perpendicular segment on pipeway <tag>; possibly due to other pipeway problems. |
| Pipeway | Unable to determine the adjacency between pipeways <tag> and <tag> because their distances from the intersection are equal and the router cannot determine which is the primary pipeway. Pipeway locations and/or widths need to be adjusted to clarify their adjacency. |
| Pipeway | Unable to determine the adjacency between pipeways <tag> and <tag> because they have crossing centerlines. |
| Pipeway | Unable to route Pipeline <tag> on vertical pipeway or chase <tag>, probably because the pipeline begins and ends at tees on this pipeway, which is not yet supported for vertical pipeways and chases |
| Pipeway | Unresolvable on-pipeway sequencing problem found. Clearing constraints between networks containing Pipelines (<list>) and Pipelines (<list>) in order to complete routing. |
| Pipeway | Unroutable cycle in pipeway networks |