When running a post-processing calculation with a large number of load cases (usually in the thousands), Bladed can fail with "Program terminated unexpectedly" error message. This is caused by a memory limitation.
Versions of Bladed affected: All versions
Article last updated: 23 May 2023
The way to solve this is to split up the post-processing run into subsets of load cases. This is fairly straighforward for most types of post-processing calculation but does present a problem for Rainflow cycle counting. This is because Bladed would not be able to provide meaningful values for the "Sum over lifetime" and "Damage equivalent loads" in these cases. You would then have to use Excel (for instance) to perform the last stage of the calculation outside Bladed. A worked example package guiding you through this process can be found at this link.