Queuing option » History » Version 1
Amber Herold, 04/22/2010 05:05 PM
1 | 1 | Amber Herold | h1. Queuing option |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | h2. Introduction |
||
7 | |||
8 | |||
9 | |||
10 | Queuing option puts in a queue the selected targets on multiple images from the same |
||
11 | acquisition node. The queue can then processed as a batch. Therefore, targets from multiple |
||
12 | squares can be selected before any hole image image is acquired in any grid square. |
||
13 | Alternatively, targets from multiple holes of the same square can be selected before any |
||
14 | exposure is taken. Because the event bindings are identical in MSI application. Target |
||
15 | processing scheme can be switched between the queuing (breadth-first) mode and the |
||
16 | depth-first mode at appropriate point. |
||
17 | |||
18 | |||
19 | |||
20 | !http://emg.nysbc.org/software/leginon/images/images/MSIQtree.png! |
||
21 | |||
22 | |||
23 | |||
24 | In queuing mode, the movement of the stage is more complicated as targets in the same |
||
25 | suptree are not acquired in close time frame and often need readjustment of targets when it |
||
26 | is finally the time to acquire the child image. This is all taken care of by the drift |
||
27 | manager by revesing the stage position (including stage z) of the parent image when the |
||
28 | first child image is to be acquired after the drift declared event. Users of the queuing |
||
29 | mode should know that this frequent interaction with the drift manager makes the time for |
||
30 | completing the target list longer but is necessary when targeting accuracy is |
||
31 | importent. |
||
32 | |||
33 | |||
34 | The other consideration is that if queuing is activated at Hole Targeting node so that a |
||
35 | large number of images are acquired in "sq" preset at LM mode in a batch without ever |
||
36 | cycling to HM presets, the objective lens may cool down sufficianly that the image alignment |
||
37 | is different from during normal acquisition cycle. We recommand that either setting the |
||
38 | scope to one of the HM mode, wait for 30 or more minute and recheck the image alignment or |
||
39 | processing a smaller batch of "sq" preset each time so that the scope does not operate in LM |
||
40 | for extended amount of time. Our experience is that it is better not to activate queuing at |
||
41 | Hole Targeting but queue up only at exposure targeting so that the above problem is less |
||
42 | likely to occur. |
||
43 | |||
44 | |||
45 | <link linkend="MSI_troubleshooting">Trouble shooting</link> |
||
46 | |||
47 | |||
48 | |||
49 | |||
50 | |||
51 | h2. Initial Queuing set-up |
||
52 | |||
53 | |||
54 | |||
55 | The user should start with <link linkend="MSI_pref">the preference and |
||
56 | configuration</link> of the nodes in MSI application in the depth-first mode and follow |
||
57 | the <link linkend="MISQuickStart">quick start procedure</link>. Once the function of all |
||
58 | nodes are confirmed to be normal, then switch to queuing. There are two possible points for |
||
59 | queuing, at Hole Targeting or at Exposure Targeting. The two can be used in any combination |
||
60 | with the depth-first mode. |
||
61 | |||
62 | |||
63 | |||
64 | |||
65 | |||
66 | h2. Configuration and operation rules for a chosen queuing point |
||
67 | |||
68 | |||
69 | |||
70 | Configuration of two nodes are affected by each queuing and they should be set in the |
||
71 | following order if the two are currently processing data: |
||
72 | |||
73 | |||
74 | * The option for "Queue up targets" should be selected in the HoleFinder. "Declare |
||
75 | drift when queue is submitted" is optional. Use it if accurate targeting is required. |
||
76 | The time required to finish target will be longer. |
||
77 | |||
78 | |||
79 | * The acquisition node that acquires the image on which targets will be selected do |
||
80 | not need to wait for HoleFinder node to process the image before next acquisition. This |
||
81 | option is deselected in /Tool/Setup/. Leave it on if you are willing to wait for |
||
82 | HoleFinder before next image acquisition. |
||
83 | |||
84 | |||
85 | |||
86 | |||
87 | In operation, the behavior of the above two nodes plus the acquisition node after the |
||
88 | queuing holefinder are affected |
||
89 | |||
90 | |||
91 | * All targets submited to the above-mentioned acquisition node will be acquired |
||
92 | first(Waiting off) rather than one after each target submission (Waiting on). These |
||
93 | targets would be considered "done" by Leginon at restart or target refresh. |
||
94 | |||
95 | |||
96 | * The normal "submit"<inlinegraphic |
||
97 | fileref="http://emg.nysbc.org/software/leginon/images/icons/play.png" format="PNG"/> |
||
98 | in the targetfinder only stores the selected targets in the queue rather than proceeding |
||
99 | to target processing. |
||
100 | |||
101 | |||
102 | * Upon "Submit Queue"<inlinegraphic |
||
103 | fileref="http://emg.nysbc.org/software/leginon/images/icons/send_queue_out.png" |
||
104 | format="PNG"/> the queued target list is processed by the next acquisition node in |
||
105 | which individual targets can be aborted by the abort button <inlinegraphic |
||
106 | fileref="http://emg.nysbc.org/software/leginon/images/icons/stop.png" format="PNG" |
||
107 | />, paused as in MSI, and the whole queue list can be aborted using the abort queue |
||
108 | button <inlinegraphic |
||
109 | fileref="http://emg.nysbc.org/software/leginon/images/icons/stop_queue.png" |
||
110 | format="PNG"/>. |
||
111 | |||
112 | |||
113 | * The queued target list is in fact a list of lists where targets are grouped by |
||
114 | their parent images. At the start of target processing of any unfinished sub-list by an |
||
115 | acquisition node, leginon reverts the z stage position to that of the parent and |
||
116 | processes rejected targets (i.e., the focus targets) first if the option is on as it is |
||
117 | for "Hole" and "Exposure" nodes whether they have been processed previously. The rest of |
||
118 | the unfinished acquisition targets are then processed. |
||
119 | |||
120 | |||
121 | * The targets that generate images in the non-waiting acquisition node is considered |
||
122 | done once acquired. Therefore, if Leginon is interrupted and restarted, you can not |
||
123 | continue the acquisition and process the queued targets by submiting refreshed targets |
||
124 | in "Square Targeting" node as in MSI. Instead, you shoulde resubmit the queue in the |
||
125 | corresponding holefinder node. Leginon will find out which targets have not been |
||
126 | completed and continue the acquisition. |