You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, argument passing from condor job submission to executable is messy. We assume an ordering and this causes a divergence between CondorTask and CMSSWTask, which have separate submit_multiple_jobs_to_condor methods.
If we make all the arguments/necessary inputs into classads attached to a job, then the job can parse the classad on the worker node to get information within the executable. Then we won't need to assume an order, and extending a generic CondorTask amounts to piling on more classads rather than rewriting the submission function. This is already done to a small extent, just need to make it more general and rework the executables.
Right now, argument passing from condor job submission to executable is messy. We assume an ordering and this causes a divergence between CondorTask and CMSSWTask, which have separate submit_multiple_jobs_to_condor methods.
ProjectMetis/metis/executables/condor_cmssw_exe.sh
Line 3 in 3d0f922
If we make all the arguments/necessary inputs into classads attached to a job, then the job can parse the classad on the worker node to get information within the executable. Then we won't need to assume an order, and extending a generic CondorTask amounts to piling on more classads rather than rewriting the submission function. This is already done to a small extent, just need to make it more general and rework the executables.
ProjectMetis/metis/CMSSWTask.py
Line 101 in 3d0f922
The text was updated successfully, but these errors were encountered: