> 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/openbrimfea/fea-library-fea/live-load-fea.md).

# Live Load \[FEA]

The Live Load group of the FEA Library workflow holds two live-load objects that work on a path of line elements rather than on an influence surface.

* [Influence Line Analysis on FELines](https://docs.openbrim.org/templates/openbrimfea/fea-library-fea/live-load-fea/influence-line-analysis-on-felines-fea.md) marches a unit load along a path of line elements and records the response at every placement; the influence lines drive the live load envelopes used in design.
* [Transverse Live Load On FELines](https://docs.openbrim.org/templates/openbrimfea/fea-library-fea/live-load-fea/transverse-live-load-on-felines-fea.md) positions wheel loads and lane loads across a set of line elements to produce the governing transverse effect, with multiple presence factors by the number of loaded lanes.

For influence surfaces, and influence lines defined in the FEA tree, see [Influence Surfaces & Lines](https://docs.openbrim.org/templates/openbrimfea/loads-fea/moving-loads-fea/influence-surfaces-lines-fea.md).


---

# 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/openbrimfea/fea-library-fea/live-load-fea.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.
