Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timestamps from control system (eg. Tango or EPICS) #1539

Open
sona-patel opened this issue Feb 7, 2025 · 1 comment
Open

timestamps from control system (eg. Tango or EPICS) #1539

sona-patel opened this issue Feb 7, 2025 · 1 comment

Comments

@sona-patel
Copy link
Contributor

Hello,
When we read any parameter from a control system (eg. Tango or EPICS) it always has a timestamp telling us when this parameter was processed/read. This is irrespective of whether this parameter is a static parameter (for eg. detector_number in NXdetector) or a new value (for eg. time_of_flight in NXdetector). We want to collect these timestamps in NeXus for debugging in case of some problem at the beamline. Would you suggest a place for these in NeXus?

Thank you :-)
Bluesky team of HZB

@rayosborn
Copy link
Contributor

rayosborn commented Feb 7, 2025

Parameters that are measured asynchronously during an experiment are normally stored in a NXlog group. There is a discussion of such use here. However, if you just store a single parameter as a scalar value, it would be possible to add an attribute to the field called 'timestamp'. Since it is impossible to specify the units of an attribute, it would have to be a ISO8601 string. There is an example of such use in the NXcanSAS application definition, although it is a group attribute in this example. I think the NIAC should consider adding documentation to formally approve this kind of use case.

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

No branches or pull requests

2 participants