RCT » History » Revision 4
Revision 3 (Amber Herold, 04/27/2010 02:52 PM) → Revision 4/10 (Eric Hou, 06/25/2010 10:22 AM)
h1. RCT 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. <highlights> Required bindings to Presets Manager <simplelist type="vert"> <member> RCTNode - (ChangePresetEvent) -> PresetsManagerNode PresetsManagerNode</member> <member> PresetManagerNode - (PresetChangedEvent) -> RCTNode RCTNode</member> </simplelist> </highlights> <highlights> Required bindings to a Target Finder <simplelist type="vert"> <member> TargetFinderNode - (ImageTargetListPublishEvent) -> RCTNode RCTNode</member> <member> RCTNode - (TargetListDoneEvent) -> TargetFinderNode TargetFinderNode</member> </simplelist> </highlights> <highlights> Required Bindings with Navigator to allow (iterative) target move correction. <simplelist type="vert"> <member> RCTNode - (MoveToTargetEvent) -> NavigatorNodeAlias NavigatorNodeAlias</member> </simplelist> </highlights> <highlights> Required Bindings for waiting for drift to stop after tilting <simplelist type="vert"> <member> RCTrNode - (DriftMonitorRequestEvent) -> DriftManagerNode DriftManagerNode</member> <member> DriftManagerNode - (DriftMonitorResultEvent) -> RCTNode RCTNode</member> </simplelist> Required Binding to correct drift from tilting as well as thermal expansion <simplelist type="vert"> <member> RCTNode - (NeedTargetShiftEvent) -> DriftManagerNode DriftManagerNode</member> <member> DriftManagerNode-(AcquisitionImageDriftPublishEvent) -> RCTNode RCTNode</member> </simplelist> </highlights> <highlights> Required Bindings to use drift check image in the node (???). <simplelist type="vert"> <member> DriftManagerNode - (AcquisitionImagePublishEvent) -> RCTNode RCTNode</member> </simplelist> </highlights> h2. Robot Robot node sits between robot controlling program and other Leginon acquisition sequence. Leginon Robot node communicates with the grid-loading robot controlling program to <highlights> <simplelist type="vert"> <member> check that the robot exists and is activated</member> <member> tell the robot to load/unload a specific grid</member> <member> hear from the robot when the grid loading/unloading is successful/failed</member> </simplelist> </highlights> Note: This node works only with NRAMM grid loading robot. You should modify it to suit your robot for the above functions. As long as it has the same event binding to perform the following functions, your custom node can be used with any Leginon acquisition sequence. For normal MSI application, the user select grids from exisiting grid tray in the Robot node first, then the node interacts with an acquisition sequence in Leginon application to <highlights> <simplelist type="vert"> <member> start the image acquisition sequence</member> <member> recieve a notice that the acquisition sequence is completed</member> </simplelist> </highlights> In the case of 2nd acquisition sequence of grids with targets selected on the old grid atlas, the robot need to also <highlights> <simplelist type="vert"> <member> recieve information on which grid to be loaded</member> </simplelist> </highlights> Normal MSI application Required bindings: <highlights> <simplelist type="vert"> <member> Robot - (MakeTargetListEvent) -> MosaicTargetMaker</member> <member> target handler such as Acquisition or TargetFilter - (TargetListDone) -> Robot</member> </simplelist> </highlights> Required bindings for 2nd Pass application that re-registrate targets on the specific grid: <highlights> <simplelist type="vert"> <member> Robot - (GridLoadedEvent) -> RobotAtlasTargetFinder</member> <member> RobotAtlasTargetFinder - (UnloadGridEvent) -> Robot</member> <member> RobotAtlasTargetFinder - (QueueGridEvent) -> Robot</member> </simplelist> </highlights> Additional Requirement: project database with robot grid and tray information. ______ [[Raster Filter|< Raster Filter]] | [[Robot|Robot >]] ______