Plans and Goals: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
Jadrian Miles (talk | contribs)
No edit summary
Line 140: Line 140:
## Work with Brad to get the measurement code accessible / reusable by other people
## Work with Brad to get the measurement code accessible / reusable by other people
## Work with Brad to get other code bases tested before I leave
## Work with Brad to get other code bases tested before I leave
----


=== Radu ===
=== Radu ===
Phd proposal
# Proposal draft and committee by June 15
* first rough skeleton draft by Feb 1
# Revise Draft by July 15
* lit search and revised draft by March 1
# Multiple views framework done by June 15
* more lit search and final proposal by April 1
# Multiple views framework deployed for Immgen July 1
* presentation by May 1
# Protein vis into multiple views framework by July 15
Vis submission
# Comparative analysis of clustering ready for evaluation by September 1
* paper sketch by Feb 1
# Plan for proposal paper 6 (annex 1) by September 1
* iteration 1 (iteration = coded concepts, evaluation scenario and feedback) by Feb 15
# Cogsci literature review done by September 1
* iteration 2 by Mar 1
* first write-up and iteration 3 by Mar 15
* submission
Immgen
*new techniques, interactions and approaches to exploring multi-dimensionality
* expansion - idea and application brainstorming
* continue with Bang at Broad (more or less in the background)
* extract insights from genomic viewer  (more evaluation)
* Immgen progress report (current + future) - by Feb 1
* Immgen progress report (current) - by May 15
TVCG submission
* tackle revision/resubmission if I get response
Other conference paper
* write 2-3 proposals for ideas (by April 15)
* select one and write paper sketch by May 1
Other
* transform the weekly todo in a habit
* improve multi-tasking/planning abilities
* more responsive and less ball droping
* cleaner submissions (of answers, code, writeups etc)


----
----

Revision as of 17:34, 1 June 2009

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
  • 3:30 - Brad
  • 3:40 - cad
  • 3:50

Current Plans and Goals

Andy

  1. mri/wrist
    1. tools
      1. registration, classification, distance-field calculation, bone proximity calc.
      2. graphical visualization/verification?
    2. modeling?
  2. $G (nightly tests, architecture, outside test-case = ADVISER)
  3. future funding candidates
    1. volume data visualization/analysis
    2. flow visualization w/ leopold/GK
    3. 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.

Çağatay

  1. Finalize the phd committee and distribute proposal by June 15.
  2. Incorporate feedback from the committee into the proposal by July15.
  3. Demonstrate the utility of Reeb graphs for dt invariants by June 24.
  4. Submit surface deformation to a journal by August 31.

David

  1. cs295J (HCI+COG+VIS) runs smoothly: new research directions, class goals met
  2. improve group infrastructure: sw, data, dissemination, tools (with help from bb, asf)
  3. proto-papers incubator
  4. more brain project deliverables; paper skeletons
  5. trey stuff happy [distance pipeline ok, modeling needs attn next semester]
  6. joslin stuff happy
  7. support group members' goals and growth, particularly impact and products
  8. refine 5-year funding/sabbatical plan – write some proposals
  9. keep up on dept/Brown service (search, facil, brdd, academic advising, mrf)
  10. keep up on professional service

Eni

  • publish a full metrics paper
  • start working on the wrist project
  • publish a paper on wrist work
  • improve programming skills
  • possibly get involved in another brain project, once metrics paper is sent out

Jadrian

  1. Assemble a thesis committee and submit my proposal to them by 2009-06-15
  2. Incorporate committee's comments into my proposal by 2009-07-15
  3. Work with Win and dhl to figure out the b matrices for the new acquisition protocol
  4. Get Mark Bastin's scans processed by 2009-06-30
  5. Make a list of papers to spawn from aims A and B of the proposal
  6. Finish clustering code and implement a couple other curve similarity measures for comparison
  7. Find or build implementations of some more sophisticated tractography techniques
  8. Work with Steve's group to get a HARDI acquisition
  9. Start working on aim I of the proposal (diffusion simulation in a detailed microstructure model)

Jian

  1. Papers / work:
    1. Finish the camber measurement paper ( first draft of the results section - by May 28)
    2. Finish the presence paper (accepted, by May 30)
    3. Finish the book chapter (accepted, by May 30)
    4. Finish the visualization paper whatever the result will be (by July 31st)
    5. Finish the display paper and submit it to TVCG (July 31st)
    6. Prepare the VR paper with a student at TJU (due in September, lead)
    7. Work on the vision paper (with the student + faculty at TJU) (invited)
  2. Career development:
    1. write up career goals and learning goals for the next 90 days and the next five years.
    2. Direct one student to work on the architecture project (for the VR paper)
    3. Direct one student to work on 3D interaction (get him to USM)
    4. inform others I will be moving
    5. improve time management / learn roles faculty to play
    6. Plan ahead for the new post (campus visit, lab space, facilities, collaborators)
  3. Travels:
    1. (maybe) ISBI (http://www.biomedicalimaging.org)
    2. SIGGRAPH (August 3-6)
    3. Campus visit (the end of June or the beginning of July)
    4. Leave the last week in July
  4. Learning:
    1. Shape
    2. continue to learn visualization + hci issues
    3. X3D
  5. Code:
    1. Work with Brad to get the measurement code accessible / reusable by other people
    2. Work with Brad to get other code bases tested before I leave

Radu

  1. Proposal draft and committee by June 15
  2. Revise Draft by July 15
  3. Multiple views framework done by June 15
  4. Multiple views framework deployed for Immgen July 1
  5. Protein vis into multiple views framework by July 15
  6. Comparative analysis of clustering ready for evaluation by September 1
  7. Plan for proposal paper 6 (annex 1) by September 1
  8. Cogsci literature review done by September 1


Trevor

  1. Distortion correction paper.
    1. Finalize content and evaluation.
    2. Submit to TMI? Consider where this will have the most impact.
  2. Work toward Vis submission on interaction histories, collaborative scientific visualization.
    1. Explore possible applications.
    2. Develop evaluation criterion.
    3. Consider software model as a contribution.
  3. Research comps proposal. (Interaction histories?)
    1. Draft complete by mid-February. (by February I mean April)
    2. Practice talk at SciVis meeting February 24th.
  4. Evaluate eye-tracking systems available at Brown.
    1. Develop webcam-based eye-tracking?
  5. Continue to explore and evaluate intern opportunities.
  6. Get through classes.
    1. CS224, CS295-J, Reading and Research.
  7. Improve time management.
  8. Improve writing.
    1. Explore opportunities for short submissions.

Wenjin

Ph.D. Proposal Draft

  • Abstract ready 2/23
  • Specific contributions 3/9
  • Preliminary Studies 3/16
  • Research Design and Methods 4/6
  • Background and Significance 4/20
  • full draft 5/4

Improve Axon Modeling and Validation with Histology, submit to MICCAI

  • Improve axon modeling
  • Validation with Macaque Histology Data

ISMRM conference

  • deliver a good presentation and poster
  • connect with people and seek for collaboration
  • gather inspiring project ideas

Aim for MRM journal submission

  • Histology validation stuff
  • Improvement on modeling

Prepare to get teaching experience in the fall


Past Plans and Goals