2018 IEEE 8th Symposium on Large Data Analysis and Visualization (LDAV) 2018
DOI: 10.1109/ldav.2018.8739204
|View full text |Cite
|
Sign up to set email alerts
|

VOIDGA: A View-Approximation Oriented Image Database Generation Approach

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
3
2
1

Relationship

3
3

Authors

Journals

citations
Cited by 8 publications
(11 citation statements)
references
References 37 publications
0
11
0
Order By: Relevance
“…To facilitate practically usability, it appears possible to introduce automation of parameters (such as number of persistence intervals or camera angles stored) through heuristics or optimization techniques, to keep the generated database within a given budget while maximizing post hoc flexibility, or alternatively, to ensure a specified degree of flexibility while minimizing database size. For example, the integration of the VOIDGA approach [18] could reduce the number of stored camera locations, which would allow to sample other parameters more densely. Finally, database generation could benefit from low-level technical improvements, such as different compression methods and data formats.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…To facilitate practically usability, it appears possible to introduce automation of parameters (such as number of persistence intervals or camera angles stored) through heuristics or optimization techniques, to keep the generated database within a given budget while maximizing post hoc flexibility, or alternatively, to ensure a specified degree of flexibility while minimizing database size. For example, the integration of the VOIDGA approach [18] could reduce the number of stored camera locations, which would allow to sample other parameters more densely. Finally, database generation could benefit from low-level technical improvements, such as different compression methods and data formats.…”
Section: Discussionmentioning
confidence: 99%
“…Originally, these databases are structured image collections that enable the interactive post hoc visual analysis of extreme-scale simulations by simply browsing images that have been stored in situ for a fixed sampling of the parameter space. The current specification [25] supports any kind of data product; in particular depth images that can be used to composite 3D renderings of the scene post hoc [18]. Biedert et al [4] also investigated the Cinema-inspired idea of combining in situ topological analysis and simplification with compact image-based storage in socalled contour tree depth images, which record at each pixel the list of depth values of individual contours from front to back.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…A Cinema database [2] is a large collection of images which are sampled based on time, visualization object and camera position, and stored along with metadata that allows interactive querying [25]. Cinema is used with image processing techniques to combine images to obtain new camera and time locations or even to reconstruct the original object using Depth Image Based Rendering [19]. Cinema has been implemented in ParaView as well as the open source Topology Toolkit TTK [30].…”
Section: The Cinema In Situ Databasementioning
confidence: 99%
“…After single contour extraction in situ, the first stage is complete, and we save depth images from varying camera positions for later reconstruction [19] based on a TTK [30] implementation in order to avoid saving large meshes of millions of triangles.…”
Section: Cinema Integrationmentioning
confidence: 99%