TRANSP Production System for PPPL users

• First time users see info on obtaining access to TRANSP data in MDSplus.
• For details see Transp Unix Mdsplus Implementation
• To setup your envirenment to run TRANSP on the unix cluster:
  • On portals
    • module load ntcc
  • On all obsolete nodes
    • . /usr/ntcc/etc/.transprc ( bash users )
    • source /usr/ntcc/etc/.transprc_csh ( tcsh users )

Note: TRANSP runs are now stored in MDSplus Server TRANSPGRID.PPPL.GOV
      Tree = TRANSP_<TOK>

Index

• Namelists
• Basic Scripts
• Steering a Run
• To Monitor Runs
• To look at Output
• Scripts for Experts

Namelists

TR.DAT and TR.INF files are in $TRINF/<TOK>/<yy>

Basic Scripts

tr_start <runid>		
-----------------			
must be run from directory where Namelist is
creates MDSplus tree for input data
writes <runid>.REQUEST file
			
uses environments
  TR_EMAIL
  EDITOR

  MDS_TRANSP_SERVER    transpgrid.pppl.gov	

  MDS_TRANSP_TREE      ( not required for default )

		
			
tr_send  <runid> [trdat] 
--------------------------			
must be run from same directory as tr_start
	queues run on petrel cluster
option: 
     trdat:   run trdat only

		
tr_cleanup <runid> <tok> 
-------------------------		
queues request to cleanup all traces of a run
if the run is still active, it will be aborted
		

tr_look <runid> [archive] 
-------------------------		
writes interim MDS output into TRLOOK_<TOK> on transpgrid.pppl.gov

options: 
     archive:   for aborted and active runs
	        archive run "as is" on final destination
		if the run is still active, it will be aborted
     nomdsplus: generate CDF file only ( in $LOOKDIR/<TOK>)
	

tr_halt <runid> <tok> [t <time>] 
---------------------------------------------		
suspend a run immediately, or at t = <time>

Steering a Run

It is now possible to halt and restart a TRANSP run under a new, or the same runid with modified input data.
The procedure for this is:

• tr_halt <runid> <tok> [t <time>]
• modify Namelist and/or Ufiles
• rs_newrun
  interactive program to verify, fixup Namelist
  enter $HALTDIR/<tok>/<runid> for "directory of old run"
• tr_start <runid>
• tr_send <runid>
  The Monitor will show the old runid under "steering".

To Monitor Runs

• Web Sites
  • FusionGrid Monitor
  • PPPL Grid Monitor
  • logfile / tail of active run
• Logfiles on disk
  • completed runs:
    $LOGDIR/runlog/<TOK>/
    
  • aborted runs:
    $RESULTDIR/<TOK>/<runid>/

To look at Output

• Interim output / Aborted runs

  rplot t s transpgrid.pppl.gov t trlook_<tok> q <runid>
   or 
  cd $LOOKDIR/<TOK>
  rplot <runid>
  

• Completed Runs

  rplot  t  y  <tok>.<yy>  q  <runid>
    --or-- newer runs are on unix cluster in $ARCDIR
  rplot  d  '$ARCDIR/<tok>/<yy>'  q  <runid>
  

• Special Output (other then .CFD)

  *.DATA* and *.XML files are in $ARCDIR/<TOK>/<yy>
  

• Default Mdsplus Trees are:
  • On Server transpgrid.pppl.gov
    • TRANSP_<TOK> for "temporary" runs
      these runs may be archived on demand (tr_save)
    • TRLOOK_<TOK> for "interim" output

Scripts for Experts

• tr_start.pl <server> <tree> <runid> [<mdsid>] [nocreate]
  to run instead of tr_start
  Examples:
  • standard PPPL - pretend to be a grid user
    tr_start.pl _transpgrid.pppl.gov transp_tftr 12345A01
    will ask if you want a tar file
    
    
  • without creating a mdsplus tree
    tr_start.pl PPPL PPPL 12345A01 nocreate
    
    
• tr_send_pppl.pl <runid> <tok> [trdat] [FAST,CREATE]
  to run instead of tr_send
  Examples:
  • pretend to be a grid user (standard or tar file)
    tr_send_pppl.pl 12345A01 tftr
    
    
  • to send to transpcomp (instead of transpgrid)
    tr_send_pppl.pl 12345A01 tftr FAST
    
    
  • NO tree was created
    tr_send_pppl.pl 12345A01 tftr CREATE
    
    
  
  
  
• tr_send_cleanup <runid> <tok>
  to run instead of tr_cleanup
  
  
• submitting a run manually
  See Submitting a Collaboratory Run