Test run operation problems » History » Version 27
Alex Kadokura, 05/12/2010 11:49 AM
1 | 1 | Amber Herold | h1. Test run operation problems |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | 21 | Alex Kadokura | * [[Test_run_operation_problems#Python-and-Leginon-windows-do-not-stay-opened-on-Windows-PC|When Leginon or Leginon Client is launched,Python window opens and closes instantaneously on Windows]] |
8 | 1 | Amber Herold | |
9 | 18 | Alex Kadokura | * [[Test_run_operation_problems#Missing-modules|ImportError "No module named xxxx"]] |
10 | 1 | Amber Herold | |
11 | |||
12 | 25 | Alex Kadokura | * [[Test_run_operation_problems#Tecnai-does-not-show-up-in-instrument-list|Microscope or CCDCamera name does not show up in the |
13 | 22 | Alex Kadokura | Leginon instrument list in Instrument Node]] |
14 | 1 | Amber Herold | |
15 | 26 | Alex Kadokura | * [[Test_run_operation_problems#Tecnai-does-not-show-up-in-instrument-list|The Microscope computer where Leginon Client runs does |
16 | not show up in the Launcher list of Leginon when opening an application]] |
||
17 | 1 | Amber Herold | |
18 | 27 | Alex Kadokura | * [[Test_run_operation_problems#Magnification-list-not-in-the-database|No Magnification saved for xxx(your |
19 | scope)]] |
||
20 | 1 | Amber Herold | |
21 | |||
22 | * <link linkend="instlT_4kfrz">Leginon fails to collect 4kx4k images</link> |
||
23 | |||
24 | |||
25 | |||
26 | |||
27 | |||
28 | |||
29 | |||
30 | h2. Python and Leginon windows do not stay opened on |
||
31 | Windows PC |
||
32 | |||
33 | |||
34 | |||
35 | <title>Why:</title> |
||
36 | * Windows closes the python process window because an error is detected. |
||
37 | |||
38 | |||
39 | |||
40 | |||
41 | <title>Testing: Start Leginon from a python command window so that the error message can be |
||
42 | read</title> |
||
43 | * Follow the following menu to open a python command window: |
||
44 | |||
45 | |||
46 | Windows/Start Menu/All Programs/Python2.5/Python (command line) |
||
47 | |||
48 | |||
49 | * Python> import start |
||
50 | |||
51 | |||
52 | * Read the error message. Copy it to your bug report when asking NRAMM for |
||
53 | help. |
||
54 | |||
55 | |||
56 | |||
57 | |||
58 | |||
59 | |||
60 | |||
61 | h2. Missing modules |
||
62 | |||
63 | |||
64 | |||
65 | <title>Why:</title> |
||
66 | * Either the python path is not set up correctly or the module was not installed |
||
67 | properly. |
||
68 | |||
69 | |||
70 | |||
71 | |||
72 | <title>Testing:</title> |
||
73 | * script: <link linkend="inst_syscheck">syscheck.py</link> |
||
74 | |||
75 | |||
76 | If the missing module is not installed under one of the Python module search path |
||
77 | found in the syscheck output, it need to be moved. |
||
78 | |||
79 | |||
80 | |||
81 | |||
82 | |||
83 | |||
84 | |||
85 | h2. "Tecnai" does not show up in instrument list |
||
86 | |||
87 | |||
88 | |||
89 | <title>Why:</title> |
||
90 | * An error is detected when the instrument is loaded. |
||
91 | |||
92 | |||
93 | |||
94 | |||
95 | <title>Testing: Import the module in pyScope package through a python command window so that |
||
96 | the error message can be read</title> |
||
97 | * Follow the following menu to open a python command window: |
||
98 | |||
99 | |||
100 | Windows/Start Menu/All Programs/Python2.5/Python (command line) |
||
101 | |||
102 | |||
103 | * * |
||
104 | Follow instruction in pyScope Bulletin Board Thread ""Testing if pyScope is working |
||
105 | with your TEM or CCD"":http://emg.nysbc.org/bb/viewtopic.php?t=246 . |
||
106 | |||
107 | |||
108 | For example, if "Tecnai" is missing from the instrument list, try |
||
109 | this:<pre>Python>from pyScope import tecnai |
||
110 | Python>myscope = tecnai.Tecnai() |
||
111 | Python>myscope.getMagnification()</pre> |
||
112 | |||
113 | |||
114 | |||
115 | |||
116 | * Read the error message. Copy it to your bug report when asking for help. |
||
117 | |||
118 | |||
119 | |||
120 | |||
121 | |||
122 | |||
123 | |||
124 | h2. Magnification list not in the database |
||
125 | |||
126 | |||
127 | |||
128 | <title>Why:</title> |
||
129 | * The first time the TEM is used by leginon and the database, the valid magnification |
||
130 | for the instrument needs to be saved in the database. |
||
131 | |||
132 | |||
133 | Solution: On the scope: Leginon/Instrument> select the microscope to display |
||
134 | parameters and click "Get Magnification" button (The icon is of a calculator) on the |
||
135 | tool bar. |
||
136 | |||
137 | |||
138 | |||
139 | |||
140 | |||
141 | |||
142 | |||
143 | h2. Leginon fails to aquire and save larger images |
||
144 | |||
145 | |||
146 | |||
147 | <title>Why:</title> |
||
148 | * Your computer does not have sufficient memory to acquire and correct the large 4kx4k |
||
149 | images. |
||
150 | |||
151 | |||
152 | Solution: |
||
153 | |||
154 | |||
155 | Put on your computer more memory and more memory swap space. |
||
156 | |||
157 | |||
158 | * If you file storage system is not on the same computer, there may be problem |
||
159 | transfering large data file. This is known to happen from a Windows machine to disk |
||
160 | storage operated under Linux through Samba. |
||
161 | |||
162 | |||
163 | Solution: |
||
164 | |||
165 | |||
166 | Let us know if you have one. |
||
167 | |||
168 | |||
169 | |||
170 | |||
171 | |||
172 | |||
173 | |||
174 | h2. Leginon fails to move the goniometer after a new |
||
175 | installation or update of pyScope |
||
176 | |||
177 | |||
178 | |||
179 | <title>Why:</title> |
||
180 | * tecnaicom.py, the python wrapper of Tecnai Scripting library, has not been created |
||
181 | in the running pyScope folder on the microscope controlling computer. |
||
182 | |||
183 | |||
184 | Solution: |
||
185 | |||
186 | |||
187 | Double click updatecom.py to run it in the (installed) pyScope folder. |
||
188 | 2 | Amber Herold | |
189 | ______ |
||
190 | |||
191 | [[Administration Tool problems|< Administration Tool problems]] | [[Network problems|Network problems >]] |
||
192 | 3 | Amber Herold | |
193 | |||
194 | ______ |