1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
This distribution contains:
README This file
sinfo-manual-4.0.pdf The SINFONI pipeline manual
install_pipeline Install script
qfits-6.2.0.tar.gz QFITS 6.2.0
cpl-3.1.tar.gz CPL 3.1
esorex-3.6.1.tar.gz esorex 3.6.1
gasgano-2.2.7.tar.gz GASGANO 2.2.7 for SunOS 5.8
sinfo-1.7.1.tar.gz SINFONI 1.7.1
sinfo-calib-1.7.1.tar.gz SNFONI calibration files 1.7.1
To install the pipeline execute the install script:
./install_pipeline
The script will ask you to specify under what directory the software
and the calibration files should be installed: you can just press
return if the proposed default (i.e., your home-directory) suits you.
The software installation will be organised in bin/, lib/, include/ and share/
sub-directories, while the calibration files will be
installed in a calib/ sub-directory. Pay attection to any information,
in particular possible warnings indicated by the install script.
To have Gasgano installed you need to make sure you have the Java Development
Kit (JDK, version 1.5.0) properly installed and the JAVA_HOME environment
varaiable set to point to the directory where the JDK is.
Alternatively, if you are an experienced user you may decide to install
only the packages you are actually going to use. To do so you have to
unpack, configure, build and install the packages of your choice manually.
You can find the packages in the root directory of the unpacked distribution,
or even download them separately from the corresponding Web pages. Note
that a cksum file is associated to each package: this file has the same
name of the corresponding package, but with extension .cksum instead of
.tar.gz (e.g., the cksum of package cpl-3.1.tar.gz is contained in the
file cpl-3.1.cksum). It is advisable to compare the output of the cksum
command applied to each package with the content of the corresponding files,
to ensure that the packages were copied withour errors. In general, the
output of the command
$ cksum *.gz
should be identical to the output of the command
$ cat *.cksum
The qfits package must be installed first, and the CPL package next.
The eclipse-sinfo external library need to be installed before the SINFONI package.
It doesn't matter in what order are installed 'esorex', 'gasgano', and
the SINFONI pipeline recipes. The packages 'esorex' and 'gasgano' are
optional, but you need at least one of them for using the SINFONI recipes.
For detailed instructions on the installation of the individual packages
please refer to the information provided by these packages. Below we provide
a typical sequence of steps for a valid installation.
1. In the following we suppose the user does an installation in the directory ${HOME}/pipelines
It is usefult to have set the environment variables CPLDIR and QFITSDIR. In our case as
(the following commands are valid if the user is running bash):
$ export CPLDIR=${HOME}/pipelines
$ export QFITSDIR=${CPLDIR}
$ mkdir ${CPLDIR}
2. Unpack the qfits distribution into a directory of your choice
and 'cd' into it. For example:
$ gunzip qfits-6.2.0.tar.gz
$ tar -xvf qfits-6.2.0.tar
$ cd qfits-6.2.0/
3. Setup the qfits package by running configure. For example
(assuming that CPLDIR points to a chosen installation directory):
$ ./configure --prefix=${CPLDIR} --max-ptrs=562168 --debug
Note:
Mac users at this stage should also specify --enable-memory-mode=1
4. Build and install qfits. For example:
$ make
$ make install
$ cd ..
5. Unpack the CPL distribution into a directory of your choice and
'cd' into it. For example:
$ gunzip cpl-3.1.tar.gz
$ tar -xvf cpl-3.1.tar
$ cd cpl-3.1/
5. Run 'configure' with the appropriate settings (installation
prefix, location of the qfits installation...). For example
(assuming that CPLDIR points to a chosen installation directory,
and that qfits was installed in the same location):
$ ./configure --prefix=${CPLDIR} --enable-debug
6. Build and install 'cpl':
$ make
$ make install
$ cd ..
7. Unpack the 'esorex' distribution into a directory of your choice
and 'cd' into it. For example:
$ gunzip esorex-3.6.1.tar.gz
$ tar -xvf esorex-3.6.1.tar
$ cd esorex-3.6.1/
8. Run 'configure' with the appropriate settings. For example
(assuming that CPLDIR points to a chosen installation directory,
and that both qfits and CPL were installed in the same location):
$ ./configure --prefix=${CPLDIR} --enable-debug
9. Build and install 'esorex':
$ make
$ make install
$ cd ..
10. Unpack the appropriate gasgano distribution for your platform
in your home directory (ensure that you are not overwriting
an existing 'gasgano' installation):
$ cd
$ gunzip -c gasgano-2.2.4-Linux.tar.gz | tar xovf -
$ ln -s gasgano-2.2.4-Linux gasgano
$ export PATH="$HOME/gasgano/bin:"$PATH
$ cd -
11. Unpack the 'sinfo' distribution into a directory of your choice and
'cd' into it. For example:
$ gunzip sinfo-1.7.1.tar.gz
$ tar -xvf sinfo-1.7.1.tar
$ cd sinfo-1.7.1
12. Run 'configure' with the appropriate settings. For example
(assuming that CPLDIR points to a chosen installation directory,
and that both qfits, CPL, eclipse-sinfo were installed in the same location):
$ ./configure --prefix=${CPLDIR} --enable-debug
13. Build and install 'sinfo':
$ make
$ make install
14. Include CPLDIR in your path:
$ export PATH=${PATH}:${CPLDIR}
15. Include CPLDIR in your path:
$ export PATH=${PATH}:${CPLDIR}/bin
16. In order to use the just installed SINFONI recipes with 'esorex'
you can either use the '--recipe-dir' command line option
and pass the path to the recipes as argument when esorex
is called. For instance,
$ esorex --recipe-dir=${HOME}/pipelines/lib/sinfo/plugins/sinfo-1.7.1 [...]
Alternatively an 'esorex' run-time configuration file can be
created and/or updated, either manually or automatically (i.e.,
using 'esorex' itself). The 'esorex' configuration file is
$HOME/.esorex/esorex.rc
If no such file exists you can create it by simply running
esorex with the command line option '--create-config' and
the '--recipe-dir' option. For example:
$ esorex --create-config --recipe-dir=${HOME}/pipelines/lib/sinfo/plugins/sinfo-1.7.1
If the configuration file already exists, the same command
will simply upgrade it: all previous settings apart from
the entry 'esorex.caller.recipe-dir' are inherited from
the previous file. The original file will be saved as
$HOME/.esorex/esorex.rc.bak .
The 'esorex' configuration file may also be modified using
an editor. The entry 'esorex.caller.recipe-dir' is the one
to modify. Its argument consist of a colon separated list
of directories, which are searched for recipes when running
'esorex'. For instance:
esorex.caller.recipe-dir=<path1>:<path2>:${HOME}/pipelines/lib/sinfo/plugins/sinfo-1.7.1
where the new path is appended to the existing ones. Old paths,
valid for older installations, may be removed from the list.
For further information about configuring 'esorex' please refer
to the 'esorex' documentation (see http://www.eso.org/cpl).
2. To add the just installed SINFONI recipe set to the 'gasgano'
recipe set, you must use the preferences dialog of 'gasgano'.
It is available from its 'File' menu on the main window.
Select the tab 'Recipe Configuration' and modify the recipe
set as found appropriate. For instance, if SINFONI was installed
in the directory tree rooted at ${HOME}/pipelines
you will find the recipes in:
${HOME}/pipelines/lib/sinfo/plugins/sinfo-1.7.1
For further information about 'gasgano' please refer to the
Gasgano User Manual (see http://www.eso.org/gasgano).
Reporting Bugs
--------------
Please report any bugs to <usd-help@eso.org>
For support contact <usd-help@eso.org> or, alternatively, Lars Lundin
<llundin@eso.org> for the installation script, and Andrea Modigliani <amodigli@eso.org>
for the pipeline recipes.
|
