How to Update from v15 (Linux) » History » Version 1
Amber Herold, 04/14/2010 03:45 PM
1 | 1 | Amber Herold | h1. How to Update from v15 (Linux) |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | The changes from v1.5 requires update of all in-house components of Leginon and dbemtools, |
||
7 | but not the database nor mrctools. instruments.cfg should be modified on each microscope host. |
||
8 | Don't forget that you need to also update the packages on the microscope-controlling computer |
||
9 | since the pyScope update need to be synchronized. |
||
10 | |||
11 | |||
12 | See <link linkend="InstT_install">Installation Troubleshooting</link> and "Leginon Bulletin Board":http://emg.nysbc.org/bb/viewforum.php?f=2 searching |
||
13 | for "install" if you run into problems. |
||
14 | |||
15 | |||
16 | |||
17 | h2. Packages required from NRAMM |
||
18 | |||
19 | |||
20 | |||
21 | Here are the packages you need to install with python installer |
||
22 | |||
23 | |||
24 | |||
25 | |_.SVN Package Name|_.Installed Python Package Name|_.Reason for update:| |
||
26 | |numextension|numextension|none| |
||
27 | |libcv|libCV|bug fixes| |
||
28 | |leginon|Leginon|new features| |
||
29 | |pyami|pyami|clean up| |
||
30 | |sinedon|sinedon|new stuff| |
||
31 | |pyScope|pyScope|new instrument configuration| |
||
32 | |ImageViewer|ImageViewer|updated and required for tomography| |
||
33 | |||
34 | |||
35 | |||
36 | |||
37 | |||
38 | |||
39 | |||
40 | h2. Download and install SVN client program: |
||
41 | |||
42 | |||
43 | |||
44 | By switching to svn package check out, you now need to install svn client. The rpm |
||
45 | package probably has the word "svn" or "subversion" in its name. |
||
46 | |||
47 | |||
48 | |||
49 | |||
50 | |||
51 | h2. Check out SVN Source Files from the depository |
||
52 | |||
53 | |||
54 | |||
55 | From a text |
||
56 | terminal:<pre>mkdir Leginon-1.6-ALL |
||
57 | cd Leginon-1.6-ALL |
||
58 | svn co http://emg.nysbc.org/svn/leginon/branches/1.6 Leginon |
||
59 | svn co http://emg.nysbc.org/svn/pyami/branches/leg1.6 pyami |
||
60 | svn co http://emg.nysbc.org/svn/pyScope/branches/leg1.6 pyScope |
||
61 | svn co http://emg.nysbc.org/svn/sinedon/branches/leg1.6 sinedon |
||
62 | svn co http://emg.nysbc.org/svn/numextension/branches/leg1.6 numextension |
||
63 | svn co http://emg.nysbc.org/svn/libcv/branches/leg1.6 libcv |
||
64 | svn co http://emg.nysbc.org/svn/ImageViewer/branches/leg1.6 ImageViewer</pre> |
||
65 | |||
66 | |||
67 | |||
68 | |||
69 | |||
70 | h2. Perform system check: |
||
71 | |||
72 | |||
73 | |||
74 | In addition to the downloads from our svn depository, there are several other |
||
75 | requirements that you will get either from your OS installation source, or from its |
||
76 | respective website. The system check in the Leginon package checks your system to see if you |
||
77 | already have these requirements |
||
78 | |||
79 | |||
80 | |||
81 | <pre>cd Leginon |
||
82 | python syscheck.py</pre> |
||
83 | |||
84 | |||
85 | |||
86 | You should have all the supporting packages installed for v1.5. If you see any lines |
||
87 | like "*** Failed...", then you have something missing. Otherwise, everything should result |
||
88 | in "OK". Note that numpy and scipy are now required by the new version even if you don't run |
||
89 | tomography. numarray is no longer used. |
||
90 | |||
91 | |||
92 | |||
93 | |||
94 | |||
95 | h2. Uninstall your existing packages: |
||
96 | |||
97 | |||
98 | |||
99 | At the beginning of the syscheck.py output, the location of the exisiting Leginon folder |
||
100 | is shown. Although new installation overwrite the old in most cases, problem has been |
||
101 | observed in the past. Therefore, it is best to remove the old files before new |
||
102 | installation. |
||
103 | |||
104 | |||
105 | For example, your Leginon folder is at /usr/lib/python/site-packages/Leginon |
||
106 | |||
107 | |||
108 | |||
109 | <pre>cd /usr/lib/python/site-packages |
||
110 | rm -r Leginon</pre> |
||
111 | |||
112 | |||
113 | |||
114 | Be aware that in some cases the installed package name is different (capitalized) from |
||
115 | your svn package name and that numextension amd libCV are not in its own subdirectory in the |
||
116 | python library but just the compiled .so files |
||
117 | |||
118 | |||
119 | |||
120 | |||
121 | |||
122 | h2. Install the packages you downloaded from NRAMM svn depository |
||
123 | |||
124 | |||
125 | |||
126 | |||
127 | |||
128 | * run syscheck.py again to make sure you have everything. |
||
129 | |||
130 | |||
131 | * Reinstall the package in each folder with commands such as |
||
132 | <pre>cd leginon |
||
133 | python setup.py install</pre> |
||
134 | |||
135 | |||
136 | |||
137 | |||
138 | |||
139 | |||
140 | |||
141 | |||
142 | |||
143 | h2. Modify sinedon.cfg if you use grid-inserting robot |
||
144 | |||
145 | |||
146 | |||
147 | * Find your sinedon.cfg. Depending on your previous setting, look in the |
||
148 | directories listed here in order: |
||
149 | *your home directory as described in syscheck.py |
||
150 | *The sinedon directory where it is called from. If unsure, start python command |
||
151 | line and type these to find |
||
152 | out:<pre>python> import sinedon |
||
153 | python> sinedon</pre> |
||
154 | |||
155 | * Add the following database configuration. The Robot2 module uses the database to |
||
156 | communicate to the robot. Applications that carries the name "Robot" requires this to be |
||
157 | set. In general, using the same database as the general leginon database is fine. |
||
158 | |||
159 | |||
160 | |||
161 | <pre>[robot2] |
||
162 | db: dbemdata</pre> |
||
163 | |||
164 | |||
165 | |||
166 | |||
167 | |||
168 | |||
169 | |||
170 | |||
171 | h2. Transfer Drift adjustment preference to use Transform Manager |
||
172 | |||
173 | |||
174 | |||
175 | * This procedure copies all most recent user settings to that required by the new |
||
176 | transform |
||
177 | manager.<pre>cd leginon |
||
178 | python update16.py</pre> |
||
179 | |||
180 | |||
181 | * Add database configuration if you intend to use grid-inserting robot. The Robot2 |
||
182 | module uses the database to communicate to the robot. Applications that carries the name |
||
183 | "Robot" requires this to be set. In general, using the same database as the general |
||
184 | leginon database is fine. |
||
185 | |||
186 | |||
187 | |||
188 | <pre>[robot2] |
||
189 | db: dbemdata |
||
190 | |||
191 | </pre> |
||
192 | |||
193 | |||
194 | |||
195 | |||
196 | |||
197 | |||
198 | |||
199 | |||
200 | h2. Install updated mrc module |
||
201 | |||
202 | |||
203 | |||
204 | php-mrc 1.5 uses fftw3. You may need to install that before installing the tool as a php |
||
205 | extension. |
||
206 | |||
207 | |||
208 | See <link linkend="install_mrc">php-mrc extenstion installation</link> section in |
||
209 | Complete Installation Chapter. |
||
210 | |||
211 | |||
212 | |||
213 | |||
214 | |||
215 | |||
216 | |||
217 | h2. Install updated dbemtools |
||
218 | |||
219 | |||
220 | |||
221 | See <link linkend="install_dbemtool">dbemtools installation</link> section in Complete |
||
222 | Installation Chapter. |
||
223 | |||
224 | |||
225 | |||
226 | |||
227 | |||
228 | |||
229 | |||
230 | h2. Reset installation status in projectdb |
||
231 | |||
232 | |||
233 | |||
234 | You can do this directly by mysql commands. |
||
235 | |||
236 | |||
237 | > mysql |
||
238 | projectdata<pre>> mysql projectdata -u usr_object |
||
239 | mysql> drop table install; |
||
240 | mysql> exit</pre> |
||
241 | |||
242 | |||
243 | Alternatively, you can use phpMyAdmin to achieve this by visiting the database, find the |
||
244 | table and click on drop. |
||
245 | |||
246 | |||
247 | |||
248 | |||
249 | |||
250 | h2. Install updated tools for project management |
||
251 | |||
252 | |||
253 | |||
254 | See <link linkend="install_projecttools">projecttools installation</link> section in |
||
255 | Complete Installation Chapter. |
||
256 | |||
257 | |||
258 | |||
259 | |||
260 | |||
261 | |||
262 | |||
263 | h2. Load default node settings for Leginon applications (optional) |
||
264 | |||
265 | |||
266 | |||
267 | Default settings are useful for new users of a new application. However, if you have |
||
268 | manually set these as administrator user in Leginon, loading these now will "overwrite" your |
||
269 | settings. |
||
270 | |||
271 | |||
272 | See <link linkend="admin_load_defaults">admintools default loading</link> section in |
||
273 | Complete Installation Chapter. |