Fusion Collaboratory Transp Production
- Prerequisite for Client:
- Client (with valid grid certificate)
- Prepare Input data and Namelist
- Site specific software
- PPPL:
- scruncher, scrunch2, xtranspin, nbfile
- Ufiles via IDL
- Run Options:
- Standard
- User creates a MDSplus Tree and sends a jobrequest with hte REQUEST file to PPPL.
- At PPPL, Namelist is extracted from MDSplus Tree specified in REQUEST file.
- Input is extracted from MDSplus Tree specified in Namelist.
- Output can be fetched as files, or is optionally written into MDSplus Tree as specified in REQUEST file.
- TREES
- User creates a MDSplus Tree, containing all Input data, and sends a jobrequest with the REQUEST file to PPPL.
- At PPPL, the tree triplets are copied via mdstcl into a "local temporary tree".
- Namelist and Input data are extracted from this local MDSplus Tree.
- Output is written into this local MDSplus Tree.
- Tree Triplets are returned to client via mdstcl as specified in the REQUEST file.
- Non-MDSplus output must be fetched.
- UFILE (not recommended)
- User prepares tar file containing REQUEST, Namelist, auxiliary files and Ufiles, to be sendt to PPPL.
No MDSplus Tree is created.
- At PPPL, REQUEST file and Ufiles are extracted from tar file.
- PPPL creates mdsPLUS tree at Clien's Server as specified in REQUEST file.
- Output: same as STANDARD.
- CREATE
- User prepares tar file containing REQUEST, Namelist, auxiliary files and Ufiles, to be sendt to PPPL.
No MDSplus Tree is created.
- At PPPL, REQUEST file, Namelist and Ufiles are extracted from tar file.
- PPPL creates a temporary MDSplus Tree.
- PPPL produces a tar file, containing MDSplus Tree files (input and output) & optional TRANSP output.
- User fetches the tar file, extracts the Tree files and moves them into the site's MDSplus directory.
- NOMDSPLUS
- User prepares tar file (via datprep) containing REQUEST, Namelist, auxiliary files and Ufiles, to be sendt to PPPL.
No MDSplus Tree is created.
- At PPPL, REQUEST file, Namelist and Ufiles are extracted from tar file.
- PPPL creates a tar file, containing TRANSP output.
- User fetches the tar file.
- Create MDSplus Pulse and fill with Namelist and Input data
Note: Skip for CREATE and NOMDSPLUS options
- PPPL: tr_start (xtranspin on unix cluster)
- MIT / GA: pretransp
- Generate <runid>.REQUEST file
- PPPL: tr_start (xtranspin on unix cluster)
- MIT / GA: pretransp
Contents of <runid>.REQUEST file
- Transfer the <runid>.REQUEST file to PPPL (globus-url-copy)
- PPPL: tr_send_pppl.pl (xtranspin on unix cluster)
- MIT / GA : pretransp
- Submit the run (globus-job-submit)
- PPPL: tr_send_pppl.pl (xtranspin on unix cluster)
- MIT / GA: pretransp
- Monitor the status of the run on the web
- JET / PPPL: tr_status
(globus-job-submit / globus-url-copy)
- Steering a run
- Request to look at intermittent Output (globus-job-submit)
- Halt an active run (globus-job-submit)
e.g.: for steering
- Fetch Output Files (globus-url-copy)
- Cancel/Cleanup a run (globus-job-submit)
- Runs, that are not fetched or canceled, are deleted after 1 month
- Server (with proxy from client)
- Read <runid>.REQUEST file
- Submit job to available host
- Obtain Namelist from MDSplus as specified in <runid>.REQUEST
- Generate scripts for processing
- Run trdat to read/process Input data as specified in Namelist
- Launch TRANSP
- Optional, write TRANSP Output into MDSplus Tree
- Write <tok><year>_<runid>.FILESREADY file
All software is available in the TRANSP cvs repository and also as a NTCC module TR_Client.
Home
Questions,comments,suggestions, etc. to: transp@pppl.gov
See also the disclaimer.