> 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/live-load-fea/transverse-live-load-on-felines-fea.md).

# Transverse Live Load On FELines \[FEA]

Applies a transverse live load across a set of finite-element lines, positioning wheel loads and lane loads to produce the governing transverse effect. Multiple presence factors are applied according to the number of loaded lanes.

## Inputs

**FELines:** The finite-element lines the transverse live load is applied to.

**Stage:** Construction stage at which the live load is applied.

**Axle Load:** Magnitude of a single wheel/axle load (default: 16).

**Lane Load:** Uniformly distributed lane load applied alongside the axle loads (default: 0).

**Max. number of lanes\[1 Lane=0/2 Lane=1/3 Lane=2/4 or More=3/No Limit=-1]:** Caps how many loaded lanes are considered when searching for the governing arrangement. **No Limit** lets the search use as many lanes as fit (default: No Limit=-1).

**Multiple Presence Factors:** Multiple presence factors applied by number of loaded lanes, in order (default: 1.2, 1, 0.85, 0.6, 0.6).

**Distance between Wheels:** Transverse spacing between the two wheels of an axle (default: 72).

**Minimum Distance between Vehicles:** Minimum transverse clear distance enforced between adjacent vehicles (default: 24).

**Alignment Direction\[X-Direction=0/Y-Direction=1]:** Global axis the alignment runs along, which fixes the transverse direction the load is swept in (default: Y-Direction=1).

**Unit Load Spacing:** Transverse increment the load pattern is stepped by while searching for the governing position (default: 36).


---

# 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/live-load-fea/transverse-live-load-on-felines-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.