> 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/nodes/model-nodes/anatomy-output.md).

# Anatomy Output

This node is designed to output all created meshes as a single package if used inside Houdini.

## Mass

{% hint style="danger" %}
You must set the mass of your character in this node!
{% endhint %}

## Outputs

This node saves your character into a single file and creates some basic bind weights for them.  The intention of the step is to have a single file that can feed the animation and simulation stage.  From here you may also export via FBX or other ROP node types.  You must save the output with no to view the results in this node.

<figure><img src="https://content.gitbook.com/content/czlF1HeE8ElPv7Dygz6P/blobs/YPwCc5M65RZzTg1IBfOC/17_outputNode.jpeg" alt=""><figcaption><p>All of the outputs represent a part of a file that has been saved for Houdini.</p></figcaption></figure>

1. **Out Models** - This output contains three packed primitives of the skin, muscles and bones.  Access them via the *character\_component* attribute and unpack them.
2. **Rest Skeleton** - Animation skeleton used for deforming the model.
3. **Rest Simple Skeleton** - Animation skeleton that is simplified and used for matching animation to this character.
4. **Muscle Simulation Geometry** - Tetrahedral meshes for simulation.
5. **Rest Muscle Lines** - Muscle Lines used to measure flexing of the muscles.&#x20;
6. **Skin Simulation Mesh** - Tetrahedral version of the skin mesh for simulation.


---

# 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/nodes/model-nodes/anatomy-output.md?ask=<question>&goal=<user_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.