Submitting a Collaboratory TRANSP Run

• Standard
  All TRANSP input must be in the Tree, specified in the REQUEST file.

  globus-url-copy file:///<path>/<runid>_<tok>.REQUEST 
   gsiftp://transpgrid.pppl.gov/~/incoming/<runid>_<tok>.REQUEST
  
  globus-job-submit -stdin -l incoming/<runid>_<tok>.REQUEST transpgrid.pppl.gov 
   /u/pshare/globus/transp_enqueue
  

• FAST with tar file
  The Tree must contain header nodes (input can be added in parallel). Your tar file must contain the REQUEST file and the input.

  globus-url-copy file:///<path>/<runid>_<tok>_tmp.tar.gz 
   gsiftp://transpcomp.pppl.gov/~/incoming/<runid>_<tok>_tmp.tar.gz
  
  globus-job-submit transpcomp.pppl.gov /u/pshare/globus/transp_enqueue 
   <runid> <tok> FAST
  

• CREATE
  No Tree is used. Your tar file must contain the REQUEST file, input, comment and auxiliary. A temporary Tree is created at PPPL and the tree files are returned via tr_fetch.

  globus-url-copy file:///<path>/<runid>_<tok>_tmp.tar.gz 
   gsiftp://transpcomp.pppl.gov/~/incoming/<runid>_<tok>_tmp.tar.gz
  
  globus-job-submit transpcomp.pppl.gov /u/pshare/globus/transp_enqueue 
   <runid> <tok> CREATE