Hi Kristen,
Thanks for the detailed and comprehensive answer!
After reviewing the release notes and bug fixes, I ended up migrating to v5.5. But I’m glad to hear that v5.4 will still provide valid ISAM results.
Btw, I noticed that my ISAM run’s memory usage jumped on the 2nd simulation day by about 15%. I periodically checked the memory usage (using the Linux “free” command) while running the simulation, and this plot shows the result:
The only difference between the first and subsequent simulation days is that the first-day simulation is a new start (from an ICON input) and the subsequent days are re-started from previous day’s CGRID outputs, and I wonder why that would require additional memory space. Can you or anyone (@Ben_Murphy, @sergey, @hogrefe.christian) shed light on this?