Skip to content

Use classads to simplify argument passing #18

@aminnj

Description

@aminnj

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.
[["taskname", self.unique_name], ["jobnum", index], ["tag", self.tag]]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions