CS6742 Fall : Final-project proposals

This page last modified Important updates will be posted to Piazza;

Goal: help you complete a successful final project by the end of the semester, one that we hope can eventually become a research publication. (Keep in mind the submission deadlines for ICWSM 2017 and ACL 2017, both a little after the end of the term.) This goal is what motivates the requirements below.

Now that you have had exposure to a variety of topics and have developed at least three small project proposals in this course, you should be in a good position to formulate your final project proposal. (That's intentional ambiguity as to what the word "final" is modifying, there).

Your proposals (and hence projects) should be done in teams, but teams consisting of a single person are fine. Henceforth, the words "you" and "your" refer to a team.

Proposal content requirements: we are expecting 3-4 paragraphs. The following must be included:

• At least one clear and concrete hypothesis (emphasize and number hypotheses with H1, H2, etc.)
• Identification of at least one appropriate data source (which you have access to or can easily obtain and use for research)
• An indication of what language features you plan to employ
• A plan for at least one concrete feasibility test. You technically need not have started the test by the time you submit, although we strongly recommend that you do start such tests before submitting; that will not only help you hone your proposal, but as a pragmatic matter, the test will need to be done by your mandatory feasibility discussion.
  • An example of a feasibility test is the shuffling test that I described in the coodination lecture. (Remember that that was a real-life example; feasibility testing is an instinct and skill you want to develop as a researcher.)
  • Other possible examples: some counts from your data source showing that there are enough examples of the phenomenon of interest; an initial check that a first cut of a sentiment classifier you intend to use has sufficient accuracy on (samples of) your data.
• A listing of the members of your team, and acknowledgments of sources of other input/inspiration - For example, if you were inspired by a particular reading, cite it; if your proposal incorporates work or ideas you've already talked about (or plan to talk about) with other students/your advisor/an internship mentor/the instructor of another class/or so on, give the names of all such people.

Your proposal can be based on proposals previously submitted for this class by you or others (I am indeed hoping that some of the proposals you've come up earlier will blossom into full-blown projects!); if so, your proposal should reference the respective piazza post and incorporate any feedback that was given.

Deadlines: In all cases, we recommend trying to finish each milestone ahead of its deadline.

• (Optional) Before Thursday the 13th: if you want to talk in-person with about your ideas, you can make an appointment for Thursday the 13th during class hours in the usual classroom; to do send me an email with subject line "CS6742 optional proposal appointment Thursday 13" by October 12th at 3pm. If you need additional feedback, you can also see during regularly-scheduled office hours (slots also need to be booked in advanced); see my website for details. These appointments are all optional.
  • Because of this activity, you do not need to come to class on Thursday the 13th. ( will be there regardless)
• Friday the 14th, 3pm: Post your proposal to Piazza, as a "Question".
• [Between the proposal posting and the next deadline: give each other helpful feedback on Piazza. If it seems like some teams should merge based on the posted proposals, arrange this among yourselves and update the Piazza proposals accordingly.]
• (Optional) Before Tuesday the 18th: if you want to talk in-person with about your existing proposal and the feedback you received, you can make an appointment for Tuesday the 18th during class hours in the usual classroom; to do that, send me an email with subject line "CS6742 optional proposal appointment Tuesday 18" by October 17th at 3pm. These appointments are optional.
  • Because of this activity, you do not need to come to class on Thursday the 18th. ( will be there regardless)
• Wednesday the 19th, 11:59pm: Post your feasibility-check results as a "resolved" followup to your proposal on Piazza.
• Come to mandatory feasibility-checks appointments be held on Thursday the 20th and Tuesday the 25th during class hours in the usual classroom. You will be presenting/discussing the results of your feasbility check with only. (Once I know the number of groups and their composition I'll assign each group to one of these two days. If you have strong preferences---e.g., due to travel or deadlines---, let me know by Tuesday 18 and I'll do my best to accomodate them; check implications on next deadline as well.)
• Because of this activity, you do not need to come to class on Thursday the 20th or Tuesday the 25th except during your appointment slot.
• Friday the 21st, 3pm (if your feasibility-check appointment was on Thursday the 20th) or Wednesday the 26, 3pm (if your feasibility-check appointment was on Tuesday the 25th): Submit to Piazza a short commitment statement: "what do I promise to accomplish on my project next week?". Do so as an unresolved followup to your proposal.
• The week after that: Do what you committed to. State the results as a reply to your followup, and mark the commitment followup as resolved.

Assessment criteria: Proposals: thoughtfulness, creativity, and feasibility are most important to . On-time completion of all requirements will be factored in.

• Extra "karma" will be awarded for thoughtfulness and creativity of the feedback you give to others on Piazza.