You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks the progress of development of error generation classes or functionality. The high-level details are outlined on confluence.
Noise (error) and delay will be added to any data that is output from sensors and published to ROS2 topics. The data that will be impacted by noise and delay is listed here on confluence.
This is representative of real sensors just having occasional spikes in readings or delays in readings when they simply don't update for a short period of time.
We want the Sensor to be responsible for only sensing data and applying noise and delay then sending the data elsewhere for it to be sent over a ROS topic.
Noise will come from distribution (specific to each type of data). It could be multivariate, univariate, or constant. Generator classes help generate this noise.
I learned that delay is a function of the Sensors and not the act of publishing. The delay is caused by sensors not updating their values immediately. The impact on the design is that delay generation is part of the Sensor class.
Purpose
Tasks the progress of development of error generation classes or functionality. The high-level details are outlined on confluence.
Noise (error) and delay will be added to any data that is output from sensors and published to ROS2 topics. The data that will be impacted by noise and delay is listed here on confluence.
This is representative of real sensors just having occasional spikes in readings or delays in readings when they simply don't update for a short period of time.
Tasks
Noise Generation
Sensor
classes:WindSensor
andGPS
, add support for noise generation, and update theOutput Interface
section on ConfluenceDelay Generation
The text was updated successfully, but these errors were encountered: