Open mtitov opened 9 months ago
This is how it will look for the user: radical-pilot-launcher rp_app.py -c job_descr.json
(where job_descr.json
includes project
, queue
, runtime
, etc.)
The same job_descr
should be used by RP for the pilot description when it starts within the batch job. Thus, user doesn't need to keep this information in sync between json file and PilotDescription
inside rp_app.py
, and RP will know which one should be used.
(*) one of the options is to use env variables for the provided config json file, keep them as part of the batch script, and PilotDescription
will use them instead of ones that are set (the case when RP determines that it started within the batch job, it can look for a corresponding env variables)
Launcher to run IMPECCABLE workflow(s) on Frontier
Proposed launcher will make a batch submission with RP script as a target application.
PMGRLaunchingComponent._prepare_pilot
to create job descriptionPilotLauncher
to make a submission(*) PR for https://github.com/radical-cybertools/radical.pilot/issues/3094 should be in place