Fusion Collaboratory Transp Production
- Prerequisite for Client:
- Client (with valid grid certificate)
- Prepare Input data and Namelist
- Site specific software
- PPPL:
- scruncher, scrunch2, xtranspin, nblist
- Ufiles via IDL
- Create MDSplus Pulse and fill with Namelist and Input data
- 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)
- Request to look at intermittent Output (globus-job-submit)
- 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.