Page History

...

11. Troubleshooting tips

It is highly unlikely possible that a module will run correctly on the first try. First step is to make sure the model runs ok outside of the configuration.

• Run the model outside of Delft-FEWS
  • Examine the input files generated by Delft-FEWS
    • If they are not ok, solve this issue first
  • Run the model outside of Delft-FEWS, but use the input generated by Delft-FEWS
    • If the model doesn't run properly, examine the model log files and solve the issue
    • If the model does run properly, import the results in FEWS by only using the import part of the generalAdapater.

If the model runs ok outside of Delft-FEWS, the cause is likely in your configuration. Here are some general tips on de-bugging the configuration. Note: These tips will not help if the module itself poses an issue.

• When you have selected the appropriate workflow in the Manual Forecast tab
  • Press ctr+r to select specific module instances within a workflow.
  • Press ctr+d to activiate debug mode for specific module instances within a workflow. FEWS will then display additional de-bugging information in the log window.
• General Adapter
  • Run only certain activities (i.e. only data export) by commenting out unwanted activities in the generalAdapter.
    You make a comment by putting the text between <!-- and -->, or in XmlSpy press ctrl-k when you have selected the text.
  • Reduce the relativeViewPeriod within the generalAdapter to shorten run times for de-bugging purposes.
• The F12 menu contains many tools that may be helpful in examining data, data conversion, and data export.
  Open this menu by pressing F12 when you have the focon the Logs window or the Map tab.
  • Database Viewer (F12 menu, Option J): to view all data imported by FEWS from the module.