 |
Read here the Frequently Asked Questions. If you are looking for a question you can't find, please contact us.
.wco files are configuration files, i.e. generated when you save your work in the Configuration Builder. .wml files are generated when you build (and parse) the .wco file, in the Configuration Builder – essentially, a .wml file combines the information on the plant layout (.wco file) with the relevant information on the models selected for each process unit, derived from the modelbase. A .wxp file is generated when you (create and) save your work in the Experimentation Environment. A .wxp file ‘reads’ (i.e. is built on top of) the corresponding .wml file. This ‘structure’ is very convenient to re-use experiment set-up, hence compare simulation results. If the .wco, .wml and .wxp files are contained within a folder, one can proceed as follows: - duplicate the entire folder and rename it - rename the .wco file .wco - rename the .wxp file .wxp Now, when you make changes to the configuration file and re-build, the .wml will be overwritten. And when you re-open the experiment file, this will read the new .wml and will maintain its original content (i.e. settings, plot windows, etc.).
Yes: by default, the WEST Manager, the Configuration Builder and the Model Editor will use the default modelbase and node library that have been copied to your disk upon installing WEST, typically in the Modelbase and Graph folders respectively, under the user’s My DocumentsHemmisWest folder. However, it is possible to work with different, custom libraries. In WEST Manager. Go to the Tools menu and select Options: under the Libraries tab, you may choose the Node Library and the Modelbase (through its root file, e.g. wwtp.msl), by browsing to the respective localtions. These model and node libraries will be used to compose new configurations. In the Configuration Builder. You may still change the model library used to create a .wml file from a configuration layout, in the Configuration Builder. Go to the menu Configuration, then Settings …: in the Libraries tab, you may specify the appropriate modelbase. In the Model Editor. Go to the Tools menu and select Options: under the Modelbase tab, you may choose the Node Library and the Modelbase (through its root file, e.g. wwtp.msl), by browsing to the respective localtions.
You create a (simple) configuration in WEST and no models are displayed in the drop-down menu for the selection of a process node sub-model. Solution. This is an indication that there is an error in the modelbase. Please note that the error may affect only the specific category that you have selected (to verify which category you have selected, go to the menu Configuration > Settings > Libraries) Proceed as follows: 1) Select the appropriate modelbase (wwtp.msl file) and open the Model Editor. 2) Select the appropriate category in the drop-down menu on the tool bar. 3) Check the modelbase (press the Check Modelbase button or F9): the error log will be displayed in the Log pane. 4) Fix the error and save the modelbase. 5) Go back to the Configuration Builder and refresh: now the correct list of sub-model should be displayed for each process node.
This typically happens when you attempt to access a category that someone else has implemented for you and it is due to the fact the WEST only makes available those categories that are implemented in the default modelbase. Solution. There are two locations where you may need to select a non-default category, i.e. in the Configuration Builder (because the list of sub-models available for a given process unit may be category-dependent) and in the Model Editor (to access the models available for a given category and to visualize the corresponding Petersen Matrix). Proceed as follows: 1) In the WEST Manager, go to the menu Tools > Options > Libraries. 2) In the box Categories, click on the Add button. 3) Enter the name of the new category: pay attention that it is case-sensitive ! The new category will now be accessible in the Configuration Builder: go to the menu Configuration > Settings > Libraries and then open the Category drop-down. Do the same, in the Model Editor: 4) Go to the menu Tools > Options > Modelbase. 5) In the box Categories, click on the Add button. 6) Enter the name of the new category. The new category will now be accessible from the drop-down menu in the toolbar of the Model Editor.
It may happen that, although you double-click on a specific process unit, the model root is still ‘focused’: as a consequence, the Properties of the general model (coupled model) will be displayed instead of the specific sub-model Properties – as you would expect. Solution. Simply, select and deselect the current unit (if necessary, one or two other units), until you see that the model root is no longer focused in the model explorer tree-view.
No, WEST 3.7.5 only allows one single text file (*.txt) to be used as an input file. This applies to input file for dynamic simulation as well as ‘cost’ input files for parameter optimization. Furthermore, one single time scale may be used within the input file: this means that all measured quantities will have the same time scale. For instance, it is not possible to input online COD determinations at 5-minute intervals and daily TSS measurements: you will have to either use (average) daily values for COD too, or to interpolate the TSS measurements to a 5-minute intervals. This however does not limit the actual number of individual wastewater streams that enter the plant or the number of individual datasets that can be used for the simulation (e.g. wastewater characterization, environmental temperature, experimental assessment of biokinetic quantities, such as growth rates, etc.). In fact, each individual stream (or dataset) may be conveniently represented by an input node. But all input nodes will access the same text file: therefore, all data will have to be arranged in one single text file in which only one column will be used as the common time scale.
This situation will prevent that you can open any of the three WEST applications, i.e. the Configuration Builder, the Experimentation Environment or the Model Editor. The error specifically indicates that the WEST Manager has lost the connection to one of its dependencies (i.e. one of the above applications). Solution. Simply shut down and then restart WEST. Should this not be sufficient and should you remark that an instance (either configuration or experiment) is active in the Workspace, go to the Task Manager and manually shut down any WEST-related running process. Then restart WEST.
This may happen when you change one of the sub-models in your configuration (typically when control units are involved) and immediately try to re-build it. This is due to the fact that all the interface links affected by the change in the sub-model are reset: if there is more than one option to link two units (typically, if one of the two is a control), WEST cannot ‘decide’ which one and will send out the error message. Solution. The error message also indicates which units are involved (From node … to node …): double-click on that connection and manually set the two interface variables.
This happens as you start a simulation and is caused by incorrect labeling of the variables in the input file (*.txt). Solution. Always make sure that the Internal Name of the input Interface Variable is the same as that used in the input file (also: it is case-sensitive). For instance, if the Internal Name in the input node is set to Influent, the variables in the input file will have to be named Influent(H2O), Influent(S_I), etc.
This message can be generated by the Borland C run-time library when the executable model attempts to compute a base-10 logarithmic function using a negative value as an argument.
|
