GA-FDP

Read this FIRST when unsure which Signal class or data path a DIII-D quantity needs. Maps physics quantities (Ip, Wmhd, beta_N, q95, NBI power, density, Te, boundary, ...) to the correct Signal class and path, how to discover IMAS paths, and which skill to use for time-alignment/correlation. Avoids the common mistake of using PtDataSignal for a quantity that lives in MDSplus or IMAS.

fdp CLI for FDP/Pelican data access — fdp run, fdp env, fdp ls, authentication, and available DIII-D data

ImasSignal for DIII-D IMAS IDS data — leaf/prefix paths, ragged arrays, channel splitting, dimension control, and shared ImasComposer

PtDataSignal and RDataSignal for DIII-D PTDATA diagnostics — constructor args, calibration, times in milliseconds, Pipeline usage, and xarray conversion

Quick-reference for writing TokSearch + DIII-D pipeline scripts — imports, invocation, API gotchas, and signal types

TokSearch compute backends — serial, multiprocessing, Ray, and Spark; when to use each and configuration options

TokSearch xarray dataset integration — fetch_dataset and align for multi-signal time-aligned analysis

MdsSignal for fetching MDSplus tree data — constructor args, location formats, TDI expressions, dims, and DIII-D efit01 signals via FDP/Pelican

Core TokSearch Pipeline workflow — creating pipelines, fetch/map/where/keep, record data access, and iterating results

MAST/MAST-U data access via FAIR MAST — the mast FDP device, MastSignal, list_shots/list_signals, and the public Zarr-on-S3 store

IMAS-path access to FAIR MAST — MastImasSignal and list_imas_paths; level-2 groups are IMAS IDSs and variables carry imas-path attributes