| On this page | |
| Since | 10.0 |
The Net Barrier uses the tracker to ensure multiple machines stay in step with each other. This is useful if some external shared drive is being used to transfer data and you need to make sure that the machines don’t out pace each other.
Parameters ¶
Save to Disk
Begins the render with the last render control settings.
Controls
Opens the Render Control window, which allows you to adjust the render parameters before rendering.
Render with Take
Uses the settings in a particular take while rendering. Choose Current to use the current take when rendering.
Valid Frame Range
Controls whether this render node outputs the current frame or the image sequence specified in the Start/End/Inc parameters.
Render Current Frame
Export only the current frame.
Render Frame Range
Export the frames in the Start/End/Inc frame range, but also allow exporting of frames referenced by in-range frames.
Render Frame Range Only (Strict)
Only export the frames in the Start/End/Inc frame range. Do not allow exporting of other frames, including frames referenced by in-range frames.
Port
The port specified when starting the simtracker.py process for communication.
Address
What machine will run the simtracker.py process for synchronization. If this is blank, no attempt at synchronization or data transfer will occur.
Job Name
The job name to describe this synchronization or data exchange event. By using different job names one can have machines part of separate data-exchange and synchronization events.
Mode
Synchronize
Cooking is blocked until the given number of peers report into the tracker that they are done. Then they are all allowed to continue. Useful if you have a bunch of machines you need to operate in lock step.
Post Barrier Value
The given synchronization value is posted as the current barrier value for the job name. The machine is allowed to continue unimpeded. This is useful for a producer machine whose output other machines depend on, but which can operate as fast as it wishes.
Wait Barrier Value
Waits for the barrier value stored in the job name to reach the synchronization value. Then it is allowed to continue. This is useful to ensure consumer machines do not outpace the producers.
Peer
The slice number that this machine should report itself as. Each machine connecting under the job name should have its own unique slice number. Sometimes this can be inferred from the operation so this parameter will be absent.
Number of Peers
Total number of machines that have to synchronize. Sometimes this can be determined from the operation so this parameter will be absent.
Synchronization Value
The barrier value to post, if in post mode, or to wait for, if in wait mode.
Scripts ¶
A script command can be specified for execution at various execution points. The expression language selected for the script parameter determines whether the command is in hscript or python.
Prior to execution, this node is automatically set as the global current node.
To run statements from a file, specify the path to the file with
either a .cmd extension (when the language is set to Hscript) or a .py
extension (when the language is set to Python). Additional arguments to the
script can also be supplied. They will be parsed in a shell-like manner.
Pre-Render Script
Run this script before any rendering.
Pre-Frame Script
Run this script before each frame.
Post-Frame Script
Run this script after each frame.
Post-Render Script
Run this script after all rendering.
Locals ¶
N
Frame being rendered.
NRENDER
Total number of frames being rendered.
Examples ¶
netbarrierpost Example for Net Barrier render node
In this example, we demonstrate how a netbarrier ROP node can be used to ensure that multiple machines stay in sync with each other.
