Open biglimp opened 4 days ago
Just to update. A new run was done and now it came further but stopped, at a grid when the db-file ate up the harddrive memory (myDbH21732916050_978621.mv.db = 75Gb). What was interesting with this run was that it came through one problem-grid where it stopped before (maybe because I removed files and increased my harddrive space).
There was two issues:
Thus it results in a domain too big along the vertical axis. I have now found the bug but I have no time this week to resolve. An option could be to remove these zones for now (I do not think it affects much the results on the ground).
Great that you found the bugs. No hurry. Let us know when you fixed so that we can try again.
If needed, here is the code without rooftop corner: https://github.com/UMEP-dev/UMEP-processing/tree/URock_noroofcorner
We are running Urock in a loop in order to estimate wind speed for a whole city (Malmö, Sweden). Some grids is done very fast but then it gets stuck in one grid. Files attached. What I can see is that a .db file gets bigger and bigger until it has eaten up my entire harddrive which creates an memory error in a Java process.
@j3r3m1 , any idea what is going on? To me it seems like the process is in a infinite loop.
veg_urock73.zip
Here is the settings used:
Here are the log print out:
Here is a detailed error message from VSCode when memory is full: