| | 12 | = How to install pipeline = |
| | 13 | |
| | 14 | 1. Getting access to PS server |
| | 15 | {{{ |
| | 16 | ssh -X username@ippc?? |
| | 17 | }}} |
| | 18 | 2. Download the pipeline into your home directory |
| | 19 | {{{ |
| | 20 | svn co http://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk |
| | 21 | }}} |
| | 22 | 3. To properly install the code, follow the instruction in README in the root directory of the pipeline. |
| | 23 | {{{ |
| | 24 | cd $TRUNK/psconfig |
| | 25 | }}} |
| | 26 | and follow INSTALL instruction. TRUNK is the path-address of the pipeline. At this stage, all necessary executable (binary) files would be compiled. |
| | 27 | * Note: Use "{{{psbuild -dev -extbuild}}}" in order to compile everything. |
| | 28 | 4. Modify {{{.tcshrc}}} in your home directory. This is where all necessary environmental variables are initialize for the shell you are using. Also see http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/wiki/IPP_on_ifaps1?action=edit |
| | 29 | |
| | 30 | Usually, looking at `~ipp/.tcshrc` will give you an idea how to set-up your own `~/.tcshrc`. |
| | 31 | |
| | 32 | 5. Source `.tcshrc` or open another `tcsh` sehll by running `tcsh`. |
| | 33 | {{{ |
| | 34 | source ~/.tcshrc |
| | 35 | }}} |
| | 36 | |
| | 37 | 6. After all, you may find you cannot still run your desired IPP commands, therefore you may need to either modify your `.tcshrc` or compile some extra packages. Normally all packages should be installed all at once, unless some last minute changes have been introduced to some components. |
| | 38 | |
| | 39 | 7. Consult to an IPP expert if you are stuck. |