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
-
-
- Done
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
Activity
Reviewed the ts_cRIOpy in GitHub.
XML changes approved.
All three PR merged, reviewed in GitHub
Petr Kubanek
added a comment - All three PR merged, reviewed in GitHub It will take a while before this is available at the summit - a new XML needs to be released, which will not happen before mid-September. After XML is at the sumit, a new CSC version shall be run (the old will fail with the old XML schema).
Petr Kubanek
added a comment - It will take a while before this is available at the summit - a new XML needs to be released, which will not happen before mid-September. After XML is at the sumit, a new CSC version shall be run (the old will fail with the old XML schema). 
Please see GitHub