Unfortunately, this has not been implemented. I am not sure what nooj is referring to. Unless I missed some contribution somehow...
Ah, I misunderstood the request. If you are developing your own reader, wouldn't it better for you to add native time support? There can be many ways of encoding time (and date) into a filename and I don't think adding support to the file series code for this is the right thing to do. I'd be happy to provide some help on creating a custom version of the file series reader for example.
I am not sure that this is the best way of adding support for time values. We have plans to extend XML based meta-files (.pvd) to support legacy VTK files. Pvd already has support for time values.
Which version of ParaView are you using?
As of 3.8, you should see performance improvement when reading EnSight or OpenFOAM files.
Can you provide some example datasets and also example use cases? Which filters you use etc...
If I understand this request correctly, it is not easy to implement. It would somehow require separating processing related to the mesh from the processing related to the variables. For example, a slice filter does not have to recompute its output geometry but it has to copy the new variables to.
In my experience, the biggest bottleneck with such problems is reloading of the geometry. Would you rather we focus on developing readers that supported static meshes?
This is definitely a bug. I submitted a report with the tracker with id 10125
2 votesAdminberk.geveci (Admin, paraview) shared this idea ·