김경종
59 lines
2.6 KiB
Markdown
59 lines
2.6 KiB
Markdown
---
|
|
type: concept
|
|
title: "Midas Civil Numerical Analysis Model"
|
|
created: 2026-06-02
|
|
updated: 2026-06-02
|
|
address: c-000159
|
|
aliases:
|
|
- MIDAS Civil numerical model
|
|
- midas Civil analysis model
|
|
tags:
|
|
- concept
|
|
- finite-element-method
|
|
- midas-civil
|
|
- modeling
|
|
status: current
|
|
related:
|
|
- "[[Midas-Civil-Analysis-Reference|Midas Civil Analysis Reference]]"
|
|
- "[[midas Civil]]"
|
|
- "[[Finite Element Method]]"
|
|
- "[[Finite Element Program Implementation]]"
|
|
- "[[Finite Element Modeling and Convergence Checks]]"
|
|
sources:
|
|
- "[[Midas-Civil-Analysis-Reference|Midas Civil Analysis Reference]]"
|
|
source_refs:
|
|
- source: "[[Midas-Civil-Analysis-Reference|Midas Civil Analysis Reference]]"
|
|
raw_path: ".raw/MidasCivilAnalysisReference/"
|
|
raw_files:
|
|
- "MidasCivilAnalysisReference_057.md"
|
|
md_indices:
|
|
- 57
|
|
match: "heuristic-heading-keyword"
|
|
confidence: low
|
|
---
|
|
|
|
# Midas Civil Numerical Analysis Model
|
|
|
|
## Definition
|
|
|
|
Midas Civil numerical analysis model is the structural model abstraction described in the [[Midas-Civil-Analysis-Reference|Midas Civil Analysis Reference]]: nodes locate the structure, finite elements convert members and continua into numerical data, and boundary conditions describe connection to adjacent bodies or supports.
|
|
|
|
## How It Works
|
|
|
|
The manual emphasizes three coordinate layers. Global coordinates define the model reference frame. Element coordinates define member or element-local quantities. Node local coordinates let users prescribe constraints, boundary springs, displacements, and reactions in arbitrary directions.
|
|
|
|
The model is intentionally simplified from the real structure. The manual's practical warning is that simplification must stay inside the analysis purpose: element type, mesh idealization, member offsets, boundary assumptions, and local axes can strongly change the computed response.
|
|
|
|
## Solver Development Notes
|
|
|
|
- Input data should separate nodes, element connectivity, element type, material, stiffness/section data, and boundary/link definitions.
|
|
- Coordinate transformations are first-class data, not postprocessing details.
|
|
- A custom solver needs diagnostics for missing stiffness, inconsistent local axes, overconstraints, and boundary assumptions.
|
|
- Verification should include model-equivalence checks: same physical bridge member modeled with different element or offset choices should be compared intentionally.
|
|
|
|
## Connections
|
|
|
|
- [[Finite Element Method]] supplies the general discretization logic.
|
|
- [[Finite Element Program Implementation]] maps this model into assembly, solve, and recovery stages.
|
|
- [[Finite Element Modeling and Convergence Checks]] captures the analyst-side reliability concern.
|