CS295J/Week 1.11

• class title [1]
• intro self [2]
• motivation for class [10]
  • a research project -- but loosely defined
  • brains work differently than user interfaces
  • specific things we know about brains should influence user interfaces
    • e.g., | seven plus or minus two
  • how?
  • what other things do we know like that?
  • can software that helps with all this, or just create ``best practices?
  • cognitive modeling, human-computer interaction, scientific visualization
• class goals [15]
  • learn how to take an abstract research concept and take it to a much more concrete research plan
  • learn about the field of research HCI
  • learn about the field of cognitive modeling
  • learn about the field of scientific visualization
  • learn some about design to apply results
  • learn about learning new areas targeted at a research agenda
  • learn to work as a group
  • learn to tersely summarize research papers
  • learn to evaluate and mitigate risk
  • be intellectually stimulated and excited
  • have fun!
• class activities
  • revise a research proposal
• an aside: structure of an NIH proposal [15]
  • specific aims
  • background and significance
  • preliminary results
  • research plan
• also NSF
• class activities
  • read and analyze proposals
  • read and analyze proposal reviews and write responses
  • find papers/books/chapters
  • read papers/books/chapters
  • write summaries of pieces related to research goals
  • identify important topics and structure within disciplines
  • organize readings into topics
  • codify design rules motivated by cognition (or from HCI or other literature)
  • codify performance predictions
  • critique interfaces based on those rules
  • analyze the critiques
  • design some preliminary results
    • experiments?
    • software systems?
  • write up and present those results
• vrl wiki tutorial
• media wiki tutorial
• pre-proposal
  • several "poses", summaries
  • 1 minute read, 1 minute write on board (refer back, but don't read more) -- critique, erase
  • 5 minute read, 1 minute write (maybe adjust write time if too short)
• augment a reading list
  • find an expert (yourself, a professor, a student)
  • surf some course syllabi (try "HCI syllabus")
• ? theory of visualization presentation (maybe tuesday)
• assignment 1 (from other wiki page)
  • spend 10 hours adding to any part of the wiki you think is relevant
  • read both Research proposal before proposals.
  • by Monday noon add new readings. If you've got a tentative summary evaluation, go ahead and add it. It's ok to edit folks summary evaluations, but try to make the result more accurate or precise without losing information.
  • by Tuesday class finish with tentative summary evaluations of your new readings and also identify at least one as-relevant-as-possible reading as yours. This can be one of the new readings you added or something someone else doesn't own. Put your name on that entry in the reading list as the "owner" so that there are no duplicates.
  • by Wednesday 5pm -- select 2 additional relevant readings that are owned and that you will read by class Thursday and be prepared to discuss. Put your name as a "discussant" in the reading list; there should be a max of two discussants per reading.
  • by Thursday class -- author a summary description, less than 250 words, in the wiki of how the reading you own relates to our project. Be prepared to describe, in two (2!) minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.
  • by Thursday class -- read and be prepared to discuss the other two readings you choose.
  • Let me know if you have any kind of problems. You should be spending right around 8-10 hours each week -- if that's a problem, let's talk.
  • The How Tos page has some tips. Edit or add as you find others.