Dead Jacob, Thank you for your response. You were right, passing person ids was the problem. Now it seems to be working. I will try to prepare some recommendations to improve documentation in the future and send it you.
Best regards, Sadullah. On Mon, May 17, 2021 at 1:57 PM Jakob Erdmann <[email protected]> wrote: > 1) dispatchTaxi does not work with person ids but rather with reservation > ids which are usually different form the person ids. The "failed to > mention" error however, does reference person ids. From the problem > description I suspect that you tried to pass a list of person ids directly. > > 2) after picking up a customer, the taxi will enter state 2 if no more > customers must be picked up in the current dispatch and state 3 otherwise. > I'm open for suggestion on how to make the wording in the documentation > more clear. > > regards, > Jakob > > Am So., 16. Mai 2021 um 23:36 Uhr schrieb S G <[email protected]>: > >> Greetings, >> >> I am currently doing some research on shared-ride Mobility on Demand >> services. Currently using SUMO to test my dispatch algorithms on a >> theoretical network. As of version 1.9.0 SUMO supports re-dispatching as it >> is currently mentioned on the documentation website. However, I am >> currently having some trouble with dispatching. I have two questions. I >> will try to ask my first question with an example. >> >> Let's assume taxi 4 already has a customer on board (Customer 12). But >> after some evaluations (based on some dispatch algorithm conditions), the >> algorithm decides another passenger (Customer 19) will be picked up before >> dropping off customer 12. How should this new dispatch be coded in Traci? >> >> I am currently doing the following: >> *traci.vehicle.dispatchTaxi(4,['12', '19', '12', '19']) * >> >> I have also tried the following: >> *traci.vehicle.dispatchTaxi(4,['19', '12', '19']) * >> >> However, I get the following error for both of these dispatch commands: >> *traci.exceptions.TraCIException: Could not interpret reservations for >> vehicle '4' (Re-dispatch did mention some customers but failed to mention >> 12).* >> >> My expectation from this code is this: Change your schedule as pick up >> "19" before dropping off "12" and drop off "12" (which is the current >> customer onboard) then drop off "19" >> >> 2) My second question is about taxi states. I don't think I fully >> understand how does taxi vehicle states change between 2 and 3. For >> example, if a vehicle has the capacity of 2 passengers. And after picking >> up a customer, does the vehicle enter state 2 as default? Or does it enter >> state 3. Website documentation says the following for taxi states: >> 0 (empty) : taxi is idle >> 1 (pickup): taxi is en-route to pick up a customer >> 2 (occupied): taxi has customer on board and is driving to drop-off >> 3 (pickup + occupied): taxi has customer on board but will pick up more >> customers >> >> Can you elaborate on how they change between these two states? >> >> >> Thank you very much for your time, >> Best Regards, >> Sadullah Goncu >> _______________________________________________ >> 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 >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
