Validation Checks

It is important your design data does not contain errors prior to processing.

Your application contains a range of validation options that allow you to check your FXS, Outline and Complex Solid design data before you commit it for processing. Checks are made based on, in some cases, validation options. These options typically define thresholds above (or below) which an error condition is assumed. For example, a check for duplicate string data is made with respect to the specified Precision Distance.

The actual checks that can be made will depend on the design type in question. This topics outlines the main checks made during a validation run, and offers advice on how to resolve them.

These checks are listed in order of significance; it is recommended to resolve such validation failures in the order shown below, starting with duplicated strings. This is because the items at the top of the list could potentially impact the outcome of processing in a more meaningful way that those lower down the list. That said, all validation failures should be reviewed, at least.

Duplicate Strings

Performed against these design types: FXS, CXS, OUT

It is important that duplicate data does not exist to avoid the creation of invalid activities later on. Coincident or near-coincident string data can be the result of erroneous digitizing or data object modification, and can give rise to unexpected processed solids later on. As such, all duplicate string data validation errors should be resolved before continuing, either by relaxing the threshold distance used to indicate coincidence.

Duplicate string data is reported as either:

Coincident string nodes. Two string nodes in the same location is often problematic. A check is made for all string nodes that fall within the specified (Precision Distance).
Coincident edge data. The threshold for this is the Minimum Edge Length Required Option. If string edges are detected below the specified length, they are highlighted.

Minimum Area

Performed against these design types: CXS, OUT

Closed/perimeter design string data used for complex solids and outlines can be validated against a minimum qualifying area value (Minimum Area) to ensure that trivial closed string shapes, possibly a noisy artefact of data capture or digitizing, are highlighted. This then allows data to be tidied up prior to processing and downstream scheduling.

Design String Length

Performed against these design types: FXS

A check is made of all fixed cross-sectional design strings to ensure they are of sufficient length overall. This is controlled by the Minimum option.

Edge Length

Performed against these design types: FXS, CXS, OUT

Similar to the Minimum Area check but instead compares string segments (the straight lines between nodes), also known as 'edges', are ignored if they fall below a given distance (Minimum). String edges that are shorter than this amount are highlighted during validation.

Azimuth Change

Performed against these design types: FXS

Severe changes in direction between string edges can indicate erroneous data. The Maximum Azimuth Change value determines the maximum permitted azimuth angle change between string edges before a string fails validation.

Dip Change

Performed against these design types: FXS

Severe changes in direction between string edges can indicate erroneous data. The Maximum Dip Change value determines the maximum permitted dip angle change between string edges before a string fails validation.

String Crossovers

Performed against these design types: FXS, CXS, OUT

Crossing over strings are always reported as they are invariably problematic during downstream processing. Crossovers are reported as one of two error types:

A "Crossover" error type indicates that independent string data within the same object are crossing over.
A "Self Crossing" error type indicates that a string is self-intersecting.

Crossover detection sensitivity is controlled using the Ignore if vertical separation distance greater than option. A string that passes over itself, such that the vertical distance between proximal string data is within the specified value, will be listed as a warned during validation. Strings that cross over with a greater vertical separation, such as a spiral decline with a deliberate crossover in plan view, won't be highlighted.

Edge Dip Errors

Performed against these design types: FXS

Edge dip errors show FXS design strings which have edges with either unacceptable sub-horizontal gradients or sub-vertical dips as specified in the validation settings under FXS. The thresholds for this check are defined using the Maximum Horizontal Gradient and Minimum Vertical Dip options.

For example, if your sub-horizontal gradients maximum is 1:7 and your sub-vertical minimum is 85 degrees, then an FXS string at a gradient of 1:5, or 80 degrees (as in, between 1:7 and 85) is considered an error.

Mixed Dip Errors

Performed against these design types: FXS

This is where strings have a combination of valid sub-horizontal edges and valid sub-vertical edges. Strings found to contain a mixture of edge dip changes will be highlighted.