Bricken, W., & Coco, G. (1994). The VEOS project. Presence: Teleoperators and Virtual Environments, 1(2), 111--129.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....EM is extensible to include low level code, such as application specific rendering or interface techniques. Many VE application support software systems decompose the VE application into components that can be executed concurrently, perhaps as part of a distributed system. One such system, VEOS (Bricken, 1994), partitions the VE application into self contained entities that have an internal persist behavior and a react behavior that takes action on events identified by its interact behavior. The self contained and hierarchical nature of the entities (entitities can be contained in other ....

Bricken, W., & Coco, G. (1994). The VEOS project. Presence: Teleoperators and Virtual Environments, 1(2), 111--129.

....and optimization algorithms (dead reckoning for NPSNET like systems) Those systems are very efficient for their specific domain but seem difficult to reuse for other applications. Application generic systems compose the second class. Good examples of this class are: DIVE [Carlsson93] VEOS [Bricken93] and AVIARY [West92] Those systems have to be the most generic possible in order to be easily used to design any application. This genericity, however, trades off with the general efficiency of the final application. For example in most of these systems, optimization algorithms are difficult to ....

W. Bricken, G. Coco, "The VEOS Project", Technical report, Human Interface Technology Lab, University of Washington, 1993.

....chunks representing objects and methods. Chunks may be grouped and maintained in distributed databases. Groups are connected by specialised chunks and may be exchanged from host to host. Modification of chunks is allowed only to the current chunk owner. VEOS (Virtual Environment Operating Shell) [Bric94] has a special focus on rapid prototyping, portability, and distributed computing. The VEOS kernel is composed of three components: SHELL is responsible for process initialisation, memory allocation and scheduling of computing time. TALK coordinates the inter process communication via unicast. ....

W. Bricken and G. Coca. "The VEOS Project." Presence, 3 (2): 111-129, Spring 1994.

....EM is extensible to include low level code, such as application specific rendering or interface techniques. Many VE application support software systems decompose the VE application into components that can be executed concurrently, perhaps as part of a distributed system. One such system, VEOS (Bricken, 1994), partitions the VE application into self contained entities which have an internal persist behavior, and a react behavior that takes action on events identified by its interact behavior. The self contained and hierarchical nature of the entities (entities can be contained in other ....

Bricken, W. and Coco, G. (1994). The VEOS Project. Presence, 1 (2), pp. 111-129.

....after the position update. Systems that provide sharing of behavior information about geometric objects and other users do not address the problem of reducing the workload of user task processes, as these processes must simulate the behavior of remote objects. On the other hand, the VEOS system [5] provides a framework for distributing task processes that maintain independent entities of a VE application, usually geometric elements of the environment. The VEOS system supports communication between entity processes using a Linda like communication structure, where information can include ....

Bricken, W. and Coco, G. The VEOS Project. Presence, 1(2), 1994, pp. 111-129.

....we will describe the most important systems. 5.2 State of the art in NVEs VEOS VEOS (Virtual Environment Operating Shell) developed by the University of Washington, was one of the first complete NVE architectures to provide an integrated software to develop general applications. VEOS [ 33 ] uses tightly integrated computing model for management of data, processes, and communication in the operating system level, hiding details from the applications as much as possible. dVS dVS, developed by Division Ltd in UK [34] is one of the commonly used VE commercial development tools ....

....locations and offices. However, it surely saves time and money for organizations. Network VR simulations could enable people in many different locations to participate together in teleconferences, virtual surgical operations, teleshopping (Figure 13) or simulated military training exercises. 33 Entertainment This is the area which starts to drive the development of VR technology. The biggest limiting factor in VR research today is the sheer expense of the technology. It is expensive because the volumes are low. For entertainment, mass production is required. Another alternative is the ....

Bricken W, Coco G (1993) The VEOS Project, Technical Report R-93-3, Human Interface Technology Laboratory, University of Washington.

....to the user. 2. Preconditions of NVEs 2.1 Target Applications There have been a number of pilot or working applications constructed in the literature. Although the theoretical approach of the early systems tried to provide a generalpurpose virtual environment for any type of application (Bricken and Coco 1993), it was later realized that these systems lack efficiency, one of the principal requirements for NVE systems. Recent efforts concentrated on characterizing applications for different dimensions. Slater et al. 1995) proposed three such dimensions: 1) the number of participants and entities ....

