osis-python 0.7.1__tar.gz → 0.7.3__tar.gz

{osis_python-0.7.1/src/osis_python.egg-info → osis_python-0.7.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: osis-python
-Version: 0.7.1
+Version: 0.7.3
 Summary: A Python client library for Osis APDL
 Author-email: "CCCC Highway Consultant Co. Ltd." <support@osisbim.com>
 License-Expression: MIT
@@ -53,10 +53,12 @@ pip install osis-python -i https://pypi.org/simple
 
 ## Requirements
 
-- OSIS >= 5.0 (includes the required Python runtime environment)
+- OSIS >= 5.1 (short-form command names like `N`/`Ele`/`Sec` are accepted by both the converter and runtime)
 - Python >= 3.8
 - **Solver-only mode** additionally requires the solver distribution that ships `PySolver.dll` (e.g. `D:\OSIS_Solver\Rbin64`).
 
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
 ## Quick Start
 
 ### 1. Using OSISEngine (Recommended)
@@ -398,7 +400,7 @@ lc.create_nforce(4, fx=200000, fy=0, fz=0)
 engine.solve()
 ```
 
-## End-to-End Demo
+## End-to-End Demo (Solver-Only Mode)
 
 See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end example that:
 
@@ -408,3 +410,109 @@ See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end exa
 - Exports LCND / LCEF / EnvND / EnvEF results to CSV
 
 The demo reuses the prep modules from `tests/output/output_py/25m简支小箱梁中梁-solveronly/`, so it serves both as a smoke test and a copy-paste template.
+
+## Batch Execution
+
+For non-interactive workflows (large models, customer scripts that took tens of minutes per command), wrap your script in `with batch():` to merge **all** OSIS commands into a **single** `OSIS_Run` HTTP request when the block exits:
+
+```python
+from pyosis import batch
+
+with batch():
+    engine.clear()
+    engine.clc()
+    engine.control.set_gravity_acceleration(9.8066)
+    engine.material.create_conc(no=1, name="C50", ...)
+    for i in range(1000):
+        engine.node.create(no=i + 1, x=i * 0.1, y=0.0, z=0.0)
+    for i in range(999):
+        engine.element.create_beam3d(no=i + 1, node1=i + 1, node2=i + 2, ...)
+```
+
+Server-side `OSIS_Run` calls `SplitOsisCommands` once and then a single `Execution(&v)`, so the network round-trip cost is paid exactly once instead of once per command. Intermediate reads (`get`, `all`) auto-flush the buffer first, so cached objects stay correct.
+
+Notes:
+
+- Nested `with batch():` is supported — the inner exit does not flush; only the outermost exit does.
+- If the block raises, the buffered commands added since `__enter__` are discarded.
+- `flush()` can be called inside the block to force an early flush.
+- `next_no()` (auto-numbering) raises inside `batch()` because it would need to query the server mid-batch; pass `no=...` explicitly, or run auto-numbering outside the batch.
+
+Benchmark on the `25m简支小箱梁中梁` project (`.out` of ~3000 commands): before `batch()` ~3000 round-trips; with `batch()` 3 round-trips (clear + clc + one final flush), **~1000x compression**.
+
+## .out → pyosis Converter
+
+pyosis ships a converter that turns an OSIS command stream (`.out`) into a clean, runnable pyosis project. This is the easiest way to migrate a legacy APDL/SML script.
+
+```bash
+python src/pyosis/transfer/out_to_python.py path/to/model.out path/to/output_project
+```
+
+Generated layout:
+
+```
+output_project/
+└── prep/
+    ├── main.py          # Entry point (batch mode, runs all 10 modules)
+    ├── _1_control.py    # Global control parameters
+    ├── _2_property.py   # Geometry / coordinate / damping / creep properties
+    ├── _3_material.py   # Materials
+    ├── _4_section.py    # Sections (incl. mesh)
+    ├── _5_node.py       # Nodes
+    ├── _6_element.py    # Elements
+    ├── _7_boundary.py   # Boundaries
+    ├── _8_loadcase.py   # Load cases
+    ├── _9_analysis.py   # Analysis settings (settlement / live / dynamic / stability)
+    └── _10_stage.py     # Construction stages
+```
+
+The generated `main.py` wraps the entire modelling flow in `with batch():`, so the whole project is sent to OSIS in one HTTP request — matching the OSIS server's native batching path.
+
+Run it:
+
+```bash
+cd output_project
+python prep/main.py            # build the model
+python prep/main.py --solve    # build + solve
+```
+
+Notes on the converter:
+
+- Both long-form command names (`Node`, `Element`, `Section`, `Material`, `LoadCase`, `Boundary`, `Stage`) and OSIS 5.1 short-form aliases (`N`, `Ele`, `Sec`/`SecOff`/`SecMesh`, `Mat`, `LC`, `Bd`, `Stg`) are recognized and normalized.
+- `SectionMesh` is emitted with the new `Index, PartID, MeshMethod, MeshSize` layout (Section 7.3.6.2) — `PartID = 1` for concrete sections, `2` for templated composite sections.
+- `Spline3D` is dispatched to `engine.geometry.create_general` / `create_natural` / `create_arc2d` / `create_arc3d` based on the type field.
+- Commands that are not yet modeled are passed through verbatim via `engine.run(...)` so the model still runs; rewrite them into pyosis calls manually if needed.
+
+## Chained Method Calls
+
+The dataclass returned by `get()` supports method chaining without server round-trips:
+
+```python
+with batch():
+    lc = engine.load.create("Self-weight", load_case_type="D")
+    lc.create_gravity()
+    lc.create_nforce(node=1, fx=0, fy=-1000, fz=0)
+    # ↑ all three commands are queued; the OSIS_Run request only fires at exit
+```
+
+Accessing identity attributes (`lc.no`, `lc.name`) does not touch the server. Accessing data fields (`lc.type`, `lc.elements`) materializes the object (one-time flush + query), then caches it.
+
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
+## End-to-End Demo (GUI Mode)
+
+The single-file demo [`tests/demo_gui.py`](tests/demo_gui.py) is a merged version of the project generated from `tests/output/xiaoxiangliang.out`. Run it against an open OSIS 5.1+ GUI:
+
+```bash
+python tests/demo_gui.py            # build the model
+python tests/demo_gui.py --solve    # build + solve
+```
+
+The file contains the engine setup, all 10 `build_*` functions (control / property / material / section / node / element / boundary / loadcase / analysis / stage), and a `build_model()` driver that wraps everything in `with batch():` — so ~250 commands hit OSIS in a single `OSIS_Run` request.
+
+To regenerate both the single-file demo and the multi-module project:
+
+```bash
+python tests/_merge_demo_gui.py                                    # -> tests/demo_gui.py
+python src/pyosis/transfer/out_to_python.py tests/output/xiaoxiangliang.out tests/output/output_py/xiaoxiangliang
+```

{osis_python-0.7.1 → osis_python-0.7.3}/README.md

@@ -22,10 +22,12 @@ pip install osis-python -i https://pypi.org/simple
 
 ## Requirements
 
-- OSIS >= 5.0 (includes the required Python runtime environment)
+- OSIS >= 5.1 (short-form command names like `N`/`Ele`/`Sec` are accepted by both the converter and runtime)
 - Python >= 3.8
 - **Solver-only mode** additionally requires the solver distribution that ships `PySolver.dll` (e.g. `D:\OSIS_Solver\Rbin64`).
 
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
 ## Quick Start
 
 ### 1. Using OSISEngine (Recommended)
@@ -367,7 +369,7 @@ lc.create_nforce(4, fx=200000, fy=0, fz=0)
 engine.solve()
 ```
 
-## End-to-End Demo
+## End-to-End Demo (Solver-Only Mode)
 
 See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end example that:
 
@@ -377,3 +379,109 @@ See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end exa
 - Exports LCND / LCEF / EnvND / EnvEF results to CSV
 
 The demo reuses the prep modules from `tests/output/output_py/25m简支小箱梁中梁-solveronly/`, so it serves both as a smoke test and a copy-paste template.
+
+## Batch Execution
+
+For non-interactive workflows (large models, customer scripts that took tens of minutes per command), wrap your script in `with batch():` to merge **all** OSIS commands into a **single** `OSIS_Run` HTTP request when the block exits:
+
+```python
+from pyosis import batch
+
+with batch():
+    engine.clear()
+    engine.clc()
+    engine.control.set_gravity_acceleration(9.8066)
+    engine.material.create_conc(no=1, name="C50", ...)
+    for i in range(1000):
+        engine.node.create(no=i + 1, x=i * 0.1, y=0.0, z=0.0)
+    for i in range(999):
+        engine.element.create_beam3d(no=i + 1, node1=i + 1, node2=i + 2, ...)
+```
+
+Server-side `OSIS_Run` calls `SplitOsisCommands` once and then a single `Execution(&v)`, so the network round-trip cost is paid exactly once instead of once per command. Intermediate reads (`get`, `all`) auto-flush the buffer first, so cached objects stay correct.
+
+Notes:
+
+- Nested `with batch():` is supported — the inner exit does not flush; only the outermost exit does.
+- If the block raises, the buffered commands added since `__enter__` are discarded.
+- `flush()` can be called inside the block to force an early flush.
+- `next_no()` (auto-numbering) raises inside `batch()` because it would need to query the server mid-batch; pass `no=...` explicitly, or run auto-numbering outside the batch.
+
+Benchmark on the `25m简支小箱梁中梁` project (`.out` of ~3000 commands): before `batch()` ~3000 round-trips; with `batch()` 3 round-trips (clear + clc + one final flush), **~1000x compression**.
+
+## .out → pyosis Converter
+
+pyosis ships a converter that turns an OSIS command stream (`.out`) into a clean, runnable pyosis project. This is the easiest way to migrate a legacy APDL/SML script.
+
+```bash
+python src/pyosis/transfer/out_to_python.py path/to/model.out path/to/output_project
+```
+
+Generated layout:
+
+```
+output_project/
+└── prep/
+    ├── main.py          # Entry point (batch mode, runs all 10 modules)
+    ├── _1_control.py    # Global control parameters
+    ├── _2_property.py   # Geometry / coordinate / damping / creep properties
+    ├── _3_material.py   # Materials
+    ├── _4_section.py    # Sections (incl. mesh)
+    ├── _5_node.py       # Nodes
+    ├── _6_element.py    # Elements
+    ├── _7_boundary.py   # Boundaries
+    ├── _8_loadcase.py   # Load cases
+    ├── _9_analysis.py   # Analysis settings (settlement / live / dynamic / stability)
+    └── _10_stage.py     # Construction stages
+```
+
+The generated `main.py` wraps the entire modelling flow in `with batch():`, so the whole project is sent to OSIS in one HTTP request — matching the OSIS server's native batching path.
+
+Run it:
+
+```bash
+cd output_project
+python prep/main.py            # build the model
+python prep/main.py --solve    # build + solve
+```
+
+Notes on the converter:
+
+- Both long-form command names (`Node`, `Element`, `Section`, `Material`, `LoadCase`, `Boundary`, `Stage`) and OSIS 5.1 short-form aliases (`N`, `Ele`, `Sec`/`SecOff`/`SecMesh`, `Mat`, `LC`, `Bd`, `Stg`) are recognized and normalized.
+- `SectionMesh` is emitted with the new `Index, PartID, MeshMethod, MeshSize` layout (Section 7.3.6.2) — `PartID = 1` for concrete sections, `2` for templated composite sections.
+- `Spline3D` is dispatched to `engine.geometry.create_general` / `create_natural` / `create_arc2d` / `create_arc3d` based on the type field.
+- Commands that are not yet modeled are passed through verbatim via `engine.run(...)` so the model still runs; rewrite them into pyosis calls manually if needed.
+
+## Chained Method Calls
+
+The dataclass returned by `get()` supports method chaining without server round-trips:
+
+```python
+with batch():
+    lc = engine.load.create("Self-weight", load_case_type="D")
+    lc.create_gravity()
+    lc.create_nforce(node=1, fx=0, fy=-1000, fz=0)
+    # ↑ all three commands are queued; the OSIS_Run request only fires at exit
+```
+
+Accessing identity attributes (`lc.no`, `lc.name`) does not touch the server. Accessing data fields (`lc.type`, `lc.elements`) materializes the object (one-time flush + query), then caches it.
+
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
+## End-to-End Demo (GUI Mode)
+
+The single-file demo [`tests/demo_gui.py`](tests/demo_gui.py) is a merged version of the project generated from `tests/output/xiaoxiangliang.out`. Run it against an open OSIS 5.1+ GUI:
+
+```bash
+python tests/demo_gui.py            # build the model
+python tests/demo_gui.py --solve    # build + solve
+```
+
+The file contains the engine setup, all 10 `build_*` functions (control / property / material / section / node / element / boundary / loadcase / analysis / stage), and a `build_model()` driver that wraps everything in `with batch():` — so ~250 commands hit OSIS in a single `OSIS_Run` request.
+
+To regenerate both the single-file demo and the multi-module project:
+
+```bash
+python tests/_merge_demo_gui.py                                    # -> tests/demo_gui.py
+python src/pyosis/transfer/out_to_python.py tests/output/xiaoxiangliang.out tests/output/output_py/xiaoxiangliang
+```

{osis_python-0.7.1 → osis_python-0.7.3/src/osis_python.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: osis-python
-Version: 0.7.1
+Version: 0.7.3
 Summary: A Python client library for Osis APDL
 Author-email: "CCCC Highway Consultant Co. Ltd." <support@osisbim.com>
 License-Expression: MIT
@@ -53,10 +53,12 @@ pip install osis-python -i https://pypi.org/simple
 
 ## Requirements
 
-- OSIS >= 5.0 (includes the required Python runtime environment)
+- OSIS >= 5.1 (short-form command names like `N`/`Ele`/`Sec` are accepted by both the converter and runtime)
 - Python >= 3.8
 - **Solver-only mode** additionally requires the solver distribution that ships `PySolver.dll` (e.g. `D:\OSIS_Solver\Rbin64`).
 
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
 ## Quick Start
 
 ### 1. Using OSISEngine (Recommended)
@@ -398,7 +400,7 @@ lc.create_nforce(4, fx=200000, fy=0, fz=0)
 engine.solve()
 ```
 
-## End-to-End Demo
+## End-to-End Demo (Solver-Only Mode)
 
 See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end example that:
 
@@ -408,3 +410,109 @@ See [`tests/pyosis_demo.py`](tests/pyosis_demo.py) for a runnable end-to-end exa
 - Exports LCND / LCEF / EnvND / EnvEF results to CSV
 
 The demo reuses the prep modules from `tests/output/output_py/25m简支小箱梁中梁-solveronly/`, so it serves both as a smoke test and a copy-paste template.
+
+## Batch Execution
+
+For non-interactive workflows (large models, customer scripts that took tens of minutes per command), wrap your script in `with batch():` to merge **all** OSIS commands into a **single** `OSIS_Run` HTTP request when the block exits:
+
+```python
+from pyosis import batch
+
+with batch():
+    engine.clear()
+    engine.clc()
+    engine.control.set_gravity_acceleration(9.8066)
+    engine.material.create_conc(no=1, name="C50", ...)
+    for i in range(1000):
+        engine.node.create(no=i + 1, x=i * 0.1, y=0.0, z=0.0)
+    for i in range(999):
+        engine.element.create_beam3d(no=i + 1, node1=i + 1, node2=i + 2, ...)
+```
+
+Server-side `OSIS_Run` calls `SplitOsisCommands` once and then a single `Execution(&v)`, so the network round-trip cost is paid exactly once instead of once per command. Intermediate reads (`get`, `all`) auto-flush the buffer first, so cached objects stay correct.
+
+Notes:
+
+- Nested `with batch():` is supported — the inner exit does not flush; only the outermost exit does.
+- If the block raises, the buffered commands added since `__enter__` are discarded.
+- `flush()` can be called inside the block to force an early flush.
+- `next_no()` (auto-numbering) raises inside `batch()` because it would need to query the server mid-batch; pass `no=...` explicitly, or run auto-numbering outside the batch.
+
+Benchmark on the `25m简支小箱梁中梁` project (`.out` of ~3000 commands): before `batch()` ~3000 round-trips; with `batch()` 3 round-trips (clear + clc + one final flush), **~1000x compression**.
+
+## .out → pyosis Converter
+
+pyosis ships a converter that turns an OSIS command stream (`.out`) into a clean, runnable pyosis project. This is the easiest way to migrate a legacy APDL/SML script.
+
+```bash
+python src/pyosis/transfer/out_to_python.py path/to/model.out path/to/output_project
+```
+
+Generated layout:
+
+```
+output_project/
+└── prep/
+    ├── main.py          # Entry point (batch mode, runs all 10 modules)
+    ├── _1_control.py    # Global control parameters
+    ├── _2_property.py   # Geometry / coordinate / damping / creep properties
+    ├── _3_material.py   # Materials
+    ├── _4_section.py    # Sections (incl. mesh)
+    ├── _5_node.py       # Nodes
+    ├── _6_element.py    # Elements
+    ├── _7_boundary.py   # Boundaries
+    ├── _8_loadcase.py   # Load cases
+    ├── _9_analysis.py   # Analysis settings (settlement / live / dynamic / stability)
+    └── _10_stage.py     # Construction stages
+```
+
+The generated `main.py` wraps the entire modelling flow in `with batch():`, so the whole project is sent to OSIS in one HTTP request — matching the OSIS server's native batching path.
+
+Run it:
+
+```bash
+cd output_project
+python prep/main.py            # build the model
+python prep/main.py --solve    # build + solve
+```
+
+Notes on the converter:
+
+- Both long-form command names (`Node`, `Element`, `Section`, `Material`, `LoadCase`, `Boundary`, `Stage`) and OSIS 5.1 short-form aliases (`N`, `Ele`, `Sec`/`SecOff`/`SecMesh`, `Mat`, `LC`, `Bd`, `Stg`) are recognized and normalized.
+- `SectionMesh` is emitted with the new `Index, PartID, MeshMethod, MeshSize` layout (Section 7.3.6.2) — `PartID = 1` for concrete sections, `2` for templated composite sections.
+- `Spline3D` is dispatched to `engine.geometry.create_general` / `create_natural` / `create_arc2d` / `create_arc3d` based on the type field.
+- Commands that are not yet modeled are passed through verbatim via `engine.run(...)` so the model still runs; rewrite them into pyosis calls manually if needed.
+
+## Chained Method Calls
+
+The dataclass returned by `get()` supports method chaining without server round-trips:
+
+```python
+with batch():
+    lc = engine.load.create("Self-weight", load_case_type="D")
+    lc.create_gravity()
+    lc.create_nforce(node=1, fx=0, fy=-1000, fz=0)
+    # ↑ all three commands are queued; the OSIS_Run request only fires at exit
+```
+
+Accessing identity attributes (`lc.no`, `lc.name`) does not touch the server. Accessing data fields (`lc.type`, `lc.elements`) materializes the object (one-time flush + query), then caches it.
+
+> OSIS 5.1 HTTP server bug workaround: the `/OSIS_Run` command-stream splitter does not strip `//` line comments, so a comment line and the command that follows it are merged into one bad command. The pyosis `.out` converter already strips comments before sending; if you ever build a raw `.out` payload yourself, pre-process the file or use `osis_run()` through the generated `main.py`.
+
+## End-to-End Demo (GUI Mode)
+
+The single-file demo [`tests/demo_gui.py`](tests/demo_gui.py) is a merged version of the project generated from `tests/output/xiaoxiangliang.out`. Run it against an open OSIS 5.1+ GUI:
+
+```bash
+python tests/demo_gui.py            # build the model
+python tests/demo_gui.py --solve    # build + solve
+```
+
+The file contains the engine setup, all 10 `build_*` functions (control / property / material / section / node / element / boundary / loadcase / analysis / stage), and a `build_model()` driver that wraps everything in `with batch():` — so ~250 commands hit OSIS in a single `OSIS_Run` request.
+
+To regenerate both the single-file demo and the multi-module project:
+
+```bash
+python tests/_merge_demo_gui.py                                    # -> tests/demo_gui.py
+python src/pyosis/transfer/out_to_python.py tests/output/xiaoxiangliang.out tests/output/output_py/xiaoxiangliang
+```

{osis_python-0.7.1 → osis_python-0.7.3}/src/osis_python.egg-info/SOURCES.txt

@@ -20,7 +20,6 @@ src/pyosis/core/all_func.py
 src/pyosis/core/apdl_sync.py
 src/pyosis/core/basic_manager.py
 src/pyosis/core/batch.py
-src/pyosis/core/build.py
 src/pyosis/core/client.py
 src/pyosis/core/command.py
 src/pyosis/core/engine.py

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/__init__.py

@@ -7,8 +7,7 @@ A library for extending OSIS functionality.
 A library that allows users to use CAE with great flexibility.
 """
 
-__version__ = "0.7.1"
-__author__ = "CCCC Highway Consultant Co. Ltd." # 中交公路规划设计院 - 工程技术研究中心 - lzh - wjh - myf
+__version__ = "0.7.3"
 
 from .core.engine import OSISEngine
 from .core.batch import batch, flush, batch_state, BatchError

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/boundary/manager.py

@@ -536,7 +536,7 @@ class BoundaryGroupManager(BasicManager):
         Returns:
             BoundaryGroup: 创建（或刷新后的）边界组对象
         '''
-        ok, err = osis_boundary_group(name, op, *param)
+        ok, err = osis_boundary_group(name, str(op).lower(), *param)
         if not ok:
             raise RuntimeError(f"创建边界组 {name} 失败: {err}")
         return self.get(name)

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/element/manager.py

@@ -316,7 +316,7 @@ class ElementGroupManager(BasicManager):
         Returns:
             ElementGroup: 创建的单元组对象
         """
-        ok, err = osis_element_group(name, op, *param)
+        ok, err = osis_element_group(name, str(op).lower(), *param)
         if not ok:
             raise RuntimeError(f"创建单元组 {name} 失败: {err}")
         return self.get(name)

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/live/manager.py

@@ -265,6 +265,7 @@ class LiveCase:
         Returns:
             更新后的 LiveCase 对象
         """
+        op = str(op).lower()
         if op in ("a", "m"):
             _MU_PARAM_COUNT = {
                 "SIMPLE": 4,
@@ -278,7 +279,7 @@ class LiveCase:
             grade_name, scalar, mu_flag = args[0], float(args[1]), int(args[2])
             rest = args[4:]
             if mu_flag == 1:
-                bridge_type = args[3] or "SIMPLE"
+                bridge_type = (args[3] or "SIMPLE").strip().upper()
                 mu_count = _MU_PARAM_COUNT.get(bridge_type, 1)
                 mu_params: list[float] = [float(x) for x in rest[:mu_count]]
                 lane_names: list[str] = list(rest[mu_count:])

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/load/manager.py

@@ -295,6 +295,8 @@ class LoadCase:
             elem, e_coord, n_range, *rest = args
             forces = [list(rest[i: i + 6]) for i in range(0, len(rest), 6)]
             return self.create_concentrated_force(elem,e_coord,is_moment=(type_key == "PTM"),forces=forces)
+        if type_key not in _creator:
+            raise ValueError(f"未知荷载类型: {type!r}，支持: {', '.join(_creator)}")
         return _creator[type_key](*args, **kwargs)
 
     def create_gravity(

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/material/manager.py

@@ -158,9 +158,10 @@ class MaterialManager(BasicManager):
             "REBAR": self.create_rebar,
             "CUSTOM": self.create_custom,
         }
-        if type not in _creator:
-            raise ValueError(f"未知材料类型: {type}")
-        return _creator[type](no, name, *args, **kwargs)
+        type_key = str(type).strip().upper()
+        if type_key not in _creator:
+            raise ValueError(f"未知材料类型: {type!r}，支持: {', '.join(_creator)}")
+        return _creator[type_key](no, name, *args, **kwargs)
 
     def create_conc(
         self,

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/property/manager.py

@@ -518,9 +518,9 @@ class DampingManager(BasicManager):
             raise ValueError(
                 f"未知阻尼类型: {type!r}，支持: {', '.join(sorted(_supported_types))}"
             )
-        if type_key == "modal":
+        if type_key == "MODAL":
             return self.create_modal(name, *args, **kwargs)
-        # type_key == "ryl"
+        # type_key == "RYL"
         method = args[0] if args else kwargs.get("method")
         _supported_methods = {0: "根据公式计算因子", 1: "自定义因子"}
         if method not in _supported_methods:

{osis_python-0.7.1 → osis_python-0.7.3}/src/pyosis/section/manager.py

@@ -384,15 +384,18 @@ class Section:
         """添加或修改组合截面 Part（按类型分发）
 
         Args:
-            type: Part 类型
+            type: Part 类型（大小写不敏感）
                 * POLYGON = 多边形
                 * LINE    = 折线
             args: 剩余参数透传给对应子方法
         """
-        if type == "POLYGON":
+        key = str(type).upper()
+        if key == "POLYGON":
             self.add_composite_part_polygon(*args)
-        elif type == "LINE":
+        elif key == "LINE":
             self.add_composite_part_line(*args)
+        else:
+            raise ValueError(f"未知 Part 类型: {type!r}，支持 POLYGON/LINE")
 
     # ── 组合截面材料 ──────────────────────────
 
@@ -682,21 +685,26 @@ class Section:
 
         Args:
             rebar_no: 钢筋编号
-            type: 钢筋输入方式
+            type: 钢筋输入方式（大小写不敏感，兼容命令流全大写写法 LINEA 等）
                 * Point  = 点输入
                 * LineA  = 直线-垂直方式 A
                 * LineB  = 直线-垂直方式 B
                 * Circle = 圆周输入
             args: 剩余参数透传给对应子方法
         """
-        if type == "Point":
+        key = str(type).upper()
+        if key == "POINT":
             self.add_rebar_point(rebar_no, *args)
-        elif type == "LineA":
+        elif key == "LINEA":
             self.add_rebar_line_a(rebar_no, *args)
-        elif type == "LineB":
+        elif key == "LINEB":
             self.add_rebar_line_b(rebar_no, *args)
-        elif type == "Circle":
+        elif key == "CIRCLE":
             self.add_rebar_circle(rebar_no, *args)
+        else:
+            raise ValueError(
+                f"未知纵向钢筋类型: {type!r}，支持 Point/LineA/LineB/Circle"
+            )
 
     def add_rebar_s(
         self,
@@ -706,21 +714,26 @@ class Section:
         """添加或修改抗剪钢筋（按类型分发）
 
         Args:
-            type: 钢筋类型
+            type: 钢筋类型（大小写不敏感，兼容 SHEARSTIRRUP 等命令流写法）
                 * BentUpRebar      = 弯起钢筋
                 * ShearStirrup     = 抗剪箍筋
                 * WebVerticalRebar = 腹板竖筋
                 * TorsionalStirrup = 扭转箍筋
             args: 剩余参数透传给对应子方法
         """
-        if type == "BentUpRebar":
+        key = str(type).upper()
+        if key == "BENTUPREBAR":
             self.add_rebar_s_bent_up(*args)
-        elif type == "ShearStirrup":
+        elif key == "SHEARSTIRRUP":
             self.add_rebar_s_shear_stirrup(*args)
-        elif type == "WebVerticalRebar":
+        elif key == "WEBVERTICALREBAR":
             self.add_rebar_s_web_vertical(*args)
-        elif type == "TorsionalStirrup":
+        elif key == "TORSIONALSTIRRUP":
             self.add_rebar_s_torsional_stirrup(*args)
+        else:
+            raise ValueError(
+                f"未知抗剪钢筋类型: {type!r}，支持 BentUpRebar/ShearStirrup/WebVerticalRebar/TorsionalStirrup"
+            )
 
     def add_rib(
         self,
@@ -730,7 +743,7 @@ class Section:
         """添加或修改加劲肋（按类型分发）
 
         Args:
-            type: 加劲肋类型
+            type: 加劲肋类型（大小写不敏感）
                 * Flat = 扁平加劲肋
                 * T    = T 形加劲肋
                 * U    = U 形加劲肋
@@ -738,14 +751,19 @@ class Section:
                 * LR   = 右 L 形加劲肋
             args: 剩余参数透传给对应子方法
         """
-        if type == "Flat":
+        key = str(type).upper()
+        if key == "FLAT":
             self.add_rib_flat(*args)
-        elif type == "T":
+        elif key == "T":
             self.add_rib_t(*args)
-        elif type == "U":
+        elif key == "U":
             self.add_rib_u(*args)
-        elif type in ("LL", "LR"):
-            self.add_rib_l(args[0], type, *args[1:])
+        elif key in ("LL", "LR"):
+            self.add_rib_l(args[0], key, *args[1:])
+        else:
+            raise ValueError(
+                f"未知加劲肋类型: {type!r}，支持 Flat/T/U/LL/LR"
+            )
 
     def add_rib_flat(
         self,
@@ -909,15 +927,22 @@ class Section:
         '''删除箍筋
 
         Args:
-            rebar_type (str): 钢筋类型
+            rebar_type (str): 钢筋类型（大小写不敏感）
                 * BentUpRebar = 弯起钢筋
                 * ShearStirrup = 抗剪箍筋
                 * WebVerticalRebar = 腹板竖筋
                 * TorsionalStirrup = 扭转箍筋
 
         Raises:
+            ValueError: 未知的钢筋类型
             RuntimeError: 删除失败时抛出
         '''
+        if str(rebar_type).strip().upper() not in (
+            "BENTUPREBAR", "SHEARSTIRRUP", "WEBVERTICALREBAR", "TORSIONALSTIRRUP",
+        ):
+            raise ValueError(
+                f"未知抗剪钢筋类型: {rebar_type!r}，支持 BentUpRebar/ShearStirrup/WebVerticalRebar/TorsionalStirrup"
+            )
         ok, err = osis_rebar_s_del(self.no, rebar_type)
         if not ok:
             raise RuntimeError(f"删除截面 {self.no} 箍筋 {rebar_type} 失败: {err}")