When moving or scaling the dataset, the interaction is flawlessly smooth. However, stepping through the time series is quite slow, about 1 step/sec, even with geometry caching enabled.
Looking at the timer log, I see the task causing the slowdown is ‘FullRes Data Migration’, taking over half a second every time step. When running locally, I don’t see this step happening and the steps take much less time (~0.01 sec in the timer log after cached).
Any help speeding up this animation would be much appreciated!
Some basic info about my current set up:
35 x “worker” nodes with 16-core Intel Xeon CPU, 2 NVIDIA GTX 1080s, 64 Gb RAM
1 x “master” node, same system config
70 x 4K LG 3D TVs, arranged around a sphere (70 unique viewports)
40 Gbps network between nodes
70 pvserver instances (2 per node, 1 per screen)
data mounted from NFS but i have also tried copying to each node with same result - its not much data… yet
This is indeed a limitation of the current implementation. In the current implementation, the geometry caching is done at the wrong end – it’s cached on the data processing side and not on the rendering side. For CAVE, we clone data i.e. all geometry from all ranks is duplicated for each tile so that interactive rendering can happen without data movement. However, since the caching for temporal data happens on the data processing side, the data movement has to happen when timestep is changed.
It’s fixable, but would need some development to move the caching location.
status update: I’m making progress. I still need a few more days to make the changes merge ready but things so far are looking promising. Here’s a comparision between 5.6 and paraview with my changes, both using animation caching.
This work looks amazing!
I am currently trying to display an animation in VR-ParaView using HTC-VIVE, but still could not find the option…
Is that what you guys are working on? If so, when are you plan to release it?
If not, do you guys have any idea whats going on with that?
and thank you for your answer.
If I understand correctly no one was able to hit play and actually watch the animation through the goggles using OpenVR, Is that right? Is that a question of libraries? Will use older versions change something?
The only work around I have found (that is not actually a solution) is to move forward one step at a time by clicking with the mouse. Is there any workaround to this issue?
yup, the fix for that is under development here. For a quick fix, just apply this change to VTK and it should overcome this issue. The commit had to be reverted due to some other issues. The MR under development attempts to fix it properly on ParaView side itself.