Lecture 8: Final Projects and Research Sharing

What makes a good final project, and how do you get from a question to a poster and a paper in four weeks? Watch the lecture in short chapters with English and Chinese subtitles, then open the project guide and the writing tips: they are the reference for everything said here.

📅 Nov. 13th, 2026 🎥 chapters · min 🖼 slides 💬 EN + 中文 subtitles 🧭 Lecture map 🚀 Get started 📋 Project guide (EN/中文) ✎ Writing tips ⬇ Slides (PDF)
Transcript follows the video · click a sentence to jump · Shift + ←/→ jumps between slides

1The lecture map

What makes a good final project — and how do you get from a question to a poster and a paper in four weeks?

Four acts, seven chapters. First the rules: what you deliver and how it is graded. Then the longest part, choosing a topic from eight tracks and a handful of fresh ideas. Then what good looks like, from past students' projects. And finally writing, because clarity is worth as many points as soundness. Click a chapter to watch it.

IRules
What you deliver, when, and how it is graded
IIILearn from the best
What strong projects look like
IVWrite
Show it so the reader sees it too
Chapter by chapter what each chapter covers, and the question it leaves for the next
  1. IRulesWhat you deliver, when, and how it is graded
  2. 1

    The Final Project: Deliverables, Deadlines and Grading

    Your first mini research project, worth 55% of the grade: teams of up to three with a concrete contribution statement, a poster session on Dec. 18 (file in by 17:00 on Dec. 17 for free printing), and a six-page report on Dec. 25. Writing clarity (15%) counts as much as technical soundness (15%).

    → So what should you actually build?
  3. IIChooseEight tracks, fresh ideas, and how to pick
  4. 2

    Choosing a Track: Agents and Training Your Own Model

    Pick one of 77 briefs in eight tracks, or propose your own LLM-related topic, and follow six rules of thumb. Track A studies the agent harness at a matched budget (a new skill, an audited AI-written survey); Track B trains models, from nanoGPT speedruns to vertical models such as HuatuoGPT, AceGPT and Soundwave.

    → What if you would rather build something people interact with, or measure the models?
  5. 3

    Interactive Systems, Evaluation and Datasets

    Track C makes interaction the variable: LLM NPCs on a virtual campus, tools for education, picture books and open tutorials, judged on fidelity and transfer rather than engagement. Track D builds benchmarks (a dataset with a scoring rule), physician-style rubrics, datasets and RAG systems whose citations can be checked.

    → What about projects that need no GPU at all — or real users?
  6. 4

    Society, Efficiency, Competitions and Startups

    Track E argues a falsifiable position and tests it, for example with a matched-persona audit; Track F measures speed with fresh-input correctness checks; Track G turns a contest into a controlled comparison; Track H runs a startup prototype judged on retention and cost, with two student startups from our campus.

    → Beyond the tracks, where else can ideas come from?
  7. 5

    Fresh Ideas, Hospital Deployments and Picking a Topic

    Seeds to brainstorm with (a robot bar, an AI seller, simulated patients, AI + VR, text-to-3D printing, text-to-game, an incubator simulator), agents deployed in the CUHK-Shenzhen hospital, and how to choose: your expertise, your background, real needs around you, and above all your interest. The teaching team is there to help, not only to judge.

    → What does a really good project look like?
  8. IIILearn from the bestWhat strong projects look like
  9. 6

    Outstanding Projects from Past Terms

    A valuable question, solid evidence and clear communication. MedGen links paper, code and data; ConsumerSim brings a question from economics; FutureSelf reports a result against its own hypothesis; TripGenie gives an honest number with a proper baseline; and four posters run from a local-LLM safety audit to an analysis of in-context learning.

    → How do you write it up so the reader sees it too?
  10. IVWriteShow it so the reader sees it too
  11. 7

    Writing Your Paper: Tips That Save Points

    A paper should read like a film with no 尿点: go from abstract to concrete, keep the straight path, motivate the paper and every component, use plain words, cut empty ones, define every term, be specific, spell out the logic, keep a consistent style — and related work is not a shopping list. Then a wrap-up and Q&A.

2Get started

The project guide and the writing tips are the reference. The Final Project Guide & Challenge Tracks page (English and 中文) holds every brief, the rules, the schedule and the FAQ; the Writing tips & samples page collects the writing advice from this lecture with past posters and papers. If anything in the video differs from those pages or the course page, the pages win.
Nov. 13team formation & optional one-page proposal
Dec. 17, 17:00poster file due (printed for you if on time)
Dec. 18poster session, a 4-minute pitch per team
Dec. 25, 23:59final report due (max. 6 pages)
Start here · Chapters 2–5

Project guide & tracks

final-project.html · EN / 中文 · PDF guide
Before you write · Chapters 6–7

Writing tips & samples

Templates · Chapter 1

Report, poster and grading

Submit the report through Blackboard
Starter notebook · Chapter 2 · ~5 min

A fair comparison, in code

  • Freeze and fingerprint a held-out test split
  • Compare a baseline and one change at a matched tuning budget
  • Seeds, a paired bootstrap interval and an exact sign test
  • Check a judge against gold labels; write traces and a booktabs table
Open in Colab .ipynb · CPU, no API key

Your first week

The closing advice of the lecture (slide 98), plus the rules of thumb from the project page (slide 18):

  1. Form your team this week, and agree on who does what; the report needs a concrete contribution statement (slide 5).
  2. Skim the project page tonight and pick two candidate briefs, or write down your own LLM-related question (slide 16).
  3. Talk to a TA whose background fits your topic, with a concrete question (slides 67–68).
  4. Freeze the task, a held-out split and the primary metric, and have a working baseline by the end of week one.
  • One change — test one idea at a time.
  • Matched budget — your method and the baseline get the same compute, tokens or model calls.
  • Held-out split — never tune on your test data.
  • Independent checker — don't let the model grade its own work.
  • Seeds — run more than once.
  • Replayable traces — log everything so someone can check it.

3Concept index

Key ideas of the lecture. Each link opens the video at the slide where the idea is explained.

5Quotes & reading

"If you do not work on an important problem, it's unlikely you'll do important work."

Richard Hamming, You and Your Research (Bell Communications Research colloquium, 1986)
Chapters 2–5: pick a question worth four weeks — and one you can actually attack.

"The first principle is that you must not fool yourself — and you are the easiest person to fool."

Richard Feynman, Cargo Cult Science, Caltech commencement address (1974)
Why the rules of thumb exist: matched budgets, held-out splits and independent checkers.

"Never use a long word where a short one will do."

George Orwell, Politics and the English Language (1946)
"Utilize" or "use"? Just say "use" (slide 89).

"一篇好的论文读起来,应该是像看一个流畅的电影,没有尿点。"

A good paper reads like a smooth film: no moment where the reader can safely leave.

Further reading

6About this video

This is an AI-narrated version of the lecture. The slides are the ones used in class. The spoken script was written from the slides with AI assistance and is read in an AI clone of Prof. Benyou Wang's voice (MiniMax speech synthesis); the picture in the corner is a still photo. The red dot points at what is being discussed. When the narration and the slides disagree, trust the slides and the in-class lecture — and please tell us, so we can fix it.
CSC5051/CSC6052/MDS5110 Natural Language Processing · CUHK-Shenzhen · Fall 2026 · Back to the course page