3.2.1: General Loads
Last updated
Last updated
Currently, Karamba3D offers the following general types of loads: gravity, point, imperfection, pretension, temperature loads, constant mesh loads, variable mesh loads, and prescribed displacements at supports. Additional options exist for beam and truss elements (see section on Beam Loads). The types of loads described in this section apply to all types of elements.
An arbitrary number of point loads, mesh loads, etc., and one gravity load can be combined to form a load case, and any number of load cases may exist. Fig. 3.2.1.1 shows the definition of loads using the “Loads” multi-component. Each load-component features an "LCase" input-plug which serves to define the load-case to which the corresponding load belongs to. The default value is "LC0". See section 3.2.5.1 for load case naming conventions.
At the bottom of the “ModelView” component (see section 3.6.1), there is a drop-down list (unfold it by clicking on the “Result Selection” menu header) that can be used to select individual load cases for display. Select “–all–” 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 allows you to change the value range and its current value).
When you place a “Loads” component on the canvas, it defaults to the setting described below.
Each load case may contain zero or one definition for the gravity vector. This allows you to simulate effects such as earthquakes by applying a certain amount of gravity in a horizontal direction. For example, in Vienna, which experiences medium earthquake loads, this equates to approximately 14% of gravity that a building must withstand horizontally. In areas with severe earthquake loads, this can rise to 100%, although the value 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 for the acceleration of gravity. In case of Imperial units is used. Otherwise the conversion from pound mass to pound force does not work. The value of can be set in the “karamba.ini”-file.
The “Point-Load” component allows you to define loads on nodes. These loads can be attached by node index or coordinate. To find out the index of a specific node, enable the “node tag” checkbox in the “ModelView” component. Provide a corresponding list of items into the “Pos|Ind” plug, similar to the “Support” component. See section 3.1.6 for information on how to predefine the index of specific nodes or node positions. Point loads can be either forces or moments. Input a force or moment vector into the “Force” or “Moment” input plug. Its components define the force or moment in the global x, y, and z directions.
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 provides the following information: node index or position where the load is applied, force vector, moment vector, the number of the load case to which it belongs, and whether the load is tied to the nodal coordinate system.
Be cautious with nodes where only truss or membrane elements are attached, as these nodes do not possess rotational degrees of freedom. A moment load will therefore have no effect and will be automatically removed from the structure.
For more information on loads and some typical values, see section A.2.3.
Karamba3D allows you to 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 .
A positive value means that the element elongates.
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 . In fig. 3.2.1.3 the supports are rigid, the elements cross section , Young’s Modulus and . This results in an axial force of 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.
Additional examples can be found in the Grasshopper main tab under Karamba3D > Help > Examples > Local Examples > Loads.
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. "T" represents a uniform temperature change over the cross section, "T" a temperature gradient over the cross section. The input vector refers to the local element coordinate system and specifies changes about the corresponding axes.
The “MeshLoad” component is used to transform surface loads into equivalent node or element loads. This allows for the definition of live loads on floor slabs, moving loads on bridges (see the example “Bridge.ghx” in the examples collection on the Karamba3D website), snow on roofs, wind pressure on facades, etc. The mesh where the load is applied and the underlying structure do not need to be connected. The mesh needs to be fed into the “Mesh” input plug.
There are two types of mesh loads:
“MeshLoad Const”: for loads that are constant throughout the mesh.
“MeshLoad Var”: for setting specific load values for each face of the mesh.
These two variants differ in 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 the information applies to “MeshLoad Var” as well.
Fig. 3.2.1.6 (left side) shows a simply supported beam and a mesh consisting of two rectangular faces. Each face covers one half of the beam and has a width of 1 m perpendicular to the beam axis. With a distributed load of 1 kN/m² in the negative global Z-direction, a uniformly distributed load of 2 kN/m results.
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 “Assemble” 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 “BeamIds” input plug, groups of elements can be specified on which equivalent loads shall be generated. By default, all beams of the model are included. To exclude beam loads, uncheck the “Line loads” button in 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 is evenly distributed among its three or four vertices. In the second step, the vertex loads are distributed among the nodes of the structure. Additional helper nodes along the beam axes are generated, spaced at one-third of the mean edge length of the given mesh.
Each mesh vertex transfers its load to the nearest node. If there are several nodes within a radius less than “LDist” as set in the “Assemble” component, the vertex load is evenly distributed among them. The loads received by the helper nodes along the beam axes are summed and divided by the element length, resulting in an approximately equivalent uniformly distributed load placed on the element. A crude mesh may lead to a locally incorrect distribution of loads. In Fig. 3.2.1.6, the points closest to the vertices are the element’s endpoints, so the helper nodes along the beam axis do not receive a share in the mesh load, resulting in no line load.
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 name of the load case in which the surface load shall act.
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 . The orientation of the load-vector depends on the checkbox selected under “Orientation” (see also fig. 3.2.1.8):
"local to mesh”: The local coordinate system for loads corresponds to that given in section 3.1.12. The local x-axis is parallel to the global x-direction unless the mesh-face normal is parallel to the global x-direction, in which case the local x-axis points in the global y-direction. The local z-axis is always perpendicular to the mesh-face, with its orientation depending on the order of the vertices. A surface load with components only in the 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, with the surface load distributed over the area resulting from projecting the mesh faces to global coordinate planes. This simulates the action of snow load.
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.
