Given by Scott Klasky at BBH Grand Challenge Meeting Austin Texas on November 5-6 1998. Foils prepared Jan 31 99
Outside Index
Summary of Material
Client-server data visualization and analysis system which took full advantage of Java (JDK1.1). |
Purpose: Provide researchers with a customizable data analysis system to aid their research. |
Collaborative Framework: Users can exchange data and their own personalized filters. |
Features: Platform Independent!!!!! 100% Java! |
Animations |
Zooms/Rotations |
Color map editors |
Custom Labels, Ticks |
White Board |
Isosurface |
Contours |
User Definable Filters |
Vector Plots |
Virtual Window Manager |
Outside Index Summary of Material
Ki, Klasky |
Syracuse University, NPAC |
11/6/98 |
Client-server data visualization and analysis system which took full advantage of Java (JDK1.1). |
Purpose: Provide researchers with a customizable data analysis system to aid their research. |
Collaborative Framework: Users can exchange data and their own personalized filters. |
Features: Platform Independent!!!!! 100% Java! |
Animations |
Zooms/Rotations |
Color map editors |
Custom Labels, Ticks |
White Board |
Isosurface |
Contours |
User Definable Filters |
Vector Plots |
Virtual Window Manager |
Scivis is a visualization server. |
Simulations servers connect to Scivis with Pipes.
|
Scivis(server) |
F90 code |
Pipe to Scivis |
java_ser |
calls |
3d Isosurfaces |
A filter is an action which is performed on a data set(s) to create a new data set based on this action. |
We provide an infrastructure for users to create their own filters. |
Filters can be created on-the-fly and can be shared among collaborators. We provide a Wizard to create filter templates. |
Examples:
|
Used Custom Socket Programming. |
Difficult for users to exchange filters, since each user ran their own server. |
Difficult for users to run the Isosurface routine. |
Slow performance for 3D graphics. |
Collaborations with many users would often kill the system. |
We wanted an easy way to incorporate "state-of-the-art" visualization routines (like Stanford's Volpack routines for raytracing, or VTK routines). |
Needed a methodology for creating "maps" of filters, so users could invoke them from C/Fortran/Java. |
Operates on the premise of shared inputs. |
We are developing a scientific visualization system to handle collaborations with large datasets which are common in computational physics and engineering. |
Our goal is to design a collaborative system (using TANGO) to allow users on various platforms to work together in an efficient manner. |
In order to accomplish these goals, we focus on multi-casting and compression schemes. |
Our system is composed of a visualization server (Java/C++) and numerous visualization clients (Scivis3d, VRML). |
The visualization server is written in Java, as well as the visualization client, Scivis. |
The SV2 server contains geometry and filter engines. |
The main tasks of the geometry engine is to compute geometry from raw data, it can also compress data. |
Features in the geometry engine are to generate volume images using ray tracing techniques, Isosurface, sample various domains in the 3d data set, etc. |
The server is written in Java, but many routines (such as the ray tracing routine), are written efficiently in C. Since current API provided by these visualization system does not support Java code, we will use the Java Native Interface(JNI) to call C/C++ API's. |
Filters are contained on the Server and Clients. |
For enhanced interactively, the image should be refined progressively as the data comes in from the remote server.
|
In order to store and transmit large scale data sets, compression schemes have to be utilized.
|
With upcoming network computers, the capabilities of a local client might be reduced significantly.
|
Java-3D allows programmers to specify geometry using a binary geometry compression format. This compression format is used with APIs, and can be used both as a run-time in-memory format for describing geometry, as well as a storage and network format. |
Data is sent from simulations(files) to the SV2 server. |
Data from the SV2 server is stored (in memory, and on disk). |
Data file headers are sent to SV2-clients.
|
To keep support for Scivis alive, we allow users to pipe data directly to SV2. |
Filter/Map creator |
Better compression Schemes. |
Viewers for selecting parts of large data sets. |
MPEG output. |
More VTK incorporation. |
More Filters. |
...... |