Plans and Goals/Spring 2013

From VrlWiki
Jump to navigation Jump to search

Connor

  • Take courses.
    • Topics in Computational Biology
    • Intro to AI or CLPS "Core Topics in Perception" grad seminar
    • Reading & Research: research comp, visual saliency, 237 data analysis
  • Select a Research Comp proposal, start working on it, and propose
    • Formulate idea by February 18th
    • Submit committee to department and have rough draft of proposal done by March 11th
  • Wrap up 237 project either immediately or create plan for eventual wrap up

_____________

January 28

  • Create new python script to analyze 237 data. Use it to convert the data into a more easily machine-readable format, and use new format for analysis
  • From brainstorming list identify trends, and write down the three most common areas (e.g., uncertainty visualization, xxxx and memory, etc.) with +’s/-’s
  • Transfer IRB accreditation from Tufts to Brown. If expiring this school year, determine if easier by means of paper filing to just let it expire and recertify at Brown

February 4

  • Looking at +’s/-’s narrow down the areas to at most two. For the filtered area(s), list at most four specific ideas.
  • For each idea list if it needs collaboration in a domain, what evaluation components it requires, and what development component it requires.
  • Report on new analysis results. List all ways it makes sense to slice the data/analyze it. This will make analysis easier to plan for.

February 11

  • Filter down the ideas to at most three ideas.
  • Write down ½ to 1 page descriptions for each. These contribution areas should read like a related works section. Use this to focus each idea more.

February 18

  • Select an idea. (This should be done soon after February 11)
  • [Conditional] Meet (or plan meeting later in the week) with any potential collaborators. Talk to them about my idea and how it fits in with what areas they’re thinking about.
  • [Conditional] Brainstorm how to tie my ideas in with collaborators
  • Finish 237 data analysis

February 25

  • Put all materials up to this point in archival form on the file system
  • Make a formalized list of each contribution of my proposal and how I propose to make that contribution. Allow contingencies.
  • Convert all writing relevant to my research comps I’ve done so far into LaTeX for my proposal. Finish A Shitty First Draft™

March 4

  • Finish second draft of proposal
  • Chunk what I have to do into a research comp schedule for the rest of the semester (including, specifically, what needs to happen by proposal). Look over with David

March 11

  • Submit research comp committee to department
  • Select proposal date that must be before April 21

March 18

  • Adapt contribution area writing to the application area to form first draft of proposal

March 25 – IN SPRING BREAK

  • Edit proposal. New revision = draft 2

April 1 – POST SPRING BREAK

  • 237 work should be fully wrapped up by end of spring break. Make a call on what to do with the work at this point.
  • Have final proposal draft done.

April 8 to End

  • Create schedule and goals for research comp
  • Make progress on those goals
  • Tie up 237 project or get ready for some sort of submission.


David

  • keep grad students moving along
  • keep Cave project moving along (Facilities groundbreaking (delivery dates)
    • facilities budget solid and approved
    • permit applied for
    • facilites work done, including floor delivery and installation
    • metal fab parts completed, delivered, assembled
    • create demo group
  • excellent cs237
  • prep for cool, new(ish?) cs16 for Spring
  • December Expeditions in Computing submission
  • volume rendering interaction in WristVis
  • brain metrics papers out with Ryan
  • longer-term funding matched with group



Jadrian

Today's Date: 12/08

  • Meta-objective: Be ready to graduate and move on in May.
    • Objective: Teach CS 931 well without it taking over my other responsibilities.
      • Key Result: Prep & teaching time are monitored throughout the semester and limited to 10 hours per week.
    • Objective: Demonstrate novelty & significance of the "blockhead" method in the dissertation.
      • Key Result: Drafts for graphics- and medical-focused voxelization papers to dhl by 01/14.
      • Key Result: Software generates large, multi-component slicemaps by 01/18.
        • Completed 01/20.
      • Key Result: Software generates voxel maps by 01/22.
      • Key Result: Software generates antialiased voxel maps by 01/31.
      • Key Result: Software generates synthetic MRIs by 02/05.
      • Key Result: Software generates chi-squared images by 02/08.
      • Key Result: Software identifies plausible optimization moves for a two-component test dataset by 02/13.
      • Key Result: Software improves objective function for two-component test dataset by 02/15.
      • Key Result: Software improves objective function for fiber cup phantom by 03/05.
      • Key Result: Software converges for fiber cup phantom by 03/15.
      • Key result: Software improves objective function for real data by 03/18.
      • Key Result: Graphics-focused paper on voxelization submitted by 02/01.
      • Key Result: Medical-focused paper on voxelization submitted by 02/22.
    • Objective: Write and defend a dissertation that covers and synthesizes the work I've done.
      • Key Result: Dissertation chapters outlined by 01/17.
        • Completed 01/16.
      • Key Result: Defense dates proposed to committee by 01/17.
        • Completed 01/16.
      • Key Result: Draft dissertation to committee by 03/20.
      • Key Result: Defense scheduled with Lauren by 03/20.
      • Key Result: Dissertation defended by 04/30.
    • Objective: Graduate.
    • Objective: Get a job.
      • Key Result: All academic job applications complete by 01/15.
        • Applications complete 01/13.
      • Key Result: Job interviews attended as invited.
      • Key Result: Non-academic job applications in process by 01/22.
    • Objective: Transition smoothly out of Brown.
      • Key Result: Software and documentation archived by 05/17.


Nathan

Steve

  • Do a good job shadowing Jadrian for CS 0931
  • Keep IVRG on track
  • Crowd-based visualization collaboration
    • By 1/30: Meet with astronomers and others to find large images (like SkySurvey) that people are actively analyzing; have list of actionable research questions (e.g., have data available to test)
    • By 2/6: Have group settle on final work plan for VisWeek or UIST pub, or decide to end meetings
    • By early April: If no submission, make plan for CHI submission in mid-September
  • Evaluating tractography in the crowd
    • By 2/1: Have benchmark data from Jian cleaned up and annotated
    • By 2/4: Send Jian and David a project plan for crowd experiments and a TVCG paper
    • By end of March: VisWeek submission, or if not ready, TVCG by May or plan for CHI in mid-September
  • Online, evaluation examples repository/vis (pushed to after VIS deadline
    • By 4/15: Data coded and moved into online MongoDB
    • Visual front end implemented by 4/30 and...
    • By 5/15: TVCG submission drafted


Ryan

  • Plan thesis proposal
  • Publish Edinburgh paper
  • Keep up with needs of Rob Paul's group
  • Publish paper(s) with Dan Dickstein
  • Contribute to CrowdVis project
  • Work on ways to organize ideas and plans more effectively
  • Be more of a paper mill


Hua

  • Required coursework: complete two CS courses (or three)
    • Topics in Distributed Databases and System (big data analysis focus!)
    • Computational Photography
    • Human Factors and Interface Design (just sitting-in, perhaps)
  • Progress on the research comp
    • Implement the interface with support for user goals
    • Do the user study
    • Submit to CHI as a work-in-progress


Retrieved from "http://vrl.cs.brown.edu/wiki/index.php?title=Plans_and_Goals/Spring_2013&oldid=6343"