CS295J/Class 1 - Revision history

E J Kalafarski: wikify How Tos

2009-01-26T13:53:56Z

wikify How Tos

← Older revision		Revision as of 13:53, 26 January 2009
Line 55:		Line 55:
	** by Friday class -- make one more wiki page titled "'''<Last-Name> week 1'''" with a list of the keys for the citations you added, the readings you summarized, the reading you presented, the two readings you were a discussant on, and any other readings you did in detail.		** by Friday class -- make one more wiki page titled "'''<Last-Name> week 1'''" with a list of the keys for the citations you added, the readings you summarized, the reading you presented, the two readings you were a discussant on, and any other readings you did in detail.
	** Let me know if you have any kind of problems. You should be spending right around 10 hours -- if that's a problem, let's talk.		** Let me know if you have any kind of problems. You should be spending right around 10 hours -- if that's a problem, let's talk.
	** The [[How Tos]] page has some tips. Edit or add as you find others.		** The [[../How Tos\|How Tos]] page has some tips. Edit or add as you find others.

Eric Sodomka at 19:15, 24 January 2009

2009-01-24T19:15:57Z

← Older revision		Revision as of 19:15, 24 January 2009
Line 49:		Line 49:
	** spend 10 hours adding to any part of the wiki you think isrelevant		** spend 10 hours adding to any part of the wiki you think isrelevant
	** by Monday noon add any potential 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 Monday noon add any potential 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 Wednesday noon finish with any summary evaluation and also identify at least one as-relevant-as-possible reading as yours. Put your name on that entry in the reading list as the ``owner'' so that there are no duplicates.		** by Wednesday noon finish with any summary evaluation and also identify at least one as-relevant-as-possible reading as yours. 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 Friday 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 Wednesday 5pm -- select 2 additional relevant readings that are owned and that you will read by Friday 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 Friday 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 minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.		** by Friday 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 minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.
	** by Friday class -- read and be prepared to discuss the other two readings you choose.		** by Friday class -- read and be prepared to discuss the other two readings you choose.

David Laidlaw at 19:47, 23 January 2009

2009-01-23T19:47:42Z

← Older revision		Revision as of 19:47, 23 January 2009
Line 49:		Line 49:
	** spend 10 hours adding to any part of the wiki you think isrelevant		** spend 10 hours adding to any part of the wiki you think isrelevant
	** by Monday noon add any potential 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 Monday noon add any potential 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 Wednesday noon finish with any summary ~~evaluatio~~ and also identify at least one as-relevant-as-possible reading as yours. Put your name on that entry in the reading list as the ``owner'' so that there are no duplicates.		** by Wednesday noon finish with any summary evaluation and also identify at least one as-relevant-as-possible reading as yours. 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 Friday 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 Wednesday 5pm -- select 2 additional relevant readings that are owned and that you will read by Friday 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 Friday 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 minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.		** by Friday 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 minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.

David Laidlaw: Class 1 moved to CS295J/Class 1

2009-01-23T18:22:11Z

Class 1 moved to CS295J/Class 1

← Older revision	Revision as of 18:22, 23 January 2009
(No difference)

David Laidlaw at 04:19, 23 January 2009

2009-01-23T04:19:01Z

← Older revision		Revision as of 04:19, 23 January 2009
Line 5:		Line 5:
	** brains work differently than user interfaces		** brains work differently than user interfaces
	** specific things we know about brains should influence user interfaces		** specific things we know about brains should influence user interfaces
	**o e.g., 7 plus or minus 2		*** e.g., [http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two \| seven plus or minus two]
	** how?		** how?
	** what other things do we know like that?		** what other things do we know like that?
	** can software that helps with all this, or just create ``best practices''?		** can software that helps with all this, or just create ``best practices''?
			** cognitive modeling, human-computer interaction, scientific visualization
	* class goals [15]		* class goals [15]
	** learn how to take an abstract research concept and take it to a much more concrete research plan		** learn how to take an abstract research concept and take it to a much more concrete research plan
Line 27:		Line 28:
	** research plan		** research plan
	* class activities		* class activities
	** find papers		** find papers/books/chapters
	** read books/chapters		** read papers/books/chapters
	** write summaries of pieces related to ~~goal~~		** 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 design rules motivated by cognition (or from HCI or other literature)
	** codify performance predictions		** codify performance predictions
Line 42:		Line 45:
	* augment a reading list		* augment a reading list
	** find an expert (yourself, a professor, a student)		** find an expert (yourself, a professor, a student)
	** surf some course ~~sylla~~		** surf some course syllabi (try "HCI syllabus")
	* assignment 1		* assignment 1
	** spend 10 hours adding to any part of the wiki you think isrelevant		** spend 10 hours adding to any part of the wiki you think isrelevant

David Laidlaw at 04:06, 23 January 2009

2009-01-23T04:06:32Z

← Older revision		Revision as of 04:06, 23 January 2009
Line 19:		Line 19:
	** be intellectually stimulated and excited		** be intellectually stimulated and excited
	** have fun!		** have fun!
	* class activities ~~(see section below)~~		* class activities
	** build a research proposal		** build a research proposal
	* structure of an NIH proposal		* an aside: structure of an NIH proposal [15]
	** specific aims		** specific aims
	** background and significance		** background and significance
	** preliminary results		** preliminary results
	** research plan		** research plan
			* class activities
			** find papers
			** read books/chapters
			** write summaries of pieces related to goal
			** 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?
	* theory of visualization presentation		* theory of visualization presentation
	* vrl wiki tutorial		* vrl wiki tutorial
	* media wiki tutorial		* media wiki tutorial
	* augment a reading list		* augment a reading list
	* do some ~~reading~~		** find an expert (yourself, a professor, a student)
			** surf some course sylla
	* assignment 1		* assignment 1
	** spend 10 hours adding to any part of the wiki you think isrelevant		** spend 10 hours adding to any part of the wiki you think isrelevant

David Laidlaw: New page: * 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...

2009-01-23T04:01:52Z

New page: * 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...

New page

* 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
**o e.g., 7 plus or minus 2
** how?
** what other things do we know like that?
** can software that helps with all this, or just create ``best practices''?
* 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 HCI
** learn about the field of cognitive modeling
** learn about the field of scientific visualization
** learn about learning new areas targeted at a research agenda
** learn to work as a group
** learn to tersely summarize research papers
** be intellectually stimulated and excited
** have fun!
* class activities (see section below)
** build a research proposal
* structure of an NIH proposal
** specific aims
** background and significance
** preliminary results
** research plan
* theory of visualization presentation
* vrl wiki tutorial
* media wiki tutorial
* augment a reading list
* do some reading
* assignment 1
** spend 10 hours adding to any part of the wiki you think isrelevant
** by Monday noon add any potential 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 Wednesday noon finish with any summary evaluatio and also identify at least one as-relevant-as-possible reading as yours. 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 Friday 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 Friday 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 minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.
** by Friday class -- read and be prepared to discuss the other two readings you choose.
** by Friday class -- make one more wiki page titled "'''<Last-Name> week 1'''" with a list of the keys for the citations you added, the readings you summarized, the reading you presented, the two readings you were a discussant on, and any other readings you did in detail.
** Let me know if you have any kind of problems. You should be spending right around 10 hours -- if that's a problem, let's talk.
** The [[How Tos]] page has some tips. Edit or add as you find others.