-
Notifications
You must be signed in to change notification settings - Fork 26
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 support for derived telemetry values #7
Comments
aywaldron
added a commit
that referenced
this issue
Oct 19, 2018
aywaldron
added a commit
that referenced
this issue
Oct 19, 2018
aywaldron
added a commit
that referenced
this issue
Oct 19, 2018
…PacketDefinition classes with derivations; adding derivation construction from yaml
aywaldron
added a commit
that referenced
this issue
Oct 19, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
…PacketDefinition classes with derivations; adding derivation construction from yaml
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
aywaldron
added a commit
that referenced
this issue
Nov 28, 2018
Issue #7 - Add support for derived telemetry values
MJJoyce
pushed a commit
that referenced
this issue
Sep 4, 2019
MJJoyce
pushed a commit
that referenced
this issue
Sep 4, 2019
MJJoyce
pushed a commit
that referenced
this issue
Sep 4, 2019
…PacketDefinition classes with derivations; adding derivation construction from yaml
MJJoyce
pushed a commit
that referenced
this issue
Sep 4, 2019
MJJoyce
pushed a commit
that referenced
this issue
Sep 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
EGSE users have specified that they would like to be able to define derived telemetry points, especially when scripting instrument functionality with
bliss.core.api
, so they can track various stats that might not be returned in telemetry. For instance, they might track the number of times that a sensor's power state has been toggled on/off.Whether this would be injected into telemetry packets in the
api
or implemented and accessed some other way is still TBDThe text was updated successfully, but these errors were encountered: