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:02:10] mortens |
prorad:usage [2022-05-31 09:29:32] (current) |
||
---|---|---|---|
Line 3: | Line 3: | ||
We recommend that the ProRad software is run by a dedicated UID, and | We recommend that the ProRad software is run by a dedicated UID, and | ||
we have chosen to install the software in the home directory of such a | we have chosen to install the software in the home directory of such a | ||
- | user. It may not be what you IT-department recommends, | + | user. It may not be what your IT-department recommends, |
have familiarised yourself with the software you will know what to do | have familiarised yourself with the software you will know what to do | ||
to comply with rules and regulations of your organisation. | to comply with rules and regulations of your organisation. | ||
Line 11: | Line 11: | ||
may copy these files to wherever you wish. | may copy these files to wherever you wish. | ||
- | In the examples to follow | + | In the following example |
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. | ||
+ | software is kept in a directory, named after the release: | ||
- | ==== Data directory ==== | + | drwxr-xr-x 29 uid uid 4096 2012-03-02 13:20 prorad-xml-1.3 |
+ | drwxr-xr-x 29 uid uid 4096 2012-03-14 14:49 prorad-xml-1.3.1 | ||
+ | drwxr-xr-x 29 uid uid 4096 2012-03-20 08:54 prorad-xml-1.3.2 | ||
+ | drwxr-xr-x 29 uid uid 4096 2012-06-21 10:18 prorad-xml-1.3.2.1 | ||
+ | And we use a set of symlinks which can be quickly rearranged if we | ||
+ | should detect problems and need to make a quick switch from one | ||
+ | release to another: | ||
- | ==== Start & stop scripts ==== | + | lrwxrwxrwx |
+ | and then we use this link to setup the symlink to the bin directory | ||
+ | lrwxrwxrwx | ||
+ | (This may seem a little counter intuitive, and it would be perfectly | ||
+ | fine to just to point the bin symlink directly to the directory | ||
+ | containing the current ProRad release. | ||
+ | things. | ||
+ | wish.) | ||
+ | |||
+ | We also keep a similar structure for the configuration files | ||
+ | |||
+ | 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 | ||
+ | |||
+ | 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. |