Plans and Goals
On this page the members of the VRL record and refine their goals for the current semester. This is a living document in which dhl will provide feedback. See the bottom of the page for links to past plans & goals documents.
Current Schedule
Meetings are on Monday.
- 2:00 - asf
- 2:10 - jadrian
- 2:20 - radu
- 2:30 - Jian
- 2:40 - dtr
- 2:50 - trevor
- 3:00 - wzhou
- 3:10 - Eni
- 3:20 - dginsbur
- 3:30 - Brad
- 3:40 - cad
- 3:50 - Laura
Current Plans and Goals
Andy
- comparison of 3d vector vis methods
- run subjects, analysis, complete paper, submit to vis'09
- mri/wrist
- tools
- registration, classification, distance-field calculation, bone proximity calc.
- graphical visualization/verification?
- modeling?
- tools
- Potentially get involved in protein project, possibly pen UIs
- $G (nightly tests, architecture, outside test-case = ADVISER)
- future funding candidates
- volume data visualization/analysis
- flow visualization w/ leopold/GK
- other?
Brad
Projects
- Migrate all of the wrist project before Evan leaves.
- Support collaborators for the Protein project.
- Continue to migrate active projects.
- Begin migrating shared libraries. Some will need to be migrated in conjunction with projects.
Infrastructure
- Write Wiki entries for creating and building projects.
- Identify external software for students to use. Currently students download software based on their immediate needs. By providing support for a small number of external packages it will make it possible to distribute their software faster and with less effort. Students will have better support when they use common external software packages.
- Extend make files for tests, local installs and kits for source and binary distributions.
- Integrate new tests into nightly test runs. This might involve upgrading the nightly test mechanism. Tests will need to be written. In order for students to write tests clear and simple procedures need to be in place.
Knowledge
- It might be useful for me to sit in on CSCI 2950J.
- As project migrations complete make documentation available so that new student developers can easily get started.
- Provide support for novice CVS users. Students should be able to check code in and out of CVS with a minimum of effort. This will not only make it easier for students to participate, but will also protect the code base. It is very easy to unintentionally damage files in CVS and the damage might go undetected for some time. Recovery can be difficult.