f361fee969
Snapshots the current development tree, headlined by proper load combinations (user request): a reusable LoadCombination entity of weighted completed static-case results (e.g. 1.2xDead + 1.6xLive). - core: LoadCombination/LoadCombinationItem entities, Project integration (lookup, unique ids, reference validation) - services: combinations.py (linear superposition + envelope), exported via services __init__ - commands: undoable Add/Delete/Update for combinations - GUI: Load Combinations manager dialog, Run-dialog evaluation, envelope display in Results panel, Combinations tab in Table dock - tests: unit coverage (validation, math, error paths) + integration superposition check vs a single factored run
31 lines
852 B
YAML
31 lines
852 B
YAML
name: Feature request
|
|
description: Propose a new feature or improvement
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: textarea
|
|
id: motivation
|
|
attributes:
|
|
label: Motivation
|
|
description: What engineering problem does this solve?
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed solution
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: phase
|
|
attributes:
|
|
label: Roadmap phase this fits into
|
|
options:
|
|
- "Phase 1 — Core Model"
|
|
- "Phase 2 — OpenSees Service"
|
|
- "Phase 3 — 3D Viewport"
|
|
- "Phase 4 — Modeling Tools"
|
|
- "Phase 5 — Properties"
|
|
- "Phase 6 — Analysis Pipeline"
|
|
- "Phase 7 — Post-processing"
|
|
- "Phase 8 — Earthquake Engineering"
|
|
- "Out of scope / new"
|