CS295J/Assignments.11 - Revision history

David Laidlaw: /* Final Handin (due before leaving for holidays) */

2011-12-20T19:18:54Z

Final Handin (due before leaving for holidays)

← Older revision		Revision as of 19:18, 20 December 2011
Line 13:		Line 13:
	:# a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.		:# a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.
	:# the changes you would make to any other section (research plan, perhaps?).		:# the changes you would make to any other section (research plan, perhaps?).
			: Each individual should write their own proposal revision. Abstracts may be joint.

	== Public Presentation (scheduled for noon, Monday 12/19) ==		== Public Presentation (scheduled for noon, Monday 12/19) ==

David Laidlaw: /* Final Handin (due before leaving for holidays) */

2011-12-15T08:53:35Z

Final Handin (due before leaving for holidays)

← Older revision		Revision as of 08:53, 15 December 2011
Line 13:		Line 13:
	:# a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.		:# a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.
	:# the changes you would make to any other section (research plan, perhaps?).		:# the changes you would make to any other section (research plan, perhaps?).

			== Public Presentation (scheduled for noon, Monday 12/19) ==

			Each project will have a maximum of 10 minutes total time, including setup and questions. I recommend targeting 5-6 minutes for presentation allowing for ~3 minutes for questions. For the most part, structuring your presentation around conclusions often works best. Think about how to explain your conclusions to someone who hasn't been in the class with us. Practice with a friend to calibrate what they would need to know. Going through the sections of your written report typically does not make a great presentation.

	== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==		== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==

David Laidlaw: /* Final Handin (due before leaving for holidays) */

2011-12-15T08:49:37Z

Final Handin (due before leaving for holidays)

← Older revision		Revision as of 08:49, 15 December 2011
Line 1:		Line 1:
	== Final Handin (due before leaving for holidays) ==		== Final Handin (due before leaving for holidays) ==

	Your project ~~report~~ should ~~have~~ two ~~elements~~:		Your final project should produce two artifacts that you hand in:
	# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have discusses in class, the [[Write a paper]] page is a good rubric for evaluating your paper; it is what I will use.		# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have discusses in class, the [[Write a paper]] page is a good rubric for evaluating your paper; it is what I will use.
	# a short description of the changes you would make to revise proposal we structured the class around. The best examples I have of revised proposals are the "A1" and "A2" versions of the "DTI+MRI ..." NIH proposal we read early in the semester.		# a short description of the changes you would make to revise proposal we structured the class around. The best examples I have of revised proposals are the "A1" and "A2" versions of the "DTI+MRI ..." NIH proposal we read early in the semester.

David Laidlaw: /* Final Handin (due before leaving for holidays) */

2011-12-15T08:48:50Z

Final Handin (due before leaving for holidays)

