How to Update from v34 (Instrument Windows Computer) » History » Version 4
Anchi Cheng, 11/16/2020 03:18 PM
1 | 1 | Anchi Cheng | h1. How to Update from v34 (Instrument Windows Computer) |
---|---|---|---|
2 | |||
3 | h2. Preparation |
||
4 | |||
5 | You will need these myami subpackages updated. |
||
6 | |||
7 | |_.Name:|_.Purpose:| |
||
8 | | leginon|modular TEM image acquisition| |
||
9 | | pyami|general functions| |
||
10 | | myami_test|test suite that is called before starting leginon| |
||
11 | | sinedon|database interaction| |
||
12 | | pyscope|microscope control and monitoring| |
||
13 | |||
14 | h2. No internet access - copy from linux Leginon workstation the python files. |
||
15 | |||
16 | If your Windows computer has no access to internet, copy from your linux processing server the git clone of myami super package of the right branch for the installation which you used to upgrade there. |
||
17 | |||
18 | See [[Download_Appion_Files|Acquiring NRAMM GIT Repository files]] for different examples and match the repository with what you do on the Linux side. |
||
19 | |||
20 | *OR* |
||
21 | |||
22 | h2. With internet access |
||
23 | |||
24 | h3. Clone the proper branch from git repository. You will want myami-3.5 |
||
25 | |||
26 | {{include(git_for_windows_cloning)}} |
||
27 | |||
28 | h2. Install |
||
29 | |||
30 | h3. Move the cloned folder according to your environment variable PYTHONPATH if you use that during the original installation. |
||
31 | |||
32 | *OR* |
||
33 | |||
34 | h3. Install to default python site-packages |
||
35 | |||
36 | * Start a command line Window from Start Menu |
||
37 | |||
38 | * Install the package in each folder (must starts with pyami) |
||
39 | <pre>cd path_to\myami-VERSION\myami\pyami |
||
40 | c:\\python27\python.exe setup.py install</pre> |
||
41 | Then continue with the other packages, replacing pyami with the package name. See the packages listed above for the complete list. |
||
42 | |||
43 | h2. Configure |
||
44 | |||
45 | [[locate global config directory on Windows]] |
||
46 | |||
47 | |||
48 | h1. FEI scopes |
||
49 | |||
50 | h2. fei.cfg |
||
51 | |||
52 | |||
53 | Compare yours_git_clone\pyscope\fei.cfg.template with your active fei.cfg. Especially if you plan to use new featured instruments or have had a TEMServer upgrade to recent versions. |
||
54 | |||
55 | h3. If you set for your Talos column |
||
56 | |||
57 | <pre> |
||
58 | FORCE_NORMALIZE_ALL_LENS_AFTER_MAG_SETTING = True |
||
59 | </pre> |
||
60 | |||
61 | please change it to use |
||
62 | |||
63 | <pre> |
||
64 | FORCE_NORMALIZE_ALL_AFTER_SETTING = True |
||
65 | </pre> |
||
66 | |||
67 | This is more generalized and produces better results. See Issue #7076 for more details. |
||
68 | |||
69 | h1. GatanK2Summit or K3 |
||
70 | |||
71 | Compare pyscope/dmsem.cfg.template with your active dmsem.cfg There are additional configuration that you may want to add. |
||
72 | |||
73 | 3 | Anchi Cheng | * Check if you need to specify ACQUISITION_SHUTTER_NUMBER differently (See Issue #7834) |
74 | 4 | Anchi Cheng | |
75 | h1. New Features |
||
76 | |||
77 | Follow [[PyScope_Changes_35]] on the installation and setup of the specific feature you want to activate. |