Monday, June 30, 2014

X3DOM - Tentative Final

X3DOM


%-------------------------------------------------------------------------------


Goal : Multi-channel visualization based on the X3DOM


Todo :



  1. Study
  • How to apply shader for edge blending and warping? 
  • (Added)How to apply render texture?
  • How to manipulate camera projection matrix on X3DOM?
  • How to synchronize variables using js?
    2. Design
  • Web-based system
  • What will be the main difference with multi-channel visualization using Unity3D?
  • Connect-and-play?
    3. Implementation
  • TBA...
%-------------------------------------------------------------------------------


  • This work is finalized through fast and brief implementation for paper submission of Pacific Graphics 2014
  • The concept of cluster rendering is illustrated in below figure.

- Web server consisted of HTML page and network server for real-time networking using socket.
- Rendering cluster requests the page as a slave or master, through web browser
- Display device, provides final image from web browser running in the rendering cluster.

  • Two major issues : Configuration & Data distribution

  1. Configuration - through local storage

- In cluster rendering, we should select one of the data distribution model, server-client or master-slave.

- We selected master-slave, since it requires less bandwidth, which is usually the headaches in real-time 3D, more than the computing power.

 - Configuration lets the cluster know their state(master or slave) and changes it's behavior.

 - Typically, division of the view frustum should be done so the related view frustum information should be described somewhere.

- HTML5 local storage is appropriate technology for it.

- So when the cluster connects, it reads the configuration information from local storage and rebuild the web page for cluster rendering, especially if it is the slave node, which also predefined through local storage.

View frustum division
Result of the configuration. For the same page, (a) shows the result when connected as a master and (b) shows the result when connected as a slave.

  • Results

    • Experiments from 4 different display platforms, three are the large high-resolution display and one is the array of tablets.
    • It works. The detailed evaluation would be published somewhere.

Since it runs through the Internet, the display device and Web server can be geographically distributed.
The results.




  • The related paper and conference presentation is submitted.
  • A lot of interesting research issues, will be discussed in later posting.




No comments:

Post a Comment