Details
-
Type:
Task
-
Status: To Do
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
The only "time of read" timestamp for most/all data-arrays is from a single time (such as cRIO_timestamp). We apparently need to establish a better way of defining how to unpack these sequential data arrays to re-construct the time-stream telemetry (for example to rendezvous with other EFD telemetry). Certainly can be done by hand, but we need this to happen with minimal effort for most end-users.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Watchers | Angelo Fausti, Brian Stalder, Petr Kubanek, Robert Lupton, Simon Krughoff, Stratejos Slack Intergration bot [ Angelo Fausti, Brian Stalder, Petr Kubanek, Robert Lupton, Simon Krughoff, Stratejos Slack Intergration bot ] | Angelo Fausti, Brian Stalder, Craig Lage, Petr Kubanek, Robert Lupton, Simon Krughoff, Stratejos Slack Intergration bot [ Angelo Fausti, Brian Stalder, Craig Lage, Petr Kubanek, Robert Lupton, Simon Krughoff, Stratejos Slack Intergration bot ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31343 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31418 ] |
| Attachment | Tracking_2021101400007_08Nov21.png [ 54641 ] |
| Attachment | Tracking_2021101400007_Shift_1p67_08Nov21.png [ 54642 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31418 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31470 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31584 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31621 ] |