test_main.sh seems to give one process more time than another

[huckl3b3rry87]

In this case, the first case runs

Running model for the: 148 time
n.r.ocp.status = :Optimal
Running model for the: 149 time
n.r.ocp.status = :Optimal
[obstacle_avoidance-1] process has finished cleanly

Then the second one is killed (which is the same except for the caseID).

Running model for the: 39 time
n.r.ocp.status = :Optimal
Running model for the: 40 time
n.r.ocp.status = :Optimal
[ INFO] [1545582768.886051818, 1.005000000]: ----System shutdown captured----

The result are stored as

@sumjos is the bash script killing the second run?

[sumjos]

I will take a look. We cannot say if the process died due to time out. I will try adding an additional parameter to record the time out scenario in the report. Right now, the default description is added to the report if any unmonitored event (which is not already added as a stopping criteria in JSON file) causes the simulation to stop.

[huckl3b3rry87]

I see, thanks. Yeah, it looks like you are restarting time here https://github.com/JuliaMPC/MAVs/blob/develop/ros/src/system/test/main/testB.sh#L37

after each time, so I am not sure why it would get killed the second time around.

[huckl3b3rry87]

@sumjos do you have any idea why the simulation might stop? It is not one of the parameters that I set it to stop at. It is stopping at: https://github.com/JuliaMPC/MAVs/blob/develop/ros/src/system/src/system_shutdown.cpp#L109 For some other reason. We are just rerunning the same simulation, so it should not stop. Any insight would be much appreciate, I have been messing with this for a while now. Thanks!

[huckl3b3rry87]

fixed