Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Visualization (graphics)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Rapid response to human input=== Experiments have shown that a delay of more than 20 [[Millisecond|ms]] between when input is provided and a visual representation is updated is noticeable by most people {{Citation needed|date=May 2015}}. Thus it is desirable for an interactive visualization to provide a [[Rendering (computer graphics)|render]]ing based on human input within this time frame. However, when large amounts of data must be processed to create a visualization, this becomes hard or even impossible with current technology. Thus the term "interactive visualization" is usually applied to systems that provide feedback to users within several seconds of input. The term ''interactive [[framerate]]'' is often used to measure how interactive a visualization is. Framerates measure the frequency with which an image (a frame) can be generated by a visualization system. A framerate of 50 frames per second (frame/s) is considered good while 0.1 frame/s would be considered poor. The use of framerates to characterize interactivity is slightly misleading however, since framerate is a measure of [[Bandwidth (computing)|bandwidth]] while humans are more sensitive to [[Latency (engineering)|latency]]. Specifically, it is possible to achieve a good framerate of 50 frame/s but if the images generated refer to changes to the visualization that a person made more than 1 second ago, it will not feel interactive to a person. The rapid response time required for interactive visualization is a difficult constraint to meet and there are several approaches that have been explored to provide people with rapid visual feedback based on their input. Some include #''[[Parallel rendering]]'' β where more than one computer or video card is used simultaneously to render an image. Multiple frames can be rendered at the same time by different computers and the results transferred over the network for display on a single [[computer monitor|monitor]]. This requires each computer to hold a copy of all the information to be rendered and increases bandwidth, but also increases latency. Also, each computer can render a different region of a single frame and send the results over a network for display. This again requires each computer to hold all of the data and can lead to a load imbalance when one computer is responsible for rendering a region of the screen with more information than other computers. Finally, each computer can render an entire frame containing a subset of the information. The resulting images plus the associated [[depth buffer]] can then be sent across the network and merged with the images from other computers. The result is a single frame containing all the information to be rendered, even though no single computer's memory held all of the information. This is called ''parallel depth compositing'' and is used when large amounts of information must be rendered interactively. #''Progressive rendering'' β where a framerate is guaranteed by rendering some subset of the information to be presented and providing incremental (progressive) improvements to the rendering once the visualization is no longer changing. #''Level-of-detail ([[Level of detail (computer graphics)|LOD]]) rendering'' β where simplified representations of information are rendered to achieve a desired framerate while a person is providing input and then the full representation is used to generate a still image once the person is through manipulating the visualization. One common variant of LOD rendering is ''[[Chroma subsampling|subsampling]].'' When the information being represented is stored in a [[Topology|topologically]] rectangular array (as is common with [[digital photo]]s, [[MRI scan]]s, and [[finite difference]] simulations), a lower resolution version can easily be generated by skipping ''n'' points for each 1 point rendered. Subsampling can also be used to accelerate rendering techniques such as volume visualization that require more than twice the computations for an image twice the size. By rendering a smaller image and then [[image scaling|scaling]] the image to fill the requested screen space, much less time is required to render the same data. #''Frameless rendering'' β where the visualization is no longer presented as a time series of images, but as a single image where different regions are updated over time.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)