Project

General

Profile

RCT » History » Version 4

Eric Hou, 06/25/2010 10:22 AM

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