Polling Lima acq_status and last_image_xxx counters at high frequency
Following up this morning meeting, @homsrego noticed on ID13 that, reading the scan logs, Bliss scan engine is pooling some Lima attributes at very high speed compared to what SPEC used to do.
I'd like to start a discussion about that. I don't consider it an issue -yet
I guess the scans we are talking about are internal trigger multi.
First last_image_xxx
counters are individual Tango properties but Bliss always read them all plus the additional ready_for_next_image
. I don't know if multi-valued property exists in Tango, but it would be nice to be able to bundle the tango requests into one. EDIT: actually Bliss uses read_attributes
, so one single Tango call.
Second reading acq_status
might be not so cheap, i.e it calls the HW interface to get the HW status and who knows what the plugin does... It could interfere with the acquisition.
@claustre @alejandro.homs What do you think? Are you confident that polling these attributes has limited impact on the acquisition?