C9: Final Report

Submit a single PDF file here on canvas by concatenating your main report text with PDF versions of the supporting notebooks.

Main report body

• Project title and team members
• Introduction (What is your system? Who is it for? What are the primary inputs and outputs?)
• Background (What's the most similar thing out there? What pre-existing Real World domain does your system attach to? Which if any of the readings from the class was most relevant to your project and how?)
• ASP Formulation (Just give the high level design of your formulation in terms of Guess/Deduce/Forbid/Optimize. Don't mention of specific predicates or rules connecting them. See Section 6.4 of this paper you already read for an example of outlining AnsProlog code in this way: https://adamsmith.as/papers/fdg2012generation.pdf Links to an external site.)
• Major problem instance (Describe your primary problem instance and the desired output of the system for that instance. Still don't mention specific predicates, but you might include a screenshot or code snippet of the thing that is being modeled in your instance. Mention the major parameters that describe the size of your instances and how this particular instance measures up: e.g., a Twine story with "30 passages, 10 story state variables, simulated for 15 timepoints".)
• Deployment Packaging (How does someone use what's on your website? Briefly, how is it architected / what is wrangled into what to plug ASP into the Real World data? Include a screenshot of your system in action in the currently deployed form: an interactive webpage, a downloadable command line tool, etc. If your system is was intended to be packaged in a different form than your website delivers, briefly describe the form of that ideal packaging.)

Supporting notebooks

Export the notebooks as PDF and look at each page of them before concatenating them together. You should try to reformat your code and data so the PDF looks somewhat nice (break long lines of code earlier so they don't run off the right size of the page; if some command produces pages and pages of output, use grep and head to show a sample of the important parts). If your notebook includes images, make sure the images really do appear in the PDF.

• Formulation notebook (Modify your old notebook or freshly create a new one that walks through solving a major problem instance. Use Markdown cells including headers to explain the process and show commands used. Leave bulk wrangling code out of this notebook similar to visualize.py from P4. We should be able to see every AnsProlog rule, but you can summarize/sample the bulk of the facts that make up a problem instance and supporting data like Arindam's giant list of all possible character names.)
• Performance characterization notebook (Show the balance of grounding and solving time for your main problem instance. Show the number of variables and constraints to give an objective sense of the size of the task the solver is given. Explain the worst grounding rules in your formulation and give the polynomial by which they scale in terms of domain objects like number of nodes, number of character, number of simulation time points, etc.)
• AnsUnit test suite notebook (Show the tests that confirm each small-ish part of your AnsProlog code works as expected; include the call to AnsUnit with the "-vv" flag to show each test running and passing.)