Skip to content

Commit

Permalink
fixed some RINFO namespaces
Browse files Browse the repository at this point in the history
  • Loading branch information
petrlmat committed Apr 18, 2024
1 parent 0a64de6 commit 521d0b1
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 4 additions & 4 deletions src/estimators/altitude/alt_generic.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -517,25 +517,25 @@ void AltGeneric::doCorrection(const z_t &z, const double R, const StateId_t &H_i
innovation_ok_ = false;
switch (exc_innovation_action_) {
case ExcInnoAction_t::ELAND: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger eland in control manager", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger eland in control manager", getPrintName().c_str());
changeState(ERROR_STATE);
break;
}
case ExcInnoAction_t::SWITCH: {
ROS_WARN_THROTTLE(1.0, "[%s]: innovation should trigger estimator switch but no eland", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: innovation should trigger estimator switch but no eland", getPrintName().c_str());
innovation_(0) = 0.0; // this is quite hacky but is there other way to switch estimators and not trigger eland by the large innovation?
changeState(ERROR_STATE);
break;
}
case ExcInnoAction_t::MITIGATE: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger estimate jump mitigation", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger estimate jump mitigation", getPrintName().c_str());
innovation_(0) = 0.0; // this is quite hacky but is there other way to switch estimators and not trigger eland by the large innovation?
is_mitigating_jump_ = true;
setState(z(0), POSITION);
break;
}
case ExcInnoAction_t::NONE: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation ignored", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation ignored", getPrintName().c_str());
break;
}
}
Expand Down
8 changes: 4 additions & 4 deletions src/estimators/lateral/lat_generic.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -545,19 +545,19 @@ void LatGeneric::doCorrection(const z_t &z, const double R, const StateId_t &sta
innovation_ok_ = false;
switch (exc_innovation_action_) {
case ExcInnoAction_t::ELAND: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger eland in control manager", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger eland in control manager", getPrintName().c_str());
changeState(ERROR_STATE);
break;
}
case ExcInnoAction_t::SWITCH: {
ROS_WARN_THROTTLE(1.0, "[%s]: innovation should trigger estimator switch but no eland", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: innovation should trigger estimator switch but no eland", getPrintName().c_str());
innovation_(0) = 0.0; // this is quite hacky but is there other way to switch estimators and not trigger eland by the large innovation?
innovation_(1) = 0.0;
changeState(ERROR_STATE);
break;
}
case ExcInnoAction_t::MITIGATE: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger estimate jump mitigation", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation should trigger estimate jump mitigation", getPrintName().c_str());
innovation_(0) = 0.0; // this is quite hacky but is there other way to switch estimators and not trigger eland by the large innovation?
innovation_(1) = 0.0;
is_mitigating_jump_ = true;
Expand All @@ -566,7 +566,7 @@ void LatGeneric::doCorrection(const z_t &z, const double R, const StateId_t &sta
break;
}
case ExcInnoAction_t::NONE: {
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation ignored", ros::this_node::getName().c_str());
ROS_WARN_THROTTLE(1.0, "[%s]: large innovation ignored", getPrintName().c_str());
break;
}
}
Expand Down

0 comments on commit 521d0b1

Please sign in to comment.