geometry defining the spatial extent and correlation of a noise item The identifier for the geometry The coordinate system of the geometry Interval specifying the horizontal spatial correlation between the consecutive values The unit for the horizontal correlation scale output item containing a noise item of the specified geometry with values generated by the noise model The identifier for the noise item The identifier for the noise item The initial value for the generated noise The standard deviation for the generated noise Time interval specifying the time correlation between the consecutive values The unit for the time correlation scale The quantity contained in the noise item The unit of the quantity contained in the noise item HACK: suppresses the saving/restoring of the internal state for the noise model. This is necessary for using a noise model in the state of e.g. the ParticleFilter, which currently is implemented by copying state between ensemble instances. However, due to the order in which noise model is computed, added to the deterministic model and then the deterministic model is computed, this leads to a (most probably unintended) collapse of the ensemble field. Configuration for OpenDA's noise model Base type for all configuration elements of geometry implementations. Implementation class of this specific geometry. Must implement org.hydpy.openda.noise.ISpatialNoiseGeometryFactory A regular grid defined by its coordinates in x and y direction. To speed up calculations the coordinates can be treated as separable. This means that correlations are computed for both spatial directions separately. This is much faster, but is only approximate for spherical coordinates, especially near the poles. An arbitrary set of points. Specialized spatial distribution of 'point' locations, where the order (within the noise vector) will be fetched from a HydPy-Server instance via its method 'getItemNames'. This ensures that the order (and dimension) of the spatial noise vector fits the model structure without need for defining it twice. The actual locations will be (for now) fetched from a separate 'locationsFile' that maps HydPy element names to locations. For the future it is planned to also fetch the location information directly from the HydPy model. Usage of this spatial geometry prerequisites the usage of the org.hydpy.openda.HydPyModelFactory. Id of the exchange item from which the order and dimension of the spatial noise vector will be derived. Path to an external file containing a mapping between HydPy element names and their geographic location. The path will be resolved against the working dir of the spatial noise model. The file format is a tabular separated table with three columns: element-name, x-coordinate and y-coordinate. Empty lines or lines starting with '#' are ignored. The locations file must contain one location for each element within the spatial noise vector aka the referenced exchange item. However the file may define more locations than needed, e.g. in order to be reused for different element sub-sets. Definition of the points along a coordinate axis (all points, or: start,next,...,end)