> For the complete documentation index, see [llms.txt](https://opencampus.gitbook.io/opencampus-machine-learning-program/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opencampus.gitbook.io/opencampus-machine-learning-program/courses/archive/python-from-beginner-to-practitioner/week-12.md). # Week 12 ### To-Do Homework: * Prepare slides for a three minute presentation of your project progress * Upload the PDF in the Mattermost channel ### Final Project * The deadline for submitting your well documented project is the **01/08/2024** * Your submission should tell a story: * What is the goal of the project? * What is the roadmap to reach that goal? * What did you try / did not work / can be improved upon? * You have to at least hand in a Jupyter Notebook documenting code snippets, also if you are just working with .py files * You can alternatively upload a zip file containing the Jupyter Notebook and needed project files (own libraries, ressources) * In a group project it should become clear, who participated and who worked on what part #### General remarks on the project * The project should at least look and feel like the Projects you build in the course * Use a GUI * Turtles at least, it has been demonstrated * Pygame is not difficult either * Tkinter? Others? * Use of libraries is encouraged! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://opencampus.gitbook.io/opencampus-machine-learning-program/courses/archive/python-from-beginner-to-practitioner/week-12.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.