Project

General

Profile

Processing Server Installation » History » Version 13

Amber Herold, 04/06/2010 02:20 PM

1 10 Amber Herold
h1. Processing Server Installation
2 1 Amber Herold
3 10 Amber Herold
4
h2.  Install prerequisite supporting packages first if missing:
5
6
7
Follow the instruction for your specific Linux distribution.
8
9
For example, SUSE users can use YaST to install them; RedHat and CentOS users can use
10
yum.
11
12
h3.  Required supporting packages:
13
14
|_.Name:|_.Download site:|_.yum package name|_.SuSE rpm name|
15
|Python 2.4 or newer| "http://www.python.org":http://www.python.org|python|python-devel|
16
|wxPython 2.5.2.8 or newer| "http://www.wxpython.org":http://www.wxpython.org|wxPython|python-wxGTK|
17
|MySQL Python client 1.2 or newer| "http://sourceforge.net/projects/mysql-python":http://sourceforge.net/projects/mysql-python|MySQL-python|python-mysql|
18
|Python Imaging Library (PIL) 1.1.4 or newer| "http://www.pythonware.com/products/pil/":http://www.pythonware.com/products/pil/|python-imaging|python-imaging|
19
|Python XML module 0.8.3 or newer| "http://pyxml.sourceforge.net":http://pyxml.sourceforge.net|PyXML|python-xml|
20
|NumPy 1.0.1 or newer| "http://www.scipy.org":http://www.scipy.org|numpy|numpy|
21
|SciPy 0.5.1 (tested, others may work)*| "http://www.scipy.org":http://www.scipy.org ,  "http://repos.opensuse.org/science":http://repos.opensuse.org/science *|scipy|python-scipy|
22
23
24
*SciPy may not build properly on some versions of SuSE due to an incompatible LAPACK
25
package that comes with SuSE. You can get scipy as well as a compatible LAPACK etc. from
26
http://repos.opensuse.org/science (need to specify your SuSE version and machine
27
etc.)
28
29
30
h2. Setup Appion programs
31
32 1 Amber Herold
Download Myami.  
33
*TODO: Place link to file here!*
34
35
h3. Perform system check:
36 8 Amber Herold
37 1 Amber Herold
In addition to the downloads from our svn repository, there are several other requirements that you will get either from your OS installation source, or from its respective website. The system check in the Leginon package checks your system to see if you already have these requirements.
38
39 10 Amber Herold
<pre>
40 1 Amber Herold
cd your_download_area/Leginon-1.6-ALL/Leginon *TODO: fix this path*
41
python syscheck.py
42 10 Amber Herold
</pre>
43 1 Amber Herold
44
If python is not installed, this, of course will not run. If you see any lines like "*** Failed...", then you have something missing. Otherwise, everything should result in "OK".
45
46 10 Amber Herold
h3. Install the package in _each folder_ with commands like these
47 1 Amber Herold
48
*TODO: move these into a single installer, ask Jim*
49
50 10 Amber Herold
<pre>
51 1 Amber Herold
cd /your_download_area/myami/leginon
52
python setup.py install
53
54
cd ../pyami
55
python setup.py install
56
cd ../pyScope
57
python setup.py install
58
cd ../sinedon
59
python setup.py install
60
cd ../numextension
61
python setup.py install
62
cd ../libcv
63
python setup.py install
64
cd ../imageviewer
65
python setup.py install
66 10 Amber Herold
</pre>
67 1 Amber Herold
68
h3. python-site-package-path: where the installed python packages went:
69
70
Python installer put the packages you installed to its site-packages directory. This enable all users on the same computer to access them. The easiest way to find where your installed package is called by python is to load a module from the package using interactive python command lines like this:
71
72
    * Start python command line from shell
73 10 Amber Herold
      <pre>> python</pre>
74 1 Amber Herold
75
    * Import a module from the package. Let's try sinedon here. All packages installed through the above setup.py script should go to the same place.
