> For the complete documentation index, see [llms.txt](https://docs.procedural-anatomy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.procedural-anatomy.com/installation/hda-installation.md). # HDA Installation Install the toolset on a computer Our toolset is integrated into a Houdini's Digital Asset. If you're new to Houdini please visit the Houdini Digital Asset Installation process at the link bellow for more details. {% embed url="" %} Houdini Help {% endembed %} Here we will explain a quick process to begin testing * Manually install, from the top menus: 1. Choose **Assets** -> **Install Asset Library...** 2. Find the Procedural Anatomy HDA file on your computer.

Manually install an HDA file from the asset library.

* Installing it in the correct folder * You can install HDAs to your Houdini preferences folder in a folder called **otls**. Houdini will load the Procedural Anatomy toolset when it starts. * Installing it with environment variables * Recommended for studios * Procedural Anatomy supports environment files and packages. --- # 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://docs.procedural-anatomy.com/installation/hda-installation.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.