OpenSite/Known limitations

From BathAfrica Documentation
Revision as of 15:09, 29 October 2026 by BathAfrica (talk | contribs) (Complete OpenSite user manual, tutorial pathways and support navigation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
OpenSite 0.0.1 · DevelopmentSource scope and availability

Use the available development workflows without assuming an engineering application milestone is complete.

Available does not mean production release

The documented source includes local documents, material data, quantities, expressions, optional GUI/Python and a viewport foundation. This is an internal development baseline, not a validated production FEM package.

Not implemented as user workflows

  • General CAD/geometry modelling, meshing, FEM solver execution and design-code checking.
  • Completed section-design/section-library workflows.
  • Production standard material grades selected and verified for distribution.
  • Saved named desktop workspaces or a public add-on marketplace.
  • Autosave/crash recovery and persistent undo history.
  • Working production online account/activation and a public installer.
  • Table/cell-reference editing and later analysis/result workflows.

Important working boundaries

Python code is trusted code and cancellation is cooperative. Plot tabs display published raster images. Unit profiles change presentation, not physical values. Material validation is not design certification. Missing providers can preserve data without making computations available.

Check your build

Menus can depend on optional features, extension availability, current selection and authorization. Read OpenSite/Documentation status for the reviewed snapshot and OpenSite/FAQ for common questions.