Plans and Goals: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
No edit summary
Line 67: Line 67:


Infrastructure
Infrastructure
* Manage the migration to the new file system.


* Continue to write Wiki entries as needed.
* Continue to write Wiki entries as needed.
Line 73: Line 75:


* Extend the build system to make kits for public source and binary distributions.
* Extend the build system to make kits for public source and binary distributions.
* Improve support for remote development.
* Launch the Windows test system.


* Continue extend the make files to support new features such as additional third party packages.
* Continue extend the make files to support new features such as additional third party packages.


* Upgrade migrated Linux code to work with gcc 4.3.
* Upgrade migrated Linux code to work with gcc 4.3 in conjunction with the summer Debian upgrade.


* Continue to integrate any new tests written by students into nightly test runs.
* Continue to integrate any new tests written by students into nightly test runs.
Line 88: Line 94:


* Meet (SciVis talk) with students to address any integration issues.
* Meet (SciVis talk) with students to address any integration issues.


=== Çağatay ===  
=== Çağatay ===  

Revision as of 19:45, 17 May 2010

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 Tuesdays. The authoritative list is in dhl's calendar.

  • 1:50 - jadrian
  • 2:00 - wenjin
  • 2:10 - eni
  • 2:20 - jadrian
  • 2:30 - bb
  • 2:40 - dtr
  • 2:50 - trevor
  • 3:00 - cad
  • 3:10 - steve
  • 3:20 - radu

Current Plans and Goals (Summar/Fall '10)

Caroline

Get oriented

  • Find out current status of framework
  • Acquaint myself with any existing modules / code / results
  • Find out who else will be working on it or has worked on it, meet with them
  • Literature review
  • Learn CPM-GOMS, refresh on ACT-R

Do whatever needs to be done to get framework going

Create a test module based on my earlier implied dynamics work [1]

  • Model a dynamics-based assessment of relationships between parts of simple visualizations
  • Test whether this can predict users' actual evaluations of a chart's structural properties
  • Maybe rethink to tie in more to affordances, interface prediction

Identify other potential modeling projects based on visual structure for future work...

  • Predicting the patterns (trends, clusters, etc.) a user sees in a visualization
  • Modeling how quickly a user can read high-level information from different vis types
  • Analyze interaction affordances in a visualization system

Get funded

  • Work on grant proposal
  • Find and apply for fellowships / postdoc grants

David

  1. get diffusion normals, one library, and one executable distributed
  2. good TBI talk in Chicago
  3. support 5 phd students' + trevor's progress
  4. si^2 proposal for 6/14, then expedition?
  5. wrist proposal possibilities, w/eni (check with Trey?)
  6. keep Vis '11 on track


Brad

Projects

  • Support the ongoing projects including collaborators. Active projects are wrist, brain, adviser, and protein.
  • Assist Radu to integrate a test and any recent code.
  • Migrate Win's mri pipeline to run in CIT.
  • Contribute to the design and development of the new cave. Integrate changes to vrg3d. Simplify the configuration and provide a quick start path for student projects.
  • Set up public distribution of diffusion imaging data.


Infrastructure

  • Manage the migration to the new file system.
  • Continue to write Wiki entries as needed.
  • Continue setting up third party software for students to use. Current imported packages are: blitz, cg, g3d, qt, camino, dtk, afni, nifti, vivro, vrpn, glut, and sdl.
  • Extend the build system to make kits for public source and binary distributions.
  • Improve support for remote development.
  • Launch the Windows test system.
  • Continue extend the make files to support new features such as additional third party packages.
  • Upgrade migrated Linux code to work with gcc 4.3 in conjunction with the summer Debian upgrade.
  • Continue to integrate any new tests written by students into nightly test runs.
  • Finish integrating the new version of the Nag libraries.


Knowledge

  • Learn more about the cave; particularly vrg3d software development.
  • Meet (SciVis talk) with students to address any integration issues.

Çağatay

  1. Resolve crossings, count cycles.

Past Plans and Goals