-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIPNET swallows all memory when met is missing in the middle of a time series #2156
Comments
An extended Kernel log is available here. |
Does the same apply if you try to run this on the machine (outside of the container)? |
Haven't tried yet, but I'll give it a whirl. |
So the problem here turned out to be that I was missing a year of met (2004, for a run from 1902 to 2008) in the middle of the time series. That apparently tripped up SIPNET. Running 1900 to 2003 worked fine and, profiling via Valgrind, only used about 20-30 MB of RAM. That missing met would kill it this way is insidious. I'm leaving this issue open but changing the name to reflect the real problem. (The missing met was partially user error -- I had already downloaded year 2004 for this site, but because I did it before my land-sea mask fix, it was all |
This issue is stale because it has been open 365 days with no activity. |
This is a SIPNET issue, not a PEcAn issue, so transferring to PecanProject/sipnet#7. |
Describe the bug
Long (multi-decadal) runs of SIPNET can exceed system memory limitations, at least on Docker.
This causes the model run process to be killed by the kernel OOM killer.
In the
logfile
, this just looks like the cryptic error messageKilled
.In the system logs (
log
command on Mac), this looks like:To Reproduce
Run SIPENT (r136) for 100 years.
Expected behavior
The model should run.
Machine (please complete the following information):
The text was updated successfully, but these errors were encountered: