areadetector-ioc

What problem does it solve?

AreaDetector IOC setups often fail or underperform because plugin chains, database templates, and file-writing parameters are configured incorrectly, leading to missing PVs, bad image routing, or unreliable acquisition-to-disk behavior.

Core Features & Use Cases

• Plugin-chain configuration: Define detector-to-plugin routing and standard plugin configuration patterns (including NDArrayPort upstream linking).
• Database template loading: Use the correct template hierarchy (NDArrayBase/ADBase/NDPluginBase and plugin-specific templates) to generate PV records consistently.
• File writing configuration: Configure HDF5/TIFF/JPEG/NetCDF/NeXus-style writers and key fields like file paths, templates, numbering, and write modes.
• commonPlugins.cmd integration: Load a standard, coherent set of plugins using expected environment variables to speed IOC bring-up.
• Build configuration guidance: Align Makefile and feature flags (e.g., WITH_HDF5, WITH_PVA, WITH_JPEG) so the resulting IOC matches the desired functionality.

Quick Start

Ask your AI assistant to generate a complete st.cmd-style plugin chain using commonPlugins.cmd with your chosen PREFIX, PORT, QSIZE, XSIZE, YSIZE, NCHANS, and NELEMENTS, then add HDF5 file writing with a correct FileTemplate and CreateDirectory setting.