76 10 Amber Herold
      <pre>python> import sinedon</pre>
77 1 Amber Herold
78
79
    * If the module is loaded successfully, call the module attribute __path__ (two underscrolls before "path" and two underscrolls after) will return the location of the module it is loaded from
80 10 Amber Herold
<pre>
81 1 Amber Herold
      python> sinedon.__path__
82
83
      RETURNS, For example,
84
      python> <module 'sinedon' from '/usr/lib/python2.5/site-packages/sinedon/__init__.pyc'> 
85 10 Amber Herold
</pre>
86 1 Amber Herold
      In this case, /usr/lib/python2.5/site-packages/ is your python-site-package-path. If you go to that directory, you will find all the packages you just installed.
87
88 10 Amber Herold
h3. Configure leginon.cfg
89 1 Amber Herold
90
A skeleton (default) configuration file is available:
91 11 Amber Herold
<pre>
92
[python-site-package-path]/Leginon/config/default.cfg
93
</pre>
94 1 Amber Herold
95
* Copy default.cfg to leginon.cfg.
96 10 Amber Herold
<pre>
97 1 Amber Herold
  cp [python-site-package-path]/Leginon/config/default.cfg [python-site-package-path]/Leginon/config/leginon.cfg
98
</pre>
99
100 11 Amber Herold
* Add a directory for images 
101
<pre>
102 1 Amber Herold
  [Images]
103
  path: your_storage_disk_path/leginon
104 11 Amber Herold
</pre>
105
106
The rest of the configuration options are fine left as default assuming your leginon database is named "leginondb", and Leginon logs into the database as a user named "usr_object" with no password set.
107 1 Amber Herold
108
h3. Names used in the example installation
109
110 10 Amber Herold
From this point on, you will need to enter database user names for different configuration files and settings. These are NOT Leginon user names but what is required by MySQL database interaction. Consistent names are essential. In the example shown here, the leginon database is called "leginondb", the project database is called "projectdb". The MySQL user name are the same, "usr_object", and in this case without a password.
111 1 Amber Herold
112
h3. Configure sinedon.cfg:
113
114
*TODO: Consider moving this after we setup Mysql username.*
115
116
Sinedon is designed to be able to interact with multiple databases. It can be configured at global or user level.
117
118
    * An example configuration file is available at:
119
      /your_download_area/Leginon-1.6-ALL/sinedon/examples/sinedon.cfg
120
121
    * Configurations for all users should be placed at the following path:
122
      [python-site-package-path]/sinedon/sinedon.cfg
123
124
    * Modify host,db,user,passwd to what is used. Note that the user here is the MySQL user Leginon uses to communicate with the database for all Leginon users. For Leginon that uses Project database, set the following:
125 10 Amber Herold
<pre>
126 1 Amber Herold
      [global]
127
      host: your_database_host
128
      user: usr_object
129
      passwd:
130
131
      [projectdata]
132
      db: projectdb
133
134
      [leginondata]
135
      db: leginondb
136 10 Amber Herold
</pre>
137 1 Amber Herold
138
    * Add database configuration if you intend to use grid-inserting robot. The Robot2 module uses the database to communicate to the robot. Applications that carries the name "Robot" requires this to be set. In general, using the same database as the general leginon database is fine.
139 10 Amber Herold
<pre>
140 1 Amber Herold
      [robot2]
141
      db: leginondb
