Imaging Tasks

Before you begin to design high-level application flows, make sure you understand what Walabot can do as explained in Imaging Features.
For an image to be received by the application, the following needs to happen:

1. Connect: Establish communication with Walabot.
2. Configure: Set scan profile and arena; optionally, set a dynamic-imaging filter and/or change the sensitivity threshold.
3. Calibrate: Ignore or reduce the signals of fixed reflectors such as walls according to environment.
   Must be performed initially (to avoid delays – preferably before Start), upon any profile change, and is recommended upon possible changes to environment.
4. Start: Start the system in preparation for scanning. Requires a scan profile to have been set.
5. Trigger: Scan (sense) according to profile and record signals to be available for processing and retrieval.
   Should be performed before every Get action.
6. Get action: Process as relevant and provide image data for the current arena, according to specified get action, current dynamic-imaging filter (if any), and current sensitivity threshold.
   Get actions retrieve the last completed triggered recording, and Walabot automatically makes sure the application doesn’t receive the same recording twice (so, you have the option of implementing Trigger and Get action in parallel).
7. Stop and Disconnect.

Configuration settings can be changed at any stage, and Walabot makes sure that `equent Get actions receive data from scans that were triggered after the change.

The scan profile can be changed at any stage, upon which Walabot automatically performs Stop > change profile > Start. Upon a profile change, Walabot should be recalibrated.

Once you've designed high-level application flow according to the above tasks, implement them in code as in Code Implementation Flow.


Fill out our 5 question survey Share Your API Feedback