Skip to main content

Project checklists

Use these lists to check your progress and coordinate your team; you don't submit them. Grading explains how we assess your work.

Topic refinement​

The Refinement guide shows how to sharpen your question, and the Proposal guide explains how approval works.

  • Picked a listed project from Topics & projects or prepared a custom topic
  • Defined a specific, testable research question
  • Identified your data sources and checked that you can access or collect the data
  • Clarified inputs, outputs and evaluation criteria
  • Explained why the question matters clinically, physiologically or scientifically
  • Outlined a feasible method (computational, analytical, experimental or survey) and a fallback plan
  • Gave at least one mini-pitch in class before sending the proposal, and used the feedback (custom topics only)
  • Named a group lead
  • Wrote the proposal (at most two pages) with the template
  • Sent the proposal to support@cacom.dev by the topic approval deadline on the Schedule
  • Received topic approval

Project execution​

  • Roles and responsibilities assigned within the team
  • Team communication channels agreed (for example email, Slack or shared documents)
  • At least one member at every class, with a short update and a question for us (see class participation)
  • A ticket sent beforehand whenever nobody from your group can make a class
  • support@cacom.dev in CC on every email with collaborators, including the first one
  • Regular check-ins held and progress written down
  • Methods piloted early on a small subset of the data
  • Evaluation metrics defined and validated
  • Feasibility risks reviewed and fallback options ready
  • Draft results reviewed within the team at least a week before the poster and video deadline

Collaboration conduct​

Details are in the collaboration policy.

  • For an established CACoM collaborator, Prof. Daumer made the introduction (ask via support@cacom.dev or in class)
  • Collaborator introduced to the whole team
  • Communication polite, timely and traceable (email preferred)
  • Meetings confirmed and followed by a short written summary
  • Feedback acknowledged and acted on
  • Confidential and proprietary information handled responsibly, and limits on collaborator-owned materials respected
  • Problems or delays reported to support@cacom.dev right away

Academic integrity and AI tools​

See the AI tools and plagiarism and citation policies.

  • The reasoning and writing are your own; AI only assisted
  • You can explain and defend every result, figure and sentence
  • All external sources (papers, datasets, code) cited, and no reference is fabricated or unverifiable
  • Meaningful AI help briefly acknowledged in the report or README
  • Plagiarism check done before each submission

Presentation package​

Requirements and the symposium format are on the Presentation package page.

  • Poster visually clear, self-contained and scientifically accurate
  • Figures and references labeled and consistent with your results
  • All collaborators and contributors acknowledged
  • Video is an MP4 in 1080p with sound, at most one minute long
  • Video makes sense without an introduction and has no promotional filler
  • Partner consent and confidentiality checked before the poster and video deadline (posters and videos are public at the symposium)
  • Poster printed in A1 (you get the printing cost refunded)
  • Poster walkthrough rehearsed, and you can explain and defend every element on the poster
  • Break rotation agreed, so at least one of you stays at the poster during every break
  • Whole team can attend the poster session

Reproducibility package​

The Reproducibility page lists what the package needs, and Data privacy covers where data may go.

  • Code organized, commented and runnable from a clean start
  • README explains exactly how to reproduce your results
  • Dependencies and environments listed (requirements.txt, environment.yml or similar)
  • Data sources documented, and each data file labeled as synthetic, anonymized or pseudonymized
  • Real or partner-provided data stored only in the CACoM Google Drive and never uploaded publicly
  • Proprietary or restricted parts clearly marked and described
  • Every core figure and result can be regenerated from your scripts
  • A team member unfamiliar with the code reproduced the results by following the README

Final submission​

Both deadlines are on the Schedule.

Before the poster and video deadline​

  • Whole team has approved the final poster and video
  • File names descriptive and consistent (not final_v3_last.pdf)
  • Poster (A1 PDF) and video uploaded to your group's Google Drive folder
  • Uploaded files open correctly
  • Ticket sent to support@cacom.dev with your group number in the subject (see the subject format)

Before the reproducibility deadline​

  • Whole team has approved the final package
  • Reproducibility package (.zip or .tar.gz) uploaded to your group's Google Drive folder, and it opens correctly
  • GitHub repository link shared with us, if you use one
  • Ticket sent to support@cacom.dev, again with your group number in the subject