Submission Link (in-person section): https://blackboard.umbc.edu/ultra/courses/_96481_1/outline/assessment/test/_8407431_1?courseId=_96481_1&gradeitemView=details
Submission Link (online section): https://blackboard.umbc.edu/ultra/courses/_98413_1/outline/assessment/test/_8407383_1?courseId=_98413_1&gradeitemView=details
It makes it easier to grade if one person from each section (online and in-person) submits.
Please be sure to double check the academic integrity and generative AI policies listed on the syllabus.
Examples from my previous AI class: Here
Project Milestone 4: Final Submission
Here are the requirements for the final submission of your project. Please refer to the appropriate section below for your project type.
How will the presentation day work?
Getting Ready
- Posters should be size 22 x 34. This can be 22” tall and 34” wide or vice versa.
- The CSEE department has generously agreed to pay for and print the posters.
- I have provided a Powerpoint poster template for you to use. You’re welcome to adapt it as much as you like except make sure to keep it 22 x 34 (or 34 x 22). It’s currently set to 22 x 34.
- You are not required to use the template at all, but make sure it’s the correct size. You can also make a poster in LaTeX, if you prefer.
- If you want Dr. Martin to look at your poster before you print it, be sure to give them a couple days before you want to print it.
- Please email your poster to Geoff Weiss and Skye Jonke by noon on December 10.
- Save your poster as a pdf before sending it to Geoff & Skye.
- In addition to emailing the poster to print, please submit the pdf on Blackboard.
- Your poster will be ready by 5:30pm on December 10th in ITE 325 by the front desk. It will need to be trimmed. Please pick up your poster and trim it before coming to the presentation day on December 11th. Please let Lara know if you can’t pick the poster up during business hours (9am-5pm) so she can get it for you.
Here are some example posters from previous classes that I liked:
On Presentation Day
- Posters will be either attached to the walls or presented on easels around the room (ILSB 116A).
- Please be in ILSB 116A on time or a bit earlier!! (10:30am on December 11th)
- The presentations will be open to the university, broadly, but mostly focused on CSEE folks.
- Within your team, designate some members to be “group 1” and the rest to be in “group 2”. The first half of the time group 1 will present and group 2 will walk around and look at other posters/demos. Everyone will switch halfway through so that you all get a chance to see each other’s work. You don’t have to tell us who is in which group; this is just to let you know what’s going to happen on presentation day.
- There will be a voting box where visitors can vote for their favorite presentation(s). The team with the most votes will get 2 points of extra credit on Milestone 4.
- For demo teams: Please bring a laptop and charger, and have your demo ready to be played with.
Poster Grading
The posters will be graded on two main criteria:
- Content: (8 points) The poster contains enough relevant information that someone can get the highlights of the project without you necessarily presenting (although you will still be presenting it).
- Information is written in clear language.
- Contains: 1) an introduction to what you did, 2) information about the methods/system, and 3) any results/discussion (for paper teams) or takeaways (for demo teams).
- Visuals: (4 points) The poster contains relevant visuals without overwhelming the reader, and the text organization is nicely displayed and not too “wordy”.
Demo: Build a novel NLP system
The final deliverable is the demo itself, a video presentation, and a supplemental document. Your demo should be a complete program that can run end-to-end.
Your demo should:
- Be runable by the grader, following the read me.
- Be posted on GitHub (or the repository site of your choice).
- Not be edited after the deadline. We will be grading the last commit pushed before the deadline.
In a separate document called team#-supplement.pdf, provide the
- system diagram, updated to include any changes you made
- LLM Use Statement - Describe exactly how you used LLMs to generate parts of your code (refer to the syllabus for guidance). If you did not use any generative text, please state so in this section.
You no longer need to mention who did what on your team.
What to Submit
- The link to your repository.
- The link to your video.
team#-supplement.pdf, the LLM use statement.
Grading
You will get full points if you 1) include all of the material listed above and 2) incorporate the feedback you got from the previous submission.
- Poster Content - 8 points (See description above.)
- Poster Visuals - 4 points
- System Diagram - 5 points - Updated to reflect your final system. This can also be put into your presentation slides, if you want.
- Minimal bugs - 5 points - Runs from beginning to end with minimal bugs (1-3 bugs, depending on the size/type of bug).
- Completeness - 10 points - The demo does what the previous milestones’ architecture claim it would do (within reason).
- Read Me - 3 points - A short document explaining what your system is, and how to setup and run your demo. Put this readme in the README.md file of your repository.
- LLM Use Statement - 1 point
Total: 36 points
Paper: Investigate an NLP research question
The final deliverable is the paper itself, a video presentation, and a supplemental document. The paper will be a continuation of the same one you’ve been building on.
Here are some example reports from previous classes again to aid you:
Your paper needs to be in a conference template, written in LaTeX.
- You can use Overleaf to write LaTeX papers together. The CSEE department has a subscription to Overleaf now, so you should be able to have multiple collaborators on the same paper.
- If you do not have a conference/workshop in mind, I recommend that you use the template from the Association for Computational Linguistics.
Your paper should include the following sections:
Note that at this stage the questions below are guiding questions. Do not include the questions themselves in your paper and make sure that what you write in each section builds to be one cohesive section. Your content in each section should contain information beyond these questions as well.
Science 101
A research question should be something that can be proved true or false. An example of a bad research question might be “Which dog is the best dog?” because it cannot be rejected (i.e., null hypothesis).
A better way to rephrase this—by potentially looking at the same problem—would be to ask “Is Pharaoh a good dog?”. This can then be tested. You just need to define how to measure “goodness” in this case.
Your paper should have the following components, in order:
- Title: What are you calling your study?
- Abstract: A high-level overview of the paper and what people should take away from it if they aren’t reading the whole thing.
- Introduction: What research question(s) or problem are you trying to solve? (Start numbering sections from here.)
- Why this it worth researching?
- What contributions does this work make? (i.e., What are you doing that’s novel?) You might have to compare to other research.
- Related Work: What previous research has been done on this research question?
- A narrative of 8-10+ related research papers, including how each of them is relevant to this work.
- Methods: What are you doing or making to address your research question(s)?
- If you are using any datasets, does the needed data already exist? If so, how much data is available? What does the data look like? If you are just using a few examples for few-shot prompting, how did you select those?
- Describe your solution to the problem/research question. What model(s) are you using? If you are using few- or zero-shot prompting, what do your prompts look like?
- Evaluation: Renamed from Experiments section What experiments will you be running?
- What are you measuring and why? What evaluation metrics do you plan to use to answer your research question(s)?
- What are your proposed baselines? (That is, what are you comparing your method against?)
- How do these experiments answer your research questions?
- Results: What did you find from your evaluation?
- This should be more than just a list of raw numbers. You should explain to the reader how to interpret any graphs or tables you have and describe any trends that you see.
- Discussion: What insights can you take away from the results? What do the results mean for your research question?
- Conclusion: In CS, this is often just a brief paragraph reminding people what the highlights of your paper were.
- References: Papers are cited correctly in the conference’s format and are references in the main text. (Do not number this section.)
In a separate document called team#-supplement.pdf, provide the
LLM Use Statement: Describe exactly how you used LLMs to generate parts of your paper (refer to the syllabus for guidance). If you did not use any generative text, please state so in this section.
What to Submit
team#-finaldraft.pdfwhich is your final paper.- A link to your presentation video.
team#-supplement.pdf, the LLM use statement.
Grading
- Poster Content - 8 points (See description above.)
- Poster Visuals - 4 points
- Results - 5 points - Data is displayed in a clear format and tables/graphs are made to accompany the text.
- Discussion - 5 points - Insights make sense and show that the results were thought about deeply.
- Tips Integrated - 3 points - All previous tips/recommendations were integrated or adjusted for.
- Completeness - 10 points - All sections listed above are included, paper seems cohesive, and paper is in correct format.
- LLM Use Statement - 1 point
Total: 36 points