Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
prorad:usage [2012-06-26 13:30:26] mortens [Configuration] |
prorad:usage [2022-05-31 09:29:32] (current) |
||
---|---|---|---|
Line 11: | Line 11: | ||
may copy these files to wherever you wish. | may copy these files to wherever you wish. | ||
- | In the following we assume you have a dedicated user for | + | In the following |
running the software, and that the software is installed in this users | running the software, and that the software is installed in this users | ||
home directory. | home directory. | ||
- | ===== Basic setup ===== | + | ===== Basic installation |
We use the following setup for our installation. | We use the following setup for our installation. | ||
Line 41: | Line 41: | ||
wish.) | wish.) | ||
+ | We also keep a similar structure for the configuration files | ||
- | ==== Data directory ==== | + | drwxr-xr-x |
+ | drwxr-xr-x | ||
+ | drwxr-xr-x | ||
+ | and here we aslo use a set of symlinks to point to various | ||
+ | subdirectories within the configuration package | ||
- | ==== Start & stop scripts | + | lrwxrwxrwx |
+ | lrwxrwxrwx | ||
+ | lrwxrwxrwx | ||
+ | ===== Diretories for storing datasets ===== | ||
+ | |||
+ | We have chosen to put the data files on a separate partition, and the | ||
+ | directories listed here is a minimum configuration for a ProRad node | ||
+ | performing volume filtering/ | ||
+ | mosaics from 2D products | ||
+ | |||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | |||
+ | We have chosen make a distinction between datasets that can easily be | ||
+ | recreated and those datasets that require more work to regenerate. The | ||
+ | former are stored in the ' | ||
+ | in the ' | ||
+ | belong in the ' | ||
+ | beam block calculations (not shown here) and PID-lock files stored by | ||
+ | each module to prevent multiple instances with identical | ||
+ | configurations to be started. |