Dynamic Visualization Store
Last update: 16.07.2025API for high-performance postprocessing visualization. More...
Detailed Description
API for high-performance postprocessing visualization.
The Dynamic Visualization Store (DVS) API is a parallel capable, high performance API for postprocessing data. This can be used to implement one API in a solver to send data to a postprocessor in parallel (in this case EnSight) while the solver is running
High Level Features:
- In-situ investigation of data from solver while solver is running.
- Auto reconnect if postprocessor is shutdown and restarted during simulation.
- Scalable design allows for distrubuted parallel solver <-> distributed parallel postprocessor if needed (not required).
- Data can be cached if needed. Adding sources behind the API so no change to solver code.
- Does not need postprocessor to be running to cache data
- Read API to interrogate caches.
- Out of the box C/C++/Python APIs for Windows/Linux
Topics | |
| Changelog | |
| The changelog for each DVS release. | |
| Current Limitations | |
| A list of limitations for each DVS release. | |
| Get DVS | |
| How to get the DVS libraries. | |
| Available APIs | |
| A list of all the APIs available in DVS | |
| Getting started | |
| Instructions and examples to get started with DVS | |
| DVS URIs | |
| Description of various URIs used within the DVS project. | |
| DVS Files | |
| Description of DVS files used to load datasets created by the DVS project. | |
| DVS Filtering | |
| Description of filtering of data within the DVS project. | |
| DVS Cache | |
| DVS Cache can be used to store postprocessing data. | |
| DVS Features | |
| Description of various features of the DVS API. | |
| DVS Reader | |
| DVS Reader API can be used to read data from a cache. | |
| DVS Data Model | |
| Description of the DVS Data Model. | |
| DVS Metadata | |
| Description of supported metadata for the DVS API. | |
| DVS Server | |
| DVS Server used to receive data from DVS Clients. | |
