Several file formats that do not directly support time allow a series of similarly named files to be treated as a time progression, which is internally implemented with a
FileSeriesReader meta reader object. The
FileSeriesReader naively ignores the name of any file in the list and assigns integer time indices starting at 0.
However, it is common practice to encode the simulation time in the file name. When this happens, ParaView ignores the simulation time, and it can be very challenging to get it back.
FileSeriesReader should check its list of files and see if it follows a pattern that has a common name with a varying number, extract that number from each filename, and use that number for the time value.
It should be possible to turn this feature off (advanced property, default to on).
I bring this up because questions on this discourse regularly come up because ParaView is ignoring the obvious time values in filenames. The most recent one is How can I adjust the starting step of the STL files?, but many others can be found.
Please write up a feature request. Add my username to it, and Sandia will fund it.
With the possibility of creating a
.series file, I’m unsure we want to add complexity to the file series reader.
Wdyt @cory.quammen ?
That’s a fair point, @mwestphal. (It would be better if the
.series reader was actually documented.)
But to argue this point a little bit, while creating a
.series file could usually be generated with something like a clever shell script, doing so is not exactly trivial and is probably beyond the skill level of many scientific ParaView users.
Ken, I’m wondering if your second paragraph is correct. pvd files aren’t that complex, and if .series files were documented well, would be easy to create.