142 10 Amber Herold
</pre>
143 1 Amber Herold
144 10 Amber Herold
h3. Compile FindEM 
145 1 Amber Herold
146
* Goto appion/findem folder to make findem.exe
147
148
* Compile the libraries and binary
149
150
<pre>
151
$ make
152
</pre>
153
154
* Test findem.exe to see if it runs
155
156
<pre>
157
$ make test
158
</pre>
159
160
*WARNING*
161
Only if the first part fails, you must add the path to libg2c.so library file.
162
Otherwise skip to next section.
163
164
* locate libg2c.so library file
165
166
<pre>
167
$ ls /usr/lib/gcc/`uname -i`-redhat-linux/3.4.6/libg2c.so
168
</pre>
169
170
<pre>
171
$ locate libg2c.so
172
</pre>
173
174
* Edit Makefile with location of libg2c.so
175
176
<pre>
177
$ nano Makefile
178
</pre>
179
180
* Example: EXLIBS=-L/usr/lib/gcc/i386-redhat-linux/3.4.6/ -lg2c
181
* Re-compile
182
183 12 Amber Herold
h3. Compile Ace2 
184 1 Amber Herold
185
The 64 bit Ace2 binary is already available in the myami/bin directory. 
186
Test it by changing directories to myami/bin and type the following commands:
187
<pre>
188
$ ./ace2.exe -h
189
$ ./ace2correct.exe -h
190
</pre>
191
Notice the help display.
192
193
<pre>
194
If this does not work or you wish to compile it yourself follow the instructions here.
195
NOTE:
196
ace2 typically requires fftw 3.2 or greater. This is significantly faster than 3.1 (which is distributed with CentOS). 
197
There is a FFTW_WISDOM_ONLY flag in Image.m that can be commented in if you are using fftw 3.2 or greater.
198
*TODO: Can we have the make file detect which version is installed?*
199
200
* Goto myami/appion/ace2
201
* compile the libraries and binary
202
* test to see if program runs
203
204
$ make
205
$ ./ace2.exe -h
206
$ ./ace2correct.exe -h
207
$ mv -v ./ace2*.exe ../bin
208
</pre>
209
210 12 Amber Herold
h3. Compile Radermacher module 
211 1 Amber Herold
212
* Goto appion/radermacher
213
214
* compile the libraries and binary
215
216
<pre>
217
$ python ./setup.py build
218
</pre>
219
220
* install module globally
221
222
<pre>
223
$ sudo python ./setup.py install
224
</pre>
225
226
* test installed module
227
228
<pre>
229
$ python
230
</pre>
231
232
<pre>
233
>>> import radermacher
234
>>> <Ctrl-D>
235
</pre>
236
237 12 Amber Herold
h3. Test Appion 
238 1 Amber Herold
239 3 Amber Herold
If appion is installed locallaly in your home directory (you are the only user that can execute it), 
240
you will need to add myami and appion to the python path.
241
242 1 Amber Herold
* Go into the appion directory
243 2 Amber Herold
244
Open .bashrc in your home directory and edit it at the end of the file:
245 1 Amber Herold
Add the following lines:
246 2 Amber Herold
247
<pre>
248 6 Amber Herold
$ export PYTHONPATH="/your-complete-path-to-myami":"/your-complete-path-to-myami/appion":$PYTHONPATH
249 3 Amber Herold
$ export PATH="/your-complete-path-to-myami/appion/bin":$PATH
250 1 Amber Herold
</pre>
251
252
* Add appion to PYTHONPATH
253
254
<pre>
255 3 Amber Herold
$ export PYTHONPATH="/your-complete-path-to-myami/appion":$PYTHONPATH
256 1 Amber Herold
</pre>
257
258
*TODO: Consider moving appionlib so you only need to set one path.*
259
260 4 Amber Herold
To confirm the changes, open a new terminal and type:
261 5 Amber Herold
<pre>
262 4 Amber Herold
 $ export
263 1 Amber Herold
</pre>
264 6 Amber Herold
265
Look for the PATH and PYTHONPATH in the output. The paths that you entered should be there.
266 4 Amber Herold
267 1 Amber Herold
* Run the test script
268 3 Amber Herold
269
If you have installed appion for all users (the script does not exist yet) or it is local and you have added the paths above, you are ready to run the test.
270 1 Amber Herold
271
<pre>
272
$ ./check.sh
273
</pre>
274
275
*NOTE*
276
You can ignore EMAN, MATLAB, and UCSF Chimera errors at this point