← Older revision		Revision as of 08:48, 15 December 2011
Line 3:		Line 3:
	Your project report should have two elements:		Your project report should have two elements:
	# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have discusses in class, the [[Write a paper]] page is a good rubric for evaluating your paper; it is what I will use.		# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have discusses in class, the [[Write a paper]] page is a good rubric for evaluating your paper; it is what I will use.
	# a short description of the changes you would make to revise proposal we structured the class around. The best examples I have of revised proposals are the "A1" and "A2" versions of the "DTI+MRI ..." NIH proposal we read early in the semester.		# a short description of the changes you would make to revise proposal we structured the class around. The best examples I have of revised proposals are the "A1" and "A2" versions of the "DTI+MRI ..." NIH proposal we read early in the semester.
	~~This~~ should include at least		::* [http://vis.cs.brown.edu/docs/pdf/bib/Laidlaw-2004-DTI.pdf Original proposal]
	## a statement that would go in the introduction describing how your work addresses one of the criticisms in the reviews		::* [http://vis.cs.brown.edu/docs/pdf/bib/NIH-2004-DTI.pdf NIH reviews]
	## a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.		::* [http://vis.cs.brown.edu/docs/pdf/bib/Laidlaw-2004-DA1.pdf 1st revised proposal]
	## the changes you would make to any other section (research plan, perhaps?).		::* [http://vis.cs.brown.edu/docs/pdf/bib/NIH-2004-DRV.PDF NIH reviews]
			::* [http://vis.cs.brown.edu/docs/pdf/bib/Laidlaw-2005-DA2.pdf 2nd revised proposal]
			::Your description of changes should include at least
			:# a statement that would go in the introduction describing how your work addresses one of the criticisms in the reviews
			:# a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.
			:# the changes you would make to any other section (research plan, perhaps?).

	== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==		== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==

David Laidlaw: /* Final Handin (due before leaving for holidays) */

2011-12-15T08:32:11Z

Final Handin (due before leaving for holidays)

← Older revision		Revision as of 08:32, 15 December 2011
Line 2:		Line 2:

	Your project report should have two elements:		Your project report should have two elements:
	# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have		# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have discusses in class, the [[Write a paper]] page is a good rubric for evaluating your paper; it is what I will use.
			# a short description of the changes you would make to revise proposal we structured the class around. The best examples I have of revised proposals are the "A1" and "A2" versions of the "DTI+MRI ..." NIH proposal we read early in the semester.
			This should include at least
			## a statement that would go in the introduction describing how your work addresses one of the criticisms in the reviews
			## a few sentences that would go in the preliminary work section to summarize your project and to make clear how it supports the overall proposal by demonstrating feasibility, reducing risk, etc.
			## the changes you would make to any other section (research plan, perhaps?).

	== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==		== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==

David Laidlaw: /* Assignment 10 (out 30 nov 2011, due 1 dec 2011) */

2011-12-15T08:20:28Z

Assignment 10 (out 30 nov 2011, due 1 dec 2011)

← Older revision		Revision as of 08:20, 15 December 2011
Line 1:		Line 1:
			== Final Handin (due before leaving for holidays) ==

			Your project report should have two elements:
			# a 2-page extended abstract appropriate for a conference submission as a research result. There are examples on the web from cs295J in 2008 as well as from cs237 from the last several times it was run. As we have

	== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==		== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==


	For class tomorrow I had a couple of ideas. One was to follow-up on the blog that Caroline forwarded:		For class tomorrow I had a couple of ideas. One was to follow-up on the blog that Caroline forwarded:

David Laidlaw: /* Assignment 9 (out 15 nov 2011, due dates through 22 nov 2011) */

2011-11-30T19:53:25Z

Assignment 9 (out 15 nov 2011, due dates through 22 nov 2011)

← Older revision		Revision as of 19:53, 30 November 2011
Line 1:		Line 1:
			== Assignment 10 (out 30 nov 2011, due 1 dec 2011) ==

			For class tomorrow I had a couple of ideas. One was to follow-up on the blog that Caroline forwarded:

			:[http://blogs.msdn.com/b/b8/ Response to windows 8 feedback]

			What I thought was interesting was the references back to Fitts's law explaining why cascading menus are a problem and also motivating how Windows 8 will have some new tiles interface. So, please skim through that to get the gist of their perspective. Whether or not it's the right perspective we can discuss in class.

			A 2nd idea was to identify analogous interface annoyances and the perceptual, psychological, or cognitive principles that might explain them. So please try to come to class with a few examples akin to the ones we've already discussed (I.e., cascading menus and Fitts's law, overloading visual and verbal working memory, and some of the interface nudging that Radu Jianu did to address some cognitive biases issues).

			And the 3rd idea was suggested by Clara:

			:I found some interesting papers on user interface design/evaluation that I thought might be worth looking at. I'd like to learn about the cognitive and software-based reasoning behind testing and evaluation (i.e. what makes a "good" interface).

			:[http://www.sciencedirect.com/science/article/pii/S0953543809000952 HCI as a Science]

			:[http://www.sciencedirect.com/science?_ob=MiamiImageURL&_cid=271473&_user=489286&_pii=S016981410800053X&_check=y&_origin=&_coverDate=31-Jul-2009&view=c&wchp=dGLbVlS-zSkWA&md5=a1bfc0cbb86a04682b933e9e4edc9700/1-s2.0-S016981410800053X-main.pdf Web evaluation: Heuristics vs. Testing]

			:[http://delivery.acm.org/10.1145/1740000/1735255/p130-hwang.pdf?ip=128.148.231.16&acc=ACTIVE%20SERVICE&CFID=70946388&CFTOKEN=73407427&__acm__=1322668488_db84650217383e4037e757f19cfb3984 Issues with sample size]

			:( this one mentions 10+-2, but I think that 5 ±2 is the right answer in some contexts, as well. -- dhl)

			Please at least skim through all 3 of these before class and we will discuss in class.

	== Assignment 9 (out 15 nov 2011, due dates through 22 nov 2011) ==		== Assignment 9 (out 15 nov 2011, due dates through 22 nov 2011) ==


	* For Thursday, read and rate two InfoVis papers from the spreadsheet in preparation for in-class discussion. Be ready to give a brief summary of any of the papers you've rated.		* For Thursday, read and rate two InfoVis papers from the spreadsheet in preparation for in-class discussion. Be ready to give a brief summary of any of the papers you've rated.

Caroline Ziemkiewicz: /* Assignment 9 (out 15 nov 2011, due 22 nov 2011) */

2011-11-16T17:57:22Z

Assignment 9 (out 15 nov 2011, due 22 nov 2011)

← Older revision		Revision as of 17:57, 16 November 2011
Line 1:		Line 1:
	== Assignment 9 (out 15 nov 2011, due 22 nov 2011) ==		== Assignment 9 (out 15 nov 2011, due dates through 22 nov 2011) ==

			* For Thursday, read and rate two InfoVis papers from the spreadsheet in preparation for in-class discussion. Be ready to give a brief summary of any of the papers you've rated.
	* For Tuesday, bring large-format (at least 2x2 pages per real page taped together) printout of one- to two-page paper outline. Be prepared to discuss and augment during class. The research contributions and results are the most important parts to have made progress on. Related work is second most important.		* For Tuesday, bring large-format (at least 2x2 pages per real page taped together) printout of one- to two-page paper outline. Be prepared to discuss and augment during class. The research contributions and results are the most important parts to have made progress on. Related work is second most important.
	* Bring printout of David's [[Write a paper]] page with an evaluation of each point for your outline. Evaluate on a 1-10 scale, with 10 being the best.		* Bring printout of David's [[Write a paper]] page with an evaluation of each point for your outline. Evaluate on a 1-10 scale, with 10 being the best.

David Laidlaw: /* Assignment 9 (out 15 nov 2011, due 22 nov 2011) */

2011-11-15T18:59:22Z

Assignment 9 (out 15 nov 2011, due 22 nov 2011)

← Older revision		Revision as of 18:59, 15 November 2011
Line 1:		Line 1:
	== Assignment 9 (out 15 nov 2011, due 22 nov 2011) ==		== Assignment 9 (out 15 nov 2011, due 22 nov 2011) ==

	* For Tuesday, bring large-format (at least 2x2 pages per real page taped together) printout of one- to two-page paper outline. Be prepared to discuss and augment during class. The research contributions and results are the most important parts to have made progress on. Related work is second most important. ~~See~~ David's Write a paper page for ~~more thoughts~~.		* For Tuesday, bring large-format (at least 2x2 pages per real page taped together) printout of one- to two-page paper outline. Be prepared to discuss and augment during class. The research contributions and results are the most important parts to have made progress on. Related work is second most important.
			* Bring printout of David's [[Write a paper]] page with an evaluation of each point for your outline. Evaluate on a 1-10 scale, with 10 being the best.

	== Assignment 7 (out 20 oct 2011, due dates through 28 oct 2011) ==		== Assignment 7 (out 20 oct 2011, due dates through 28 oct 2011) ==

David Laidlaw: /* Assignment 9 (out 15 nov 2011, due 22 nov 2011) */

2011-11-15T18:57:48Z

Assignment 9 (out 15 nov 2011, due 22 nov 2011)

← Older revision		Revision as of 18:57, 15 November 2011
Line 1:		Line 1:
	== Assignment 9 (out 15 nov 2011, due 22 nov 2011) ==		== Assignment 9 (out 15 nov 2011, due 22 nov 2011) ==

	*		* For Tuesday, bring large-format (at least 2x2 pages per real page taped together) printout of one- to two-page paper outline. Be prepared to discuss and augment during class. The research contributions and results are the most important parts to have made progress on. Related work is second most important. See David's Write a paper page for more thoughts.

	== Assignment 7 (out 20 oct 2011, due dates through 28 oct 2011) ==		== Assignment 7 (out 20 oct 2011, due dates through 28 oct 2011) ==