> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/folderstructurets.md).

# Folder Structure

The **LTT TS directory** is the root of the LTT test execution system. At top level it contains the actual TestStand sequence file implementing your specific LTT testplan (and/or the template sequence file). It also contains the following sub folders:

![TS Folders](https://1704635928-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH5etzy4TvPRLxLRNfHlb%2Fuploads%2Fgit-blob-7b1f5777f938383055c17cfb848899a30eefc5ed%2FTS_FOLDERS_1.png?alt=media)

| Folder   | Content                                                                                                                                                                                                                                                                                                                                   |
| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| config   | Contains the TestStand configuration like StationGlobals, search paths, type definitions and so on. During installation of the LTT software the TestStand configuration directory will be set to this location. The default TestStand configuration directory is at `C:\ProgramData\National Instruments\TestStand\` and stays untouched. |
| examples | Contains MesSy examples sequences for both MesSy V1 and V2. You can copy those sequences into your own testplan as needed.                                                                                                                                                                                                                |
| lib      | Contains code modules (LabView, .NET) needed to operate the LTT. Specifically you will find there:ddd                                                                                                                                                                                                                                     |
| model    | Contains the [LTT process model](/ltt/documentation/ltt-gui-manual/teststand/processmodel.md)                                                                                                                                                                                                                                             |

## The lib folder

The lib folder contains some standard sub folder and files, which will be explained here. But it is also the place to put in your project specific assets, like additional DLL's or LabView VI's. Feel free to add more sub folders / LLB's / DLL's or VI's. But do **not** place your specific assets into one of the existing standard sub folders, since they get replaced by each LTT software update!

| Item                      | Description |
| ------------------------- | ----------- |
| IRS.MesSy                 |             |
| IRS.MesSyFD               |             |
| IRS.Mod                   |             |
| IRS.LTT.Mod.API.lvlibp    |             |
| IRS.LTT.Mod.Loader.lvlibp |             |
| IRS.LTT.Mod.Test.exe      |             |
| IRS.LTT.TS.API.lvlibp     |             |
| IRS.LTT.TS.UserLib.lvlibp |             |
| IRS.Rendezvous.lvlibp     |             |


---

# 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.irs.systems/ltt/documentation/ltt-gui-manual/teststand/folderstructurets.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.