Result type: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
m (Rudolf@tygron.nl moved page Result type to Result child type Overlay without leaving a redirect)
m (Rudolf@tygron.nl moved page Result child type Overlay to Result type without leaving a redirect)
(No difference)

Revision as of 10:27, 15 June 2020

A result type is a configuration for a specific output from a Grid Overlay performing a complex calculation. A number of overlays offer configurable result types.

How result types work

Some Grid Overlays, such as the Water Overlay, perform complex calculations with multiple forms of input and intermediate steps, and possibly also multiple kinds of output. For these Overlays, a specific result type can be configured which indicates what information should be output when the calculation completes. For example, for the Water Overlay the result types include the surface last value result type and the groundwater result type for water above and below ground respecitvely.

Even though a calculation may calculate intermediate results as it progresses, or even a variety of end-results, only the results specified by the configured result type are stored. All other values are discarded.

Result child type Overlay

Generally, Overlays which offer multiple result types also offer the ability to add additional output overlays, which are automatically linked to the calculation model, so that more different kinds of results can be obtained after the calculation completes. These are Result child type Overlays. They are automatically added as Child Overlays to the related calculation model. Otherwise, these Overlays function the same as other Overlays. They can be named, have their own legend and Attributes, and can be selected in the user interface. They can also be queried for their results, and exported.

The benefits of using Result child type Overlays rather than multiple individual Grid Overlays configured identically other than their result type, are:

  • Only a single Overlay contains the configuration for the desired calculation. If multiple configurations have to be kept identical, the chance of a user making a mistake when making a change to the configuration is much greater.
  • Only a single calculation needs to be performed. If multiple calculations need to run, even if they are configured the same, the waiting time for them all to complete would be greater for each added Overlay.

Unlike other Child Overlays, when the Parent Overlay is removed, the Result child type Overlays are automatically removed as well.

Notes

  • When a Result child type Overlay has its result type changed, its legend is automatically updated (unless a custom legend is configured). However, the actual data is not immediately updated. The Grid Overlay the Result child type Overlay is related to needs to be recalculated.

How-to's