Hi Jakob,
this is our rerouting option.
<routing>
<routing-algorithm value="dijkstra"/>
<device.rerouting.adaptation-interval value="30"/> <!--The interval for
updating the edge weights -->
<device.rerouting.adaptation-steps value="4"/> <!--The number of
adaptation steps for averaging (enable for values > 0) -->
<device.rerouting.period value="120"/> <!--The period with which the
vehicle shall be rerouted -->
<device.rerouting.output value="rerouting.adapting_weights.sumout"/>
</routing>
So you suggest to use astar /CHWrapper and add <device.rerouting.threads>.
Shall we remove all the other settings?
We created a small subset and will share it via filecloud to show the latest
error. Can I send the link and pw to your DLR email?
One further issue: The calibrators show on some edges to high/low flow than we
configured. We monitored it it via the GUI and using induction loops.
You should be able to see it as well via our subset.
Best,
Florian
--
Dr. Florian Berkes
umlaut
cell +49 151 27654 587
[email protected]
www.umlaut.com<http://www.umlaut.com>
umlaut solutions GmbH
legal disclaimer, mandatory information and the umlaut office addresses can be
found at
imprint.umlaut.com/SOL<https://imprint.umlaut.com/SOL>
Information about the processing of your personal data can be found
here.<https://imprint.umlaut.com/gdpr-SOL>
Von: [email protected] <[email protected]> Im Auftrag
von Jakob Erdmann
Gesendet: Montag, 25. November 2019 16:18
An: Sumo project User discussions <[email protected]>
Betreff: Re: [sumo-user] Error using load-state option with calibrators
Hello,
1) options are fine. I would not expect a 90mb simulation network to drop below
real-time simulation speed. Possibly your simulation spends a lot of time
computing routes. Check if either of the following options speeds things up:
--routing-algorithm astar
--routing-algorithm CHWrapper
--device.rerouting.threads <INT>
2) Car following models are not used in mesosim. Slope is taken into account in
mesosim only for emission/fuel consumption.
3) The error indicates that a vehicle with the same ID already exists in the
simulation. This may be a bug but I would need a (small!) failing example to
look into this.
regards,
Jakob
Am Mo., 25. Nov. 2019 um 12:29 Uhr schrieb
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>:
Hi Jakob,
thanks for your quick reply and fixes.
“Regarding vehicles with reroute="0". Can you please provide a minimal sample
input that reproduces this issue?”
Sharing the network file will be difficult. The file is about 90 MB. Any
suggestion how we can provide a smaller subset?
The meso simulation takes also a quite long time, we thought it will be much
faster.
Currently, 1 hour simulation takes about 24h real time.
* We use the options --mesosim true --meso-junction-control.limited true
--meso-overtaking
Are they fine?
* We also use the carfollowing model KraussPS to consider slopes. The
altitude was extracted from SRTM data.
Is this model used if we simulate with mesosim?
* We still have an error with an calibrator after we load the state file
from the previous:
Loading state from 'state_25200.00_fixed.xml'... done (18747ms).
Loading done.
Simulation version 1.3.1 started with time: 25200.00
Error: Emission of vehicle 'cali_133849585.25233991.0' in calibrator
'cali_133849585'failed!
Quitting (on error).
DijkstraRouter answered 1014 queries and explored 43169.76 edges on average.
DijkstraRouter spent 42128ms answering queries (41.55ms on average).
Segmentation fault
Thanks again for your help,
Florian
--
Dr. Florian Berkes
umlaut
cell +49 151 27654 587
[email protected]<mailto:[email protected]>
www.umlaut.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.umlaut.com&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163842971&sdata=NmjNiLz7at5MXkoSLmEqmr4AiDEME3TtD4Dt4M2x%2Be4%3D&reserved=0>
umlaut solutions GmbH
legal disclaimer, mandatory information and the umlaut office addresses can be
found at
imprint.umlaut.com/SOL<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimprint.umlaut.com%2FSOL&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163842971&sdata=ukYuTsRy%2FU1eNhILwNZGbvfeu8GX%2FWHBVH7Zx9mUJZo%3D&reserved=0>
Information about the processing of your personal data can be found
here.<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fimprint.umlaut.com%2Fgdpr-SOL&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163842971&sdata=ot4fEQKfGUKf7dH7oee%2FlmFBvYrrN1qf3YvSfCJu3q0%3D&reserved=0>
Von: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> Im
Auftrag von Jakob Erdmann
Gesendet: Samstag, 23. November 2019 09:19
An: Sumo project User discussions
<[email protected]<mailto:[email protected]>>
Betreff: Re: [sumo-user] Error using load-state option with calibrators
Hello,
the 'depart' value within the statefile encodes departDelay. This can become
negative due to
https://github.com/eclipse/sumo/issues/964<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fissues%2F964&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163852965&sdata=2W%2FFstxPgBp7HjeIC0z1RCijA6PBHtb98A10EDHZHjQ%3D&reserved=0>
The error you are seeing comes from our xml-schema validation
(https://sumo.dlr.de/docs/XMLValidation.html<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsumo.dlr.de%2Fdocs%2FXMLValidation.html&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163852965&sdata=Ka%2FeTBDkz3Zs7v%2FvqEUUy%2F3LprehHoIB6mBBkLU3Meg%3D&reserved=0>)
I've updated the schema files to allow negative departDelay.
To prevent the error you can either
- copy my patch to the schema files
(https://github.com/eclipse/sumo/commit/406a75fa444098139ddf70a949310eeb3a74280b<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fcommit%2F406a75fa444098139ddf70a949310eeb3a74280b&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163862961&sdata=ZXxu4Ar5LawiSlmjfuEk1W1BHZ1mQDw4ieYktlW6KUE%3D&reserved=0>)
- disable xml validation (--xml-validation never)
Regarding invalid routeDistribution: Thanks for letting me know. This is now
fixed:
https://github.com/eclipse/sumo/issues/6308<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feclipse%2Fsumo%2Fissues%2F6308&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163862961&sdata=cttKkN221JIO%2BtG6YG%2BHP8UoAGwaCQ7AdCb3o65JEKQ%3D&reserved=0>
Regarding vehicles with reroute="0". Can you please provide a minimal sample
input that reproduces this issue?
Regarding lane placement: Mesosim mostly does not take lanes into account
(except turn lanes at intersection). Placement of vehicles in the rightmost
lane is therefore purely a visual issue.
regards,
Jakob
Am Fr., 22. Nov. 2019 um 09:22 Uhr schrieb
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>:
Hi Jakob,
we run a 24h scenario’s using sumo meso (v1.3) using
* randomtrips generate for each hour,
* multiple calibrators (> 1000) in 1min-frequency, only streets with prio 7
to 13 and larger than 100 m
* using the option load-save state for every hour suffix (xml)
We had some issues with the calibrators attributes and did some fixes:
* vehicle inserted by calibrators with attribute reroute=0. When loading
the state, insertion of these vehicles fails. Fix: set reroute=1
* some routeDistribution entries have attribute probabilities="", which
results in an error when loading the state. Fix: removing these distributions
After 5am of the simulation, we faced the following error loading the state
file:
Error: value '-4327.00' must be greater than or equal to minInclusive facet
value '0'
<delaybegin="959343"depart="-4327.00"end="932642"number="26119"time="125970483.00"/>
We deleted the line in the state file and continue the simulation.
However at 7 am we faced again an error for one calibrator.
In the GUI we see that most of the vehicles are mostly placed at the right lane
(effect of meso simulation?)
Any idea what could be wrong with the calibrators?
Thanks
Florian
_______________________________________________
sumo-user mailing list
[email protected]<mailto:[email protected]>
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Fsumo-user&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163872957&sdata=HflcEeCoZQvF%2FFkFB3GNjl%2FRC%2B8m2K%2FYDXOW%2Fk0fK%2FY%3D&reserved=0>
_______________________________________________
sumo-user mailing list
[email protected]<mailto:[email protected]>
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Fsumo-user&data=02%7C01%7Cflorian.berkes%40umlaut.com%7C7b7dd3e5b720430ed41008d771babd12%7C58d65043cd9d409f828b59b40ef5f919%7C0%7C0%7C637102919163872957&sdata=HflcEeCoZQvF%2FFkFB3GNjl%2FRC%2B8m2K%2FYDXOW%2Fk0fK%2FY%3D&reserved=0>
_______________________________________________
sumo-user mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user
