> 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/bat-tracking/overview.md). # Overview Theia Bat Tracking integrates biomechanics and bat trajectory analysis at scale, without the need for sensors or instrumented bats. It enables team-scale, real-environment data capture, from bullpen sessions to on-field performance without requiring any additional hardware. The system simultaneously captures both bat motion and full-body athlete kinematics, allowing for the analysis of natural, unrestricted swings. Theia Bat Tracking is offered as an add-on package to active Theia3D licenses. ### Bat Detection and Tracking Theia Bat Tracking identifies several points on each bat to capture detailed motion and trajectory throughout the swing. Each bat must be linked to a tracked athlete, as the system does not support independent bat-only tracking. This means that the bat must be used by an athlete during recording in order to generate synchronized motion data for both the athlete and the bat. The bat object is tracked using the base and tip landmarks, and as a result does not convey meaningful information about the axial rotation of the bat. The bat segment coordinate system is located at the base landmark. --- # 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/bat-tracking/overview.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.