pvsm used to load data set with fewer timesteps has original higher number of time steps
If you create a pvsm file for a time sequence of .vts (and probably other formats) files. myfile-0.vts, myfile-1.vts, etc.. Then load that pvsm and point to a different time sequence, with fewer files/timesteps, the original number of time steps is maintained and the original files from the pvsm are pointed to for higher number time steps. This is somewhat annoying and there are workarounds, but it seems that the pvsm is storing more data than necessary and expecting a specific number of timesteps creating distrust in the process of applying a paraview pipeline to another timeseries dataset using the pvsm mechanism. @utkarsh.ayachit @cory.quammen
Edited by John Patchett