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

Add PV's for start/end times as timestamps #12

Open
canismarko opened this issue Apr 19, 2023 · 0 comments
Open

Add PV's for start/end times as timestamps #12

canismarko opened this issue Apr 19, 2023 · 0 comments

Comments

@canismarko
Copy link

Currently, the following PVs are available on the local BSS module as strings:

  • Proposal start (${P}:proposal:startDate)
  • Proposal end (${P}:proposal:endDate)
  • ESAF start (${P}:esaf:startDate)
  • ESAF end (${P}:esaf:endDate)

If possible, could there also be PVs with these values as numbers given the unix-epoch timestamp? Not sure if integers or floats is better, probably depends on how much precision the source data has?

Two use cases come to mind:

  1. Compatibility with the pydm date time widget, which expects numbers.
  2. These signals could then be included in the ophyd BSS device and used to do math for how old the proposal/ESAF are.

Use case 2 is not that tricky to work around by converting the string to a timestamp, but use case 1 requires a custom widget or a regular QDateTime widget with the logic in python.

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

1 participant