diff --git a/docs/developer-guide/rosplane/estimator/estimator-base.md b/docs/developer-guide/rosplane/estimator/estimator-base.md index fcb6161..b7a88df 100644 --- a/docs/developer-guide/rosplane/estimator/estimator-base.md +++ b/docs/developer-guide/rosplane/estimator/estimator-base.md @@ -19,7 +19,7 @@ They are summarized in the table below: | ROS Interface | Topic | Explanation | Message Type | |:------:|:-------:| :---: | :---: | -|
`vehicle_state_pub_`
| `/estimated_state` | Publishes the estimated state of teh vehicle. | State.msg | +|
`vehicle_state_pub_`
| `/estimated_state` | Publishes the estimated state of the vehicle. | State.msg | |
`gnss_fix_sub_`
| `/navsat_compat/fix` | Subcribes to the GNSS position information. | NavSatFix.msg | |
`gnss_vel_sub_`
| `/navsat_compat/vel` | Subcribes to the GNSS velocity information. | TwistStamped.msg | |
`imu_sub_`
| `/imu/data` | Subcribes to the IMU data (both Gyro and Accel). | Imu.msg | diff --git a/docs/developer-guide/rosplane/estimator/estimator-example.md b/docs/developer-guide/rosplane/estimator/estimator-example.md index 2dd682a..d8fa500 100644 --- a/docs/developer-guide/rosplane/estimator/estimator-example.md +++ b/docs/developer-guide/rosplane/estimator/estimator-example.md @@ -13,7 +13,7 @@ The other states are then estimated as a all at once. This is called the position estimation step, though more than just position is estimated during this step. The estimator runs on a set timer with a configurable frequency (see Parameters section for details). -The estimator makes large use of something called a pseudo-measurements. +The estimator makes large use of something called a pseudo-measurement. These measures assume that the side slip angle is zero and the corresponding wind triangle solution. This allows us to take these measures and then find the wind in the north and east directions along with the yaw of the aircraft. They are more fully explored in section 8.11.4 of the UAV book. @@ -36,7 +36,7 @@ They are more fully explored in section 8.11.4 of the UAV book. ## Sensor Model Inversion -The roll, pitch and yaw rates are directly measured by the rate gyro and low pass filtered. +The roll, pitch and yaw rates are directly measured by the rate gyro and then low pass filtered. The low pass filter is a simple alpha filter described by: $$ @@ -246,7 +246,7 @@ With this propagated estimate and covariance we are now ready for a measurement -Because the GPS measures come in slower than the model propagates, the measurement step is only run when their is new GPS information. +Because the GPS measures come in slower than the model propagates, the measurement step is only run when there is new GPS information. This process is identical to the measurement update in the attitude step. This will likely change before release, but the only difference is that it is done one measurement at a time. This has advantages for querying the values while debugging, but is on the whole less clear and is more error prone. @@ -337,7 +337,7 @@ Next, replace `estimator_example.cpp` in the `CMakeLists.txt` with the newly cre | ![Estimator CMake Change Location](../../../assets/estimator_assets/estimator_cmake.png "Estimator CMake Change Location") | |:--:| -|*Figure 1: The location to replace the file for the new estimator file.*| +|*Figure 2: The location to replace the file for the new estimator file.*| ## Parameters @@ -368,6 +368,6 @@ Next, replace `estimator_example.cpp` in the `CMakeLists.txt` with the newly cre | `wind_e_initial_cov` | Initial covariance entry for wind east. | double | 0.04 | | `psi_initial_cov` | Initial covariance entry for heading. | double | 5.0 | | `num_propagation_steps` | Number of propagation steps to run between measurements. | int | 10 | -| `max_estimated_phi` | The maximum roll estimate, over this and the estimator saturates. | double | ~90.0 degrees | -| `max_estimated_theta` | The maximum pitch estimate, over this and the estimator saturates. | double | ~80.0 degrees | +| `max_estimated_phi` | The maximum roll estimate before estimator saturation. | double | ~90.0 degrees | +| `max_estimated_theta` | The maximum pitch estimate before estimator saturation. | double | ~80.0 degrees | | `estimator_max_buffer` | The buffer that the esimator returns the estimate to after saturation. | double | ~3.0 degrees | diff --git a/docs/developer-guide/rosplane/estimator/estimator-overview.md b/docs/developer-guide/rosplane/estimator/estimator-overview.md index f67909f..ce25e43 100644 --- a/docs/developer-guide/rosplane/estimator/estimator-overview.md +++ b/docs/developer-guide/rosplane/estimator/estimator-overview.md @@ -12,7 +12,7 @@ For a more in depth look at which states are estimated in which way visit the [E The estimator takes in sensor information from `rosflight_io` computes an estimate and publishes it to the rest of ROSplane. -| ![Diagram of Estimator ROS Interactions](../../../assets/estimator_assets/estimator_ros_input_output.png "Diagram of Estimator ROS Interactions") | +| ![Diagram of Estimator ROS Interactions](../../../assets/estimator_assets/estimator_full_ros_interactions.png "Diagram of Estimator ROS Interactions") | |:--:| |*Figure 1: ROS network interactions for the estimator.*|