Skip to content

Conversation

@dylanmcreynolds
Copy link
Contributor

@dylanmcreynolds dylanmcreynolds commented Jan 7, 2026

This PR adds the timepix "heatmap streaming" zmq listener.

For the time being, we support two modes for the xps_operator:

  • Bassler streaming where our operator code builds heatmaps
  • Timepix mode, where upstream code produces heatmaps

Wwe will soon probably remove the bassler/heatmap building code from this repo, but not today.

docker-compose.yml has been updated to make timepix the defult.

This also adds a uv.lock file for development.

This PR does not result in end-to-end processing of timepix. When the timepix code sends a start and stop message, then we will follow up with a PR here to use those to reset counters.

Copy link

@gabrielgazollalbl gabrielgazollalbl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in schemas.py:

  1. maybe it is not clear the difference between

frame_number and shot_num

maybe rename to:

current_frame_number, total_shot_number ?

  1. Should we have a validation logic for the fields ?

=====

in websockets.py:

Why removing these lines? Not needed for Timepix?

"shot_mean": convert_to_uint8(message.shot_mean.array),
"shot_std": convert_to_uint8(message.shot_std.array),

=====

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants