ADComponentData Properties

Additional outputs

List of AD components

Holder of read/write information

List of custom types stored in the data object and that must be serialized.

A custom type is e.g. a user implemented structure or catchment model. In order to store information on the custom type in the .m1dx file, the system needs to know which custom types are being used, and they must be added to this list.

Flag indicating whether dispersion takes place between nodes and the surrounding reaches. This is relevant for nodes with volume only.

Default is true

Flag indicating whether dispersion takes place between open boundaries and external waters.

Default is true

Dispersion parameters per reach. Overrides the global values.

Holds data from an extended DataContract

List of hotstart files, prioritized, the first one being tried first.

Several hotstart files can be added. Each of the hotstart files can contain data for different components and different parts of the network. Network need not to match exactly, interpolation will take place where appropriate.

Example: If merging two AD setups into one, the two original AD hotstart files from each of the original setups can be added here.