Hi guys,
Have you thought about per frame dependency? Right now with a simple dependency, there’s a lot of time wasted because of waiting for the whole precursor job to finish instead of the relevant part.
Ah, that’s very cool!
Unfortunately it wouldn’t work with a job that has only one task, i.e. a simulation job. but oh well.
We also have asset & script dependencies, so perhaps these could be used to query for something and if the asset is present or the python script returns True, then a dependent job is released, or released on a per frame offset amount. I think I would need to understand the context better to advise further.
Cheers,
Mike
Yes, the script dependency sounds good. I’m having a Naiad simulate, then convert to PRT, then render a Frost/Vray job for the surface, then render a Krakatoa job for the splash.
Cool. Here’s an example to get you started: youtube.com/watch?v=U-q_EH-OISI#t=512
About 7min 30sec’s in, I start talking about using a Python script to release a job and dealing with taskIDs.
Nice, thanks a lot! I’ll check it out.
true “frame” dependency would be really, really nice. checking for an asset may or may not work based on whether you’re doing a new sim or re-simming over an old test. if the script dependency thing is really a viable option, then perhaps that could be folded into deadline to more closely mimic a real “frame” dependency situation.
and on the topic, it would be nice to move the “frame” toggle to the dependency itself and not the job. so you could have a task that has 3 job dependencies and 2 frame dependencies…
In Deadline v7 you can set this at the job level, but also have per-dependency overrides, which will allow the above configuration. 