This is because the traci library version does not match the sumo version (1.9.0 has 10 instead of 9 reservation parameters). Compare /usr/share/sumo/tools/traci/_person.py with the 1.9.0 version: https://github.com/eclipse/sumo/blob/0d34f1f23bdec0abd25a8b61dc21433b4208bbff/tools/traci/_person.py
Am Mi., 21. Apr. 2021 um 10:49 Uhr schrieb Roessler, Andreas < [email protected]>: > Hi, > > > > I’m using the example > > /tests/complex/traci/vehicle/taxi/basic/runner.py > > > > The very STRANGE fact: > > the example runs without error on one computer (Ubuntu 20, sumo 1.9.0, > 32GB RAM) > > > > On another computer (VM, same OS, same sumo version, 4GB) I get: > > > > Retrying in 1 seconds > > Loading configuration ... done. > > ***Starting server on port 50661 *** > > Loading net-file from 'input_net4.net.xml' ... done (12ms). > > Loading done. > > Simulation version 1.9.0 started with time: 0.00 > > taxiFleet ('taxi_0',) > > Traceback (most recent call last): > > File "runner.py", line 61, in <module> > > reservations = traci.person.getTaxiReservations(0) > > File "/usr/share/sumo/tools/traci/_person.py", line 246, in > getTaxiReservations > > result.append(_readReservation(answer)) > > File "/usr/share/sumo/tools/traci/_person.py", line 63, in > _readReservation > > assert(result.read("!i")[0] == 9) > > AssertionError > > Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown > > Quitting (on error). > > DijkstraRouter answered 1 queries and explored 1.00 edges on average. > > DijkstraRouter spent 0.00s answering queries (0.00ms on average). > > > > Any ideas how to fix this are highly appreciated. > > > > Best regards > > Andreas > > > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
