Submit a publicly accessible link to your presentation materials here on Canvas.
You should try to present from your own laptop if you can (bring the appropriate dongles for connecting to our VGA projector), but you can present Google Slides stuff from Adam's laptop if you need. You can show interactive demos in his Chrome browser, but don't expect to be able to install any supporting code for running command-line demos.
Aim for 10-15 minutes of presentation. Practice your presentation in front of a friend. Even if they don't understand any of the ASP parts, they should still be able to understand that you built a concrete system for some purpose they can follow.
The overall format of the presentation is up to you and your estimation of what conveys the Challenge and Achievement of your project with the most Clarity. However, you should aim to cover at least the items below.
Opening: Lead with your major problem instance and the packaged/deployed form of your system. At this point, we've seen the setting for you project described before, but we haven't seen that major problem instance or how it gets plugged into your system.
Formulation: Without showing more than at most a few key AnsProlog rules, describe your formulation in high level Guess/Deduce/Forbid/Optimize terms (as in the Report).
Execution: Show your system in action if possible (or save demonstration outputs if it doesn't run interactively). While it is running, remind us of the ground / solve time split and describe the ground-time scaling in general terms: e.g., "linear in the product of passages and timepoints" or "quadratic in the number of keys".
Challenges: What was the hardest part of the ASP side of the project and what techniques did you use to get over it (debugging, testing, etc.)? What was the hardest part of the non-ASP side of the project and what techniques or support did you get to get past it?
Future work: If someone were to work on the project for three more months, what should they do (either or both ASP and non-ASP parts)?