Plans and Goals: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 72: | Line 72: | ||
---- | ---- | ||
== Past Plans and Goals == | == Past Plans and Goals == | ||
*[[/Spring 2013|Spring '13]] | * [[/Spring 2013|Spring '13]] | ||
* [[/Fall 2012|Fall '12]] | * [[/Fall 2012|Fall '12]] | ||
* [[/Summer 2012|Summer '12]] | * [[/Summer 2012|Summer '12]] | ||
Revision as of 14:44, 21 May 2013
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 Mondays. The authoritative list is in dhl's calendar.
Current Plans and Goals (Spring '13)
Connor
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.