CS295J/Week 5.11 - Revision history

David Laidlaw: /* thursday class notes */

2011-10-06T16:07:33Z

thursday class notes

← Older revision		Revision as of 16:07, 6 October 2011
Line 38:		Line 38:
	*An Insight-Based Methodology for Evaluating Bioinformatics Visualizations		*An Insight-Based Methodology for Evaluating Bioinformatics Visualizations
	**could do this kind of evaluation with a scientist		**could do this kind of evaluation with a scientist
			*any input from brain scientists?
			**build into next assignment of draft proposal
			* critique a few revision comments
	*what kind of projects should we do?		*what kind of projects should we do?
	**recording and analysis of Eni using diffusion tract tools		**recording and analysis of Eni using diffusion tract tools
Line 47:		Line 50:
	**scope		**scope
	**research contribution AND/OR demonstration of feasibility or risk reduction		**research contribution AND/OR demonstration of feasibility or risk reduction
	* critique a few revision comments
	*concrete things to do		*concrete things to do
	**5-day project -- watch a few people do something potentially analogous		**5-day project -- watch a few people do something potentially analogous
	**draft proposal for a 50-day project		**draft proposal for a 50-day project
	**yes, we are somewhat clueless, but that is how research is sometimes		**yes, we are somewhat clueless, but that is how research is sometimes

David Laidlaw: /* thursday class notes */

2011-10-06T16:05:45Z

thursday class notes

← Older revision		Revision as of 16:05, 6 October 2011
Line 37:		Line 37:
	**the scary ambiguity of low level action and how it correlates to higher level intent -- BIG RISK -- can we ameliorate/demo? understand better?		**the scary ambiguity of low level action and how it correlates to higher level intent -- BIG RISK -- can we ameliorate/demo? understand better?
	*An Insight-Based Methodology for Evaluating Bioinformatics Visualizations		*An Insight-Based Methodology for Evaluating Bioinformatics Visualizations
	**		**could do this kind of evaluation with a scientist
	*what kind of projects should we do?		*what kind of projects should we do?
	**recording and analysis of Eni using diffusion tract tools		**recording and analysis of Eni using diffusion tract tools

David Laidlaw: /* thursday class notes */

2011-10-06T16:05:15Z

thursday class notes

← Older revision		Revision as of 16:05, 6 October 2011
Line 1:		Line 1:
			=== tuesday class notes ===

			* remaining papers from Thursday
			** continue to build on project ideas
			** what are the next steps?
			* draft or storyboard a usage scenario of a brain scientist using "the tool"
			* critique a few revision comments
			* pair up to work on some
			* critique the changes
			* feedback on class
			** superficial paper discussions, going too fast; do some in more depth?
			** maybe too much breadth -- connect back to a theme (or a few?)

	=== thursday class notes ===		=== thursday class notes ===
Line 35:		Line 47:
	**scope		**scope
	**research contribution AND/OR demonstration of feasibility or risk reduction		**research contribution AND/OR demonstration of feasibility or risk reduction
			* critique a few revision comments
	*concrete things to do		*concrete things to do
	**5-day project -- watch a few people do something potentially analogous		**5-day project -- watch a few people do something potentially analogous
	**draft proposal for a 50-day project		**draft proposal for a 50-day project
	**yes, we are somewhat clueless, but that is how research is sometimes		**yes, we are somewhat clueless, but that is how research is sometimes

David Laidlaw: New page: === thursday class notes === * Theory: implications for HCI leading Russian psychology approach should HCI progress be as fast as technological progress? **“Computer supported coope...

2011-10-06T16:02:17Z

New page: === thursday class notes === * Theory: implications for HCI **leading Russian psychology approach **should HCI progress be as fast as technological progress? **“Computer supported coope...

New page

=== thursday class notes ===
* Theory: implications for HCI
**leading Russian psychology approach
**should HCI progress be as fast as technological progress?
**“Computer supported cooperative work" (C S C W)
**this seems like a whole other set of literature
**object exist, not just as affordances
**actions, goals, motives -- frustration higher as each is blocked
**six inter-related principles: mind/environment, objects, hierarchical-, internalization-externalization, mediation, development
**I like the "other tools than computers" aspect, including social
**HCI methods (theories?) are "inevitably obsolete soon after they are formulated"
**I would like more concrete examples
*Spanning seven orders of magnitude: a challenge for cognitive modeling
**2002
**educational application: applicable to analysis?
**Biological, Cognitive, Rational, Social: 10ms to 10hrs
**Theses: Decomposition, Relevance (don't use quantum for bridges), Modeling, unit-task level useful
**need more work to establish relevance and modeling theses at lower levels (as of 2002)
**accessible writing
**observed tendency of humans to break things up into pieces of different sizes. interesting paper from last year talked about a bunching of tasks into units of attention, some number of minutes around 10 -- might have been 7 or 17 or 12?
**EPIC, SOAR, ACT-R/PM
**high-density sensing
**“read the error message”
**the scary ambiguity of low level action and how it correlates to higher level intent -- BIG RISK -- can we ameliorate/demo? understand better?
*An Insight-Based Methodology for Evaluating Bioinformatics Visualizations
**
*what kind of projects should we do?
**recording and analysis of Eni using diffusion tract tools
*** others did other similar ethnographic projects
***other user analyses: e-mail (low level, but decamp&modeling?)
**longer projects from last class (check on wiki)
*50-day Project criteria
**logical chain connecting it to brain science and connectivity and interaction and cognition
**scope
**research contribution AND/OR demonstration of feasibility or risk reduction
*concrete things to do
**5-day project -- watch a few people do something potentially analogous
**draft proposal for a 50-day project
**yes, we are somewhat clueless, but that is how research is sometimes

CS295J/Week 5.11 - Revision history

David Laidlaw: /* thursday class notes */

David Laidlaw: /* thursday class notes */

David Laidlaw: /* thursday class notes */

David Laidlaw: New page: === thursday class notes === * Theory: implications for HCI **leading Russian psychology approach **should HCI progress be as fast as technological progress? **“Computer supported coope...

David Laidlaw: New page: === thursday class notes === * Theory: implications for HCI leading Russian psychology approach should HCI progress be as fast as technological progress? **“Computer supported coope...