> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/current-peer-reviewed-immersive-technologies/cave-an-emerging-immersive-technology-a-review.md). # CAVE: An Emerging Immersive Technology - A Review Currently, the CAVE (Cave Automatic Virtual Environment) systems are one of the best virtual reality (VR) immersive devices available for portraying the virtual environment. ## Overview **Authors:** Siddhesh Manjrekar, Shubhrika Sandilya, Deesha Bhosale, Sravanthi Kanchi, Adwait Pitkar, Mayur Gondhalekar **Publication Date:** 23 February 2015 **Link:** [https://ieeexplore.ieee.org/abstract/document/7046051]() **Keywords:** CAVE, CAVE 2, Immersive Virtual Reality, Tracking System, Versions of CAVE, Applications of CAVE **Type:** Peer-Reviewed Journals/White Papers ## Summary Currently, the CAVE (Cave Automatic Virtual Environment) systems are one of the best virtual reality (VR) immersive devices available for portraying the virtual environment. The CAVE gives the illusion of being surrounded by a fictional world, providing a fully interactive, scientific visualization. The CAVE systems can provide a completely new dimension to scientific experimentation as well as entertainment. At the same time, the CAVE systems are a work-in-progress, with CAVE2 having improvements to reduce the complexity, high costs, and cumbersome hardware required by the original CAVE systems. In this paper, we give a system overview of the CAVE systems, its applications and enhancements. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://library.xrguild.org/current-peer-reviewed-immersive-technologies/cave-an-emerging-immersive-technology-a-review.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.