I suggest you ...

Enable caching of (static) meshes for transient data

Following on from:

http://markmail.org/message/b3ro3hvuqqenxyfg

- for transient cases employing static meshes, provide a mechanism to cache the mesh so that it is not necessary to rebuild the complete visualization pipeline

80 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
andy shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Adminberk.geveci (Admin, paraview) commented  ·   ·  Flag as inappropriate

    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?

Feedback and Knowledge Base