Thomson data

The TS data files are in /p/ltxdata/tvts/shots/ . There are a few different kinds of data mixed in there - individual shots, groups of shots for a single profile, and groups of profiles for time scans. There's also raw and smoothed profiles/scans.

A dictionary defining the shots that go into various profile run ids in /u/dboyle/idl/ltx/tsdict.pro . The file now also has a list of TRANSP runs that correspond to TS time scan run ids. The file can be read as text or if the directory is in your IDL path you can call tsdict = tsdict(trshots) . In the future TS run ids can be incorporated into the run logs.

Plots from many of these runs are in /u/dboyle/plots/ .

A few notes:

• There's no strict naming rules but typically the TS runs are named TS[Month][Day][TS time][code]
• A single profile will typically (but not always) have a TS time while a time scan will not
• TS time is typically time in milliseconds after 400ms
• The most common codes are 'f': failed beam/no beam/before beam and 'b': beam
• other codes include (but may not mean exclusively) l/m/h: low/medium/high density, h/s/a/e: HFS/SGI/all/early fueling, a/p/n/o: AM/PM/new Li/old Li, z/y/x/w/v/u/...: usually generic groupings without any meaning
• numbers after a letter may indicate beam timing/voltage/etc., density, etc.
• The TRANSP run id is typically the nominal 'median' shot number + a runid (typically 0101 or alternatively A01 is a semi-automated run with minimally processed TS data, magnetics-only reconstructions, no Ti data, no NUBEAM, etc.)

For the saved json/txt files:

• The filename could be an individual shot number, a list of shot numbers for a single profile, a profile run id for a single time, or a group run id for a time scan. The data structures are presently a little different for the different types.
• The 'sm' suffix refers to uncertainty-weighted smoothing of profiles in space and/or time
• The 'mu' suffix refers to an uncertainty-weighted average of multiple profiles

The easiest way to read the TS data in IDL is to read the JSON files into IDL structures using the following (change the filename as needed)

data=json_parse('/p/ltxdata/tvts/shots/TS429bsm.json', /tostruct, /toarray)

Depending on which kind of file the structures will be different, you can see the various fields using

help, data

help, data[0]

For a simple plot with error bars,

ploterror, data[0].r, data[0].t/data[0].valid, data[0].et