2013
DOI: 10.1117/12.2005335
|View full text |Cite
|
Sign up to set email alerts
|

Real-time volume rendering of digital medical images on an iOS device

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
7
0

Year Published

2014
2014
2017
2017

Publication Types

Select...
3
3

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…It was impossible to compare this method with others because no other real-time mobile volume raycaster that support 3D and 4D data could be found after an exhaustive literature search. Therefore, the results of this research were compared, when possible, with an fMRI desktop implementation [41] similar to this work as well as a previous iPad volume renderer using orthogonal texture slicing instead of raycasting [38]. The data initialization times were 16.4 and 29.8 s with dataset 1 and 18.1 and 47.8 for dataset 2 using two different implementations for storing the volume data ( Table 1).…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…It was impossible to compare this method with others because no other real-time mobile volume raycaster that support 3D and 4D data could be found after an exhaustive literature search. Therefore, the results of this research were compared, when possible, with an fMRI desktop implementation [41] similar to this work as well as a previous iPad volume renderer using orthogonal texture slicing instead of raycasting [38]. The data initialization times were 16.4 and 29.8 s with dataset 1 and 18.1 and 47.8 for dataset 2 using two different implementations for storing the volume data ( Table 1).…”
Section: Discussionmentioning
confidence: 99%
“…To date, there has not been a successful real-time volume raycasting implementation for mobile devices. Achieving real-time volume rendering has required using a less computationally expensive method, such as orthogonal texture slicing [38]. The only available application for visualizing fMRI data in 3D on a mobile device is NeuroPub [39], an application for Apple's iOS platform.…”
Section: Mobile Raycastingmentioning
confidence: 99%
“…The improved frame rates are expected with a 2.6GHz Intel Core i7 processor, 16 GB of RAM, and a NVIDIA GeForce GT 750M graphics card. The comparison iPad application used orthogonal texture slicing and a similar dataset of 256 x 256 pixels per slice and 128 slices and saw frame rates between 114 45-50 fps for the structural static condition[163]. The improved frame rates can largely be attributed to the use of a less computationally expensive orthogonal texture slicing algorithm, even running on an iPad 2.When increasing the sampling step size to twice the width of a single voxel, the frame rates increased as expected.…”
mentioning
confidence: 72%
“…It is impossible to compare this method with others, because there currently is no real-time volume raycaster that support 3D and 4D data. Therefore, the results of this research were compared, when possible, with a fMRI desktop implementation [183] similar to this work as well as a previous iPad volume renderer using orthogonal texture slicing instead of raycasting [163].…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation