> For the complete documentation index, see [llms.txt](https://docs.dietrichs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/dach/dachassistent.md). # Roof Assistant The roof assistant generates timbers on the roof surfaces according to specific rules, which are selected during the assignment. This allows the entire roof to be covered with timber at the push of a button. The degree of automation can be increased significantly by storing the preconfiguration file to be used directly within the roof surface specification. The information on how the timbers should be generated is stored in preconfiguration files. These preconfiguration files are assigned to the individual roof surfaces. Each roof surface can be assigned a different preconfiguration file, or all roof surfaces can be assigned the same file. This assignment is made either directly during the assignment process or in advance by assigning the files to the roof surface specifications. The principle of the roof assistant is simple and effective. Because of this principle, all options for manual timber input are automatically available: in the dialog boxes for manual timber entry (purlins - ridge/valley rafters, common rafters, collar beams) you can save the settings. To do this, click the disk icon at the top edge of the dialog box and then enter the desired name. You will then find this setting in the configuration dialog of the roof assistant and can select it. However, the roof assistant’s preconfiguration file does not only store the names of the chosen settings but also all the setting values themselves. Thus, you can delete a setting in the manual timber input and the roof assistant’s preconfiguration file will still function. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/dach/dachassistent.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.