Project

General

Profile

RCT » History » Revision 2

Revision 1 (Amber Herold, 04/23/2010 10:08 AM) → Revision 2/10 (Amber Herold, 04/23/2010 10:10 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</member> 
 <member> PresetManagerNode - (PresetChangedEvent) -> RCTNode</member> 
 </simplelist> 
 </highlights> 
 <highlights> 

 Required bindings to is really a Target Finder 

 <simplelist type="vert"> 
 <member> TargetFinderNode - (ImageTargetListPublishEvent) -> RCTNode</member> 
 <member> RCTNode - (TargetListDoneEvent) -> TargetFinderNode</member> 
 </simplelist> 
 </highlights> 
 <highlights> 

 Required Bindings with Navigator to allow (iterative) target move correction. 

 <simplelist type="vert"> 
 <member> RCTNode - (MoveToTargetEvent) -> NavigatorNodeAlias</member> 
 </simplelist> 
 </highlights> 
 <highlights> 

 Required Bindings for waiting for drift to stop after tilting 

 <simplelist type="vert"> 
 <member> RCTrNode - (DriftMonitorRequestEvent) -> DriftManagerNode</member> 
 <member> DriftManagerNode - (DriftMonitorResultEvent) -> RCTNode</member> 
 </simplelist> 

 Required Binding to correct drift from tilting as well as thermal expansion 

 <simplelist type="vert"> 
 <member> RCTNode - (NeedTargetShiftEvent) -> DriftManagerNode</member> 
 <member> DriftManagerNode-(AcquisitionImageDriftPublishEvent) -> RCTNode</member> 
 </simplelist> 
 </highlights> 
 <highlights> 

 Required Bindings to use drift check image in raster generator. It adopted the node (???). 

 <simplelist type="vert"> name because it is a subclass of 
 <member> DriftManagerNode - (AcquisitionImagePublishEvent) -> 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 TargetFilter that the robot exists takes in targets 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> output targets. 

 Note: This node works only with NRAMM grid loading robot. You should modify it to suit 
 your robot Required bindings 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 recieving targets selected on the old grid 
 atlas, the robot need to also and publishing targets: 

 <highlights> 
 <simplelist type="vert"> 
 <member> recieve information on which grid to be loaded</member> previous Target Finder - (TargetListPublishEvent) -> Raster Filter</member> 
 </simplelist> 
 </highlights> 
 Normal MSI application Required bindings: 

 <highlights> 
 <simplelist type="vert"> 
 <member> Robot Target Filter - (MakeTargetListEvent) (ImageTargetListPublishEvent) -> MosaicTargetMaker</member> next Acquisition</member> 
 <member> target handler such as Acquisition or TargetFilter Target Filter - (TargetListDone) (QueuePublishEvent) -> next Acquisition</member> 
 Robot</member> 
 </simplelist> 
 </highlights> 
 Required bindings for 2nd Pass application that re-registrate targets on the specific 
 grid: proper waiting among nodes: 

 <highlights> 
 <simplelist type="vert"> 
 <member> Robot - (GridLoadedEvent) Raster Filter- (TargetListDoneEvent) -> RobotAtlasTargetFinder</member> previous Target Finder</member> 
 <member> RobotAtlasTargetFinder next Acquisition - (UnloadGridEvent) (TargetListDoneEvent) -> Robot</member> Raster Filter</member> 
 <member> RobotAtlasTargetFinder - (QueueGridEvent) -> Robot</member> 
 </simplelist> 
 </highlights> 

 Additional Requirement: project database with robot grid and tray information.