Useful Reading Papers about: Fight of the Bumblebees VRML Dream - - PDF document

1

Fight of the Bumblebees

Technical Teams

Useful Reading

• Papers about:

– VRML Dream (IEEE CG&A – March 1999) – It/I (ISEA ’97)

• Both linked from DIARY on Web site.

Plan for this evening

• Team Descriptions / Preliminary

Assignments

• Introduction to Networking Infrastructure

Logistics

• The LDAP database

– Be sure that your e-mail is correct. – All of you should have received mail from me.

Logistics

• Course Web Site:

– http://www.cs.rit.edu/~jmg/vtheatre – Handouts

Fight of the Bumblebees (RIT 2004)

2

MUPPETS

• The Multi-User Programming Pedagogy for

Enhancing Traditional Study

• Developed in IT (Andy Phelps/Kevin Bierre/ Dave

Parks)

• A Collaborative Virtual Environment
• Java based integrated development environment
• http://muppets.rit.edu/

Technical Teams

• Team MUPPETS (audience)
• Team CAVE (stage manager)
• Team FLOCK (flocking model)
• Team MERRY MELODIES (music / audio)
• Team VR (actor – lead bee)
• Team INFRASTRUCTURE (networking)

Team MUPPETS (audience)

• Main viewing app

– Display stage, actors, staging

• Multiple audience members
• Import Maya objects / animations

– Cueing object definition (with Team CAVE)

• Audio – Music

– (in conjunction with Team MERRY MELODIES)

• Audience participation
• Event Response

– Actors, staging, audio

Team MUPPETS

• Dennis Colburn (audio interface…still

registered?)

• James DiCamillo
• Jon Heise (networking interface)
• David Parks

Team CAVE (stage manager) Team CAVE (stage manager)

• Hardware setup /networking of UT-CAVE in Breakout

Room 2.

• Main viewing app in UT format

– Display stage, actors, staging

• Import Maya objects / animations

– Into UT format

– Cueing object definition (with Team MUPPETS)

• Networking from Java to UT
• Event Creation

– Controls for staging

• Event Response

– Actors, staging, audio (probably not)

3

Team CAVE

• Lomax Escarmant
• Draft choice -- Christopher Boyd (?)

Team FLOCK (flocking model)

• Emotive motion
• Flock object

– Interoperate with team MUPPETS – Interoperate with team CAVE

• Event Response

– From lead-bee

Team FLOCK

• Kathy Law (Emotive motion)
• David Rusbarsky (Flock Object?)

Team MERRY MELODIES

• Emotive Music
• Audio/Musician “object”

– Event Response

• From lead bee

– Interoperate with Team MUPPETS

Team MERRY MELODIES

• Ryan Becker (emotive music)
• Dennis Colburn (MUPPETS interface…still

registered?)

• Christopher Boyd (? MUPPETS interface?)

Team VR (actor – lead bee)

I-glasses Head Mounted Display w/head tracker 5DT Data Glove

4

Team VR (actor – lead bee)

• Hardware

– Get HMD and Data Glove working

• “Actor” object

– Generate events (from data glove)

• Viewer App

– In conjunction with team MUPPETS – C to Java conversion (if required)

Team VR (actor – lead bee)

• James Tranovich
• Draft choice (Damian Eads?)

Team INFRASTRUCTURE

• Basic networking to be done in Java
• Implementation of VT networking classes

– Thin wrapper over M2MI

• Event recorder

– For offline rendering – Test for network traffic

Team INFRASTRUCTURE

• Roderick Campbell
• Jon Heise (MUPPETS interface)

Draft Choices

• Because of too little or too much info:

– Damian Eads (Team VR?) – Ryan Kidder (Team CAVE?) – Christopher Boyd (MELODIES or CAVE) – Joe Spears (are you registered?)

• Joe Geigel

– Overflow – common interface specification

• Event heirarchy
• Cueing object.

– Others as needed.

Logistics

• Access to Breakout Room 2
• MUPPETS on ICL6 and BOR2 machines.
• Talk on MUPPETS

– Student Availability…after class or Friday?

5

Networking Philosophy

• Components should be loosely coupled.
• Serverless protocol

– Broadcast

• Ridiculously simple programmer interface.
• Observer Design Pattern

– EventGenerators – EventListeners

M2MI

• Many-to-Many Invocation

– Anhinga Project (A. Kaminksy/HP Bischoff) – Java based networking library – Serverless broadcast model – http://www.cs.rit.edu/~anhinga

M2MI

• Small mobile computing devices

– Not much CPU, memory, battery life

• Proximal wireless networks

– Broadcasting is inherent

• Ad hoc networks

– Automatic network configuration

• Collaborative applications

– Chat, groupware, file sharing, sensor networks, . . .

• Many-to-many communication patterns

– Every device talks to every other device

M2MI

• Object oriented abstraction of many-to-

many communication

M2MI Handles

• Handles (remote references)

– Omnihandle: Refers to all objects that implement an interface – Multihandle: Refers to a group of objects that implement an interface – Unihandle: Refers to one object that implements an interface

M2MI Handles

M2MI.export (a, Foo.class); Foo allFoos = (Foo) M2MI.getOmnihandle (Foo.class); allFoos.y();

6

VT Networking

• Event Generators

– Invoke sendEvent method on all event listeners

• Event Listeners

– Will receive event messages and respond appropriately

• Usually 1 generator / many listeners for

each event type

VT Networking

• Event “classes”

– ActorEvents – FlockEvents – AudioEvents – AudienceEvent – StagingEvent (include startPerformance/cues)

• Each event sent will have reference back to
• bject that sent the event

VT Networking

• Simple programming interface

– Distributed Performance object

VT Networking

• Simple programming interface

– For all

• Performance.register(this);

– For event generators

• Perfomance.broadcast(someEvent);
• Calls on each listener L

– L.eventHappened (someEvent);

– For event listeners

• Listener Types will be interfaces
• Must implement eventHappened()

VT Networking

• Will not use M2MI directly.
• Performance <-> M2MI should be straight

forward

• Job of Team INFRASTRUCTURE.

Job of teams in coming week

• Determine if component is

– Event Generator – what kind of events – Event Listener

• What kind of events
• What will be the response
• Determine set of tasks / deliverable

– Develop schedule for checkpoints

• Set up team Web site

7

Questions? For next time

• Send me e-mail

– Yea/Ney on current assignment – Final team assignments will be ready on Monday. – Team organization to occur on Monday.

• Start thinking about events and deliverables.

– Complete Event Hierarchy / interface presented on Monday.

• Questions?