Closed gac55 closed 5 years ago
First thing that would come to my mind is not enough memory; with not enough memory it often dies around there. Try -Xmx8000m or so (or even more if you have that).
Still, the JVM should give an error. Hm.
Interesting. I've seen a memory error before, but usually surfaces as a JVM error as you say.
Will try something bigger now :)
Increasing memory provision has had no impact unfortunately. Memory usage peaked at about 40% just before the above error occurred. Is there anything else I can try @kainagel ? Thanks!
A small update:
I have used a different set of input network and schedule and bypassed this error without any changes to the above config file.
I think it's likely this an issue related to the network, albeit an undiagnosed issue. Hope to try and better understand how the error manifests as perhaps it'll enable a more useful error message to be used.
It remains strange. Normally, it should at least throw an exception and thus print a stacktrace. With the info we have, we can't even say if it gave up inside the Umlauf thing or later; it just looks like a regular shutdown. Do you think you could sent me the failing setup (google drive or dropbox link) so I could look myself? I would presumably try to add a bunch of print statements to see where it fails. Or use a debugger, but I am not so good with those ...
Thank you @kainagel, that would be great. I'll prepare the docs and share
Hello everyone. Some help would be greatly appreciated. I am struggling to move past an "Generating UmlaufStuecke" error. The error occurs post network creation and quadTree
Matsim Version -
0.10.1
Config file:
The error trace:
I've tried adding a multimodal module, as shown in the Berlin, multimodal example :
However this results in:
Exception in thread "main" java.lang.RuntimeException: Unmaterialized config group: multimodal
Any guidance much appreciated!