Currently Karamba3d supports these types of loads: gravity-, point-, imperfection-, pretension-, temperature-loads, constant mesh-loads, variable mesh-loads and prescribed displacements at supports. An arbitrary number of point-, mesh-, etc.-loads and one gravity-load may be combined to form a load-case of which again an arbitrary number may exist. Fig. 3.2.1.1 shows the definition of loads with the help of the **“Loads”** multi-component. On the bottom of the **“ModelView”**-component (see section 3.6.1) there is a drop-down-list (unfold it by clicking on the **“Result-case Selection”**-menu header) which can be used to select single load-cases for display. Select **“–all–”** in order to view all existing load-definitions of all load-cases simultaneously. Use the force-slider to scale the size of the load-symbols (double-clicking on its knob lets you change the value range and its current value).

It is the default setting when you place a **“Loads”**-component on the canvas.

Each load case may contain zero or one definition for the vector of gravity. In this way one can e.g. simulate the effect of an earthquake by applying a certain amount of gravity in horizontal direction. For Vienna, which has medium earthquake loads, this amounts to approximately 14 % of gravity that a building has to sustain in horizontal direction. In areas with severe earthquake loads this can rise to 100 % (the value however also depends on the stiffness properties of the structure and underlying soil).

Gravity applies to all active elements in the structural model for which the specific weight gamma (see section 3.4.1) is not zero. The gravity vector defines the direction in which gravity shall act. A vector of length one corresponds to gravity as encountered on earth.

When working in SI-units Karamba3D assumes a value of $10m/s^2$ for the acceleration of gravity. In case of Imperial units $g = 9.8066352 m/s^2$ is used. Otherwise the conversion from pound mass to pound force does not work. The value of $g$ can be set in the “karamba.ini”-file, which resides in the Karamba3D installation folder.

The component **“Point-Load”** lets you define loads on points. These get attached to their points either by node-index or coordinate. In order to find out the index of a specific node enable the **“node tag”**-checkbox in the **“ModelView”**-component. Feed a corresponding list of items into the **”Pos|Ind”**-plug (quite analogous to the **“Support”**-component). Point-loads can be either forces ($kN$) or moments ($kNm$). Feed a force- or moment-vector into the **“Force”** or **“Moment”** input-plug. Its components define the force or moment in global x-, y- and z-direction.

When set to **“True”** the boolean input **“Local?”** makes loads and moments follow the nodal rotations in large displacement calculations (see section 3.5.4).

Plugging a point-load into a panel component gives the following information: Node-index where the load gets applied or position, force-vector, moment vector, the number of load case to which it belongs and whether the load is tied to the nodal coordinate system.

By default point loads will be put into load case zero. Any positive number fed into the **“LCase”**-plug defines the load case to which the corresponding load will be attributed. A value of $-1$ signals that the load acts in all existing load cases.

For more information on loads and some typical values see section A.2.3.

There exists no such thing as an ideally straight column positioned perfectly vertical. The deviation of a real column from its ideal counterpart is called imperfection. This term comprises geometric and material imperfections.

The **“Imperfection”** variant of the **“Loads”** multi-component allows to specify geometric imperfections (see fig. 3.2.1.2). **“psi0”** takes the vector of the initial inclination of the beam axis about the axes of the local element coordinate system in radians. With **“kappa0”** one can specify the initial curvature. A positive component of curvature means that the rotation of the middle axis about the corresponding local coordinate axis increases when moving in longitudinal beam direction. Small inclinations and curvatures are assumed.

In fig. 3.2.1.2 one can see displacements and reaction forces of an initially straight beam with a second order theory normal force of $N^{II} = 10 kN$, an initial inclination of $0.1 rad$ about the local y-axis and an initial curvature of $0.1 rad/m$.

Imperfection loads do not add directly to the beam displacements. They act indirectly and only in the presence of a normal force $N^{II}$. An initial inclination $\psi_0$ causes transverse loads $\psi_0 \cdot N^{II}$ at the elements endpoints. An initial curvature $\kappa_0$ results in a uniformly distributed line load of magnitude $\kappa_0 \cdot N^{II}$ and transverse forces at the elements endpoints that make the overall resultant force zero. For details see e.g. [10].

Karamba3D lets you define initial strains. Fig. 3.2.1.3 shows a beam with both ends fixed, subject to a positive initial constant strain and curvature. The unit of dimension of the pretension which gets fed into the **“Eps0”** plug is $mm/m$.

A positive value means that the element gets longer.

Applying initial strain to an element is not the same as applying a pair of opposite forces or moments at its endpoints: In case of initial strain, the axial force in the element depends on its boundary conditions: If the structure to which it connects is very stiff then the resulting axial force will be $N = -\epsilon _0 \cdot A \cdot E$. In fig. 3.2.1.3 the supports are rigid, the elements cross section $A = 25 cm^2$, Young’s Modulus $E = 21000 kN/cm^2$ and $\epsilon _0 = 0.00015$. This results in an axial force of $N = -78.75 kN$ and shows up as horizontal support reactions. When the rest of the structure does not resist, then a pretension-load merely results in lengthening or shortening the corresponding element.

The **“Kappa0”**-input is a vector of curvature values with respect to the local element axes. A positive component value signifies an anti-clockwise rotation about the corresponding axis. The input plug **“ElemIds”** defines the elements where the load acts and **“LCase”** the load-case.

