Cheetah hardcodes timezone

[FilipeMaia]

Cheetah hardcodes the timezone to US/Pacific. This can potentially cause problems when processing data from SACLA or other places.

[antonbarty]

Yes, this is old history. We needed it at the time to make the timestamps match the log book (and not spit out Europe time)

We don’t want the user to have to configure everything from scratch, even though that’s the most flexible.
One way to solve this is to have a few standard setups: for example, experiment location = LCLS/CXI sets by default the cspad, and US/Pacific timezone etc. experiment location = SACLA would set other parameters.

A.

On 10 Feb 2015, at 10:19, Filipe Maia [email protected] wrote:

Cheetah hardcodes the timezone to US/Pacific. This can potentially cause problems when processing data from SACLA or other places.

—
Reply to this email directly or view it on GitHub https://github.com/antonbarty/cheetah/issues/17.

[FilipeMaia]

A solution that might work automagically is to hardcode the timezone in the light source specific code part (cheetah_ana_mod and cheetah-sacla).

[antonbarty]

Yes, that would work. CXI is unlikely to suddenly appear in Japan or Germany.

Anton

Anton Barty
Centre for Free Electron Laser Science
+49 (0)170 639 0539

On 10 Feb 2015, at 11:25 am, Filipe Maia [email protected] wrote:

A solution that might work automagically is to hardcode the timezone in the light source specific code part (cheetah_ana_mod and cheetah-sacla).

—
Reply to this email directly or view it on GitHub.