InstallationUpdate problems » History » Version 6
Alex Kadokura, 05/07/2010 01:54 PM
1 | 1 | Amber Herold | h1. InstallationUpdate problems |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | 6 | Alex Kadokura | * [[InstallationUpdate problems#Failed pyScope numExtension Window installation through |
9 | python|Python installer fails on pyScope and numExtension for |
||
10 | Windows]] |
||
11 | 1 | Amber Herold | |
12 | 6 | Alex Kadokura | * [[InstallationUpdate problems#Incomplete Leginon update|Not all files are updated]] |
13 | 1 | Amber Herold | |
14 | |||
15 | 6 | Alex Kadokura | * [[InstallationUpdate problems#Incomplete Leginon update|New Group/User added does not show up in the selection |
16 | list in Web Leginon Administration Tool]] |
||
17 | 1 | Amber Herold | |
18 | 6 | Alex Kadokura | * [[InstallationUpdate problems#Installation without a class of nodes|I can't install SciPy/NumPy on SUSE]] |
19 | 1 | Amber Herold | |
20 | 6 | Alex Kadokura | * [[InstallationUpdate problems#SciPy Installation failed in SuSE|Something is not showing in Web viewer or the |
21 | administration tool components]] |
||
22 | 1 | Amber Herold | |
23 | 6 | Alex Kadokura | * [[InstallationUpdate problems#Display errors on webviewer and web administration tools|Stage does not move after a pyScope update on the |
24 | computer controlling the microscope]] |
||
25 | 1 | Amber Herold | |
26 | |||
27 | |||
28 | |||
29 | |||
30 | h2. Failed pyScope numExtension Window installation through |
||
31 | python |
||
32 | |||
33 | |||
34 | |||
35 | |||
36 | |||
37 | <title>Why:</title> |
||
38 | * Specially compiled pyScope and numExtension are needed to comunicate with Gatan |
||
39 | CCD camera. Currently we only have them compiled for python2.5 |
||
40 | |||
41 | |||
42 | Solution: Download and use python2.5 and use the window-installer in win-install |
||
43 | folder (start by double-clicking them) not "python setup.py install". |
||
44 | |||
45 | |||
46 | |||
47 | |||
48 | |||
49 | |||
50 | |||
51 | |||
52 | |||
53 | h2. Incomplete Leginon update |
||
54 | |||
55 | |||
56 | |||
57 | This normally happens to files that you have modified in the previous version. |
||
58 | |||
59 | |||
60 | |||
61 | |||
62 | <title>Why:</title> |
||
63 | * unknown |
||
64 | |||
65 | |||
66 | Solution: Remove the old installation first. |
||
67 | |||
68 | |||
69 | |||
70 | |||
71 | * Find the location of your Leginon installation. Once you have tried,even |
||
72 | unsuccessfully, to install Leginon. You can use the following command to find |
||
73 | the directory: |
||
74 | |||
75 | |||
76 | |||
77 | <pre>Linux> cd |
||
78 | Linux> start-leginon.py -v</pre> |
||
79 | <pre>Window> Go to \All Programs\Leginon\Leginon Folder from your Start Menu</pre> |
||
80 | |||
81 | |||
82 | |||
83 | * Go to the directory above it. This is normally the site-package directory |
||
84 | under your python installation |
||
85 | |||
86 | |||
87 | |||
88 | <pre>Linux> rm -r Leginon |
||
89 | Window> drag the Leginon folder to Recycle Bin</pre> |
||
90 | |||
91 | |||
92 | |||
93 | * Redo Leginon installation. |
||
94 | |||
95 | |||
96 | |||
97 | |||
98 | |||
99 | |||
100 | |||
101 | |||
102 | |||
103 | |||
104 | |||
105 | |||
106 | |||
107 | h2. Installation without a class of nodes |
||
108 | |||
109 | |||
110 | If you encounter a problem with node classes that you don't actually use, you may avoid |
||
111 | loading the codes with the following modification: |
||
112 | |||
113 | |||
114 | |||
115 | |||
116 | * Fnd the location of your Leginon installation |
||
117 | |||
118 | |||
119 | |||
120 | <pre>Linux> cd |
||
121 | Linux> start-leginon.py -v</pre> |
||
122 | |||
123 | |||
124 | |||
125 | * go to the subdirectory of noderegistry |
||
126 | |||
127 | |||
128 | |||
129 | <pre>Linux/home> cd leginon_directory/noderegistry</pre> |
||
130 | |||
131 | |||
132 | |||
133 | * edit the file "default.ncr" to coment out the registry of the class of nodes that |
||
134 | you do not need (Tomography node class in this example): |
||
135 | |||
136 | |||
137 | |||
138 | <pre>#[Tomography] |
||
139 | #module: tomography |
||
140 | #type: Pipeline |
||
141 | #package: tomography</pre> |
||
142 | |||
143 | |||
144 | |||
145 | |||
146 | |||
147 | |||
148 | |||
149 | |||
150 | |||
151 | |||
152 | h2. SciPy Installation failed in SuSE |
||
153 | |||
154 | |||
155 | |||
156 | SciPy may not build properly on some versions of SuSE due to an incompatible LAPACK |
||
157 | package that comes with SuSE. You can get scipy as well as a compatible LAPACK etc. from |
||
158 | http://repos.opensuse.org/science (need to specify your SuSE version and machine etc. |
||
159 | |||
160 | |||
161 | |||
162 | |||
163 | |||
164 | h2. Display errors on webviewer and web |
||
165 | administration tools |
||
166 | |||
167 | |||
168 | |||
169 | To display error and report them to get help for the php, including mysql-php and mrc |
||
170 | extension, do the following: |
||
171 | |||
172 | |||
173 | * Find your php.ini the following parameters and change them accordingly: |
||
174 | |||
175 | |||
176 | |||
177 | <pre>display_errors = On |
||
178 | error_reporting = E_ALL & ~E_NOTICE</pre> |
||
179 | |||
180 | |||
181 | |||
182 | * Restart your apache server |
||
183 | |||
184 | |||
185 | |||
186 | <pre>> /etc/init.d/apache2 restart</pre> |
||
187 | |||
188 | |||
189 | |||
190 | * From your webbrowser, refresh the problematic page. If you don't know what to do |
||
191 | 2 | Amber Herold | with it, report it when you ask for help. |
192 | |||
193 | ______ |
||
194 | 3 | Amber Herold | |
195 | 2 | Amber Herold | |
196 | 5 | Amber Herold | [[Getting Help|< Getting Help]] | [[Administration Tool problems|Administration Tool problems >]] |
197 | |||
198 | |||
199 | 1 | Amber Herold | ______ |