-
Notifications
You must be signed in to change notification settings - Fork 52
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
Task timeSeriesSeaIceAreaVol appears to have trouble dealing with data beyond a certain length #981
Comments
@wlin7, thanks for reporting this. I'm sorry your having trouble with MPAS-Analysis. I will take a look tomorrow. The error you're seeing may indeed indicate that a process was killed with an out-of-memory issue (perhaps not |
@xylar , thank you for looking into the problem. Make sense it is an out-of-memory issue., which could be during some later step of the task. The |
@wlin7, I'm just now getting around to investigating this issue. I had to try to clean up some space because From the logs of individual tasks, it does look like |
Yes, I can reproduce the problem. It is that we are trying to load a 59 GB data set and then operate on it. I will fix this as soon as I can, hopefully tomorrow. I will also hopefully have a test deployment of e3sm-unified 1.9.3rc1 for you to to see if the fix works by tomorrow. Today, I have 4 hours of meetings starting soon so I won't be able to make a lot of headway. |
@xylar , great you have isolated the problem. Thanks a lot. While we definitely need this fix, there is no hurry for that for the current piControl-spinup. I also use shorter time series (a latter anomaly reference year) to better display the trend in latest simulation period. So please take your time. |
Thanks @wlin7. It's helpful to know that this bug isn't keeping you from making immediate progress. That should give me time to fix the problem in a better way, rather than just trying to do it quickly. |
mpas-analysis for v3.LR.piControl-spinup failed to complete if including the full time series that are longer than around 1350 years. The problem started with the generation of ts_0051-1400_climo_1351-1400, with the following error message
The generation for mpas_analysis_ts_0001-1350_climo_1251-1350 was still fine. Shortening the length with ts_0101-1400_climo_1351-1400 was also fine. However, the same errors would occur for ts_0051-1400_climo_1351-1400.o465258 or ts_0101-1450_climo_1401-1450.o465657.
Full zppy logs the running mpas-analysis for these periods can be viewed at
The text was updated successfully, but these errors were encountered: