To make errors more obvious to a user monitoring behavior through the GUI's /infoLog topic, we can publish a warning whenever task starts in an initialized state.
A user should know whether the restart message is concerning, depending on whether the rover was put in manual mode temporarily.
Logging a restart message is more reliable than trying to publish an error message on exit because rospy doesn't guarantee your messages will be published if your node exits immediately afterward.
To make errors more obvious to a user monitoring behavior through the GUI's
/infoLog
topic, we can publish a warning whenevertask
starts in an initialized state.A user should know whether the restart message is concerning, depending on whether the rover was put in manual mode temporarily.
Logging a restart message is more reliable than trying to publish an error message on exit because rospy doesn't guarantee your messages will be published if your node exits immediately afterward.