Differences

This shows you the differences between two versions of the page.

--- prorad:description [2012-03-16 08:21:23]
mortens
+++ prorad:description [2012-06-26 13:43:27]
mortens [Zero administration - almost]
@@ Line 1: / Line 1: @@
 ====== Overview ======
-The development of the ProRad software system started late 2005, and the first operational version was installed at met.no in June 2008. The parts of ProRad developed for processing polar volume data are currently pre-operational, and will be made operational early January 2012.
 ProRad in it's current configuration is capable of making mosaics, or composites, from 2D products, process polar volume data, produce 2D products from processed volume data to mention a few highlights.
@@ Line 8: / Line 5: @@
 The processing suite for 2D data and polar volumes includes
   * VPR correction
-  * clutter classification (sea, ground, sun flare - not tested for RLAN interference)
+  * clutter classification (sea, ground, sun flare - limited testing for RLAN interference)
-  * blockage calculation for 2D products and polar volumes
+  * beam blockage calculation for 2D products and polar volumes
   * precipitation classification - currently based on NWP data
   * accumulations
@@ Line 17: / Line 14: @@
   * clutter classification (e.g. sun flare, sea clutter, ground clutter)
   * clutter probability
-  * beam block percent (geometric)
+  * beam blockage percent (geometric)
   * precipitation classification (NWP based classification)
+====== Zero administration - almost ======
+All modules included in ProRad are built/coded in such a way that they will restart themselves if they should crash. This restart is logged to syslog. Datasets that would normally result from the processing, will be lost.
+ProRad's libraries for writing data are written so that they will return with an error if data could not be written to disk. The ProRad modules are coded to keep running if the disk where data should be stored becommes full or unavailable due to stale NFS-handles. The modules will resume normal operation as soon as disk space is available again; normally it will not be necesarry to restart the ProRad modules. Datasets that would normally result from the processing during the error state, will be lost.