Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:4
-
Sprint:TSSW Sprint - Aug 01 - Aug 15
-
Team:Telescope and Site
-
Urgent?:No
Description
The M1M3 component currently has several event topics that are streamed at 50Hz alongside telemetry. Since events are configured to have historical data, this ends up puts some strain in the middleware. It also puts some strain in LOVE which is configured to treat event asynchronously, whereas telemetry is handled at a lower rate.
This also represents a bit of a deviation on the intention of events, as we expect them to be asynchronous rather than streaming, which is what telemetry is designed for.
The following is a list of events I have identified that needs to be converted, but please, make sure I didn't missed anything as you know a lot more about the m1m3 than I do.
logevent_appliedCylinderForces
|
logevent_appliedForces
|
Attachments
Issue Links
- is triggering
-
DM-35880 Send zeroed applied*Forces events when forces are zeroed
- Done
- relates to
-
CAP-931 Catch all ticket for TSSW XML 13.0 work
-
- Done
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Please see GitHub