RCT » History » Version 2
Amber Herold, 04/23/2010 10:10 AM
1 | 1 | Amber Herold | h1. RCT |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | 2 | Amber Herold | RCT stands for Random Conical Tilt. It can also used for Orthogonal Tilt image |
8 | acquisition. This should be used with Navigator multiple move for best results. |
||
9 | |||
10 | 1 | Amber Herold | <highlights> |
11 | 2 | Amber Herold | |
12 | Required bindings to Presets Manager |
||
13 | |||
14 | 1 | Amber Herold | <simplelist type="vert"> |
15 | 2 | Amber Herold | <member> RCTNode - (ChangePresetEvent) -> PresetsManagerNode</member> |
16 | <member> PresetManagerNode - (PresetChangedEvent) -> RCTNode</member> |
||
17 | 1 | Amber Herold | </simplelist> |
18 | </highlights> |
||
19 | 2 | Amber Herold | <highlights> |
20 | 1 | Amber Herold | |
21 | 2 | Amber Herold | Required bindings to a Target Finder |
22 | |||
23 | <simplelist type="vert"> |
||
24 | <member> TargetFinderNode - (ImageTargetListPublishEvent) -> RCTNode</member> |
||
25 | <member> RCTNode - (TargetListDoneEvent) -> TargetFinderNode</member> |
||
26 | </simplelist> |
||
27 | </highlights> |
||
28 | 1 | Amber Herold | <highlights> |
29 | 2 | Amber Herold | |
30 | Required Bindings with Navigator to allow (iterative) target move correction. |
||
31 | |||
32 | 1 | Amber Herold | <simplelist type="vert"> |
33 | 2 | Amber Herold | <member> RCTNode - (MoveToTargetEvent) -> NavigatorNodeAlias</member> |
34 | 1 | Amber Herold | </simplelist> |
35 | </highlights> |
||
36 | 2 | Amber Herold | <highlights> |
37 | |||
38 | Required Bindings for waiting for drift to stop after tilting |
||
39 | |||
40 | <simplelist type="vert"> |
||
41 | <member> RCTrNode - (DriftMonitorRequestEvent) -> DriftManagerNode</member> |
||
42 | <member> DriftManagerNode - (DriftMonitorResultEvent) -> RCTNode</member> |
||
43 | </simplelist> |
||
44 | |||
45 | Required Binding to correct drift from tilting as well as thermal expansion |
||
46 | |||
47 | <simplelist type="vert"> |
||
48 | <member> RCTNode - (NeedTargetShiftEvent) -> DriftManagerNode</member> |
||
49 | <member> DriftManagerNode-(AcquisitionImageDriftPublishEvent) -> RCTNode</member> |
||
50 | </simplelist> |
||
51 | </highlights> |
||
52 | <highlights> |
||
53 | |||
54 | Required Bindings to use drift check image in the node (???). |
||
55 | |||
56 | <simplelist type="vert"> |
||
57 | <member> DriftManagerNode - (AcquisitionImagePublishEvent) -> RCTNode</member> |
||
58 | </simplelist> |
||
59 | </highlights> |
||
60 | |||
61 | |||
62 | |||
63 | |||
64 | |||
65 | |||
66 | h2. Robot |
||
67 | |||
68 | |||
69 | |||
70 | Robot node sits between robot controlling program and other Leginon acquisition |
||
71 | sequence. |
||
72 | |||
73 | |||
74 | Leginon Robot node communicates with the grid-loading robot controlling program to |
||
75 | |||
76 | <highlights> |
||
77 | <simplelist type="vert"> |
||
78 | <member> check that the robot exists and is activated</member> |
||
79 | <member> tell the robot to load/unload a specific grid</member> |
||
80 | <member> hear from the robot when the grid loading/unloading is successful/failed</member> |
||
81 | </simplelist> |
||
82 | </highlights> |
||
83 | |||
84 | Note: This node works only with NRAMM grid loading robot. You should modify it to suit |
||
85 | your robot for the above functions. As long as it has the same event binding to perform the |
||
86 | following functions, your custom node can be used with any Leginon acquisition |
||
87 | sequence. |
||
88 | |||
89 | |||
90 | For normal MSI application, the user select grids from exisiting grid tray in the Robot |
||
91 | node first, then the node interacts with an acquisition sequence in Leginon application |
||
92 | to |
||
93 | |||
94 | <highlights> |
||
95 | <simplelist type="vert"> |
||
96 | <member> start the image acquisition sequence</member> |
||
97 | <member> recieve a notice that the acquisition sequence is completed</member> |
||
98 | </simplelist> |
||
99 | </highlights> |
||
100 | |||
101 | In the case of 2nd acquisition sequence of grids with targets selected on the old grid |
||
102 | atlas, the robot need to also |
||
103 | |||
104 | <highlights> |
||
105 | <simplelist type="vert"> |
||
106 | <member> recieve information on which grid to be loaded</member> |
||
107 | </simplelist> |
||
108 | </highlights> |
||
109 | Normal MSI application Required bindings: |
||
110 | |||
111 | <highlights> |
||
112 | <simplelist type="vert"> |
||
113 | <member> Robot - (MakeTargetListEvent) -> MosaicTargetMaker</member> |
||
114 | <member> target handler such as Acquisition or TargetFilter - (TargetListDone) -> |
||
115 | Robot</member> |
||
116 | </simplelist> |
||
117 | </highlights> |
||
118 | Required bindings for 2nd Pass application that re-registrate targets on the specific |
||
119 | grid: |
||
120 | |||
121 | <highlights> |
||
122 | <simplelist type="vert"> |
||
123 | <member> Robot - (GridLoadedEvent) -> RobotAtlasTargetFinder</member> |
||
124 | <member> RobotAtlasTargetFinder - (UnloadGridEvent) -> Robot</member> |
||
125 | <member> RobotAtlasTargetFinder - (QueueGridEvent) -> Robot</member> |
||
126 | </simplelist> |
||
127 | </highlights> |
||
128 | |||
129 | Additional Requirement: project database with robot grid and tray information. |