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 > <[email protected] <mailto:[email protected]>>: > > 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 > [email protected] <mailto:[email protected]> > 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 > [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
