You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The process of acquiring images ranges from snapping a single image to
4
-
recording overnight (or longer) time lapses of samples from N different
5
-
angles. See [Acquisition Controls](#Acquisition_Controls"wikilink") for
6
-
detailed descriptions of the controls.
3
+
The process of acquiring images ranges from snapping a single image to recording overnight (or longer) time lapses of samples from N different angles. See [Acquisition Controls](##acquisition_controls) for detailed descriptions of the controls.
7
4
8
5
## Acquiring a Single Image
9
6
10
7
To acquire a single image using the OpenSPIM plugin:
11
8
12
-
1. Navigate the 4D stage to the location you want to image (see
13
-
[Operation](Operation"wikilink") for details).
14
-
2. Set Stack Depth to 0. This will limit the position to a single
15
-
plane. (You should not need to change the Step Size.)
16
-
3. Click *Stack at this Z plus:* to add this plane to the position
17
-
list.
18
-
4. You may specify an Output directory if you would prefer the image be
19
-
written straight to disk as an OME-TIFF, rather than opened in Fiji.
20
-
1. The other options have no effect for a single plane, with the
21
-
exception of Snap Continuously (which should be unchecked).
22
-
5. Finally, click *Oh Snap\!* to take the image.
9
+
1. Navigate the 4D stage to the location you want to image (see [Operation](Operation) for details).
10
+
2. Set Stack Depth to 0. This will limit the position to a single plane. (You should not need to change the Step Size.)
11
+
3. Click *Stack at this Z plus:* to add this plane to the position list.
12
+
4. You may specify an Output directory if you would prefer the image be written straight to disk as an OME-TIFF, rather than opened in Fiji.
13
+
1. The other options have no effect for a single plane, with the exception of Snap Continuously (which should be unchecked).
14
+
5. Finally, click *Oh Snap!* to take the image.
23
15
24
16
## Acquiring a Stack
25
17
26
18
Acquiring a single stack is very similar to acquiring a single position.
27
19
28
20
1. Begin by navigating to the place the stack should begin.
29
21
2. Specify the Stack Depth in μm, and the Step Size (also in μm).
30
-
3. Click *Stack at this Z plus:* to add the stack to the positions
31
-
list.
22
+
3. Click *Stack at this Z plus:* to add the stack to the positions list.
32
23
4. Configure whichever settings are desired:
33
-
1. The *Set Z-stage velocity* and Z settle time controls may be
34
-
useful for reducing jitter.
35
-
2. Snap Continuously can be used if recording at the precise
36
-
locations specified for your stack is of less importance than
37
-
acquiring images constantly.
38
-
3. Update Live View will display each slice in the Live Window as
39
-
it is acquired (allowing you to abort the acquisition early if
40
-
necessary).
41
-
4. Lase Full Stack is not generally necessary when recording a
42
-
single stack, as the reduced time between slices is negligible.
43
-
5. Though a single stack can easily fit into memory, it is
44
-
recommended that you specify an Output directory so the stack is
45
-
saved in OME-TIFF format.
46
-
6. Using Asynchronous Output is optional, though it will reduce the
47
-
time spent acquiring considerably.
48
-
5. Click *Oh Snap\!* to acquire the stack.
24
+
1. The *Set Z-stage velocity* and Z settle time controls may be useful for reducing jitter.
25
+
2. Snap Continuously can be used if recording at the precise locations specified for your stack is of less importance than acquiring images constantly.
26
+
3. Update Live View will display each slice in the Live Window as it is acquired (allowing you to abort the acquisition early if necessary).
27
+
4. Lase Full Stack is not generally necessary when recording a single stack, as the reduced time between slices is negligible.
28
+
5. Though a single stack can easily fit into memory, it is recommended that you specify an Output directory so the stack is saved in OME-TIFF format.
29
+
6. Using Asynchronous Output is optional, though it will reduce the time spent acquiring considerably.
30
+
5. Click *Oh Snap!* to acquire the stack.
49
31
50
32
## Single-Plane Time Lapse
51
33
52
-
To acquire a time lapse of a single plane, set up the recording exactly
53
-
as if you were going to record only [one
54
-
image](#Acquiring_a_Single_Image"wikilink").
34
+
To acquire a time lapse of a single plane, set up the recording exactly as if you were going to record only [one image](#acquiring_a_single_image).
55
35
56
-
1. Enable the Time box and specify an Interval (0 seconds is allowed)
57
-
and a Count.
36
+
1. Enable the Time box and specify an Interval (0 seconds is allowed) and a Count.
58
37
2. Optionally specify an Output directory.
59
-
3. Click *Oh Snap\!* to begin the time-lapse.
38
+
3. Click *Oh Snap!* to begin the time-lapse.
60
39
61
40
## Multi-View Imaging of a Fixed Sample
62
41
@@ -67,147 +46,75 @@ To record multiple views of a fixed sample:
67
46
2. Specify the Stack Depth and Step Size.
68
47
3. Click *Stack at this Z plus:* to mark that location.
69
48
2. Choose the appropriate options:
70
-
1. The *Set z-stage velocity* and Z settle time controls are useful
71
-
for reducing jitter.
72
-
2. Snap Continuously will record the stacks as fast as possible,
73
-
rather than at precisely the given locations.
74
-
3. Update Live View will show each slice of each stack as it is
75
-
taken.
49
+
1. The *Set z-stage velocity* and Z settle time controls are useful for reducing jitter.
50
+
2. Snap Continuously will record the stacks as fast as possible, rather than at precisely the given locations.
51
+
3. Update Live View will show each slice of each stack as it is taken.
76
52
4. Lase Full Stack can reduce acquisition time.
77
-
5. Choose an Output directory (highly recommended as these data
78
-
sets can become quite large).
79
-
6. Asynchronous Output is useful, but not required for fixed
80
-
samples.
81
-
7. If your stacks are particularly far apart and your motor
82
-
velocity is low, you may wish to override the Device Timeout.
83
-
3. Click *Oh Snap\!* to begin the multi-view imaging.
53
+
5. Choose an Output directory (highly recommended as these data sets can become quite large).
54
+
6. Asynchronous Output is useful, but not required for fixed samples.
55
+
7. If your stacks are particularly far apart and your motor velocity is low, you may wish to override the Device Timeout.
56
+
3. Click *Oh Snap!* to begin the multi-view imaging.
84
57
85
58
## Multi-View Time Lapses
86
59
87
-
The acquisition tab makes recording a time lapse of any number of views
88
-
simple: Simply set up a multi-view acquisition as described
89
-
[above](#Multi-View_Imaging_of_a_Fixed_Sample"wikilink"), and then:
60
+
The acquisition tab makes recording a time lapse of any number of views simple: Simply set up a multi-view acquisition as described [above](#multi-view_imaging_of_a_fixed_sample), and then:
90
61
91
-
1. Optionally enable Anti-Drift (long-term multi-view time lapses are
92
-
where anti-drift truly shines).
62
+
1. Optionally enable Anti-Drift (long-term multi-view time lapses are where anti-drift truly shines).
93
63
2. Enable the time controls, then specify an interval and count.
94
-
3. Once everything is set up, click *Oh Snap\!* to begin the
95
-
acquisition.
64
+
3. Once everything is set up, click *Oh Snap!* to begin the acquisition.
{% include image src="spimgui-acquiring-annotated.png" width="100%" caption="" %}
101
69
102
70
- (1) Positions List
103
-
This table shows the list of stacks of images to acquire. Each
104
-
timepoint will consist of the images recorded at each position in
105
-
this list (as well as the Z slices described by the MATLAB range in
106
-
the final column).
71
+
This table shows the list of stacks of images to acquire. Each time point will consist of the images recorded at each position in this list (as well as the Z slices described by the MATLAB range in the final column).
107
72
- (2) Insert Current Position
108
-
Clicking this button will add a row to the end of the table with
109
-
only the current position; i.e. when acquiring, a single slice will
110
-
be taken at the given location.
73
+
Clicking this button will add a row to the end of the table with only the current position; i.e. when acquiring, a single slice will be taken at the given location.
111
74
- (3) Delete Selected Rows
112
-
Clicking this will remove any currently-highlighted rows from the
113
-
table. You can select multiple rows by shift-clicking (to select a
114
-
range) or control-clicking (to select individual rows).
75
+
Clicking this will remove any currently-highlighted rows from the table. You can select multiple rows by shift-clicking (to select a range) or control-clicking (to select individual rows).
115
76
- (4) Stack at this Z plus
116
-
Clicking this button will add a row to the end of the table with the
117
-
current position of the stage motors and the stack dimensions/step
118
-
size as entered.
77
+
Clicking this button will add a row to the end of the table with the current position of the stage motors and the stack dimensions/step size as entered.
119
78
- (5) Stack Depth
120
-
Any stacks added by the "Stack at this Z plus" button will be this
121
-
deep, in um.
79
+
Any stacks added by the "Stack at this Z plus" button will be this deep, in um.
122
80
- (6) Step Size
123
-
Stacks added by the "Stack at this Z plus" button will advance the
124
-
motor by this many um in between each slice.
81
+
Stacks added by the "Stack at this Z plus" button will advance the motor by this many um in between each slice.
125
82
- (7) Estimates
126
-
This text displays the estimated size of the output dataset, and the
127
-
available storage space (in RAM or on disk, depending on whether or
128
-
not the output directory is empty).
83
+
This text displays the estimated size of the output dataset, and the available storage space (in RAM or on disk, depending on whether or not the output directory is empty).
129
84
- (8) Laser power
130
-
This slider (and associated number box) will change the laser's
131
-
output power in 0.01 mW units. Changing this during the acquisition
132
-
*will* cause a change in brightness in the recorded images.
85
+
This slider (and associated number box) will change the laser's output power in 0.01 mW units. Changing this during the acquisition *will* cause a change in brightness in the recorded images.
133
86
- (9) Exposure
134
-
This slider will control the exposure duration of the camera, in
135
-
milliseconds. Changing this during acquisition *will* cause a change
136
-
in brightness in the recorded images.
87
+
This slider will control the exposure duration of the camera, in milliseconds. Changing this during acquisition *will* cause a change in brightness in the recorded images.
137
88
- (10) Set z-stage velocity
138
-
This option can control the speed of the focus motor, to allow for
139
-
more careful positioning at the expense of additional time for the
140
-
motor to move.
89
+
This option can control the speed of the focus motor, to allow for more careful positioning at the expense of additional time for the motor to move.
141
90
- (11) Use Anti-Drift
142
-
In long-term, multi-view time lapses, a common problem is the
143
-
shrinking of the agarose column containing the sample. Enabling this
144
-
option will activate interactive anti-drift, to combat this. See
145
-
[Anti-Drift](Anti-Drift"wikilink").
146
-
- (12) Update Live View
147
-
If enabled, every time the camera takes an image it will update the
148
-
live window. This can make identifying a shifting sample easy, but
149
-
may also increase acquisition time.
91
+
In long-term, multi-view time lapses, a common problem is the shrinking of the agarose column containing the sample. Enabling this option will activate interactive anti-drift, to combat this. See [Anti-Drift](Anti-Drift).
92
+
- (12) Update Live View
93
+
If enabled, every time the camera takes an image it will update the live window. This can make identifying a shifting sample easy, but may also increase acquisition time.
150
94
- (13) Lase Full Stack
151
-
By default, the laser will blink for each slice in a stack. Enabling
152
-
this will cause the laser to remain on for the entire stack, then
153
-
turn off in between time points. This speeds up acquisition, but can
154
-
cause bleaching.
95
+
By default, the laser will blink for each slice in a stack. Enabling this will cause the laser to remain on for the entire stack, then turn off in between time points. This speeds up acquisition, but can cause bleaching.
155
96
- (14) Output directory
156
-
If a directory is given, the acquired images will be written out as
157
-
an OME-TIFF dataset. Otherwise, the images will be stored in memory
158
-
and opened in Fiji after acquisition. Outside of testing
159
-
acquisition, it is strongly recommended that an output directory be
160
-
specified.
97
+
If a directory is given, the acquired images will be written out as an OME-TIFF dataset. Otherwise, the images will be stored in memory and opened in Fiji after acquisition. Outside of testing acquisition, it is strongly recommended that an output directory be specified.
161
98
- (15) Asynchronous Output
162
-
Rather than writing out each slice as soon as it is taken, if this
163
-
is checked the images will be buffered and written out as soon as
164
-
the program finds time. This can greatly speed up acquisition, but
165
-
if an acquisition fails or is aborted, the metadata in the stored
166
-
images will be inconsistent.
99
+
Rather than writing out each slice as soon as it is taken, if this is checked the images will be buffered and written out as soon as the program finds time. This can greatly speed up acquisition, but if an acquisition fails or is aborted, the metadata in the stored images will be inconsistent.
167
100
- (16) Time
168
101
If the checkbox is enabled, a time-lapse will be recorded.
169
102
- Interval
170
-
The number of seconds between the ideal start of each time
171
-
lapse. If acquiring a sequence (the entire positions list) takes
172
-
less time than this interval, the system will wait until the
173
-
remaining time has elapsed.
103
+
The number of seconds between the ideal start of each time lapse. If acquiring a sequence (the entire positions list) takes less time than this interval, the system will wait until the remaining time has elapsed.
174
104
- Count
175
-
The number of sequences to record. Each sequence will record the
176
-
entire positions list.
105
+
The number of sequences to record. Each sequence will record the entire positions list.
177
106
- (17) Device Timeout
178
-
If specified, this will override µManager's default timeout (5
179
-
seconds). It should only be enabled if you encounter "device
180
-
timeout" errors (i.e. if the stage has to move a long distance, but
181
-
its velocity is too low to cover that distance in five seconds).
107
+
If specified, this will override µManager's default timeout (5 seconds). It should only be enabled if you encounter "device timeout" errors (i.e. if the stage has to move a long distance, but its velocity is too low to cover that distance in five seconds).
182
108
- (18) More Options
183
-
Clicking the *Show Dialog* button will open the Acquisition Options
184
-
dialog below the main window. This window contains additional
185
-
options which may be desired, but are less commonly-used than most
109
+
Clicking the *Show Dialog* button will open the Acquisition Options dialog below the main window. This window contains additional options which may be desired, but are less commonly-used than most
186
110
others.
187
-
- (19) Oh Snap\!
188
-
Pressing this button starts the acquisition. While the acquisition
189
-
is running, this button will read "Abort\!" and can be pressed to
190
-
cancel an acquisition.
111
+
- (19) Oh Snap!
112
+
Pressing this button starts the acquisition. While the acquisition is running, this button will read "Abort!" and can be pressed to cancel an acquisition.
191
113
- (20) Z settle time
192
-
Specifying a time interval here will cause each movement of the
193
-
stage to be followed by the given delay, to prevent jitter. This
194
-
will also add time to acquisitions.
114
+
Specifying a time interval here will cause each movement of the stage to be followed by the given delay, to prevent jitter. This will also add time to acquisitions.
195
115
- (21) Continuous Mode
196
-
Rather than take precisely one image each time the motor reaches a
197
-
position (either in the list, or at a slice within a stack), if this
198
-
is checked the camera will record images constantly while the stage
199
-
moves. (In between time-points, the acquisition will stop.) This can
200
-
cause blurry images, however, since the stage is often moving while
201
-
the camera exposes.
116
+
Rather than take precisely one image each time the motor reaches a position (either in the list, or at a slice within a stack), if this is checked the camera will record images constantly while the stage moves. (In between time-points, the acquisition will stop.) This can cause blurry images, however, since the stage is often moving while the camera exposes.
202
117
- (22) Monitor Async Output
203
-
If this checkbox is checked while Asynchronous Output is also
204
-
checked, a monitor window will be displayed showing the current
205
-
state of the async output buffer as it fills and empties. This may
206
-
be useful if the asynchronous output is providing unusual results.
118
+
If this checkbox is checked while Asynchronous Output is also checked, a monitor window will be displayed showing the current state of the async output buffer as it fills and empties. This may be useful if the asynchronous output is providing unusual results.
207
119
- (23) Profile Acquisition
208
-
If this checkbox is checked, the acquisition system will track the
209
-
time elapsed during certain parts of the process. This may be useful
210
-
to break down the time usage if the process seems unusually slow.
If this checkbox is checked, the acquisition system will track the time elapsed during certain parts of the process. This may be useful to break down the time usage if the process seems unusually slow.
0 commit comments