| |
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
||||
| |
|
|
|
|
||||||
| |
|
|||||||||
Instructions for Setting Up NSTX TRANSP Runs
S. Kaye 1/11/02
The process for setting up TRANSP runs for NSTX has been automated to make it quick and easy to set up a run. VMS command files and IDL pro files have been developed that, when run, create the necessary 1D and 2D UFILES for a TRANSP run. Some smoothing of the 1D and 2D signals have been done in these automated files, although no smoothing or deglitching of the MPTS or CHERS data has been done. It is up to the user to use the UFILE tools to check these data files and do the appropriate smoothing and/or deglitching. These profiles often need this type of modification.
It is assumed that the user will know how to set up the tr.dat namelist for the run and that all the TRANSP VMS system logicals have been defined. These instructions will not go into that. For further information on that, please see TRANSPHELP on VMS.
The process for setting up a TRANSP run has four steps. All steps are to be performed on a VMS machine.
The UFILE for the time dependent outer boundary is created by running scruncher
$ run trexe:scruncher
This routine reads the outer boundary information from the EFIT01 tree for the shot of interest, decomposes the boundary into time-dependent Fourier coefficients, and writes a 3-D UFILE (M######.MRY). Use the defaults when running scruncher (i.e., host is “local”, tree is “EFIT01”), and typically 6 Fourier moments are used and an asymmetric boundary UFILE is created, allowing for up-down asymmetries. Please scan through at least some of the boundaries when prompted.
Routines to create these files can be obtained from kaye$:[transp.setup]. Copy the following files into your area (not the tr_disk: area, as those files are continually skimmed).
trsetup.com
gsm1.ifi
gsm2.ifi
tsufw.pro
qpufw.pro
tiwrites.pro
gettsfitn.pro
trsetup.com is the control command file that runs the utilities and procedures to create the ufiles. To run trsetup, type the following
$ @trsetup ###### area
where ####### is the shot number of interest, and area is the tr_disk area into which you want the ufiles written (i.e., if you want shot 123456 ufiles in tr_disk:[kaye], type
@trsetup 123456 kaye). trsetup runs the various utilities and procedures.
gsm1.ifi creates the following 1-D ufiles:
f######.cur plasma current from \engineering::ip1(5 msec averaged)
f######.rbz R*Bt from \engineering::itf (5 msec averaged)
f######.vsf surface voltage from \efit01::vsurf
f.######.flx diamagnetic flux from \engineering::fdia (3 msec averaging)
f######.zef zeff from \passivespec::zeff (5 msec averaging)
f######.nts total neutron flux from \particles::total_neutrons_zns (3 msec avg.)
gsm2.ifi creates the follwing 2-D ufile
a######.bol radiated power from \passivespec::bolom_pwrdensity (5 msec time
averaging)
tsufw.pro invokes IDL, and uses gettsfitn to read MPTS data from the data file (not yet from the tree) and creates 2-D ufiles of the raw electron density and temperature spline fits to the data.
qpufw.pro is an IDL procedure that reads the q-profile as a function of time from the EFIT01 tree, and creates a ufile for this 2-D quantity. If a q-profile is being used, the magnetic diffusion calculation in TRANSP does not have to be done.
tiwrites.pro is an IDL procedure that reads the CHERS data from rbell:[ichers.fits]ic######.dat and creates the 2-D ufiles for ion temperature and toroidal rotation velocity from the spline fits to the data.
Once the ufiles are created, it is important to review them using UGRAF1 and UGRAF2, and deglitch and smooth further as necessary using GSMOO1 and GSMOO2.
Trsetup.com takes about a minute or two to run for each shot. If data is missing, the routine moves on to the next step. Please reply accordingly at each prompt.
Set up a ######xxxtr.dat namelist for the run (see instructions in TRANSPHELP). ###### is shot number, and xxx is an alphanumeric identifier for the run. a01, a02, etc. are used for analysis runs, p01,…. for predictive runs, x01…. For “crazy idea” runs (not the typical analysis).
Once the namelist is set up, type
$ nblist
This is a routine that automatically updates the namelist with neutral beam information and creates a 2-D ufile containing the power and voltage of all three sources as a function of time. Give the NSTX related choices at the prompts.
These four steps take approximately 5 to 10 minutes for each run. Once complete, run prtran and trdat to set up the run command files, and submit the run (see TRANSPHELP for these details).