forrestv
commented
9 years ago It probably makes more sense to just have some kind of status monitor node that monitors all the relevant topics and issues a kill if something is wrong. IMO that's better than cluttering up all the nodes with checks and kill broadcaster code.
On Mon, Jun 29, 2015 at 2:04 PM, fnivek notifications@github.com wrote:
All over our code nodes rely on other nodes, if something hangs up, such as odometry, it causes other nodes to hang. We need to identify these issues and resolve them. In example when AZI drive does not get an odometry message it just sits and waits until it does. Instead AZI drive should have some default behaviour such as continue with last known odometry until some allowable amount of time has passed after which it would send a kill.
This is a major task involving review of all of our code. We need to make a standard and plan ahead before starting to patch up all these issues.
— Reply to this email directly or view it on GitHub https://github.com/uf-mil/PropaGator/issues/39.
All over our code nodes rely on other nodes, if something hangs up, such as odometry, it causes other nodes to hang. We need to identify these issues and resolve them. In example when AZI drive does not get an odometry message it just sits and waits until it does. Instead AZI drive should have some default behaviour such as continue with last known odometry until some allowable amount of time has passed after which it would send a kill.
This is a major task involving review of all of our code. We need to make a standard and plan ahead before starting to patch up all these issues.