Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Calibration interval isn't as defined
The random routes only serve as a candidate reservoir so the only downside of having too many is the running time of the sampling algorithm. I don't have a rule of thumb for a good number of routes yet but would suggest that you start low (a few thousand routes) and increase the number if routeSampler cannot find a good result.

Am Mi., 12. Aug. 2020 um 13:48 Uhr schrieb Simon.Frentrup@xxxxxxxxxx <Simon.Frentrup@xxxxxxxxxx>:

Hey Jakob,

 

I prepared the traffic counts, created some routes for a small test area and it seems to work fine, thanks!

 

I want to expand the simulation to a whole city and therefore need to create a lot of random routes. Can I somehow determine an appropriate number of random routes or do I need to use my gut feeling and test it?

 

Best regards

Simon

 

From: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Jakob Erdmann
Sent: Dienstag, 11. August 2020 11:47
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Subject: Re: [sumo-user] Calibration interval isn't as defined

 

Since you're using calibrators, I assume that you already know the desired amount of traffic in many places. In this case, you could also build your scenario with routeSampler: https://sumo.dlr.de/docs/Tools/Turns.html#routesamplerpy

 

Am Di., 11. Aug. 2020 um 08:49 Uhr schrieb Simon.Frentrup@xxxxxxxxxx <Simon.Frentrup@xxxxxxxxxx>:

Hey Jakob,

 

thanks for the hint. This actually showed me that the issue is somewhere else and just causes the same symptoms as long calibration intervals.

 

The problem is the amount of traffic inserted by random trips and the calibrators. Is there any other way to find the right amount of traffic inserted into a macroscopic simulation other than try and error?

 

Thanks and best regards

Simon

 

 

From: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Jakob Erdmann
Sent: Montag, 10. August 2020 16:06
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Subject: Re: [sumo-user] Calibration interval isn't as defined

 

I misread your flow definition so ignore my prior comment.

Please check if there are delayed insertions on the calibrator edge (https://sumo.dlr.de/docs/Simulation/VehicleInsertion.html#investigating_insertion_delay). If that is not the case, send in your input files so I can take a look.

 

 

 

Am Mo., 10. Aug. 2020 um 14:27 Uhr schrieb Simon.Frentrup@xxxxxxxxxx <Simon.Frentrup@xxxxxxxxxx>:

Hey Jakob,

 

thanks for your reply.

 

Where do I exactly have to add the end-attribute? In the flows it’s already present, just not directly after the begin-attribute.

 

Best regards

Simon

 

From: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Jakob Erdmann
Sent: Montag, 10. August 2020 14:17
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Subject: Re: [sumo-user] Calibration interval isn't as defined

 

You need to define the 'end' attribute of the calibrator flows explicitly.

 

regards,

Jakob

 

Am Mo., 10. Aug. 2020 um 10:08 Uhr schrieb Simon.Frentrup@xxxxxxxxxx <Simon.Frentrup@xxxxxxxxxx>:

Hey guys,

 

I’m currently running a simulation for one hour with calibrators, but they don’t behave as they should. The file with the calibrator definitions looks like this:

 

<?xml version="1.0" ?>

<additional xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/additional_file.xsd">

<routeProbe begin="0.00" edge="-26953591#1" file="probe.xml" freq="1" id="routeProbe_-26953591#1" name="-26953591#1"/>

…

<inductionLoop file="inductionLoop.xml" freq="10" id="inductionLoop_-26953591#1_0" lane="-26953591#1_0" pos="-1"/>

…

<calibrator edge="-26953591#1" id="cali_-26953591#1" pos="1" routeProbe="routeProbe_-26953591#1">

        <route edges="-26953591#1" id="cali_-26953591#1"/>

        <flow begin="53" departPos="free" departSpeed="max" end="112" route="cali_-26953591#1" type="private" vehsPerHour="55.576395141497045"/>

<flow begin="113" departPos="free" departSpeed="max" end="172" route="cali_-26953591#1" type="private" vehsPerHour="55.08124042362967"/>

        …

</calibrator>

</additional>

 

All calibration intervals are set to 60 seconds, but what I get as a result from the variable interval_sampledSeconds in the induction loop file looks like this:

 

The result looks like the calibration interval is for the complete hour and not for the defined intervals, which leads to a massive insertion of traffic and thereby to massive traffic jams.

 

Do you have any suggestions for me what I need to change in order to make it work in the intended way? Thanks in advance!

 

Best regards

Simon

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

Back to the top