VRG3D Requirements: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== High-level goals == | == High-level goals == | ||
# Let new users get started in a few minutes through online documentation | # Let new users get started in a few minutes through online documentation | ||
## Implementation idea: regular diagnostics at the hardware and support-library levels to minimize undetected failures that block users (this needs rephrasing and possibly division into multiple requirements) | |||
# Create rich immersive virtual worlds with high update rates and low-latency | # Create rich immersive virtual worlds with high update rates and low-latency | ||
# Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles. | # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles. | ||
| Line 6: | Line 7: | ||
# Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.) | # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.) | ||
# Interoperate (to some degree) with geometry and color calibration system | # Interoperate (to some degree) with geometry and color calibration system | ||
# Easy to make applications run on other universities systems (dhl: maybe implies small dependencies) | # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies) | ||
## implementation idea: binaries and as source code (what is plan for data distribution?) | |||
# A simulator (probably inside VRG3D) | # A simulator (probably inside VRG3D) | ||
# | # Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” | ||
## implementation idea: provide support for regular testing of applications to minimize code rot | |||
# Need a scripting interface (e.g., for testing without all hardware available, sharing, "slowing down time", etc.) | # Need a scripting interface (e.g., for testing without all hardware available, sharing, "slowing down time", etc.) | ||
# Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?) | # Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?) | ||
Revision as of 19:42, 15 January 2010
High-level goals
- Let new users get started in a few minutes through online documentation
- Implementation idea: regular diagnostics at the hardware and support-library levels to minimize undetected failures that block users (this needs rephrasing and possibly division into multiple requirements)
- Create rich immersive virtual worlds with high update rates and low-latency
- Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.
- Desktop debugging and development environment (so you can run it without a Cave)
- Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)
- Interoperate (to some degree) with geometry and color calibration system
- Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)
- implementation idea: binaries and as source code (what is plan for data distribution?)
- A simulator (probably inside VRG3D)
- Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos”
- implementation idea: provide support for regular testing of applications to minimize code rot
- Need a scripting interface (e.g., for testing without all hardware available, sharing, "slowing down time", etc.)
- Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?)
VRG3D Requirements
- documentation
- "make doc" makes doxygen style documentation
- it's possible to make introduction page...
- examples
- lowest-level events
- have short-term milestones & then get guinea pigs to test it (is it actually easy to use?)
- synching
- interaction
- 3D graphics
- multiple displays
- multiple OS's
- testability
- "ease-of-use"
- code repository & code access