Important Steps and Deadlines
Spring 2017 semester projects schedule:
Date extended for students who did not sign-up on Dec. 18, 2016.
|Apr 3-7, 2017||Sign up to give an Oral Presentation|
|April 4, 2017||Attend "How to Write an IW Paper" 12:30 PM Rm. TBA|
|April 11, 2017||
Attend "How to Give an IW Talk" 12:30 PM Rm. TBA
|Apr 23, 2017||Submit Slides for an Oral Presentation|
|Apr 24-28||Give an Oral Presentation|
|May 5, 2017||Submit a Written Final Report|
|May 10, 2017||Submit a Poster|
|May 11, 2017||
Best posters from Fall 2016 are located outside of CS 105.
Theses/Two semester projects:
|Apr 3 -7, 2017||Sign up to give an Oral Final Presentation|
|April 4, 2017||Attend "How to Give an IW Talk" 12:30 PM|
|April 11, 2017||Attend "How to Write an IW Paper" 12:30 PM|
|April 24 - 28, 2017||Give an Oral Presentation|
|May 5, 2017||Submit a Written Final Report|
Fall 2016 semester projects schedule
|Sep 15, 2016|
|Oct 5, 2016|
|Oct. 24, 2016|
|Nov. 17, 2016|
|Nov. 28 - Dec.2, 2016|
|Dec. 1, 2016|
|Dec 11, 2016|
|Dec 12 - 16|
|Jan 10, 2017|
|Jan 11, 2017|
|Jan 12 - AM & PM Session||
Best posters from Spring 2016 are located outside of CS 105.
The Computer Science Department offers two styles of independent work advising: seminar and individual. The IW seminars allow students and a faculty adviser with shared interests to meet weekly as a group and optionally work on related projects. Students doing individual IW projects work on their own and schedule meeting with their advisors independently. All students except AB seniors are eligible to satisfy their IW requirements with either advising style. AB and BSE theses must be advised individually.
Most students who plan to do independent work for the first time should sign up for an IW seminar. Specifically, this includes all AB juniors and all BSE students signed up for COS 397/8 or 497/8 for the first time. Though the seminars will be targeted at first-time independent work students, they are open to any COS major who is not working on a senior thesis. The content of the IW seminars will include not only independent work on a project, but also guidance about how to choose projects, evaluate progress, design experiments, collaborate with others, make presentations, and other project management skills. These skills are essential for becoming an effective researcher, and provide great training for working in a company or startup. Thus, the IW seminars are perfectly suited for students doing independent work for the first time. A list of IW seminars for the upcoming semester with titles and abstracts is provided to help you choose amongst the IW seminars. The instructors and topics may change every semester.
If you already have done a previous semester of independent work, or if want to work on a project outside the scope of the topics offered in any of the IW seminars, then you can make arrangements with a Princeton faculty to advise you individually. To do so, contact the faculty that you would like to work with to discuss potential project ideas well before the semester starts (and certainly before the IW Sign Up deadline). Initial inquiries are probably best by email, with in-person meetings to discuss possible project topics as a follow up. A list of Independent Research Projects and Faculty is provided to help you choose advisors to contact. Faculty will be updating this web page with new research ideas all the time. Also check out web pages and research project pages for faculty whom you know or have taken their class. Please note that any Princeton faculty can be the advisor for your COS independent work, as long as there is a significant computer science component to your project (check with the IWCs if you are not sure). In fact, many students have done inter-disciplinary projects in the past, often advised by faculty in another department or co-advised with a COS faculty. Note that the list linked above includes non-CS faculty who have done research with CS students in the past or are looking to do interdisciplinary projects with CS students in the future.
How to Submit: Once you have selected IW seminars or found an individual project and advisor, you must indicate your selections by filling out the IW Sign Up form. The form asks you to choose one of the following options:
_ I will be in an independent work seminar next semester
(the usual choice for first-time IW students)
_ I will be doing one-on-one research with a professor next semester
(the usual choice for senior BSE students with previous IW experience)
_ I will be doing a senior thesis this year
(the usual choice for senior AB students, plus some senior BSEs)
_ I will not be doing any form of independent work next semester
If you select the first option (you will be in an independent work seminar), then you will be asked to indicate which seminar(s) you would like to take in the "Independent Work Seminar" section of the IW Sign Up form. The form will ask you to enter your ranked preferences for every seminar (like you did for the writing seminars during freshman year) and optionally provide a paragraph of text describing your interests in independent work. Then, we will use that information to match you to the best seminar, doing everything we can to assign your top choice. You will be notified of your assignment before the semester starts.
If you select the second or third option (you will be advised individually), then you should fill out the "Independent Work as an Individual" section of the IW Sign Up form. You will have to provide the name of the faculty who has agreed to advise you with a tentative title and 100-200 word description of your planned project. Please work closely with your faculty advisor before the IW Sign Up form deadline to work out as detailed a project plan as possible.
You can revisit the IW Sign Up form as many times as you like to adjust your selections. If you do not fill out the form before the deadline, then you will be assigned an IW seminar or individual advisor at our discretion.
During the first few days of the semester, we will have a meeting to explain the key requirements, review the schedule for the semester, and provide information about the seminars. Attendance is mandatory for all students starting IW that semester. Here are slides from the most recent meeting.
During the second half of the semester, there will also be meetings to provide students with information and guidelines about "how to give an IW talk" and "how to write an IW paper." These sessions will provide critical information about what content to include and what formating to use for your work. They are mandatory for all students doing IW for the first time.
The McGraw Center for Teaching and Learning
The McGraw Center for Teaching and Learning will have a representative in the E-Quad beginning Feb 8, 2017 on Wednesdays 11:30am-1:30pm Room C-205 (just outside Dean Bogucki’s office) for Independent Work Learning Consultations.To schedule an engineering consultation with Christopher Chen, please visit https://mcgraw.princeton.edu/undergraduates/learningstrategies-consultations/schedule-consultation at least 24-hours in advance in order to give him time to prepare. Wednesdays aren’t good? Sign up for a one-to-one session in the McGraw Center (328 Frist) at the link listed above or email firstname.lastname@example.org. The McGraw Center can also help with: Self-regulation and time management Avoiding perfectionism and overcoming procrastination Dealing with large projects Engaged and active reading Advanced problem-solving Effective note-taking Exam preparation
Three or four weeks into the semester, you must submit a 1-2 page written proposal describing your intended project plan. The written proposal should have the following sections:
- Title. Include your name, class, project title, and advisor.
- Motivation and Goal. Give a high-level introduction to your topic area and state specifically what problem you will be addressing. You should clearly state the goal of your project with a sentence beginning “The goal of my project is …”. Explain why that goal is important and/or interesting, perhaps with a description of applications or people enabled by achieving it.
- Problem Background and Related Work. Place your project in context of prior work. Give some background of what has been done before to achieve your stated goal. Include citations to closely related academic papers and/or list commercial products targeted at the same goal. Finish this section with a brief explanation of the problem unsolved by previous work that will be addressed by your project.
- Approach. Provide a concise description of the key idea underlying your approach to achieving the stated goal. Provide an argument of why your approach is a good idea – i.e., why it can achieve the stated goal where others have not.
- Plan. Describe the steps you plan to take and/or the issues you plan to address during the execution of your project. What data sets will you have to acquire? What algorithms will you have to develop? What theorems will you have to prove? etc. For the steps that are non-trivial, provide a brief description of the issue, options, and planned approach. Please indicate any particularly risky aspects of the project and discuss contingencies in case they do not go as planned.
- Evaluation. Describe the methodology you plan to use to evaluate how well your project has achieved the stated goal. Be specific. What data will you use? What test will you run? What quantitative metric will you use to measure success? etc. This is a very important and often over-looked aspect of a project plan – please think about it before finalizing your project selection.
How to Submit:
- Create a PDF file named "written_project_proposal.pdf"
- Submit the PDF file via this CS dropbox link
- Email the PDF file to your advisor
By the Monday of midterms week, you and your advisor must fill out a checkpoint form. The purpose of the form is to make sure that you are making good progress on your project. It serves as a checkpoint to provide feedback to you and to the department about whether are making consistent progress, whether you should meet with your advisor more often, and/or whether there are any potential roadblocks to completing the proposed project.
Preparing the checkpoint document is not supposed to be difficult or take much of your time. All you must do is write a brief description of what you have accomplished so far and what remains to be done. The checkpoint form is divided into three parts:
- Progress to date: Mention any ideas you have had, software you have built, related research you have evaluated and papers or textbooks you have read.
- Current difficulties: If you are having difficulty making progress on your project due to some obstacle, explain the obstacle and a plan for overcoming the problem.
- Next steps: Detail how you anticipate proceeding for the rest of the term.
As a guideline, you should be meeting approximately weekly with your advisor and updating him/her on your progress. Of course, this will happen naturally if you are in an IW seminar. If not, setting up a schedule to meet your advisor every week at the same time is highly recommended. Failure to meet with your advisor will almost certainly cause you to get behind schedule and could even cause you to fail the course if you do not make good enough week-by-week progress. As a rule of thumb, try to allocate 6-10 hours of time per week for progress on your independent work project.
How to Submit:
- Complete the midsemester checkpoint form via the iw portal well in advance of the deadline.
- Your adviser will receive an email notifying them that you have submitted the form with a link for their feedback,
- Adviser will review your checkpoint form and add their feedback/comments by March 17, 2017.
During the last week of the semester, you must give a presentation describing your project to a small group of people. There are four steps that you must complete: 1) sign up for a time slot, 2) upload slides in advance of your talk, 3) give your presentation during your time slot, and 4) provide feedback to the other presenters within the same time slot.
Slides: You can make your presentation in any presentation tool (e.g., Keynote or PowerPoint), as long as it can export PDF. Although many talk organizations are possible, it is strongly recommended that yours adhere to the following outline:
- Title slide. Include your name, class, project title, and advisor.
- Motivation and Goal. Give a high-level introduction to your topic area and state specifically what problem you will be addressing. You should clearly state the goal of your project (i.e., “The goal of my project is …”). Explain why that goal is important and/or interesting. What people and/or applications would benefit? Giving some examples of the problem being addressed may help make it easier to understand.
- Problem Background and Related Work. You probably are not the first person to work towards this goal, nor will you be the last. Give some background of what has been done before. Have academics already written papers on this topic? Are there already products on the market? Why do they not solve the problem? What aspects of the problem are still uninvestigated? It is always the case that someone has done something that can be related to what you are going to do. Find out the most closely related pieces of work and explain the relationship to your proposed project.
- Approach. Clearly explain the key idea behind the approach you are taking and explain why it is a good idea. What is your key insight to solve the problem? What makes your approach unique in comparison to previous work? It might be that you are asking a different question than others have before, or attacking the problem in a different way, or using different tools, or leveraging different data sets. In any case, describe the most interesting “key idea” behind your project and justify why you chose it.
- Implementation. Describe the steps you have completed and/or the subproblems you have solved to make progress on your project. For each of them, you may want to describe: What was the main issue? What options were available? What solution did you create/choose and why? How did you perform the implementation? What tools did you use? How well does your solution work? What is remaining to be done? If your implementation is not complete, outline any logistical or technical problems you anticipate and explain any contingency plan you have for avoiding or coping with them.
- Results. Every project should have some means of measuring success. Explain the methods you will use to evaluate how well your implementation achieves the goal articulated at the beginning of the talk. Perhaps you will need to describe your test data sets, your measurement techniques, your evaluation metrics, etc. If possible, provide some quantitative comparisons of your results to alternative methods (e.g., the previous state-of-the-art, random results, etc.). Part of (not the entire presentation) may involve giving a demo of your results.
- Conclusion. Sum up the most important aspects of the talk concisely.
Note that some of the points may not be relevant for some types of projects, and others will probably require more than one slide. Please do not feel constrained by the number of slides, and do not feel that you have to address every point raised above. Please tell a coherent story about what you are trying to do, how you are doing it, and how well your solution works …. while staying within the time limits.
Please use images or graphics to support your points wherever possible, minimizing the use of text on slides. In particular, please do not put all the text you will say on your slides – so boring. The text on slides should be short sentences or phrases that convey key points after a quick glance, not sentences and paragraphs that provide the entire script for the talk. Many excellent research talks are composed almost exclusively of pictures and graphs.
Your slides should be well-organized, uncluttered, easy to read, and visually appealing. Most presentation programs have some pre-packaged slide backgrounds, etc., that have reasonable color/font schemes for text, bullets, etc. You should probably use them but do not use an overly-gaudy background that distracts from the content of your slides. Similarly, don't use clipart and animations gratuitously just to make your talk zippier. The slides should convey the content as clearly as possible without distractions -- how slides are organized, sized, colored, etc. are important aspects of the presentation, as they have great effect on the ease with which a viewer can follow your ideas.
Presentations in the Fall will be given to an audience of at least one instructor and several other students. All projects will have nine (9) minutes long for the talk, plus three (3) minutes for questions. If your talk is too long you will be cut off in the middle – so manage your time carefully!
Presentations in the Spring will be given to an audience of at least one instructor and several other students. For one-semester projects, you will have at most nine (9) minutes long for the talk, plus three (3) minutes for questions. For two-semester projects, you will have at most twelve (12) minutes for the talk, plus three (3) minutes for questions. If your talk is too long you will be cut off in the middle – so manage your time carefully!
Please read the section on giving a good talk to prepare. Also, be sure to practice in advance, by yourself and if possible to your friends, and to go over your talk with your advisor. Your advisor will be able to give you good feedback on both the content and the style of presentation. You will be assessed on both the proposal content and the clarity and effectiveness of your presentation. You should not assume that the audience has a specialized knowledge of your field. Assume your audience is a group of senior undergraduates from Princeton who have not necessarily taken the courses that are most closely related to your research area.
Feedback will be provided by both an instructor and other students. You are expected to stay for and pay attention to all of the talks in your one-hour time slot and fill out a feedback form for each one. You will give the forms to the other students in your group to provide them tips that will help them improve their presentation skills.
How to Sign-up for a Time Slot:
- Sign up for a one-hour time slot for your presentation via WASS. During your time slot (starting and ending on the hour), your talk will be one of approximately five. Please plan to stay for the entire hour and listen closely to the other talks.
How to Submit Slides:
- Create a zip file named "oral_presentation.zip" containing all the files needed for your talk
- THIS MUST BE SUBMITTED IN THE REQUIRED FILES SECTION IN DROPBOX
- Submit the zip file via this CS dropbox link by midnight on the day before your talk
- Email a PDF file with your slides to your advisor
Every thesis must have both an adviser and a second reader. The second reader reviews your thesis and provides input to your grade. So, you may want to choose and involve a second reader early in your project. If your adviser is a faculty member who is not in the Computer Science Department then your second reader must be a faculty member in the Computer Science Department.
How to Submit:
- Complete the second reader form, please log into the iw portal
Students doing 2-semester IW or a Thesis must submit a written draft paper. This is not expected to be a full thesis, but it should include a complete outline and give you some practice with technical writing. It should be at least 4-5 pages long (single-spaced).
You should discuss the exact requirements for the paper with your advisor. However, in general, the paper might contain (one or more of) the following components:
- Background information and problem description. What is the general area of research and the specific problem that will be tackled?
- Related research. Have there been previous academic papers on this or related topics? Are there companies that have developed related software products? What is the historical context? Be sure to cite related research properly. Include a bibliography at the end of your paper.
- Progress so far. Explain your major accomplishments so far. Be as precise as possible. What papers have you read? What are they about? Give examples, charts, diagrams and proofs to back up your ideas wherever possible and appropriate. What new algorithms have you defined? -- describe them in detail if they are sufficiently interesting and novel. Have you defined your overall software architecture? -- describe it in detail and justify your design. Do you intend to prove something about your research? -- Give a proof outline. Have you proven any intermediate theorems or lemmas? State what they are and explain the proof.
- Plan for the remainder of the year. Outline the steps you will take to complete your thesis. Explain how you will evaluate your results. Include a table with a concrete set of deadlines for finishing major components of the project. Include at least 3 weeks for writing.
If you do a good job on writing your draft, you can reuse this material as a chapter of your final thesis. For example, the paper could be the introduction of your final thesis or the related work section of your final thesis.
How to Submit:
- Create a PDF file named "draft_paper.pdf"
- Submit the PDF file via this CS dropbox link
- Email the PDF file to your advisor
Every IW project will result in a written final report describing the goal(s), related work, approach, implementation, results, and conclusion of the project, using much the same outline as suggested for the Oral Presentation. Unlike the oral presentation, which must be extremely concise due to time constraints, the written report can delve into more details, cite all relevant previous work, present results of many experiments with tables and plots, etc.
The written final report should look like a professional document -- 12pt Times-Roman font, 1-inch margins, double-spaced. Here is a template for some formatting guidelines, and here are the files used to produce such a document using LaTeX and BibTex. It should contain a proper bibliography, and all non-original text should be properly attributed. Failing to cite appropriate sources for ideas, tables, text or diagrams is a serious violation of Princeton's code of ethics. If you are unsure about how to cite ideas or research papers properly and create a bibliography, speak with your advisor -- they can tell you exactly how to do it. Your report will be graded on the basis of its technical content, organization, creativity of ideas, and quality of writing. (The Princeton Writing Center is another resource for assistance with writing a research paper.)
The final written reports for one-semester projects should be 20-25 pages long. Theses should be 40-50 pages long. Relevant charts, tables, diagrams, etc., should be included, with accompanying captions. Be sure to refer to each such chart in the main body of the text, clearly explaining its nature and purpose. The technique of "padding" papers using multiple, overly-large figures is well-known, and should be avoided. If you have lengthy code or auxiliary examples or detailed algorithms or long proofs or supplementary data of other kinds, it may not be appropriate to include this in its entirety in the main body of your report. However, you are encouraged to include such auxiliary data (if you feel it is appropriate) in a final portion of your report clearly labeled "Appendix." The Appendix may be as long as is necessary -- it may extend beyond the page limit.
Talk to your advisor about how to write your final report. It is usually best to start writing the report early in the semester and refine it continuously throughout the semester. Talk to your advisor about exactly what they are looking for in your report. The best reports are prepared with enough time for the adviser to read over a draft and give comments for revision.
For additional resources about how to write the report, here are some slides on how to write a good research paper, and here are lists of example single-semester project reports and two-semester theses from previous years. .
For additional help, note that The Writing Center offers student writers free, one-on-one conferences with experienced fellow writers trained to consult on assignments in any discipline. The Princeton Writing Program also offers resources for writers in a broad range of technical fields through Writing In Science and Engineering (WSE).
How to Submit:
- Create a PDF file named "written_final_report.pdf"
- Submit the PDF file via this CS dropbox link
- Email the PDF to your advisor
Every non-thesis independent work student will produce a "poster" or poster-like display for the final poster session. The poster session is typically held in the Friend Center Convocation Room. There will be one poster session in January for Fall independent work students and one poster session in May for Spring independent work students.
Poster Logistics: Usually, each student will have 1 side of a bulletin board that is 4ft by 4ft to mount their display. Most people will have conventional posters as displays. However, we encourage students to come up with new and creative ways to communicate the intellectual content of their theses to other students and faculty. Thumb tacks for mounting conventional posters will be provided for you. If you are considering something unconventional, please check with the UGC and IWC well in advance to determine if the idea is feasible. In general, space is limited so while creative ideas are wonderful, they need to fit in the same space as a conventional poster presentation.
Poster Spiel: During the poster session, various faculty and other students will walk from poster to poster. When a faculty member or student arrives at your poster, you should be prepared to give them a clear, interesting, 3-minute explanation of your project. Think of it like a miniature, informal presentation. Your spiel should be well structured: introduction (set the context, explain the main goal of the research) followed by technical details of how it works (what did you build? what did you prove? what was the interesting tricky bit that will catch people's attention?) followed by any results (experimental data, demo, proofs) followed by related work, future work and a conclusion. You don't have to have such a spiel memorized. In fact, it is often better not to because it will seem more natural. However, it is useful to think about and practice what you might say.
Poster Content: During the poster session, faculty and students will wander from poster to poster and engage you in conversations about your research. Therefore, each poster should be created in such a way that best helps you explain the intellectual content, importance, creativity, and overall "coolness" of your IW project to a faculty member or student working outside your area of research. Like a good research talk, you should start any conversation with a faculty member with a high-level explanation of the basic problem you are solving and why it is important. Once the faculty member understands the problem, you should move on to explaining the most interesting elements of your solution to the problem. After explaining the basics of the solution you can move on to discussing any experiments or proofs you have done to evaluate or validate your ideas. Do not be afraid to explain negative results in which experiments showed that your ideas did not necessarily pan out as you thought they might. Sharing negative results is a part of good science. Remember that like in a good talk, pictures, graphs, and charts are often worth 1000 words. Also remember that like a good talk, a poster presentation must be practiced in order to be effective. Give practice presentations to your advisor and your friends. Have your friends try to think of difficult questions for you to answer in the middle of your presentation so you are prepared. You should be ready to give a three minute presentation, a five minute presentation or a fifteen minute presentation to a faculty member who walks by. Give me a punchy three minute spiel on why your work is great. Other faculty will only visit a subset of the posters and will spend more time with each presenter.
Example Poster: Here is an example of a poster. Here is another example of a poster, this time as a PowerPoint file so you can use it as a template that you can edit to include your own content. However, you do not need to emulate the style; these are just examples.
Demos: If you would like to do a demo of your project, you may bring your own laptop as well as your own stool (or stack of boxes or other contraption) to support your laptop next to your poster. Note that demoing your software does not replace the need for you to create a poster. If you need power, or want to do some kind of more elaborate set up of devices, you should check with the IWC and UGC to get their opinion as to whether it will work... Space is the main constraint during the poster session. We will do what we can to make your ideas work. However, we do need some advance warning. If you have creative ideas, please consult with us via email prior to the demo scheduling deadline. If you do not send us email by the deadline, we may not have space and/or be able to give you access to power or other things you need in the Convocation Room.
Printing posters. WARNING: Don't wait until the day before to figure out how to create and print your poster -- you will be out of luck! No excuses about being unable to create a poster on time will be accepted. It is your responsible to figure how to do it and get it done on time. Here are some options for creating posters:
- Simple I: Print out a series of slides and pin them up individually to the 4ft by 4ft bulletin board that will be provided for you. Surrounding each individual slide by colored construction paper looks good.
- Simple II: Print out a series of slides and glue or tape them on to poster board. Pin up the single poster on your bulletin board.
- Large-Format Printers: Create a single large PDF or PowerPoint slide with all the information you want on your poster like this one and print it at one of the large-format printers on campus. One option is Print Services, who have a large-format printer and student pricing. Another option is PRISM Poster Printing but they fill up quickly in the few days before the poster session.
- Award winning posters are located in the halls of the Computer Science Building the most recent winners are located outside of CS 105 in the banana gallery.
- FedEx Office (Kinkos), Triangle, etc (or other commercial copying facilities): Often have facilities for printing posters, but tend to be expensive, in the $50-$100 range.
Awards: One additional goal of the poster session is to help the faculty identify award-caliber independent work. Awards may be given out for the best Senior Thesis and best Junior and Senior Independent Work as well as the best Demo or best Poster.
How to Submit: In addition to presenting your poster, you must do the following before the poster session:
- Create a PDF file of your poster named "poster.pdf"
- Submit the PDF file vis this CS dropbox link
- Email the PDF to your advisor