PDF version
Each student chooses one of two singularities, computes it, submits the work as a pull request to the course repository, and presents and defends it in the final session. The repository README is the authoritative brief; this page summarises it. For the teaching sequence, see the 2026 course page.
Slides
PDF 1 MB · PowerPoint 4 MB · Keynote 2 MB
| Part | Weight |
|---|---|
| Pull request (code, figures, README, AI log) | 40% |
| Presentation and defence in the final session | 60% |
Dates (Wednesdays, 2026)
| Date | Step |
|---|---|
| 18 November | choose Option A or Option B |
| 2 December | open your pull request |
| 2–9 December | written feedback on your pull request |
| 9 December | present and defend your work in the final session |
The questions
Every singularity in the course is examined with the same four questions (see Singularities):
- Singular? Which quantity goes to zero, or diverges, and where or when?
- Self-similar? Do rescaled profiles collapse onto one curve?
- Universal? What does the local solution forget about the initial or far-field conditions?
- Regularised? Which physics, absent from the equation, stops the divergence?
Each option asks a subset of them. Answer them with evidence from your own computations.
Option A: a moving contact line
A liquid wedge moves steadily over a solid. In the frame of the contact line, the film thickness
with
(the film ends at the contact line), (unit slope at the contact line), (the curvature dies out far away).
The constant
Questions: Is the problem singular? How is it regularised? Is the result universal?
Option B: a rupturing film
A thin liquid film on a solid is thinned by van der Waals attraction. In dimensionless form, its thickness
on a periodic domain, starting from
Questions: Is the flat film unstable? Is the rupture singular? Is it self-similar? Is it universal?
What to submit
Open a pull request to the course repository that adds your files directly in submissions/, each name starting with your exact GitHub username and an underscore:
- your code, in any language;
- the figures you discuss;
<github-user>_README.md: the problem, your approach, your answers to the questions for your option, and how to run your code;<github-user>_AI-log.md: what you asked, what the AI returned, how you tested it, and what you changed.
Public submission
The repository is public. Read its visibility and consent section before you upload or push any file to your fork. Your files, commit history, username and pull-request discussion will be publicly visible and may remain in the repository history. Never include student numbers, marks, private contact details, API keys, passwords or tokens. If you need a private route, contact the instructor before you start.
The repository README gives step-by-step instructions for the browser and the terminal.
AI is encouraged
Use any AI tool for any part of the work, and keep the log as you go: what you asked, what came back, how you tested it, and what you changed. In the final session you must be able to explain every line of your code and every figure you show; the defence is about your understanding, whoever typed the code.
The final session
Each presentation covers the problem, how you approached it (including the checks that make you trust your numbers), what you found for each question, and then a defence: any line of code or any figure can be questioned. Plan for about 5 minutes plus 3 minutes of questions; the exact timing depends on the size of the class.
Reading
- J. Eggers & M. A. Fontelos, Singularities: Formation, Structure, and Propagation, Cambridge University Press (2015). Chapters 1–3 for the framework; §15.2 for contact lines.
- J. H. Snoeijer & B. Andreotti, Moving contact lines: scales, regimes, and dynamical transitions, Annu. Rev. Fluid Mech. 45, 269–292 (2013).
- A. Oron, S. H. Davis & S. G. Bankoff, Long-scale evolution of thin liquid films, Rev. Mod. Phys. 69, 931–980 (1997).
- V. Sanjay, Singularities in soft matter systems, Contemporary Physics (2026), doi:10.1080/00107514.2026.2721118; arXiv:2608.11060.
Questions: open an issue in the course repository or ask in class.
