$ vroom -i example_2.json | jq .routes[].steps[]
{
"type": "start",
"arrival": 0,
"duration": 0
}
{
"type": "job",
"id": 1414,
"service": 0,
"waiting_time": 0,
"job": 1414,
"arrival": 2104,
"duration": 2104
}
{
"type": "job",
"id": 1515,
"service": 0,
"waiting_time": 0,
"job": 1515,
"arrival": 4359,
"duration": 4359
}
{
"type": "end",
"arrival": 5461,
"duration": 5461
}
$ cat example_2_sol.json | jq .routes[].steps[]
{
"type": "start",
"arrival": 0,
"duration": 0
}
{
"type": "job",
"job": 1414,
"service": 0,
"waiting_time": 0,
"arrival": 2104,
"duration": 2104
}
{
"type": "job",
"job": 1515,
"service": 0,
"waiting_time": 0,
"arrival": 4359,
"duration": 4359
}
{
"type": "end",
"arrival": 5461,
"duration": 5461
}
Running
vroom -i example_2.jsonno longer produces the same output asexample_2_sol.json:There looks to be an additional
idfield present in each of the job steps.