controlDistributorType

single controlDistributor bundling several controlElements

Within some analyses, it might occur that overlapping control element settings are specified. In this case, it is assumed that a cumulative setting is built by summing up the individual settings. As the behavior of these settings is not necessarily linear, a certain order of summation has to be followed:

The command inputs for each <controlDistributor>, coming from the <configurationUID>, as well as from separate settings have to be summed up to a total <commandInput>.
With this total <commandInput>, each corresponding <controlDistributor> definition has to be evaluated, in order to get <controlParameter> settings for a number of <controlDevices>.
All <controlParameter> settings for a control device, coming from the <configurationUID> , from the <controlDistributors> and from separate control device settings have to be summed up to get a total <controlParameter> for each controlDevice.
With this total <controlParameter>, each corresponding control device definition has to be evaluated, in order to find out what the control device finally is doing.
During the summation process (depending on the order of processing within step 1 to 4), <commandInputs> or <controlParameters> might exceed the specified limits for that <controlDistributor> or <controlDevices>. As an intermediate result, this should be accepted – however, when it comes to evaluation in step 2 and 4, all <commandInputs> and <controlParameters> have to be within the specified limits.

Attributes

Name	Type	Use	Description
`@externalDataDirectory`	`xsd:string`	optional	Directory of the external file the element was read from, as URI
`@externalDataNodePath`	`xsd:string`	optional	Path of the parent element in the merged dataset, at which the element was inserted from an external file
`@externalFileName`	`xsd:string`	optional	Name of the external file the element was read from
`@uID`	`xsd:ID`	required	UID

Child elements

Name	Type	OccurrenceHow often the element may appear at this place. The schema writes it as minOccurs and maxOccurs on the declaration.	Description
allThe children below may appear in any order. Each may appear at most once.
`name`	`stringBaseType`	[0..1] optional	Name
`description`	`stringBaseType`	[0..1] optional	Description
`commandInputs`	`stringVectorBaseType`	[1..1] required	Vector of command inputs. The minimum and maximum value is given by the lowest and highest entry of the vector, respectively.
`controlElements`	`controlElementsType`	[1..1] required	Control elements driven by the control distributor

controlDistributorType

Attributes

Child elements

Used by

In a dataset · 2 paths

In the schema · 1 declaration