Seminar 5: Show Your Navigator, Defend the Call

Friday 10:00–12:00 CEST · live on Zoom · mandatory.

You present the single-cell navigator you built in Wednesday’s lab and the call you made on your data owner’s cluster — and the room questions it. Same format as every seminar; this page tunes it to Week 5. A few of you are drawn at random to present (7 min + 3 min discussion); everyone should come ready.

What to show (≈7 minutes, driven from your live app)

  • The question, in your owner’s words — the one decision they had to make.
  • Your navigator, live. Don’t screenshot a slide deck — open the app and drive it: colour the map by the genes and quality numbers that mattered, land on the cluster in question.
  • The call, with the evidence on screen. What the cluster actually is, and the genes/QC that say so — not what the owner hoped. If you changed their mind, show the moment the data did it.
  • One honest limit — what you did not check, or what would change your answer.

Prefer showing the live app to reading bullet points. If your network is shaky, have a couple of screenshots as backup, but the app is the star.

What the room (and we) will push on

  • Did you answer the owner’s actual decision, or just describe the clusters?
  • Is your call backed by marker genes and quality numbers, or by where cells sit on the map?
  • Did you take the owner’s instinct on faith, or did the navigator settle it?
  • Could a stranger open your GitHub repo, read the README, and run your navigator?

Build your own style

Make the navigator and the README yours — a tool and a repo you’d be proud to hand a collaborator. If you’ve seen an app or a README you admire, show it to Pi and ask it to take inspiration (say so). The goal isn’t a template everyone copies; it’s your own clear, honest, runnable piece of work.

Previous