[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [sumo-user] NETCONVERT freezes on very large networks
|
Can you make your input file available? I stilll think there is a bug somewhere.
The size of the network before processing:
831430 nodes and 1441826 edges. I didn't find the final network size in the log file and didn't save each network separately, so can't be sure if I can say the size of the resulted network after processing :-/
Here are the other two statistics (in the sequence of the above notebook cells)
1- 0 Nodes removed.
Summary:
Node type statistics:
Unregulated junctions : 0
Dead-end junctions : 9354
Priority junctions : 802752
Right-before-left junctions : 1830
Traffic light junctions : 16969
2- 327343 nodes removed.
Summary:
Node type statistics:
Unregulated junctions : 0
Dead-end junctions : 9352
Priority junctions : 381203
Right-before-left junctions : 1746
Traffic light junctions : 111261
3- 425644 nodes removed.
Summary:
Node type statistics:
Unregulated junctions : 0
Dead-end junctions : 9340
Priority junctions : 381589
Right-before-left junctions : 1822
Traffic light junctions : 12510
4- 425644 nodes removed.
Summary:
Node type statistics:
Unregulated junctions : 0
Dead-end junctions : 9340
Priority junctions : 377231
Right-before-left junctions : 1799
Traffic light junctions : 16891
Best,
Sasan
I find these values quite surprising since the running time for node removal should be linear in the removed nodes when there are no traffic lights and quite low compared to all the other computations that are going on.
can you please report
- the number of nodes removed (verbose output should say: Removing empty nodes and geometry nodes. X nodes removed)
- the number of junctions in either network (verbose output lists them in the node type statistics)
- the final network size when removing/not removing nodes.
regards,
Jakob
I tried some variations, you can see the times below. It got generally faster after I rebooted my computer. --geometry.remove is by far the most influential factor:
I still suspect a bug rather than a "simple" algorithm-to-slow problem. To rule out one piece of slow-algorithm in the context of geometry.remove, can you try running with option --tls.discard-loaded?
I didn't measure the time in my script, but it wasn't more than 5 minutes. and the network is entire Germany's road network from OSM down to "highway.secondary".
How long does it run without --geometry.remove?
True. It ended after >36 hours. I am using version 1.7.0 actually.
Hi,
if it occurs only with the latest nightly build but not with 1.8 it
might as well be https://github.com/eclipse/sumo/issues/8270. It does
not freeze it just takes very long, I also noticed that with the Berlin
network.
Best regards,
Michael
Am 19.02.21 um 07:48 schrieb Jakob Erdmann:
> My guess would be that this isn't about size but somewhere in that big
> network is a piece of input which triggers a bug. You could try to split
> your input in half and convert each individually to check this hypothesis.
>
> regards,
> Jakob
>
>
> Am Do., 18. Feb. 2021 um 21:34 Uhr schrieb Sasan Amini
> <aminissn@xxxxxxxxx <mailto:aminissn@xxxxxxxxx>>:
>
> Dear all,
>
> I am trying to convert a very large OSM file to a SUMO network using
> NETCONVERT. When I set --geometry.remove, the processes freezes when
> trying to remove empty nodes and never ends. Is this a memory issue
> or somehow NETCONVERT doesn't like to remove that many nodes? btw, I
> have 40GB of RAM and 12 CPU cores and without --geometry.remove I
> get the network in less than 5 minutes.
>
> Thanks,
> Sasan
> image.png
> _______________________________________________
> sumo-user mailing list
> sumo-user@xxxxxxxxxxx <mailto:sumo-user@xxxxxxxxxxx>
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/sumo-user
> <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
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
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
