Page History

...

At the catchment level, an enabled tag is configured for each of the three modules within the catchment workflow. Each enabled <attributeId> is associated to the module to be modified, allowing flexibility in toggling each module. 

To configure the location of the modified attribute, a dummy variable must be created, which was configured within a transformation module (URBS_Merge_Rainfall in this example). The other two modules in the workflow are general adapter modules, which I’m unsure if variable’s can be configured in the way that is required (potentially in the export/import activity sections). The variable contains each of the locations configured in the SystemSettings.csv, which can then be referenced across the entire workflow, as long as transformation URBS_Merge_Rainfall is configured within the workflow. 

<workflow xmlns="http://www.wldelft.nl/fews" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.wldelft.nl/fews 
http://fews.wldelft.nl/schemas/version1.0/workflow.xsd" version="1.1">
	<properties>
		<string key="CATCHMENT" value="Burringbar"/>
		<string key="TIME_ZONE" value="AEST"/>
		<int key="MODEL_START" value="-7"/>
		<string key="REGION" value="Tweed"/>
	</properties>
	<activity>
		<properties>
			<string key="CATCHMENT" value="Burringbar"/>
		</properties>
		<enabled locationId="Burringbar_System" attributeId="URBS_Deploy"/>
		<runIndependent>true</runIndependent>
		<workflowId>Update_Model_Directory</workflowId>
	</activity>
	<activity>
		<properties>
			<string key="CATCHMENT" value="Burringbar"/>
		</properties>
		<enabled locationId="Burringbar_System" attributeId="URBS_Merge"/>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>URBS_Merge_Rainfall</moduleInstanceId>
		<moduleConfigFileName>URBS_Merge_Rainfall</moduleConfigFileName>
	</activity>
	<activity>
		<properties>
			<string key="CATCHMENT" value="Burringbar"/>
		</properties>
		<enabled locationId="Burringbar_System" attributeId="URBS_Fcst"/>
		<runIndependent>true</runIndependent>
		<moduleInstanceId>URBS_Burringbar_Forecast</moduleInstanceId>
	</activity>
</workflow>

...

To configure the location of the modified attribute, a dummy variable must be created, which was configured within a transformation module (URBS_Merge_Rainfall in this example). The other two modules in the workflow are general adapter modules, which I’m unsure if variable’s can be configured in the way that is required (potentially in the export/import activity sections). The variable contains each of the locations configured in the SystemSettings.csv, which can then be referenced across the entire workflow, as long as transformation URBS_Merge_Rainfall is configured within the workflow. 

...

	<variable>
        <variableId>Dummy_Modifier_1</variableId>
		<timeSeriesSet>
			<moduleInstanceId>URBS_Merge_Rainfall</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>P.obs</parameterId>
			<locationSetId>SystemSettings_$REGION$</locationSetId><!-- tag for template use -->
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="hour"/>
			<readWriteMode>read only</readWriteMode>
		</timeSeriesSet>
    </variable>

 Image Removed

 Some tinkering is still required to summarize the modifier display, although it worksThis is sufficient to make it wor, toggling modules for the 3 catchments (Burringbar Creek, Crabbes Creek, Tweed River) and toggling the Archive workflow for the entire Tweed region workflow. 

You can add configuration to summarize the modifier display etc (see ModifierTypes.xml). 

 Image Added