Meta Control File
After reading the Control File, RiverWare writes the “Meta Control File.” The Meta Control File is similar to the Control File, but all symbolic representation of objects, slots, and file names are fully resolved. (See
Object.Slot Specifications and
File Name and Directory Specification information on symbolic representation of objects, slots, and file names in the Control File.)
Consider the following example:
• A model has three reservoir objects: Blue Lake, Green Lake, Deep Lake.
• The environment variable RIVERWARE_DATA is C:\RiverWareData
• The Control File has the following line:
Reservoir.Inflow: file=$RIVERWARE_DATA/Inputs/%o.%s.dat
This will result in the following three lines in the Meta Control File.
Blue Lake.Inflow: file=C:/RiverWareData/Inputs/Blue_Lake.Inflow.dat
Green Lake.Inflow: file=C:/RiverWareData/Inputs/Green_Lake.Inflow.dat
Deep Lake.Inflow: file=C:/RiverWareData/Inputs/Deep_Lake.Inflow.dat
The Meta Control File is written before RiverWare starts the DMI Executable, so the Meta Control File is available for reading by the DMI executable.
The default location of the Meta Control File is in the user’s temp folder, in a sub-folder with the DMI’s name. That is usually something like the following:
C:\Users\<user name>\AppData\Local\Temp\<DMI_Name>\metaControl
If the environment variable RIVERWARE_DMI_DIR has been set, the Meta Control file will be located as follows:
$RIVERWARE_DMI_DIR\<DMI_NAME>\metaControl
For example, if the DMI name is “Operations Inputs DMI,” and RIVERWARE_DMI_DIR is C:\RiverWareData, the Meta Control File will be at
C:\RiverWareData\Operations_Inputs_DMI\metaControl
RiverWare will create the folder with the DMI name if it does not exist.