Closed qku closed 4 months ago
At the moment, there are basically two scanning modes:
We basically need to introduce a third mode which is essentially like a 2D scan but without stepping a slow axis.
@LukePiewalker As the bare minimum, we could add the following attributes to ScanSettings
(as in #97):
int
which defaults to 1float
which defaults to 0, indicating the time (in s) to pause in between scansTo make it clear what kind of scan is wanted, we could introduce e.g. an enum to replace ScanSettings.scan_dimension
like
class ScanMode(Enum):
SINGLE_AXIS: 0
TWO_AXES: 1
SINGLE_AXIS_REPEATED: 2
This could make it easier for logic etc. to check if they actually support this scan mode, i.e. they can display / process the data.
This functionality is very specific to laser scanning and not so relevant for confocal scans. Therefore it might not make sense to include that here.
Feature Description
Extend the functionality of the scanning-probe toolchain to allow for repeated 1D scans.
Specifically, any hardware implementing the
ScanningProbeInterface
should accept instructions to perform a predefined number of forwards-backwards scans of a single axis. Taking the NI interfuse as an example, a single jump list comprising all repetitions should be sent to the hardware. This enables hardware timing and avoids software-timed loops.Additionally, an option should be included to include a break in between line scans. This could be extended to doing something in the break, e.g. sending out a hardware trigger.
Related Problem
This feature would be useful for photo-luminescence excitation measurements. Here, a single axis (a voltage sweeping a laser frequency) is commonly scanned repeatedly. Sometimes a pulse from a different laser is required in between scans.
Considered Alternatives
Use a software loop to perform a repeated 1D scan. This was done in the past for the laser scanner in old qudi.
Drawbacks include:
Additional Context
No response
Contact Details
No response