Enhancements for TimePix

[dylanmcreynolds]

Several changes have to be made switch from the Bassler camera to timespix. Assuming that we can stream frames from timepix, we now have a situation where we might be getting start/stop messages over ZMQ from labview, but frames from a different ZMQ stream from Timepix.

So, we will need two listener instances, both feeding messages to the one operator.

One big change will be in the cli class:

https://github.com/als-computing/ArroyoXPS/blob/d74a5f96b6a423010022136dc72d77a4f10814d5/src/tr_ap_xps/apps/processor_cli.py#L62C19-L62C86

To register multiple ZMQ listeners:

listener = XPSLabviewZMQListener(operator=operator, **zmq_socket=lv_zmq_socket)**

becomes something like the following, after we build the timepix listener to get frames from timepix

labview_ listener = XPSLabviewZMQListener(operator=operator, zmq_socket=lv_zmq_socket)
timepix_listener = TimepixZMQListener(operator=operator, zmq_socket=timepix_zmq_socket)

So we need to create a TimepixZMQListener (once we have ZMQ streams from timepix). This new class will be similar to the XPSLabviewZMQListener, but will only handle frames, whie start and stop messages will still come from the XPS LabviewZMQListener.

This might all change a bit when we have it all running at the beamline, but not matter what, we will need the TimepixZMQListener

[dylanmcreynolds]

Thinking more on this. We do not know whether the timepix will be able to stream and write data at the same time. Also, the current workflow for timepix is very painful. The vendor software creates a .tpx file, and then a script converts that to hdf5.

If we could ourselves write the hdf5 file in a new operator at the same time as doing the visualizatoink, that would be really great.

Another idea might be: send the frames to tiled and let tiled write them to zarr files, then modify the analysis scripts to read either zarr or be a tiled client.

To say it another way:

current workflow
vendor software writes tpx --> script converts to h5 --> analysis reads h5

Phase 1
pymepix streams frames to TimepixZMQListener --> new H5WritePublisher writes to h5 directly --> analysis reads h5

Phase 2
pymepix streams frames to TimepixZMQListener --> TiledPublisher writes to Tiled --> analysis reads from tiled

Phase 2 is probably something we would look into during the next shutdown