Integration boundaries

These explanations connect public pipeline declarations to the compiler, storage, viewers, and optional deployment packages. Generic mechanics live with the first-party package that owns them; these pages explain the OpenHCS boundary rather than prescribing a task sequence.

• Pipeline compilation workflow
  • Inputs
  • Compiler authorities
  • Execution boundary
  • Debugging
• Array and memory integration
  • Declaration boundary
  • Compiler and runtime boundary
  • Package ownership
• Viewer streaming
  • Display-axis ownership
  • ROI inspection and cropping
  • Spatial graphs and neuronal morphology
  • Streaming, checkpointing, and named artifacts
• Fiji streaming
  • Setup
  • Lifecycle
  • Settlement and inspection boundary
• OMERO integration
  • Durable artifact materialization
  • Compiler contract
  • Testing

Choose an explanation

pipeline_compilation_workflow

Why compilation is a declaration-to-runtime boundary and which authorities participate.

memory_type_integration

How ArrayBridge input, output, and execution metadata enters callable contracts and framework-local worker planning.

viewer_management and fiji_viewer_management

OpenHCS streaming configuration and the boundary with ZMQRuntime.

omero_integration

Ownership split among OpenHCS, omero_openhcs, and PolyStore.

For the underlying architecture, start with System overview. For API imports, use Public API orientation. For current examples and recipe lookup, use Reference.