[Deadline 6.2] command line and dependencies

Deadline
1

Hi,

I’ve submitted a job via the following commandline:
/opt/Deadline6/bin/deadlinecommand -SubmitCommandLineJob -executable "Render " …
This works great.

Now I need to submit another job which would be depending on the first one (and frame dependent).
The first job’s ID is: 546a89240e485c039abb05c3

I’ve tried adding this to the above commande:
-JobDependencyIDs=546a89240e485c039abb05c3
-JobDependencyIDs 546a89240e485c039abb05c3
-SelectDependencies=546a89240e485c039abb05c3
-SelectDependencies 546a89240e485c039abb05c3
-jobDependencies=546a89240e485c039abb05c3
-jobDependencies 546a89240e485c039abb05c3
… with comas and without … I’m running out of ideas and obviously cannot find it in any help, online or when using -h on the deadline command in a terminal.

Could you help me with this please ?
Deadline Version: 6.2.0.32 R

Thank you

2

Hello,

I think that thinkboxsoftware.com/deadlin … cy_Options would have the option you need, which appears to be

JobDependencies=<jobID,jobID,jobID>

so it looks like you may have been just one capital J away from success.

3

Thanks for the answer.
But it still doesn’t work.

I’ve now tried:
(…) jobDependencies=546a89240e485c039abb05c3
(…) -jobDependencies=546a89240e485c039abb05c3
(…) JobDependencies=546a89240e485c039abb05c3
(…) -JobDependencies=546a89240e485c039abb05c3
… and the same with quotation marks around the jobID, with ‘=’ and without ‘=’ … I’m lost.

Here is the log:
Error: unrecognized argument: -JobDependencies=546a89240e485c039abb05c3 (System.Exception)
at Deadline.Applications.Consoles.SubmitCommandLineJob.Invoke (System.String[] args) [0x00000] in :0

I need some help, please.
Anyone from Thinkbox ?

Thank you.

4

Hello,

So I looked into this a bit more, and it turns out when using deadlinecommand for the commands, versus the job files, you actually need to put prop in front. What you’re looking for is

-prop JobDependencies=546a89240e485c039abb05c3

Let me know if that works.

5

Thank you, dwallbridge.

There are some progress.
The job goes in the farm now, but the dependencies are not working.
Here is the log:

The job was submitted successfully, but there were some warnings:

  • Key-value pair not supported: “JobdepenDencies=546d0b100e485c035366734d”

I really appreciate your help.

6

Hello,

Can you verify if you open the job properties in the monitor, whether the Dependencies tab has anything listed? Also, I noticed there is a capital D in the middle of Dependencies, and was wondering if that is just a typo in translation, or if the setting was typed wrong, as it does need to be JobDependencies, with the upper case letters in the proper spots. Could you provide the full command you are using so I can try to reproduce here? Thanks.

7

Oh gosh, it’s in fact a typo.
This is now working, I think.
I now need to make this frame dependant as the first job creates ass files for arnold and the second should run kick and render them.

Thanks again.

8

Ahhh no worries, we all make them. Glad you’re a bit further along now!

9

I have one last question though.

My 2nd job runs kick (arnold) to render the .ass files created by the 1st job.
One machine in he farm should render one frame.

But when I mention
myAssFile..ass
it’s looking for myAssFile.1.ass
instead of myAssFile.0001.ass

How do I force it to use padding ?
Or is there a way to mention something else than ?

Actually, it would be very useful for me to have an example of the command to be ran, such as:
os.system( ’ /opt/Deadline6/bin/deadlinecommand -SubmitCommandLineJob -executable “kick” -arguments " -dw myAssFile..ass " -initialStatus Active -frames 1-10 -pool linux -group 32Gb -priority 50 -chunksize 1 -prop “JobDependencies=123456789” -prop “IsFrameDependent=true” ’ )

Thank you again.

10

Hello,

While I try to gather the info I would need to answer the final question, can I ask if there is a particular reason you aren’t using the submitters built into Deadline for all of this? It seems like a lot of extra work when we have submitters that work fine.

Getting that command together is going to taker a bit, though, as we do not have the ability to test commands, and I am not familiar with what formulates a valid command. Could you send over an archived job that had the wrong padding? support@thinkboxsoftware.com is the support email

11

Hi,

The reason for all of this is that I need to use pre-render scripts.
So far, I was able to submit a job using the ‘Render’ executable, with a pre-render script that I use to create my different ‘renderlayers’ and set some default values like sampling etc.
And this works like a charm, using the -executable ‘Render’ command.

My goal this week is now to go further, and doing a 2 steps submission:

  • 1 job creates ass files (this works for me, using 'mayapy" with a py script as the executable)
  • 1 job renders the ass files (kick as executable)
12

Hello,

I was looking over your latest forum and ticket replies, and I was wondering ​​what issues have you found with the maya submitter using the arnold export and letting it make the dependent job? It seems like the integrated submitter, with a pre render script in use, should be able to do all the stuff you are trying to do without all the extra work. Thanks.

Cheers,

Dwight

13

Hi,

I’ve finally found what was causing my renders to be stuck forever.
It’s a flag that needs to be added in the kick options ( -nstdin ), that I didn’t find any documentation about.
Now everything works as expected.

I’ve also found on your website how to use padding (0004 instead of 4).
So that’s all goo as well.

Finally today, I’m happy everything is working the way I need.
Thanks again for all your help.

Is there anything I should do to close the ticket ?

14

Hello,

Glad to hear that things have smoothed out. I’ll take care of your support ticket for you. Let us know if you need anything else.

Cheers