Running TRANSP : Data Step

Next (Trdat step)
Back (Config step)
Home

The data step is similarly executed by typing:

JETtransp 'runID' step data

This step begins by running a set of secondary codes which perform various data preparation tasks. They are:

• RF : Two programs are executed in this stage: ececon which uses the raw ECE PPF signals to determine the ECE temperature as a function of frequency which is a required input when RF heating is being used; TrICH which prepares the required ICRH heating data for TRANSP.


• KK3jt : If the namelist specifies that KK3 (Electron Cyclotron Emission) data is to be used for the electron temperature then the KK3jt program is run. This reads the input KK3 data and converts it into a form useable by TRANSP. The input KK3 data consists of a set of temperature and radius profiles for the different diagnostic channels. These are converted to a 2D profile of electron temperature against fixed major radius and time. The results are stored in DDA KK3J with datatypes: TERA, Electron temperature versus major radius RA; TERC, Electron temperature versus major radius RC and TEFR, Electron temperature versus frequency. TRANSP uses the TERA profile.


• Nblist : Nblist checks which neutral beams and which PINIs were active during the specified shot and reads the input power profiles into a Ufile. It also stores this information in a PPF with DDA name PNBI owned by user tranppf. Lastly it writes the geometry information of the active PINIs into the TRANSP namelist file. This information is used by NUBEAM.


• SCRUNCHER : SCRUNCHER decomposes the EFIT plasma boundary into a set of fourier moments. This information is stored in a PPF named MSCR owned by user ID tranppf.

After executing these programs the data step executes a program called TrFile which reads the PPFs specified in the trdat namelist and writes Ufiles from them. If the PPFs are public PPFs these Ufiles are written to the System Data Directory ($SDD) so they can be used by other runs of the same shot. If they are private user PPFs then the Ufiles are written to the TRANSP Data Directory ($TDD) for the particular run being performed. These Ufiles will only be used by the current run. Any user generated Ufile data used by the run is also written back to the PPF system under the user ID 'tranppf' to keep a permanent record of the data used for the run.

Lastly the step writes information about the data used back to the namelist file. This information is appended to the EXT card of the appropriate data set. An example is:

PREQPR='EFIT'
EXTQPR='Q_0011 PPF:2:tranppf:0342:$SDD:Q_PROFILE(PSI_NORM) :'

This indicates that the Q profile was taken from a PPF, that it is a 2-Dimensional profile, that the owner of the PPF was user 'tranppf', that the sequence number of the PPF was 0342 and that the Ufile produced from the PPF is stored in the System Data Directory ($SDD). The last field is a comment line describing the data read, in this case that the q profile has a radial coordinate given by the normalised poloidal flux.

The next step is the Trdat step.

Next (Trdat step)
Back (Config step)
Home