...
- Take some time to understand what files are stored where and why in the configuration
- Understand the way how the configurations of different files are related to each other
- Practise the file relations and the navigation to the related files (e.g. workflows & workflow descriptor etc.)
- Create a (visual) overview containing the different functions of the files (e.g. explorer.xml, filters.xml, topology.xml etc.)
- Create a (visual) overview of relations between configured elements and time lengths
- The clientConfig.xml that is used to create a shortcut is placed under “RootConfigFiles”
- If you create a short cut for an Operator Client or Config Manager place each of those in separate folder, not in your region home.
Understanding the project structure system and configuration task
- Follow the conventions used in a projectsystem
- Use the Workflow Navigator to understand the system, especially helpful could be the right click -> Highlight Usage function
- Make a list of every step that is required to get to the desired solution in advance
- Create a (visual) overview of the problem implementation
- Take into account how the configured element will be used by the end user
- If available have a look at an example for your first configuration tasks.
...
- F10: shows time series graphically in timeseries display (selecting a time series)
- F11: shows time series graphically in spatial display (selecting a time series)
- Right-click on a time series provides additional options
Workflow Navigator
- F10: shows time series graphically in timeseries display (selecting a time series); Before version 2024.01 this shortcut was Ctrl+6
- F11: shows time series graphically in spatial display (selecting a time series); Before version 2024.01 this shortcut was Ctrl+9
- Right-click on a time series provides additional options
Data handling
- Always reload the configuration in FEWS with F5 after making changes to the configuration.
- When importing always check that the data is still available in the import folder.
- Use a version tracking system like subversion for managing changes.
- If not configured differently data from the import folder is deleted after the import → make a safety copy of the data in this case
- To avoid that the data is deleted from the import folder in a testing phase it is possible to use “deleteImportedFiles = false” in the configuration
- In case of mistakes or during debugging it might be useful to have a clear database viewer. First make a safety copy of the local data store (region home) to a separate folder.
...
- Keep in mind to start with the export activity in the general adapter module, because:
- Export: fews > model,
- Import: model > fews
- The modules folder (region home) is constantly overwritten by the ModuleDataSetFiles→ it doesn’t make sense to change anything in the modules folder
- For debugging it could be useful to run the model once outside Delft-FEWS