VrlWiki - User contributions [en]

Action Items for Oct. 27th, 2009

2009-11-02T15:43:15Z

Sharon King: New page: Attendees: David, Sharon, John, Brad, Andy (Sam – sick) '''Agenda for meetings in CA''' John review with Sam to see if items need to be added Sam is sick and may not be well enough to ...

Attendees: David, Sharon, John, Brad, Andy (Sam – sick)

'''Agenda for meetings in CA'''
John review with Sam to see if items need to be added
Sam is sick and may not be well enough to travel – not good as Sam needs to pick Gregg’s brain…..
Is it possible for Sam to call in or should we reschedule the trip? ( already done – planned for 11/11)
John needs to read paper on StarCAVE

'''Display discussion'''
Mitsubishi support is pretty responsive (Laservue). John got to tier 3 almost immediately but his call was the 1st one they’ve received re: 3D
Asked what graphics card we are using so they can recreate the problem there.

LCD not fast enough and doesn’t do stereo. They are just coming out now, but problem will be the boarder.
Rear projection TV’s – very good still a better bet than LCD

LG – Boarder less one (small boarder) – worth looking at

Add issue: alternative display technologies – John to add to agenda and to wiki
Talk to Greg about this i.e. boarder less, projection. LCD w/fiber optics
Everything John has seen, rear projection TV is still the best option.

'''VRPN – Brad'''
Tried to build on all compilers
G3D- MS suite - only one they support. Can develop on Linux
Will not use unsupported versions of anything per DHL

New CAVE Design

2009-11-02T15:31:12Z

Sharon King: /* Weekly Cave action items */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]
* [[Action Items for Sept. 29th, 2009]]
* [[Action Items for Oct. 27th, 2009]]

== Initial Design Issues ==

=== University facility ===
* Problem: What are the requirements for University researchers in general?
* Input needed
** Interview existing Cave-users and potential Cave-users to consider needs/requirements
* Experiments needed
** (None?)
* Decision: ?

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Software: commercial quality ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

=== Software: researcher/developer tools ===

* [[Cave Software Overview]]
* [[VRG3D Requirements]]

* [[Vis 2009 discussion dfk/dhl/asf]]

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

=== Upcoming Trip to Californina ===
*[[Agenda and action items for Disney Imagineering]]
*[[Agenda and action items for CALLIT2]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

Action Items for Sept. 29th, 2009

2009-10-05T20:05:40Z

Sharon King: New page: Due by 10/6 Hardware – Action items update the wiki with hardware issues and send email to dhl when it’s done (John) tracking - nothing for this yet, as it is a lower priority. It’...

Due by 10/6

Hardware – Action items
update the wiki with hardware issues and send email to dhl when it’s done (John)
tracking - nothing for this yet, as it is a lower priority. It’s okay to list concerns/issues w/? so we can have a structure in place (John)

Travel plans – Action items
Date of October 28th has been confirmed. Sam and David need to decide on return time/date. Do we need 2 or 3 days.
Once this has been decided, we need to confirm date/time with the Disney folks. (DHL/Sam)
Create separate pages on the wiki for the trip i.e.; Calit and Disney. List agenda items for both. They should be some overlapping. (John)

Project Management – Action Items
MS project has been installed on Sharon’s machine. John and Sharon have begun to populate sheet. They will continue to work on this and will bring a copy of what they’ve accomplished to the next meeting. (Sharon/John)

Software – Action Items
Brad and John met this past week to discuss software tools and $G; need further discussions (John/Brad)
Brad update layer cake on wiki. (DONE)

New CAVE Design

2009-10-05T20:03:42Z

Sharon King: /* Weekly Cave action items */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]
* [[Action Items for Sept. 29th, 2009]]

== Initial Design Issues ==

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

[[Cave Software Overview]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

New CAVE Design

2009-10-05T20:02:10Z

Sharon King: /* Weekly Cave action items */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]
* ((Action Items for September 29, 2009))

== Initial Design Issues ==

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

[[Cave Software Overview]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

Action Items for Sept. 22nd, 2009

2009-09-24T19:23:50Z

Sharon King:

Hardware - new issue
* Mitsubishi laservue 3D mode gets ghosting (John update) due by Tuesday, 9/29
* Display contender shootout comparison table (John) due by Tuesday, 9/29 Mitshubishi is not as impressive as hoped for, good black level, very thin
* Tracking contender shootout comparison table (John) due by Tuesday, 9/29
new issues from discussion with Mark (imagineering)
* Samsung - all color correction goes away with 3D and may be fixable (John) due by Tuesday, 9/29
signals for each visit and visitor e.g. Mel: person-monitoring stuff; e.g. starcave, angle stuff
* Travel/visit planning - need action items for these (Sam) due by Tuesday, 9/29
* Travel to starcave (san diego), and imaineering (glendale/burbank) (Sharon) due by Tuesday, 9/29
* Project Management software initial setup: (John/Sharon) due by Tuesday, 9/29

DONE: G3D and VRG3D layer cake : Brad
* one more iteration, (Brad and John) due by Tuesday, 9/29

Action Items for Sept. 22nd, 2009

2009-09-24T18:00:28Z

Sharon King:

New CAVE Design

2009-09-24T17:17:36Z

Sharon King: /* Weekly Cave action items */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]

== Initial Design Issues ==

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

[[Cave Software Overview]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

Action Items for Sept. 15th, 2009

2009-09-18T15:38:39Z

Sharon King:

* Travel/visit planning (Sam) Put together a list of questions for the trip today. If Sam can't do it, then John can take a first pass at it by tomorrow (9/16). Need list before scheduling trip. Send blackout dates for travel to Sam through October 31.
* Timeline due today; integration by Tuesday (9/22) (John)
* Project management software initial setup by Tuesday, 9/22 (John/Sharon)
* G3D and VRG3D layer cake by Tuesday, 9/22 (Brad)
* Engines and Libraries - New Issue for wiki (John) by Tuesday, 9/22
* Cost sharing and ARRA reporting - (David) discuss with Jane
* FTE's and time commitment for people - PAFS: 5/5/5/10/25 asf/loomis/brad/sgf/john (Sharon/Jane)

Action Items for Sept. 15th, 2009

2009-09-18T15:38:11Z

Sharon King:

Action Items for Sept. 15th, 2009

2009-09-18T15:37:01Z

Sharon King:

* Travel/visit planning (Sam) Put together a list of questions for the trip today. If Sam can't do it, then John can take a first pass at it by tomorrow (9/16). Need list before scheduling trip. Send blackout dates for travel to Sam through October 31.
* Timeline due today; intergration by Tuesday (9/22) (John)
* Project management software initial setup by Tuesday, 9/22 (John/Sharon)
* G3D and VRG3D layer cake by Tuesday, 9/22 (Brad)
* Engines and Libraries - New Issue for wiki (John) by Tuesday, 9/22
* Cost sharing and ARRA reporting - (David) discuss with Jane
* FTE's and time commitment for people - PAFS: 5/5/5/10/25 asf/loomis/brad/sgf/john (Sharon/Jane

Action Items for Sept. 15th, 2009

2009-09-18T15:32:17Z

Sharon King:

Action Items for Sept. 15th, 2009

2009-09-18T15:26:15Z

Sharon King:

Action Items for Sept. 15th, 2009

2009-09-18T14:33:00Z

Sharon King:

* One
* two
** Three

Action Items for Sept. 15th, 2009

2009-09-18T14:28:16Z

Sharon King: /* Action Items for Sept. 15th, 2009 */

* One
* two
* Three

Action Items for Sept. 15th, 2009

2009-09-18T14:24:48Z

Sharon King: New page: = Action Items for Sept. 15th, 2009 = * One * two * Three

= Action Items for Sept. 15th, 2009 =

* One
* two
* Three

New CAVE Design

2009-09-18T14:23:08Z

Sharon King:

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]

== Initial Design Issues ==

=== Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon

=== Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?

=== Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Goals: wireless, accurate, low-latency, unobtrusive
* Examples: head-tracking, tracking fingers and body, tracking "phicons"/props
* Q: Is camera-based tracking reliable in a Cave?

=== Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Decision:

== Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)