Turn out it is a bug in my part (86.400 seconds is a day, I have a variable to calculate what time it is inside simulation environment, and actually use it).
Thanks and best regards, Thang On Dec 15, 2016, at 1:46 PM, Jakob Erdmann <[email protected]<mailto:[email protected]>> wrote: version 0.23.0 can only represent times up to 24.85 days. By upgrading to the latest version this limit is raised to 292 million years. regards, Jakob 2016-12-15 11:39 GMT+01:00 Thang Luu <[email protected]<mailto:[email protected]>>: Hi all, I developed a SUMO simulation that intended to run “forever” (vehicles are adding by another process). It works well and correct for several hours. But then, when the simulation step go to around 8639x, the simulation reset its step number to 0 and start processing from there. Is it normal behavior for SUMO? How can I make it so that the number keeps going up? My SUMO version is 0.23 running on Centos (if that help), the command use these variable: - --configuration-file - --begin - --step-length - --remote-port Thank you! Thang ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/sumo-user ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
