> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-collection/data-collection-principles.md). # Data Collection Principles {% hint style="success" %} The following guidelines describe data collection best practices, but are not exhaustive. You may obtain high quality markerless motion capture data under different conditions from those described below. {% endhint %} ## **Camera Setup** Camera system setups differ from location to location, and may be subject to challenging data collection environment constraints. General recommendations for setting up your camera system include: * Cameras as close as possible to the capture volume, while ensuring the entire capture volume remains within view for all cameras. * Cameras 4-8 feet (1-2.5 m) above the ground. * Avoid partial views of subjects, such as lower body or upper body only. * Avoid unusual camera views, especially those positioned very high or very low, or extremely tilted. * Aim for a symmetrical camera setup that surrounds the entire capture volume, such as a circle, oval, or rectangle. ## **Camera Settings** The camera settings you choose will depend on the movements being collected. Selection of appropriate camera settings is crucial for collecting clear, crisp video images. The most important camera settings to consider include: * Frame rate: fast movements require high frame rates, to capture the movement smoothly. Check out this [blog post](https://www.theiamarkerless.com/blog/key-characteristics-of-video-data-for-theia3d) for discussion and recommendations. * Shutter speed / Exposure: should be set to ensure the subject and their body segments are not blurry during the movement. Faster shutter speeds or shorter exposures will capture images with less movement blur, but may reduce the image brightness. If you are collecting high-speed movements, you may need to consider introducing additional light into your capture volume in order to capture videos that are adequately bright. In general, faster movements require higher frame rates, faster shutter speeds / shorter exposures, and more light. Check out this blog post for more details on [important characteristics of video data](https://www.theiamarkerless.com/blog/key-characteristics-of-video-data-for-theia3d) . ## **Subject Attire** Theia3D provides 3D pose estimates that are robust to changes in attire. General recommendations for subject attire include: * Body-fitting clothing. Each limb should be discernible from the rest of the body. * Clothing should provide rich visual features, such as visible creasing, shadows, or other textures. * Lighting is often more important than attire color, as it impacts the visual richness of the attire. Under adequate lighting conditions black attire is acceptable, but lighter colors generally provide more visual features, especially in low-light environments. {% embed url="" %} --- # 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.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-collection/data-collection-principles.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.