openfoam reader fails with uncollated lagrangian data
The reader seems to have been written on the assumption that any lagrangian data are available on all processor sub-directories. It uses a central naming mechanism accordingly. However, OpenFOAM can generate data sets in which lagrangian data are only available on a subset of processors.
The current logic means that missing lagrangian data will scan as zero clouds (the last result) instead of retaining what had been scanned until that point.