ME 449 Projects 2012 - Revision history

Lynch at 23:17, 28 May 2012

2012-05-28T23:17:54Z

Lynch at 17:10, 28 May 2012

2012-05-28T17:10:54Z

Lynch at 17:10, 28 May 2012

2012-05-28T17:10:02Z

Lynch at 17:09, 28 May 2012

2012-05-28T17:09:00Z

Lynch at 17:08, 28 May 2012

2012-05-28T17:08:34Z

Lynch: /* Project List */

2012-05-18T21:27:03Z

Project List

Show changes

Lynch: /* Milestone */

2012-05-11T02:20:22Z

Milestone

Lynch: /* Milestone */

2012-05-11T02:15:32Z

Milestone

Lynch: /* Milestone */

2012-05-11T02:12:13Z

Milestone

Lynch: /* Project List */

2012-05-10T21:27:55Z

Project List

← Older revision		Revision as of 23:17, 28 May 2012
Line 1:		Line 1:
	'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu, {kmlynch, t-vose, jcryu}@northwestern.edu. All projects should be a zip file. At the top level of the zip file is your final project report as a pdf file (e.g., projectname.pdf ~~file~~) and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory with information on how to run the code. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''		'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu, {kmlynch, t-vose, jcryu}@northwestern.edu. All projects should be a zip file. At the top level of the zip file is your final project report as a pdf file (e.g., projectname.pdf) and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory with information on how to run the code. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''

	You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.		You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.

@@ Line 3: / Line 3: @@
 You will work in teams of two on your ME 449 final projects.  Each final project output will be a paper in two-column conference paper format.  Each paper should include a review of the assigned paper as well as a description of your new results.  For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible.  If your main project is to write code, then your report should give the results of some illustrative examples.
-A typical conference paper is 6 pages, though your paper can be anywhere from 4 to 10 pages.  Papers will be graded on the clarity of the review of the assigned paper, the quality and depth of the new results, and the quality of the presentation (good paper outline, logical flow of the paper, clear writing, clear introduction of all variables and necessary equations, good figures that support the notation and the results, etc.).  In other words, the kinds of things that are considered in reviews of conference papers.
+A typical conference paper is 6 pages, though your paper can be anywhere from 4 to 10 pages.  Papers will be graded on the clarity of the review of the assigned paper, the quality and depth of the new results, and the quality of the presentation (good paper outline, clear review of the assigned paper, clear problem statement for your project, logical flow of the paper, clear writing, clear introduction of all variables and necessary equations, good figures that support the notation and the results, etc.).  In other words, the kinds of things that are considered in reviews of conference papers.
 These projects are open-ended, and in some cases have not been done before by anyone (as far as we know).  Yet we expect that you can make progress on them.  The project is a chance for you to get deeply involved in a particular manipulation problem and see what you can do.  There will be no answer to the questions "Is this sufficient for the project requirements?" and "What do we need to do to get an A?" and "Is this even possible to do?"  You may need to modify your project description as you go, as you learn more about the problem.  In that case, you should alter your project so you can still say something significant.

← Older revision		Revision as of 17:10, 28 May 2012
Line 1:		Line 1:
	'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu, {kmlynch, t-vose, jcryu}@northwestern.edu. All projects should be a zip file. At the top level of the zip file is your ~~projectname.pdf~~ ~~file~~ ~~with~~ ~~your~~ ~~final~~ ~~report~~ (~~must be~~ pdf ~~format~~)and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''		'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu, {kmlynch, t-vose, jcryu}@northwestern.edu. All projects should be a zip file. At the top level of the zip file is your final project report as a pdf file (e.g., projectname.pdf file) and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory with information on how to run the code. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''

	You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.		You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.

← Older revision		Revision as of 17:09, 28 May 2012
Line 1:		Line 1:
	'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu ({kmlynch, t-vose, jcryu}@northwestern.edu). All projects should be a zip file. At the top level of the zip file is your projectname.pdf file with your final report (must be pdf format)and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''		'''Final projects are due by 9 AM Thursday of finals week (June 7). Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu, {kmlynch, t-vose, jcryu}@northwestern.edu. All projects should be a zip file. At the top level of the zip file is your projectname.pdf file with your final report (must be pdf format)and two directories, one named "code" and one named "source." If you developed code, that should be placed in the "code" directory. (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.) In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc. If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory. If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''

	You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.		You will work in teams of two on your ME 449 final projects. Each final project output will be a paper in two-column conference paper format. Each paper should include a review of the assigned paper as well as a description of your new results. For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible. If your main project is to write code, then your report should give the results of some illustrative examples.

@@ Line 1: / Line 1: @@
+'''Final projects are due by 9 AM Thursday of finals week (June 7).  Your projects should be mailed to Prof. Lynch, Tom Vose, and Ji-Chul Ryu ({kmlynch, t-vose, jcryu}@northwestern.edu).  All projects should be a zip file.  At the top level of the zip file is your projectname.pdf file with your final report (must be pdf format)and two directories, one named "code" and one named "source."  If you developed code, that should be placed in the "code" directory.  (Matlab is highly preferred; if you want to use some other language, be sure to check with Prof. Lynch first.)  In the "source" directory, you should put your paper source (.doc or .docx for MS word, or .tex and possibly .bib files for latex) as well as separate files for each figure in your paper (pdf, jpg, whatever), data (e.g., excel spreadsheet), etc.  If a movie is appropriate for your project, you can put it on youtube with a link in the paper, or you can put it in the "source" directory.  If your zip file is larger than 20 MB so the mailer refuses to send it, then your email to us should instead include the URL where we can download the zip file.'''
-'''The ME 449 final project is due by email to Prof. Lynch by 9 AM Thursday of finals week (June 7).'''
 You will work in teams of two on your ME 449 final projects.  Each final project output will be a paper in two-column conference paper format.  Each paper should include a review of the assigned paper as well as a description of your new results.  For most projects you will also include a piece of code (e.g., a simulation or analysis); you should use matlab if at all possible.  If your main project is to write code, then your report should give the results of some illustrative examples.

