You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In spite of the RawBinaryCompressed mode, my vtu files are still way too large to transfer over the internet. I would like to find a good way to compress them even more.
My code does use single precision and I wander if it would be possible to use single precision within the files (instead of doubles). Would this cause problems with Paraview?
The text was updated successfully, but these errors were encountered:
If you have a lot of data there might only be so much you can do to reduce the file size. Make sure you have zlib enabled since RawBinaryCompressed otherwise silently forwards to RawBinary (see this line). Then, you can choose smaller data types as you already mentioned. Single precision is one option, but a significant amount of data might come from the mesh data structure for which you may be able to choose smaller integer types. Generally paraview shouldn't have issues with that, although I had problems with unsigned integer types in the past. Lastly, you might get a few additional percentages by packaging your (already compressed) files into a compressed archive before sending them over a network.
If that doesn't help you probably have to find a different solution. If you cannot reduce the amount of data, postprocessing on the remote machine may be the only option left. Paraview allows you to start a server on the remote machine and connect to it with your local client (see here). Alternatively, you could script your postprocessing on the remote machine and only transfer the images and videos.
In spite of the RawBinaryCompressed mode, my vtu files are still way too large to transfer over the internet. I would like to find a good way to compress them even more.
My code does use single precision and I wander if it would be possible to use single precision within the files (instead of doubles). Would this cause problems with Paraview?
The text was updated successfully, but these errors were encountered: