> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/truss-bridge-workflow/loading-tb/loads-tb/buckling-tb.md).

# Buckling \[TB]

The stability of the structure, during erection or when complete, can be evaluated in this section.

* **Buckling Case** runs a linear eigenvalue buckling analysis and reports the critical load factor of each buckling mode against the load carried at a construction stage.
* **Geometric Imperfection** takes a mode shape of a Buckling Case and scales it into an initial out-of-straightness.
* **Nonlinear Buckling Case** applies that imperfection and traces the structure with geometric nonlinearity to the peak of its load path, giving the collapse load factor of the imperfect structure.

By default (both cases on the same stage, with no Reference Load on the Buckling Case and no Traced Load on the Nonlinear Buckling Case) the two analyses use the same reference load, so the linear factor (an upper bound for the perfect structure) and the nonlinear factor can be compared directly.

For the parameters of each object, refer to the related page in the documentation.


---

# 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.openbrim.org/templates/truss-bridge-workflow/loading-tb/loads-tb/buckling-tb.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.
