Differences

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

--- prorad:usage [2012-06-26 14:10:29] – [Basic setup] mortens
+++ prorad:usage [2012-08-21 08:50:45] (current) – [Diretories for storing datasets] christofferae
@@ Line 40: / Line 40: @@
 things.  Feel free to deviate from this recommendation if you so
 wish.)
+We also keep a similar structure for the configuration files
+  drwxr-xr-x  8 uid uid 4096 2012-02-09 12:36 config-xml-1.3
+  drwxr-xr-x  8 uid uid 4096 2012-03-19 15:17 config-xml-1.3.1
+  drwxr-xr-x  8 uid uid 4096 2012-03-20 09:41 config-xml-1.3.2
+and here we aslo use a set of symlinks to point to various
+subdirectories within the configuration package
+  lrwxrwxrwx  1 uid uid   16 2012-03-29 16:26 prorad-config -> config-xml-1.3.2
+  lrwxrwxrwx  1 uid uid   17 2012-01-16 10:06 etc -> prorad-config/etc
+  lrwxrwxrwx  1 uid uid   21 2012-01-16 10:06 scripts -> prorad-config/scripts
@@ Line 52: / Line 66: @@
   /disk1/proradfiles/permanent
   /disk1/proradfiles/permanent/var-run
+  /disk1/proradfiles/permanent/foo-mask
+  /disk1/proradfiles/permanent/map-mask
   /disk1/proradfiles/short-term
   /disk1/proradfiles/short-term/reproj-files
   /disk1/proradfiles/short-term/geotiff
   /disk1/proradfiles/script-dirs
   /disk1/proradfiles/script-dirs/images
   /disk1/proradfiles/script-dirs/ftp-logs
   /disk1/proradfiles/long-term
   /disk1/proradfiles/long-term/mom-messages
   /disk1/proradfiles/long-term/log4cxx
   /disk1/proradfiles/long-term/prorad-acrr
@@ Line 70: / Line 82: @@
   /disk1/proradfiles/long-term/mosaics
   /disk1/proradfiles/long-term/prorad-import
+  /disk1/proradfiles/long-term/prodgen-products
+We have chosen make a distinction between datasets that can easily be
-==== Data directory ====
+recreated and those datasets that require more work to regenerate. The
+former are stored in the 'short-term' directory, the latter are stored
+in the 'long-term' directory. There is also a category of files which
-==== Start & stop scripts ====
+belong in the 'permanent' directory, these include datasets related to
+beam block calculations (not shown here) and PID-lock files stored by
+each module to prevent multiple instances with identical
+configurations to be started.