Menu
PtDataSignal and RDataSignal for DIII-D PTDATA diagnostics — constructor args, calibration, times in milliseconds, Pipeline usage, and xarray conversion
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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
Quick-reference for writing TokSearch + DIII-D pipeline scripts — imports, invocation, API gotchas, and signal types
| name | toksearch-d3d-ptdata |
| description | PtDataSignal and RDataSignal for DIII-D PTDATA diagnostics — constructor args, calibration, times in milliseconds, Pipeline usage, and xarray conversion |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Claude Code |
| metadata | {"author":"GA-FDP","version":"2.0","url":"https://ga-fdp.github.io/toksearch/"} |
The canonical PtDataSignal documentation lives in the toksearch_d3d package docstring.
Access it with: help(toksearch_d3d) or python -c "help(toksearch_d3d)"
For detailed constructor parameters: help(toksearch_d3d.PtDataSignal)
Covers: constructor args, common point names, calibration, times in milliseconds, remote vs local, RDataSignal, and xarray conversion.
