Uploading data to Tiled takes approx 1s for a small scan. This value may as well be higher for scan collecting lots of data. This is an issue for adaptive scan use case where based on current scan data you want to do another scan within a plan. Currently I have to wait until the Tiled update is finished. There is a risk of missing an event of interest because of the Tiled update latency.
Given a scan has completed and data is being uploaded to Tiled, and an adaptive workflow is running, could we introduce some feature that enables next scan to start without waiting for the Tiled upload to complete?
Acceptance Criteria
- Tiled upload does not block adaptive scan execution
Uploading data to Tiled takes approx 1s for a small scan. This value may as well be higher for scan collecting lots of data. This is an issue for adaptive scan use case where based on current scan data you want to do another scan within a plan. Currently I have to wait until the Tiled update is finished. There is a risk of missing an event of interest because of the Tiled update latency.
Given a scan has completed and data is being uploaded to Tiled, and an adaptive workflow is running, could we introduce some feature that enables next scan to start without waiting for the Tiled upload to complete?
Acceptance Criteria