Changes between Version 1 and Version 2 of ParallelIPPvers
- Timestamp:
- Apr 1, 2009, 9:12:10 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ParallelIPPvers
v1 v2 1 1 2 = Making an IPP installation accessible to multiple users = 2 3 … … 5 6 There's one directory where all IPP installations live. By default, it's ~/psconfig/ but you can make it a different location by creating a file ~/.psconfigrc which contains 6 7 8 {{{ 7 9 set PSCONFDIR = /IPP/ 10 }}} 8 11 9 12 Then create a directory $PSCONFDIR/psconfig and copy the psconfig.bash and psconfig.csh scripts there from the source tree (this is something that the build/install will probably do automatically in future). … … 11 14 The only thing that's missing is an alias for psconfig that reads those .csh or .bash files: 12 15 16 {{{ 13 17 bash: alias psconfig='source /IPP/psconfig.csh' 14 18 csh: alias psconfig "source /IPP/psconfig.bash" 19 }}} 15 20 16 21 Alternating between versions installed in a global directory and versions installed in your own home directory is possible, but you need to unset PSCONFDIR, make sure that there's no .psconfigrc (e.g. by renaming it), and point psconfig at the different different directory, so I don't recommend it. … … 22 27 If ipp was installed with 23 28 29 {{{ 24 30 psbuild -bootstrap PSCONFDIR 31 }}} 25 32 26 33 the psconfig.bash and psconfig.csh point to the IPP installations in PSCONFDIR by default. Thus, for other users to use a given IPP install, they just need to create the same psconfig alias as the person who installed IPP, i.e. 27 34 35 {{{ 28 36 alias psconfig="source PSCONFDIR/psconfig.bash" 37 }}} 29 38 30 39 for bash, or 31 40 41 {{{ 32 42 alias psconfig "source PSCONFDIR/psconfig.csh" 43 }}} 33 44 34 45 for [t]csh. … … 38 49 In Heidelberg, there's always a softlink ipp-default pointing to the most recent installed version of IPP. To use that, then just issue the command 39 50 51 {{{ 40 52 psconfig ipp-default 53 }}} 41 54 42 55 on the command-line. … … 48 61 IPP has a config file hierarchy. There are two per-user config files: 49 62 63 {{{ 50 64 ~/.ipprc # Definitions for psphot etc. 51 65 ~/.ptolemyrc # Definitions for dvo 66 }}} 52 67 53 68 There are templates for both files, so to begin with, just copy those into your home directory. In Heidelberg, suitable templates are at 54 69 70 {{{ 55 71 cp /IPP/ipprc.template ~/.ipprc 56 72 cp /IPP/ptolemyrc.template ~/.ptolemyrc 73 }}} 57 74 58 75 The configuration system is hierarchical, with defaults in the global ippconfig directories that can be overridden by definitions in user-specified directories. E.g. to include camera definitions that are located in your own file area, edit the PATH in .ipprc: 59 76 77 {{{ 60 78 PATH STR /home/jester/IPP/ippconfig/:MYINSTALLDIR/share/ippconfig: 79 }}} 61 80 62 81 This looks for any required configuration files first in /home/jester/IPP/ippconfig/ and if it does not find a match there, takes the IPP-wide defaults. At present, you have to replicate an entire file in your own area if you want to change a single setting from the default. Also note that there is an internal hierarchy, with files in the recipes/ folder setting defaults that can be overriden in camera-specific files; the catch is that a concept MUST be present in the recipes/ version of a config file (i.e. you can't add new things in a camera-specific file). … … 69 88 70 89 Get IPP tarfile or export from cvs and set the new version ID; including the date if from cvs, or using the version number if a numbered release 90 91 '''Warning: these are outdated as we have moved from cvs to svn. However, I haven't done the equivalent in svn yet.''' 92 93 {{{ 71 94 # Access IPP cvs 72 95 export CVSROOT=cvs.pan-starrs.ifa.hawaii.edu:/cvsroot/pan-starrs; export CVS_RSH=ssh … … 86 109 psbuild -dev -extbuild 87 110 # omit the -dev if building from a version-numbered tarball 111 }}} 88 112 89 113 If using pantasks, update your <code>~/.bashrc</code> (or equivalent) to point to the new version. Done! … … 93 117 I wanted an install tree that has just Ohana i.e. dvo. To do that, I say 94 118 119 {{{ 95 120 psconfig dvo-2.2 121 }}} 96 122 97 123 which sets up a new install tree $PSCONFDIR/dvo-2.2. I then compile and install only Ohana: 98 124 125 {{{ 99 126 psbuild -only Ohana -rebuild -clean 127 }}} 100 128 101 129 I definitely need -rebuild because otherwise there may still be files pointing to the previous install directory and nothing happens because those are still up to date. I just threw in -clean for good measure, as I wouldn't bet on everything working without it. … … 105 133 == Just analysis tools but not pipeline or anything that requires sql == 106 134 135 {{{ 107 136 psconfig ipp-2.2-nosql 108 137 psbuild -only Ohana -rebuild && psbuild -start psLib -stop ppSim -rebuild && psbuild -only ippconfig -rebuild 138 }}} 109 139 110 140 I tried these without -clean and will see what happens. … … 114 144 To use my just-Ohana tree, I log in and say 115 145 146 {{{ 116 147 psconfig dvo-2.2 148 }}} 117 149 118 150 I can then use dvo. … … 120 152 Similarly, for the analysis-only distribution I say 121 153 154 {{{ 122 155 psconfig ipp-2.2-nosql 156 }}} 123 157 124 158 and can run psphot.
