This is all a bit hacky. I recommend backing up your task_events collection before using. This doesn't edit them, but you never know given my recent form.
Instructions:
1) Run rosrun task_executor task_events_unique.py to uniquify all task event ids (ids are unique as of a month ago or so, but neither deployment system has that from the start). Note my code is ugly and inefficient and this could take a long time the first time it's run.
2) rosrun task_executor task_summary.py to get a table of executions. There are time arguments to bound the printing to a given window. Note again my code is ugly and inefficient and this could take a long time the first time it's run.
Don't merge yet!
This is all a bit hacky. I recommend backing up your task_events collection before using. This doesn't edit them, but you never know given my recent form.
Instructions:
1) Run
rosrun task_executor task_events_unique.pyto uniquify all task event ids (ids are unique as of a month ago or so, but neither deployment system has that from the start). Note my code is ugly and inefficient and this could take a long time the first time it's run.2)
rosrun task_executor task_summary.pyto get a table of executions. There are time arguments to bound the printing to a given window. Note again my code is ugly and inefficient and this could take a long time the first time it's run.