-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: run simulations sequentially #149
Conversation
5144b3b
to
37e2347
Compare
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
Regardless of if openjd-adaptor-runtime keeps the interface version, we can delay the decision by bumping it regardless. |
a223488
to
fc97c73
Compare
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Joel Wong <127782171+joel-wong-aws@users.noreply.github.com> Signed-off-by: Stephen Crowe <crowest@amazon.com>
…ing (aws-deadline#154) Signed-off-by: Joel Wong <127782171+joel-wong-aws@users.noreply.github.com> Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: client-software-ci <129794699+client-software-ci@users.noreply.github.com> Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
src/deadline/houdini_submitter/python/deadline_cloud_for_houdini/submitter.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
try: | ||
connected_node = rop_steps[-1] | ||
except IndexError: | ||
return [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: it would be better to raise an exception here (otherwise an exception will be raised down the chain), but based on the current code, this statement is actually unreachable, so not blocking
…ni/submitter.py Co-authored-by: Morgan Epp <60796713+epmog@users.noreply.github.com> Signed-off-by: Stephen Crowe <crowest@amazon.com>
Signed-off-by: Stephen Crowe <crowest@amazon.com>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this Stephen, looks great!
What was the problem/requirement? (What/Why)
The submitter previously always rendered each frame as a task, and tasks would be distributed to different Deadline Cloud workers. But some node types like simulations must be run sequentially - each frame depends on the previous one.
What was the solution? (How)
Introduce a new sequential rendering strategy where all frames are rendered inside a single Deadline Cloud task which ensures they are sequentially on a single worker.
Specific changes include:
What is the impact of this change?
Simulations are run efficiently.
How was this change tested?
I submitted a hip file with simulations and regular rendering. The simulations resulted in single tasks and the renders resulted in 1 task per frame.
Was this change documented?
No, but it needs to be.
Is this a breaking change?
No. Changing the runData schema could have been a breaking change, but I took care to ensure the old
frame
parameter is still handled correctly.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.