In computational fluid dynamics, visualization is a frequently used tool for data evaluation, understanding of flow characteristics, and qualitative comparison with flow visualizations originating from experiments. Building on an existing visualization software system that allows for a careful selection of state-of-the-art visualization techniques and some extensions, it became possible to present various features of the data in a single image. The visualization shows vortex position and rotation as well as skin-friction lines, experimental oil-flow traces, shock-wave positions, and time surfaces. Animation provides a natural perception of flow in combination with an abstract representation of phenomena. By adding experimental flow visualization, a comparison between numerical simulation and wind-tunnel flow becomes possible up to a high level of detail. Since some of the underlying algorithms are not yet described in detail in the visualization literature, some experiences gained from the implementation are illustrated. The dedicated techniques which are illustrated in this paper address specific properties of vector quantities in the flow field, such as the velocity vector or the friction vector. Image complexity is reduced by employing complex visualization methods. Thus, the room is created which is necessary to study the interaction of various phenomena.>

In computational fluid dynamics visualization is a frequently used tool for data evaluation, understanding of flow characteristics, and qualitative comparison to flow visualizations originating from experiments. Building on an existing visualization software system, that allows for a careful selection of state-of-the-art visualization techniques and some extensions, it became possible to present various features of the data in a single image. The visualizations show vortex position and rotation as well as skin-friction lines, experimental oil-flow traces, and shock-wave positions. By adding experimental flow visualization a comparison between numerical simulation and wind-tunnel flow becomes possible up to a high level of detail. Since some of the underlying algorithms are not yet described in detail in the visualization literature, some experiences gained from the implementation are illustrated.>

Abstract Several feasibility studies for cooperative visualization were performed based on an existing modular visualization system. Two different architectures for the implementation of a cooperative system were identified, implemented and tested. One architectural model, the broadcast model, assumes either one single visualization system running on a central facility driving multiple displays or in case of cooperative work it assumes that each visualization module drives multiple displays. The second model, the synchronized visualization systems, features distributed visualization tools with synchronization mechanisms. The synchronization ensures that all partners create identical images from identical data. This model requires special control features to avoid conflicts created by user‐interaction. Both architectures are complete by adding bi‐directional video connection and audio communication over the network plus offering remote cursor functionality. Two prototype implementations were produced to compare the two architectures and to evaluate the feasibility of cooperative visualization on existing hardware. Because of the poor access to wide‐area networks, the prototypes were tested in a local area network. Visualization protocols, data communication, video and audio ran on a standard Ethernet based on TCP/IP communications. The tests were done using typical data from aerodynamics or numerical flow simulations. In spite of the limits due to low network bandwidth and slow performance of some hardware components the second architecture using the synchronized systems seems to be useful and feasible even under today's circumstances. There are no additional features identified which would be needed to run the cooperative visualization on a wide area network but a higher network throughput would be required.