File>Open
n/a
Loop
Launches data acquisition - any programs set to 'External' will be included in the acquisition cycle.
Timing Control
DAQ board timing - The acquisition runs continuously for the number of iterations specified. Data are stored in a single .xsg file, i.e., as a single long trace (consisting of multiple 'tracelets').
CPU timing - The acquisition is discontinous; i.e., one .xsg file per iteration.
Suggested Usage
Use CPU timing if the interval between iterations is relatively long compared to the trace length, and high-precision timing of the intervals is not essential. Otherwise, use DAQ timing.
Busy mode
Sets how to handle data in CPU mode when the interval is too short
Iteration counter
Increments after each iteration.
Interval
The time in seconds between acquisition iterations.
- In CPU mode, the value should be somewhat greater than the trace length. This value is both system and configuration dependent. For simple configurations (e.g. involving only ephys) is is typically at least 0.5 sec; adding other channels from other programs (e.g. stimulator) will increase the time needed to fully 'settle' between traces. If the desired interval is only 2 sec (or less) longer than the trace length, either test the efficacy of the looper the configuration, or use DAQ mode.
- In DAQ mode, the interval is defined as equal to the trace length; i.e., the same value should be used in the Interval windos of the loopGui as in the trace length window of I/O programs (ephys, stimulator, acquirer).
If there is a discrepancy, a warning gui is displayed, and the value used for the loopGui Interval is applied to the other programs.
Iterations
Specifies the number of iterations in the looped acquisition.
Last iteration time, Last start time
Self-explanatory.