Bricken W., Coco G. (1993) The VEOS Project, Technical Report R-93-3, Human Interface Technology Laboratory, University of Washington.

....architectures, limited in capability, difficult to extend, and or available on only a few platforms, if not just one. The most significant of such toolkits include Alice [8] AVIARY [27] BrickNet [26] DIVE [5] dVISE [9] EasyScene [6] MASSIVE [11] NPSNET [13] Vega[20] MR Toolkit [10] VEOS [3], and World Toolkit [24] The architecture described in this paper, Bamboo, is the result of years of trying to develop the right toolkit for the research and development of networked VEs. Historical observation suggests that no single toolkit can hope to address all user needs, while modern ....

Bricken, W. and G. Coco (1994). "The VEOS Project." Presence 3(2): 111-129.

....mimic many aspects of operating systems. For example, the now defunct system developed by the Human Interface Technology Laboratory, Virtual Environment Operating Shell (VEOS) provided much of the functionality of a distributed operating system in the way of programming language services [16,6]. However, we are primarily concerned with a single application and not a general purpose computing environment. Therefore, the most important questions about virtual environment software architectures we address here are: What is distributed . What are the modalities of the distribution . Why ....

Bricken, William and Coco, Geoffrey, "The Veos Project", ftp.u.washington.edu:/public/VirtualReality/HITL/ papers/tech-reports/Veos_Project.ps, 1993.

....mimic many aspects of operating systems. For example, the now defunct system developed by the Human Interface Technology Laboratory, Virtual Environment Operating Shell (VEOS) provided much of the functionality of a distributed operating system in the way of programming language services [79,21]. However, we are primarily concerned with a single application and not a general purpose computing envi 11 ronment. Therefore, the most important questions about virtual environment software architectures we address here are: What is distributed . What are the modalities of the ....

Bricken, William and Coco, Geoffrey, "The Veos Project", ftp.u.washington.edu:/public/ VirtualReality/HITL/papers/tech-reports/Veos_Project.ps, 1993.

....video using existing Web facilities. 15 Various research works toward Virtual Environments and Virtual Reality have already produced a number of software packages, architectures, and operating systems. Two examples are as follows: i) The VEOS (Virtual Environment Operating Shell) project [10], which is a management facility for generation of, interaction with and maintenance of virtual environments. An early demonstration in a blocks world allowed four participants to independently navigate and manipulate movable objects in a shared virtual space. ii) The work of [30] allows informal ....

W. Bricken and G. Coco, "The VEOS Project", Technical Report, Tech Report R-93-3, Univ. of Washington, 1993.

.... The most significant of such toolkits include Alice (Deline, 1993) AVIARY (Snowdon, 1994) BrickNet (Singh, 1994) DIVE (Carlsson, 1993) dVS (Division, 1998) EasyScene (Coryphaeus, 1998) MASSIVE (Greenhalgh, 1995) MR Toolkit (Shaw, 1993) NPSNET (Macedonia, 1994) Vega (Paradigm, 1998) VEOS (Bricken, 1994), and World Toolkit (Sense8, 1998) Another general failing of distributed VEs is that the networking solutions tend to lack flexibility. Historically, for lack of better methods, a single, all encompassing, highly enumerated, networking protocol, such as DIS (IEEE, 1993) would be utilized. ....

Bricken, W. and G. Coco (1994). "The VEOS Project." Presence 3(2): 111-129.

No context found.

Bricken W., Coco G., "The VEOS Project", Technical report, Human Interface Technology Lab, University of Washington, 1993.

No context found.

Bricken, W., and Coco, G., [1993], "The VEOS Project", technical report from the Human Interface Technology Laboratory, University of Washington FJ-15, Seattle 98195.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC