Monash, LAVA, EVL, Oregon, AIST Meeting

Get Started. It's Free
or sign up with your email address
Rocket clouds
Monash, LAVA, EVL, Oregon, AIST Meeting by Mind Map: Monash, LAVA, EVL, Oregon, AIST Meeting

1. VR

1.1. Short summary

2. Areas of interest for Monash

2.1. Monash Immersive Visualisation Platform 1. David Barnes 2. Owen Kaluza

2.1.1. Spatial mapping / GIS 1. archaeology 2. geoscience 3. railway infrastructure 4. digital agriculture 5. remote vision

2.1.1.1. Point clouds

2.1.1.2. Photogrammetry

2.1.1.3. "virtual fieldwork" tools

2.1.2. Unity environments 1. Virtual supermarket

2.1.3. New / Future Facilities 1. Future Control Room 2. VR Arena

2.1.4. Workflow / integration / frameworks

2.1.4.1. web-based previs

2.1.4.2. LavaVU, iPython notebooks, LavaVR

2.1.4.3. S2PLOT

2.2. Monash Faculty of IT 1. Matthias Klapperstueck

2.2.1. Unity environments 1. Ankgor Wat 2. Elwood Flooding

2.2.2. SAGE2

2.2.2.1. ContextuWall

2.2.2.2. MDE / Taktile user input

3. Areas of interest for Hawaii

3.1. VR

3.1.1. Unified SteamVR/CyberCANOE API

3.1.1.1. On the immersive side, we have our own API based on Unity. https://github.com/uhmlavalab/CyberCANOE

3.1.1.2. UnReal and VR

3.1.1.3. We also have a point cloud library and shader for Unity. And I have a couple of students doing random acts of astronomy visualization with Brent Tully.

3.2. SAGE

3.2.1. Apps

3.2.1.1. Decision Support in Large Display Environments

3.2.1.1.1. HAVEN - Renewable Energy

3.2.1.1.2. Ike wai - Water sustainability

3.2.1.1.3. NetSage - IRNC network monitoring

3.2.1.1.4. Visualizing topic modeling for NSA

3.2.2. Linked Visualizations

3.2.2.1. Creating ways for SAGE visualizations to be aware of each other and to be able to automatically or semi-automatically create linkages.

3.2.3. For SAGE2 weʻve been surveying web-based viz portals/apps and seeing which ones work in SAGE2 via WebView. The goal is to:

3.2.3.1. 1. rate these in terms of compatibility

3.2.3.2. 2. determine which ones we might be able to make compatible by modifying SAGE2 in some way.

3.2.3.3. 3. find ones we could potentially partner with to help make them SAGE2 compatible.

3.2.3.4. 4. Come up with general guidelines for app and UI development on big walls to facilitate maximal usability and compatibility with SAGE2.

3.2.4. We are also interested in getting new apps developed and shared on the SAGE2 “store”.

3.2.5. SAGE3

3.2.5.1. Smart Amplified Group Environment

3.2.5.1.1. Developing a suite of AI integrated visualization tools

3.2.5.2. In thinking about the future (i.e. SAGE3) we are interested in the merging of AI with SAGE for the purposes of:

3.2.5.2.1. Automating UI interactions

3.2.5.2.2. Adding intelligence to existing SAGE apps- like Pdf viewer

3.2.5.2.3. Automated chart generation based on applying data science algorithms

3.2.5.2.4. Tools for enhancing collaborative creativity

3.2.5.2.5. Lastly, weʻre interested in novel user-interfaces- in particular natural language. We have been doing some work extending from our prior work in Articulate- to translate natural language queries into visualization. EVL is also interested in putting sensors in project room environments, and I have a faculty member who works on Internet of Things also potentially interested in doing something revolving around Intelligent meeting environments.

4. Areas of interest for Chicago

4.1. SAGE2

4.1.1. Unity WebGL output for SAGE2

4.1.1.1. Loading in as a webpage

4.1.1.2. can it be syn'ed

4.1.1.2.1. hacking the JS

4.1.1.2.2. frame sync API ?

4.1.2. SAGE2 runtime for WebApps to enable more apps to work out of the box

4.1.2.1. UI that works

4.1.2.1.1. fonts size

4.1.2.1.2. scaling elements

4.1.2.1.3. text entry and mouse events

4.1.2.2. Synchronization

4.1.2.2.1. Frame sync

4.1.2.2.2. Data sync

4.1.2.3. Drag-drop webapps

4.1.2.3.1. a la Emperor

4.1.2.3.2. a la Emperor

4.1.3. SAGE2 Cloud

4.1.3.1. SAGE2 servers on-demand

4.1.3.2. Limits of this model

4.1.3.2.1. one machine or a cluster for large number of servers

4.1.4. Video streaming

4.1.4.1. Live H264 into SAGE2

4.1.4.1.1. HSLS

4.1.4.1.2. DASH

4.1.4.2. RGB/YUV pixel streaming from external sources

4.1.4.2.1. Old SAGE1 model

4.1.5. Jupyter integration

4.1.5.1. what's the model: people edit on their laptop or on the wall

4.1.5.1.1. webview

4.1.5.1.2. sharing graphs

4.1.5.2. jupyter hub / jupyter lab

4.1.6. Users in SAGE2

4.1.6.1. what's a user

4.1.6.2. roles and permissions

4.1.6.3. tracking and understanding

4.1.7. Appstore

4.1.7.1. Apps

4.1.7.1.1. monetization

4.1.7.2. Sessions

4.1.7.2.1. medias and layout

4.1.7.3. Webapps

4.1.7.3.1. URLs

4.2. SDN

4.2.1. Setup resource allocation for collaboration

4.2.1.1. Network path between collaborator

4.2.1.2. Access to remote resources: storage, ...

4.2.2. IPv6

4.2.2.1. important for some part of the world

4.2.3. control a large amount of devices in a room

4.2.4. IoT

4.2.4.1. Make sense of what users are doing or trying to do

4.3. VR

4.3.1. Exploring WebVR

4.3.2. 'electro' style VR in JS

4.3.2.1. inside or outside SAGE2

4.3.3. Unity3D export

5. Areas of interest for Japan

5.1. SAGE2

5.1.1. Linked visualizations

5.1.1.1. 2D vs 3D representations

5.1.1.2. Single vs multiple users

5.1.1.3. VR streaming integration

5.1.2. UI/UX improvements and modalities

5.1.3. Identifiers for visualization sessions

5.1.3.1. Persistent Identifiers (PID)

5.1.3.2. Data type registries (DTR)

5.2. VR

5.2.1. Multi-scale modeling

5.2.1.1. Disaster management

5.2.1.2. Urban environments

5.2.1.3. Bioinformatics

5.2.2. Data sources

5.2.2.1. Sensors

5.2.2.2. Hi res maps

5.3. AR/MR

5.3.1. Marine museum

5.3.2. Urban environments

6. Areas of interest for Oregon

6.1. Bringing in faculty

6.1.1. Student participation

6.1.2. List of VW faculty projects from other places

6.2. Funding for staff

6.2.1. Tools that are applicable to multiple user groups (SAGE2)

6.3. Work flows

6.3.1. Effective ways to educate users

6.3.2. Ways to encourage faculty input and feedback

6.3.3. Identifying capabilities that use the room as more than a 'big screen'

6.3.4. How to charge for services

6.4. Room design and lighting

6.5. Learn from everyone!

6.6. AR

6.6.1. Hololens

6.6.1.1. Neuronal connections

6.6.1.2. Conservation mapping

7. Schedule

7.1. May 21

7.1.1. Group dinner at 5:30 at Tikis Grill

7.1.1.1. tikisgrill.com

7.2. May 22

7.2.1. Jurgen joining remotely via hangout

7.2.2. Group dinner if interested

7.2.3. To discuss: https://conference.eresearch.edu.au/abstract-submission/#1491374085095-5b0d201f-2e84

7.3. May 23

7.3.1. SAGE2

7.3.1.1. Overview of current state SAGE2 capabilities

7.3.1.2. Overview of new SAGE2 acitivities

7.3.1.3. General discussion of priorities / interests

7.3.1.4. Group dinner if interested

7.4. May 24

7.4.1. Strategy meeting of SAGE3 (Chicago/Hawaii only)

7.4.1.1. What can community do over the summer

7.4.1.2. Next SAGE grant

7.5. May 25

7.5.1. Afternoon social?

7.6. Restaurant possibilities

7.6.1. thepigandthelady.com

7.6.2. mwrestaurant.com

7.6.3. Himilayan Kitchen

7.6.4. 12 ave grill

7.6.5. JJ French Bistro

8. Location

9. Attractions

10. Contact Info

10.1. Monash

10.1.1. Arrive Sunday, Depart Friday, no vehicle, Aqua Pacific Monarch hotel

10.1.2. David Barnes - [email protected]

10.1.3. Matthias Klapperstueck - [email protected]

10.1.4. Owen Kaluza - [email protected]

10.2. Hawaii

10.2.1. Jason Leigh

10.2.2. Alberto Gonazalez

10.2.3. Dylan Kobayashi

10.2.4. Ryan Theriot

10.2.5. Tyson Seto-Mook

10.3. AIST

10.3.1. Jason Haga - [email protected]

10.3.2. Aqua Skyline at Island Colony (445 Seaside Avenue), no vehicle

10.3.3. Saturday morning - Thursday

10.4. EVL

10.4.1. Luc Renambot - [email protected]

10.4.1.1. Saturday afternoon - Thursday

10.4.2. Maxine Brown

10.4.2.1. Sunday afternoon - Tuesday March 30

10.5. Oregon

10.5.1. Vehicle TBD

10.5.2. Duncan Barth - [email protected]

10.5.3. Hans Kuhn - [email protected]

10.5.4. Dean Walton

10.6. UCSD

10.6.1. Jurgen Schulz