Experimental SDI Configuration for Continuous Computes

Experimental Settings

Please reach out to the HEC-WAT team if you are planning to use this feature.

The information provided below is useful for running the SDI plugin with continuous computes, that is where each lifecycle consists of a single event spanning multiple years - as this is a frequently used but also incomplete SDI feature, this information is provided for use at your own risk. These settings must be entered in the HEC-WAT.config file that can be found next to the HEC-WAT.exe executable file. Modifying this file may break the functioning of the HEC-WAT software or expose unintended behavior or untested features to the user. Use caution when editing this file, making regular backups of your model and validating all model results independently.

Enabling the SDI plugin's continuous compute logic requires adding the following text to the HEC-WAT launch process. Typically by adding the following to the HEC-WAT.config file that is located in the HEC-WAT application directory or the user's HEC-WAT-Personal.config file.

HEC-WAT.config additional text

[...]

vmparam -DSDI.MultiYearComputeOffsetEnabled=true
vmparam -DSDI.HasMultiYearEvent=true
vmparam -DSDI.MultiYearComputeValidationEnabled=false

TEXT

These settings do the following:

Multi Year Event Flag: "HasMultiYearEvent"

This flag enables the choice to define multiple events per year, or a single event that spans multiple years. Events are defined through the presence of null data in the data record for the primary location.

Multi Year compute offset: "MultiYearComputeOffsetEnabled"

This flag will prevent SDI from shifting data from the originally stated date and time in the SDI input data. We strongly recommend leaving this setting enabled for continuous computes.

Multiple Year Compute Validation: "SDI.MultiYearComputeValidationEnabled"

This flag will prevent SDI from validating SDI input data at compute time. We strongly recommend against turning this off, however some input data may fundamentally violate assumptions of the SDI input validation process, and this flag is necessary for the compute to proceed.