2017
DOI: 10.1109/tvcg.2016.2599043
|View full text |Cite
|
Sign up to set email alerts
|

A Versatile and Efficient GPU Data Structure for Spatial Indexing

Abstract: Fig. 1. Many real-world volume data sets are sparse, lending appeal to rendering and processing techniques that benefit from such a property. Using our novel, storage-efficient data structure allows us to efficiently store such data sets as bricked textures on the GPU. From left to right: Stagbeetle (832 × 832 × 494, bricksize 7 3 , 5.01% non-empty, 245.5KB index); Pawpawsaurus Campbelli skull (958 × 646 × 1088, bricksize 15 3 , 15.1% non-empty, 50.21KB index); Angiography (416 × 512 × 112, bricksize 3 3 , 2.2… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 10 publications
(8 citation statements)
references
References 16 publications
(19 reference statements)
0
7
0
Order By: Relevance
“…An extensive body of work has embarked on the redesign of data structures for construction and general computation on the GPU [88]. Within the context of searching, these acceleration structures include sorted arrays [3], [4], [8], [51], [66], [67], [98] and linked lists [116], hash tables (see section III), spatial-partitioning trees (e.g., k-d trees [57], [115], [120], octrees [57], [119], bounding volume hierarchies (BVH) [57], [64], R-trees [71], and binary indexing trees [59], [99]), spatial-partitioning grids (e.g., uniform [36], [53], [62] and two-level [52]), skiplists [81], and queues (e.g., binary heap priority [43] and FIFO [17], [101]). Due to significant architectural differences between the CPU and GPU, search structures cannot simply be "ported" from the CPU to the GPU and maintain optimal performance.…”
Section: Gpu Searchingmentioning
confidence: 99%
See 1 more Smart Citation
“…An extensive body of work has embarked on the redesign of data structures for construction and general computation on the GPU [88]. Within the context of searching, these acceleration structures include sorted arrays [3], [4], [8], [51], [66], [67], [98] and linked lists [116], hash tables (see section III), spatial-partitioning trees (e.g., k-d trees [57], [115], [120], octrees [57], [119], bounding volume hierarchies (BVH) [57], [64], R-trees [71], and binary indexing trees [59], [99]), spatial-partitioning grids (e.g., uniform [36], [53], [62] and two-level [52]), skiplists [81], and queues (e.g., binary heap priority [43] and FIFO [17], [101]). Due to significant architectural differences between the CPU and GPU, search structures cannot simply be "ported" from the CPU to the GPU and maintain optimal performance.…”
Section: Gpu Searchingmentioning
confidence: 99%
“…Schneider and Rautek [99] denote sparsity encoding as a memory overhead cost for providing unconstrained access, or empty cell querying, in the spatial perfect hashing approach of Lefebvre et al [65]. This study proposes a compact, GPU-based Fenwick tree data structure that supports unconstrained accesses without additional occupancy storage to denote empty cells.…”
Section: B Perfect Hashingmentioning
confidence: 99%
“…be achieved by means of min-max range queries [WFKH07, KTW * 11, Wal19]. An alternative approach to update an existing data structure is the one by Schneider et al [SR17] who use Fenwick trees, which bare similarities to the summed area tables that our techniques use as auxiliary data structures.…”
Section: Related Workmentioning
confidence: 99%
“…Alternative SVT representations such as 3D Fenwick trees [Fen94,Mis13,SR17] offer a memory-efficient intermediate data structure from which an adaptive space partition can be constructed. 3D Fenwick trees have a memory consumption of O(n) bits, yet recovering the integral values requires a number of O(log 3 n) data fetch operations.…”
Section: Introductionmentioning
confidence: 99%