All software encounters error messages from time to time and Kubla Cubed is no different. In this chapter, we discuss the ‘Calculation Error’ message, which may occur when working on complex projects. We also discuss Kubla Cubed's calculation steps and the error reporting features. This section discusess quite advanced topics and is intended for experienced users.
Overview
Calculation error messages in Kubla Cubed are displayed when the calculations fail, or where a validation step fails. Validation steps are run at numerous points during the calculation to ensure the integrity of the final result. No calculation engine is going to be entirely error-free, especially one whose calculations are based on Triangular Prisms, as in Kubla Cubed. This method is the most accurate, but is also far, far more technically challenging than the grid and cross-section methods that are used by some other earthworks software.
Kubla Cubed offers users the flexibility to create as many phases of work as they wish, with each phase containing an unlimited number of earthworks elements. While this flexibility is advantageous, it also allows for very complex projects to be defined, increasing the likelihood of calculation errors compared to more restrictive software.
Calculation Steps
To understand the sources of calculation errors, it is helpful to understand the steps involved in the calculation. We will briefly summarise the process below. These steps are repeated for each phase in the project.
For each earthworks element in a phase, there is a three-step process:
|
Step One : Generating the surface mesh. For a platform, this is trivial and unlikely to cause an error. However, it is potentially quite complicated for a feature surface with many ground features. It can also be challenging for a strip or overlay, where the ground below is complex. |
|
|
Step Two : Generating batter slopes. Batter slopes are the side slopes that will be used to connect the surface mesh to the terrain. The complexity of this process depends largely on the complexity of the element's outline. However, if the batters are set to vertical (0.01) this step is quite straightforward for the software to complete. |
|
|
Step Three : Merging the element with the terrain. This is usually a fairly challenging step for the software, particularly if the existing and/or proposed meshes are complex. |
|
Once all of the earthworks elements have been processed in this way, two meshes will exist: the mesh at the start of the phase and the mesh after all the elements have been merged into it. The final step is to project the initial mesh edges onto the final mesh. This will create a mesh which contains all the edges of both the initial and the final meshes. This ‘Calculation Mesh’ is crucial to generate volumes and to present cut and fill maps. However, this final step of the process is extremely complex and commonly a source of error messages.
If an error occurs when merging an earthworks element into the terrain, the software will identify the element that caused the error. However, if an error occurs during the generation of the calculation mesh, it is not possible to identify a specific element that has caused the problem. For this reason, these errors can be particularly difficult for our customers to resolve with the current error messages.
General Approach
At Kubla, we use the following approaches to minimise the frequency and impact of calculation errors:
|
|
|
We believe that our validation, calculations and support are amongst the best available in the industry, although we continue to improve these areas. However, user feedback has indicated that error messages can be difficult to interpret and do not always provide enough information for them to find a solution on their own. For this reason, the latest release of the software includes work to improve this aspect of the software. This work is ongoing and will continue in subsequent updates. |
The validator in Kubla Cubed aims to prevent errors in the terrain definition. It will block blatant errors, such as contour lines crossing each other with different levels. It will also warn the user about likely errors, such as one elevation which is very different from all of the others. |
Improvements to Error Reporting
In earlier versions of the software, only one error message could be displayed to the user. This provided limited ability for our developers to communicate the source of the error to the user of the software. A significant upgrade to error reporting now presents the full error path to the user, allowing for more detailed information about the error.
However, the most notable improvement to error reporting is the capability to display the region where the error has occurred on the screen. This empowers our users to inspect the problematic area, and see if they have made any mistake, or if they could simplify the way they have defined the ground levels in this area. Sometimes, even just moving some features in this area by a negligable amount may cause errors to go away.
However, it’s essential to understand, that due to the complexity of the calculations, it’s not always obvious where they have initially gone wrong. The displayed error regions will sometimes represent a ‘best guess’ of the location of the error source. The project should be checked in the vicinity of the identified error region, as well as within the region itself. It should also be noted that it is not possible to identify an error region for every type of error, and it will not always be displayed. However, the most common errors will now have error regions, and coverage will be expanded to more error types in the future.
