OR/14/011 Troubleshooting: Difference between revisions

From MediaWiki
Jump to navigation Jump to search
Ajhil (talk | contribs)
Created page with "__NOTOC__ {{OR/14/011}} OPENING EXECUTABLE • Check the number of available screens on computer. If displaying on a projection, the model may be opening on a separate screen...."
 
Ajhil (talk | contribs)
No edit summary
Line 1: Line 1:
__NOTOC__
__NOTOC__
{{OR/14/011}}
{{OR/14/011}}
OPENING EXECUTABLE
====Opening executable====
• Check the number of available screens on computer. If displaying on a projection, the model may be opening on a separate screen. This can be checked by searching the Applications list in Windows Task Manager for the CLiDE executable running.
* Check the number of available screens on computer. If displaying on a projection, the model may be opening on a separate screen. This can be checked by searching the Applications list in Windows Task Manager for the CLiDE executable running.


OPENING XML FILE
====Opening XML file====
• If the XML file has been edited using a text editor, an item within the XML may have been renamed. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.
* If the XML file has been edited using a text editor, an item within the XML may have been renamed. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.
• An XML saved in an older version of CLiDE may not work with newer versions and vice versa due to a different list of variables required in the XML file. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.
* An XML saved in an older version of CLiDE may not work with newer versions and vice versa due to a different list of variables required in the XML file. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.
 
LOADING INITIALISATION DATA
• Check that the size of each array matches the other arrays and the header information.
• Check date information in Setup tab is as expected.
• Use a different text editor to view input files (line returns are picked up by some and not others). Notepad++ is recommended.
 
SIMULATION FREEZES
• Allow the simulation time to process large amounts of data. When processing a catchment with a large number of nodes the daily timestep may take a few minutes to complete.
• Increase the amount of memory available to the program by reducing the memory limit in the
Setup tab to 1.
• Check groundwater input file for zero, negative or small values (<10 m). If the groundwater reaches zero during the simulation this can cause instability. To prevent this, the entire catchment can be uplifted by adding 50 m to each nodal elevation in the DEM, bedrock and initial groundwater files. This can be removed during post-processing if required.
• Check rainfall and potential evapotranspiration data exist for the previous, current and proceeding timestep being simulated when the platform froze.
• Ensure output from previous simulation is not open in another program, as output files can not be over-written (as an exception, some text editors will allow this).
 
NO OUTPUT IS PRODUCED
• Check the save file time in the Setup tab is as expected (a value of 1440 is daily).
 
• Check options are checked in the Save Options bar at the top of the GUI.
• Check you are in the CLiDE


====Loading initialisation data====
* Check that the size of each array matches the other arrays and the header information.
* Check date information in Setup tab is as expected.
* Use a different text editor to view input files (line returns are picked up by some and not others). Notepad++ is recommended.


====Simulation freezes====
* Allow the simulation time to process large amounts of data. When processing a catchment with a large number of nodes the daily timestep may take a few minutes to complete.
* Increase the amount of memory available to the program by reducing the memory limit in the
* Setup tab to 1.
* Check groundwater input file for zero, negative or small values (<10 m). If the groundwater reaches zero during the simulation this can cause instability. To prevent this, the entire catchment can be uplifted by adding 50 m to each nodal elevation in the DEM, bedrock and initial groundwater files. This can be removed during post-processing if required.
* Check rainfall and potential evapotranspiration data exist for the previous, current and proceeding timestep being simulated when the platform froze.
* Ensure output from previous simulation is not open in another program, as output files can not be over-written (as an exception, some text editors will allow this).


====No output is produced====
* Check the save file time in the Setup tab is as expected (a value of 1440 is daily).
* Check options are checked in the Save Options bar at the top of the GUI.
* Check you are in the CLiDE
[[Category:OR/14/011 CLiDE version 1.0 user guide | 06]]
[[Category:OR/14/011 CLiDE version 1.0 user guide | 06]]

Revision as of 11:39, 9 March 2022

Barkwith, A* and Coulthard, T J**. 2011. CLiDE version 1.0 user guide. British Geological Survey Open Report, OR/14/011.

* British Geological Survey, Environmental Science Centre, Keyworth, Nottingham, NG12 5GG, UK
** Department of Geography, Environment and Earth Science, University of Hull, Cottingham Road, Hull, HU6 7RX, UK

Opening executable

  • Check the number of available screens on computer. If displaying on a projection, the model may be opening on a separate screen. This can be checked by searching the Applications list in Windows Task Manager for the CLiDE executable running.

Opening XML file

  • If the XML file has been edited using a text editor, an item within the XML may have been renamed. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.
  • An XML saved in an older version of CLiDE may not work with newer versions and vice versa due to a different list of variables required in the XML file. Save a new XML under a different name and compare the name of each variable to the XML that is needed. Update differing variable names.

Loading initialisation data

  • Check that the size of each array matches the other arrays and the header information.
  • Check date information in Setup tab is as expected.
  • Use a different text editor to view input files (line returns are picked up by some and not others). Notepad++ is recommended.

Simulation freezes

  • Allow the simulation time to process large amounts of data. When processing a catchment with a large number of nodes the daily timestep may take a few minutes to complete.
  • Increase the amount of memory available to the program by reducing the memory limit in the
  • Setup tab to 1.
  • Check groundwater input file for zero, negative or small values (<10 m). If the groundwater reaches zero during the simulation this can cause instability. To prevent this, the entire catchment can be uplifted by adding 50 m to each nodal elevation in the DEM, bedrock and initial groundwater files. This can be removed during post-processing if required.
  • Check rainfall and potential evapotranspiration data exist for the previous, current and proceeding timestep being simulated when the platform froze.
  • Ensure output from previous simulation is not open in another program, as output files can not be over-written (as an exception, some text editors will allow this).

No output is produced

  • Check the save file time in the Setup tab is as expected (a value of 1440 is daily).
  • Check options are checked in the Save Options bar at the top of the GUI.
  • Check you are in the CLiDE