Create a Jupyter notebook (in the style of notebooks you created for past programming assignments in this class) that introduces your application setting and explains your current formulation. This doesn't mean you need to finish your entire project first. However, you do need to offer some evidence that the ASP side of your applied project is realistic (that the project isn't doomed). Feel free to strip out features that slow or messy and turn the parameters impacting the size of your example instance way way down.
You will present the contents of this notebook in class on Tuesday, May 30th. Expect to talk for 2-5 minutes. If there are any additional files or pictures you want to show, embed them in the notebook as well (or at least provide links you can click on from Adam's laptop).
A small-but-realistic-ish problem instance
A valid solution to that problem instance encoded as facts
One or more code cells that develop the various .lp files that you need to solve the problem.
An example execution of clingo confirming that combining the expected solution with the problem instance and your formulation is satisfiable. (Or anything else equivalent that you'd like to show instead if, for example, the goal is optimization.)
Various Markdown cells that make the notebook easy to understand. It doesn't need to be an entirely self-contained document because you'll be presenting it to us, but it shouldn't just be piles of code and esoteric output data.
Your final report will include the contents of this notebook as an appendix, but it is very likely that the version included there has evolved significantly since the one you present here.
Can't change a rubric once you've started using it.