> 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/developers/paramml-developer-guide/core-objects/finite-elements-objects/feline.md).
# FELine
An FELine object is used to model beams, columns, and other structural elements that connect two Node objects. To create an FELine object, two Node objects and a Section object are required. The beta parameter represents the angle of rotation of the section around the Z-axis and is expressed in radians.
**Example Syntax:**
```
...
...
...
```
**Example:**
```xml
```
 To view this example in the library, see ()
**Example:**
```xml
```
 To view this example in the library, see ()
Rigid diaphragms have extremely high in-plane stiffness properties, so they do not experience membrane deformation or generate the associated forces.
Given these benefits, we can use rigid diaphragms for calculations in our projects.
In OpenBrIM's Finite Element Analysis, rigid diaphragms can be defined “**Rigid Line”** as shown in the example.
**Example:**
```xml
```
 To view this example in the library, see ()
**Parameters of FELine Object:**
\| | **Label** | **Mandatory** | **Name and Type Attributes** | **Default Description and Value Attributes** | **Other Attributes** | | --- | --- | --- | --- | --- | | 1 | Node 1 | Yes | N="Node1" T="Node" | D="Node 1: The start node of the finite element." V="" | Role="Input" | | 2 | Node 2 | Yes | N="Node2" T="Node" | D="Node 2: The end node of the finite element." V="" | Role="Input" | | 3 | Beta Angle | No | N="BetaAngle" T="Expr" | D="Beta Angle: The orientation angle to rotate the cross-section about the length of the finite element." V="0" | Role="Input" UT="Angle" UC="Section" | | 4 | Section | Yes | N="Section" T="Section" | D="Section: The cross-section property of the finite element." V="" | Role="Input" |
---
# 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/developers/paramml-developer-guide/core-objects/finite-elements-objects/feline.md?ask=&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.