@@ Line 12: / Line 12: @@
 == Milestone ==
-'''Updated May 10:'''  In class on Tuesday May 22 and Thursday May 24, your group will have 10 minutes to present an overview of your assigned paper.  Your job is to summarize the results clearly and succinctly, so that others in the class can learn the key points in the paper.  (If the paper has many points, strategically pick a couple to emphasize that you think are most important.) At the same time, you will be demonstrating your mastery of the paper.  You can either use the projector or the blackboard, though given your limited time, the projector is likely to be the best option.  The milestone will be part of your final project grade.
+'''Updated May 10:'''  In class on Tuesday May 22 and Thursday May 24, your group will have 10 minutes to present an overview of your assigned paper.  Your job is to summarize the results clearly and succinctly, so that others in the class can learn the key points in the paper.  (If the paper has many points, strategically pick a couple to emphasize that you think are most important.) At the same time, you will be demonstrating your mastery of the paper.  You can either use the projector or the blackboard, though given your limited time, the projector is likely to be the best option.  The milestone will be part of your final project grade.  You will turn in your slides and/or notes for your presentation afterward.
 '''Tuesday May 22:''' Ansari and Natarajan; Singh and Trazkovich; Abbott and Kessler; Grant and Yeh; Lv and Leong

@@ Line 12: / Line 12: @@
 == Milestone ==
-In class on Tuesday May 22, your group will have 5 minutes to present an overview of your assigned paper.  Your job is to summarize the results clearly and succinctly, so that others in the class can learn the key points in the paper.  (If the paper has many points, strategically pick a couple to emphasize that you think are most important.) At the same time, you will be demonstrating your mastery of the paper.  You can either use the projector or the blackboard, though given your limited time, the projector is likely to be the best option.  The milestone will be part of your final project grade.
+'''Updated May 10''':  In class on Tuesday May 22 and Thursday May 24, your group will have 10 minutes to present an overview of your assigned paper.  Your job is to summarize the results clearly and succinctly, so that others in the class can learn the key points in the paper.  (If the paper has many points, strategically pick a couple to emphasize that you think are most important.) At the same time, you will be demonstrating your mastery of the paper.  You can either use the projector or the blackboard, though given your limited time, the projector is likely to be the best option.  The milestone will be part of your final project grade.
 == Sample LaTeX File ==

@@ Line 39: / Line 39: @@
 '''Stability measure for nonprehensile manipulation'''
+Alex Ansari and Keerthana Natarajan
 Paper:  [[Media:Maeda-Arai-ICRA2002.pdf|Maeda and Arai, ICRA 2002]]
@@ Line 46: / Line 48: @@
 '''Testing for inconsistent finger control modes'''
+Harman Singh and Alex Trazkovich
 Paper:  [[Media:Maeda-Arai-IROS2003.pdf|Maeda and Arai, IROS 2003]]
@@ Line 53: / Line 57: @@
 '''Two-dimensional impact'''
+Rebecca Abbott and Andrew Kessler
 Paper:  [[Media:Wang-Mason-JAM1992.pdf|Wang and Mason, Journal of Applied Mechanics 1992]]
@@ Line 60: / Line 66: @@
 '''Second-order form closure'''
+Tom Grant and Robbin Yeh
 Paper:  [[Media:Rimon-Burdick-TRA1998.pdf|Rimon and Burdick, Transactions on Robotics and Automation 1998]]
@@ Line 67: / Line 75: @@
 '''LCP simulation of the meter stick trick'''
+Zhen Lv and Yoke Peng Leong
 Paper:  [[Media:Berard-Egan-Trinkle-ICRA2004.pdf|Berard, Egan, and Trinkle, ICRA 2004]]
@@ Line 76: / Line 86: @@
 '''Dynamic rolling and sliding manipulation'''
+Jian Shi and Lu Xia
 Paper:  [[Media:Srinivasa-Erdmann-Mason-IROS2005.pdf|Srinivasa, Erdmann, and Mason, IROS 2005]]
@@ Line 83: / Line 95: @@
 '''Rolling simulation'''
+Antonio Moualeu and Yiming Shi
 Paper:  [[Media:Ryu-ICRA2012.pdf| Ryu, Ruggiero, and Lynch, ICRA 2012]] (the dynamic modeling part)
@@ Line 90: / Line 104: @@
 '''Sliding and bouncing'''
+David Meyer and Samhitha Poonacha
 Paper:  [[Media:Tuffilaro-Albano-AJP86.pdf|Tufillaro and Albano American Journal of Physics 1986]]
@@ Line 97: / Line 113: @@
 '''Stable transport of an assembly:  the waiter's problem'''
+Adam Barber and Vy Pham
 Paper:  [[Media:Mattikalli-TRA96.pdf|Mattikalli, Baraff, and Khosla, Transactions on Robotics and Automation 1996]]
@@ Line 104: / Line 122: @@
 '''Throwing together an assembly'''
+Zishuo Bai, Tim Rockers, and Andy Rosenkranz
 Paper:  [[Media:Yashima-JSDD2011.pdf|Miyashita, Yamawaki, and Yashima, Journal of System Design and Dynamics 2011]]