Does deadlinecommand still assume the third argument for job submission is a “scene file?” It seems like the value in that position is just being stored as the first aux. file, but I’m wondering if it is being given special treatment on purpose.
I’ll start another thread to discuss aux. file synchronization, but this third argument to deadlinecommand is currently being synchronized to the slave by default at task execution time, even though I have not set SynchronizeAllAuxiliaryFiles to True.
Ok, so it’s not just the third argument that’s being synchronized when it shouldn’t… it’s all auxiliary files. But I’m still curious if Deadline treats or thinks of the third positional argument/first aux. file any differently than any of the others, and if so, in what situations.
Thanks.
That third file is also considered the job’s “data file”. It’s shown in the Data File column in the job list, and it’s returned by the GetDataFilename() function in the Deadline plugin API. Other than that, it is treated just like any other auxiliary file.
Cheers,
Thanks for the info Ryan.
Can I ask how deadlinecommand determines whether the second argument is a “pluginInfo” file or an auxiliary file? That is, if I’m submitting a job that requires no pluginInfo, but takes auxiliary files, how does deadlinecommand ensure that it won’t misinterpret the arguments?
In that case, you would just pass an empty file as the second file.