Further workaround for #1655: Avoid hangup automatically when using writeIterations()

[franzpoeschel]

When using writeIterations(), the currently active Iteration should be flushed regardless if it is dirty (unless it has been closed).

#1655, @guj

[guj]

originally writeIterations()[timestep] was created to serve for adios streaming steps. The file based write iterations were still using series->iterations[timestep]. As we discussed yesterday, sounds like the distinction is not there anymore. I just want to double check. An iteration will either be from writeIterations() or readIterations()?

[guj]

By the way, thanks for putting the test in.

[ax3l]

Thanks for the fix!

[franzpoeschel]

originally writeIterations()[timestep] was created to serve for adios streaming steps. The file based write iterations were still using series->iterations[timestep]. As we discussed yesterday, sounds like the distinction is not there anymore. I just want to double check. An iteration will either be from writeIterations() or readIterations()?

writeIterations() was always usable both for streaming and file writing, see the documentation:

The writing end of the streaming API enforces further restrictions that become necessary through the nature of streaming. It can be used to write any kind of openPMD-compatible dataset, stream-based and filesystem-based alike.

writeIterations() is necessary to create ADIOS2 output that uses steps; but it never mattered if that output were files or a stream. (Other backends can be used, too, where steps will then just be ignored)

[guj]

Out of curiosity, if I use iterations() instead of writeIterations,
will this fix still work?