Not directly relevant to this ticket.. I noticed that in ctrl_orca/ups/ctrl_orca.table, there are these two setup Ray added long time ago:

setupOptional(condor)

setupOptional(condor_glidein)

But I don't see packages named "condor" or "condor_glidein" in our github lsst. Are they still needed?

Those can be removed, so I'll do that.

Can you take another look at this?

After your review, I found a bug where two things could happen: A job that didn't specify node set could run on allocated nodes and nodes that weren't tagged with a node set could run jobs that did specify a node set.

We never ran across either issue before because of the way we ran things, but because of the way we now do allocations, it's possible to have an independent job owned by the user take over nodes that it shouldn't.

Basically, this keeps the user from accidentally screwing up either own jobs by accident.

The new changes in ctrl_platform_verification looks good to me.

I tried runOrca and some stack ProcessCcd task and it worked great.

merged ctrl_execute and ctrl_execute
ctrl_platform_verification was added, but will be renamed as ctrl_platform_lsstvc