Re: [HTCondor-users] Access to renamed DAG node names

[Brian Candler <b.candler@xxxxxxxxx>]

On 12/01/2015 09:10, Brian Candler wrote:
> My use case is to be able to be able to compose a DAG from components, 
> e.g.
>
> - write out a master DAG, and children dag1 and dag2
> - the master DAG uses splices or subdag to run dag1 and dag2
> - dag1 and dag2 are built using the same script, and therefore have 
> colliding node names
> - I want the submit files for dag1 and dag2 to be able to use a common 
> submit file with
>
> output = $(JOB).out
> error = $(JOB).err 
Actually a couple of other requirements:

- a generic SCRIPT POST which reads the output of a job and delivers it 
elsewhere
- given a report of a failed node in JOBSTATE.LOG or NODE_STATUS file, 
be able to locate the stdout and stderr relating to that job, for 
diagnostic purposes

So I might had dag.dag containing

SPLICE FOO dag1.dag
SPLICE BAR dag2.dag

with dag1.dag and dag2.dag both containing

JOB A generic.sub
VARS A job=A
SCRIPT POST A send_results $(job)

and generic.sub has

output = $(job).out
error = $(job).err

The documentation for -usedagdir suggests that it's only when multiple 
independent dags are submitted on the command line; it doesn't describe 
whether or not this applies to subdags or splices.

I'll try to cook this up into a more representative example set of DAGs 
to see if I can make it clearer.

Regards,

Brian.