areadetector-ioc

Configure EPICS areaDetector IOCs with plugin chains and HDF5 file writers.

1|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BCDA-APS/opencode-skills --skill areadetector-ioc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: areadetector-ioc
Source: https://github.com/BCDA-APS/opencode-skills/tree/main/areadetector-ioc
Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill areadetector-ioc

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about areadetector-ioc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure EPICS areaDetector plugin chains in st.cmd?

Configure areaDetector plugin chains in st.cmd by linking detector output to standard plugins using NDArrayPort routing, loading database templates with correct macro substitution, and integrating commonPlugins.cmd with environment variables like PREFIX, PORT, and QSIZE.

Why does my areaDetector IOC fail to write HDF5 files during acquisition?

AreaDetector HDF5 file writing fails when file paths, templates, or write modes are configured incorrectly. Ensure your st.cmd sets proper CreateDirectory parameters and FileTemplate fields to enable robust acquisition-to-disk behavior.

What's the best way to deploy an EPICS areaDetector IOC with correct database templates?

Deploy areaDetector IOCs correctly by loading the appropriate template hierarchy—NDArrayBase, ADBase, NDPluginBase, and plugin-specific templates—to generate PV records consistently and avoid missing PVs during acquisition.

Does areaDetector support extending plugin chains with ROI and process plugins?

Yes, areaDetector supports extending plugin chains with ROI, process, and output patterns. Connect these plugins via NDArrayPort upstream linking in your st.cmd to route NDArray data through standard analysis and display paths.

Can I use EPICS PVA with areaDetector file writing plugins?

Yes, you can enable optional PVA support in areaDetector by aligning Makefile feature flags like WITH_PVA and WITH_HDF5 during build configuration so the resulting IOC matches your desired plugin chain and file format functionality.

What are common limitations when setting up areaDetector file writers for different formats?

AreaDetector file writer limitations arise from mismatched build feature flags like WITH_HDF5 or WITH_JPEG and incorrect template macro substitution, leading to missing PVs, bad image routing, or unreliable file writing behavior.