~We currently do an error-check if users accidentally touched an Iteration that is currently closed. It seems like we'll need to stop doing that as it leads to O(n^2) runtime where n is the number of Iterations~ The check is still needed even in the regular logic, so the alternative was to make it more performant by tracking this information from the beginning.
~We currently do an error-check if users accidentally touched an Iteration that is currently closed. It seems like we'll need to stop doing that as it leads to O(n^2) runtime where n is the number of Iterations~ The check is still needed even in the regular logic, so the alternative was to make it more performant by tracking this information from the beginning.
Fix: Clear dirty files after flushing in ADIOS2
cc @ax3l