TEMPUS is a new detector system being developed for photon science. It is based on the Timepix4 chip and, thus, it can be operated in two distinct modes: a photon-counting mode, which allows for conventional full-frame readout at rates up to 40 kfps; and an event-driven time-stamping mode, which allows excellent time resolution in the nanosecond regime in measurements with moderate X-ray flux. In this paper, the initial prototype, a single-chip device, is introduced, and the readout system described. Moreover, and in order to evaluate its capabilities, some tests were performed at PETRA III and ESRF for which results are also presented.

We are currently setting up the Tempus flow and have ran into some mismatched data regarding ECO and timing reports. I generated a timing report before running ECO and saw six total setup violations. When running opt_signoff -setup, the initial setup summary that was printed in the shell only showed one violation. I can see that violation from the initial setup summary in my pre-ECO timing report and it is not the worst path. Upon further investigation, I forced the tool to try to fix setup on one of the other five violations from the timing report using the opt_signoff_select_setup_endpoints attribute and the tool said that the endpoint had positive slack and would be ignored.

Has anyone experienced something like this before?