Draft. This manual is new and still growing. If something here does not match what you see in the software, the software is right — tell us and we will fix the page.
Explicit analysis
Where it is
Not a setup-tree node. Embedded in the application.
Controls
ANALYSIS
Drop height
- Control: value (
ValueField) - Unit: m
- Value modes: none (plain entry)
- Shown when:
root.drop
The fall is not simulated - only the landing. The part starts just above the floor at the speed a fall from this height gives, sqrt(2gh), so the run spends its steps on the impact.
Velocity X
- Control: value (
ValueField) - Unit: m/s
- Value modes: none (plain entry)
- Shown when:
!root.drop
Velocity Y
- Control: value (
ValueField) - Unit: m/s
- Value modes: none (plain entry)
- Shown when:
!root.drop
Velocity Z
- Control: value (
ValueField) - Unit: m/s
- Value modes: none (plain entry)
- Shown when:
!root.drop
The floor is a plane normal to +Z below the part, so a negative Z velocity is what hits it. A velocity with no floor is a body flying freely, which the validator refuses.
Rigid floor
- Control: on/off (
ToggleRow) - Shown when:
!root.drop
An infinite rigid plane under the lowest node of the part. A drop always has one; an impact may be into it or, later, into another part.
Floor clearance
- Control: value (
ValueField) - Unit: m
- Value modes: none (plain entry)
- Shown when:
root.drop || ExplicitState.floor
The gap between the lowest node and the floor when time starts. Small, so the run does not spend its steps on free flight; not zero, so the first step is not already a penetration.
TIME
Event duration
- Control: value (
ValueField) - Unit: s
- Value modes: none (plain entry)
How long to follow the impact. The time STEP is not asked for: an explicit code sets it from the smallest element and the speed of sound in the material (the Courant limit), and a finer mesh means smaller steps and a longer run.
Animation interval
- Control: value (
ValueField) - Unit: s
- Value modes: none (plain entry)
How often a state is written. The results shown are the LAST state - the end of the event - with stress and plastic strain averaged from the elements onto the nodes.
Problems reported against this step
The application reports no problems against this step.
… marks a value the application computes at run time, so the source carries no fixed text for it.