1.8 KiB
1.8 KiB
FEM batch 690f881fa00a180cd0c4bff1
Edits only; build, sync and business acceptance remain owned by the outer pipeline.
- ElementFluid1D and ElementGeometry1D now enter the existing ObjectsFem factory path in the caller's open document, apply properties transactionally, and join the active analysis. Their former temporary-document route closed the created object before returning.
- The FEM application adapter checks native analysis membership for these two commands, ElementRotation1D, MaterialReinforced and MaterialSolid before changing selection.
- Selected element/material creation rejects malformed property maps and assignments that bypass native ownership or proxy initialization. MechanicalNonlinear continues to use the desktop material factory and its native Nonlinear link.
Remaining implementation boundaries:
- EquationDeformation and EquationElasticity require selected Elmer solver ownership; the current generic analysis factory invocation does not implement that desktop contract.
- MeshRegion still explicitly rejects execution pending the selected native mesh factory/ownership path.
- PostFilterGlyph and ResultShow still explicitly reject execution pending real native result data and mounted Web visualization. ResultShow edits an existing result; it must not be validated as creation.
- Desktop task editing for the selected creation commands is not implemented by these edits. JSON property submission remains the existing application path.
- No command is declared business-accepted by this note. The six element/material commands also require outer-pipeline runtime verification, including property behavior, rollback and document persistence.
The bounded ObjectsFem source lookup was rejected with SCHEDULER_SOURCE_BUDGET_REACHED. No factory signatures or result visualization behavior were invented to bypass that boundary.