What's Coming Next

Here is what has landed recently and what is still ahead.

Natural language agent for TokSearch (shipped)

FDP includes an AI assistant that turns plain-language requests into TokSearch pipelines and runs them against the FDP data stack. Ask it to "fetch ip for shot 200000 and report the peak in MA" and it writes the query, runs it, and iterates when something fails. It is available from the terminal (fdp chat, fdp query), a local GUI, coding assistants via installable skills, an MCP server, and the Python Session API.

Provenance capture (shipped)

Every TokSearch run can now record what produced it, and write that record to CMF. See Provenance and CMF.

IMAS support (reading works, writing does not yet)

Reading IMAS data works today: ImasSignal resolves IDS paths and pulls DIII-D data into pipelines, backed by the imas_composer resolver, both part of fdp-core.

The other direction is still to come: writing TokSearch and CMF outputs back out as IMAS-compliant pulse files, with provenance and metadata attached, so results can be shared across facilities including ITER.

Search and publication (planned)

The goal is to make curated results findable as well as reproducible: public CMF repositories that anyone can clone, and a searchable portal over them with filters for shot range, diagnostic type or device, and browsable data lineage.

This part of the platform is not yet built and we are not quoting a date for it. For now, sharing means sharing a CMF repository directly.

Additional devices

fdp-core already provides data access for both DIII-D and MAST/MAST-U, and work on further devices is ongoing. The device layer is a plug-in point, so a new facility joins by contributing a package rather than by changing FDP itself.