documentation: mention that ParaView (Windows) and VisIt (all platforms) can't read BP5 files about openpmd-api HOT 5 OPEN

FYI, there is planned support for BP5 on Windows in ADIOS2 v2.10, which is going to be released ahead of schedule for this reason.
Given that BP4 and BP5 both exist (and BP5 is not going to fully replace BP4), it is better to use the new filename extensions .bp4 and .bp5 now to avoid confusion, and also to potentially override the default file engine in ADIOS2.

Documentation-wise it's maybe generally a good time now to update some hints on ADIOS2 file engines and their use.

from openpmd-api.

To clarify, will openPMD select the right engine automatically if I give it a filename with .bp4 extension? That would certainly solve my current issues.

Yep, .bp4 and .bp5 will explicitly select those ADIOS2 engines, while .bp will use whatever default ADIOS2 thinks should be used.

from openpmd-api.

This issue can be demonstrated with the test data attached to #1572.

from openpmd-api.

Also, it looks like ADIOS2 itself can't be compiled with BP5 support on Windows.

from openpmd-api.

To clarify, will openPMD select the right engine automatically if I give it a filename with .bp4 extension? That would certainly solve my current issues.

from openpmd-api.