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