The definition of temperature loads works analogously to defining pretension loads (see section 3.2.1). The coefficient of thermal expansion (see section 3.4.1) characterizes the response of a material to temperature changes.

Fig. 3.2.1.5 shows a tilted structure consisting of three beams under the action of a uniformly distributed load at elements “0” and “2”. The load acts parallel to the beams local z-axis. The components of the load vector are assumed to be given in kilo Newton per meter $kN/m$ . The input-plug **“BeamIds”** receives a list of the identifier of the beams on which the load shall act. See section 3.1.6 for how to attach identifiers to beams. By default beams are named after their index in the FE-model. There are three options for the orientation of the load: **“local to element”**, **“global”** and **“global proj.”**. Their meaning corresponds to the options available for mesh-loads (see fig. 3.2.1.7). The input-plug **“LCase”** which designates the load case defaults to “0”.

The **“MeshLoad”**-component can be used to transform surface loads into equivalent node- or element-loads. This lets you define life-loads on floor slabs, moving loads on bridges (see example “Bridge.ghx” in the examples collection on the Karamba3D web-site), snow on roofs, wind-pressure on a facade, etc.. The mesh where the load is applied and the underlying structure do not need to be connected. It needs to be fed into the **“Mesh”**-input-plug.

There exist two types of mesh-loads:

**“MeshLoad Const”**: for loads which are constant throughout the mesh.**“MeshLoad Var"**: lets one set specific load-values for each face of the mesh.

These two variants differ with respect to the data-structure expected at the input **“Vec”** and **“Vecs”** respectively: Either a single vector for specifying a constant load or a list of vectors. In the latter case the list items are applied to the mesh-faces based on the longest list principle. In what follows the **“MeshLoad Const”**-variant will be depicted but everything mentioned there applies to **“MeshLoad Var”** also.

Fig. 3.2.1.6 left side shows a simply supported beam and a mesh which consists of two rectangular faces. Each face covers one half of the beam and has a width of $2m$ perpendicular to the beam axis. With a distributed load of $1kN/m^2$ in negative global Z-direction a uniformly distributed load of 2 $kN/m$ results.

In order to define structure nodes where equivalent point-loads may be generated, plug a list of their coordinates into the **“Pos”**-plug. These need to correspond to existing nodes – otherwise the Assembly-component turns red. Offending nodes will be listed in its run-time error message. By default all points of the structure are included. Uncheck **“Point loads”** to avoid point-loads.

With the input-plug **“BeamIds”**, groups of elements can be specified on which equivalent loads shall be generated. By default all beams of the model are included. In case no beam loads shall be included uncheck the **“Line loads”** button on the **“Generation”** submenu.

The procedure for calculating nodal loads and uniformly distributed beam loads from surface loads consists of the following steps: First Karamba3D calculates the resultant load on each face of the given mesh. Then the resultant load of each face gets evenly distributed among its three or four vertices.

The second step consists of distributing the vertex-loads among the nodes of the structure. In order to arrive at beam loads additional helper-nodes along their axes get generated. The mutual distance of those is chosen equal to a third of the mean edge length of the given mesh.

Each mesh vertex transfers its load to the nearest node. In case that there are several nodes within a radius of less than **“LDist”** as set at the Assemble-component (see section 3.1.1) the vertex load gets evenly distributed among them. The loads received by the helper-nodes along beam axes get summed up and divided by the element length. This results in the approximately equivalent uniformly distributed load which is placed on the element. From the procedure described, one can see that a crude mesh may lead to a locally incorrect distribution of loads. In the system shown in fig. 3.2.1.6 the points closest to the vertices are the element’s end-points. Therefore the helper nodes along the beam-axis do not receive a share in the mesh-load and thus no line-load results.

Fig. 3.2.1.7 shows a similar setting as in fig. 3.2.1.6. The difference lies in the refined mesh with more vertices along the beam axis. Now loads from the mesh vertices get distributed also to the helper nodes along the element axis. This leads to the generation of a uniform line-load.

Set the **“LCase”**-input to the index of the load case in which the surface load shall act. Indexing of load-cases starts with zero, “−1” is short for all load cases.

The right side of fig. 3.2.1.7 shows what data the **“MeshLoad const”**-component collects: The input-plug **“Vec”** expects a vector which specifies the surface load. Its physical unit is kilo Newton per square meter $kN/m^2$. The orientation of the load-vector depends on the checkbox selected under **“Orientation”** (see also fig. 3.2.1.8):

**"local to mesh”**: The convention for local coordinate systems for local loads corresponds to that given in section 3.1.14: The local x-axis is parallel to the global x-direction unless the mesh-face normal is parallel to the global x-direction. In that case the local x-axis points in the global y-direction. The local z-axis is always perpendicular to the mesh-face and its orientation depends on the order of the vertices: If the z-axis points towards ones nose, the order of the face vertices is counter-clockwise.This means a surface load with components only in Z-direction acts like wind pressure or suction.

**“global”**: The force-vector is oriented according to the global coordinate system. This makes the surface load behave like additional weight on the mesh plane.**“global proj.”**: The force-vector is oriented according to the global coordinate system. The corresponding surface load is distributed on the area that results from projecting the mesh-faces to global coordinate planes. In such a way the action of snow load can be simulated.

By default, the **“MeshLoad const”**-component creates point- and line-loads. The radio-buttons in the submenu **“Generation”** can be used to disable the first or the latter.