Skip to content

computation-engine.md

Latest commit

 

History

History
47 lines (35 loc) · 2 KB

computation-engine.md

File metadata and controls

47 lines (35 loc) · 2 KB

Computation engine (Sigima)

The engine that actually computes signals and images is Sigima, a headless Python library shared between desktop DataLab and DataLab-Web. Whatever the host application, the algorithms, parameters and numerical results are the same.

Where the documentation lives

There is no separate Sigima documentation for the Web, by design. The existing reference on the DataLab project website — even though its screenshots show the Qt desktop UI — describes the same parameters and the same outputs as those exposed here.

Useful entry points (desktop-framed but Web-relevant):

How processings appear in DataLab-Web

The menu bar is populated automatically by introspecting Sigima's catalog (build_signal_catalog() / build_image_catalog()). When a new processing is added to Sigima upstream, it shows up in DataLab-Web at the next release without any UI code change.

Parameter dialogs

Each processing's parameters are described by a guidata.DataSet schema. DataLab-Web reads that schema and renders the dialog automatically — the same data model that the desktop application uses to draw its Qt forms.

What the desktop docs do not cover

  • The runtime constraints of the browser (memory limits, OPFS, cross-origin isolation) — see Differences from desktop DataLab.
  • DataLab-Web-specific UI affordances (Plotly toolbar, macro / notebook workers, plugin loader).
  • The TypeScript SDK for embedding DataLab-Web in another web app.

For everything else — operators, filters, fits, detection algorithms, units, ROI semantics, HDF5 file format — the desktop documentation is authoritative.