Exec NodeThe Exec node is the main process control function for the Chalice system. The Exec node instructs the system to begin processing a Chalice network and specifies which frames to process and the order in which to process them. In other words, the Exec node "executes" a Chalice network. The Exec node is the terminus node for the network. The Exec node has no output connector, since no other node may be placed downstream from it. The Exec node accepts multiple inputs. Using the Exec NodeEach time you connect an input to an Exec node, Chalice creates an entry in the Exec parameter tab that enables you to specify the sequence of execution for the frames referenced by the network. ![]() You specify the starting and ending frames, and an increment value. For example, if you key in 1 for the Start value, 50 for the End value, and 2 for the Increment value, when you execute or validate the network, the Exec node sends the frame values 1, 3, 5, ..., 49 upstream to the source nodes to begin processing. (For more information about how image data flows through a network, see Dataflow Mechanics of the Chalice System in chapter 4, "Key Concepts .") As an alternative to keying in Start, End, and Increment values you can specify the name of an ASCII text file that contains a list of numbers representing the frames to be processed. The Exec node also includes a slicing option that enables you to slice frames into smaller sections for greater efficiency when processing large image formats. During processing, the Exec node displays an Exec notifier panel that indicates the current frame. You can cancel processing by clicking the Cancel button on the notifier panel. If you cancel processing, all frames that have already been written to disk are retained. You can resume processing with the first unprocessed frame, or start again from the beginning and overwrite the first batch of frames. Processing Multiple Exec EntriesEach entry to the Exec node includes a checkbox labeled "Active" that enables you to turn the layer off (or back on) before processing. This gives you complete control over whether or not any particular sequence connected to the Exec is processed in the next execution cycle. Executing Finals and TempsDuring the creation of an effects shot, it is often necessary to create temporary composites ("temp comps"). Composited frames may be needed for evaluation purposes or for reference by another artist before the final shot is ready to be rendered. Temp comps are usually lower resolution and quality than the final output imagery will be. The name, directory path, and format of these files are specified in the Temps tab of the Disk Output node ; however it is the Exec node that controls which type of file is output: press the Finals Execute button to render finals and the Temps Execute button to render temps. Exec Parameter Tab![]() Execute FinalsPress the Execute Finals button to instruct Chalice to begin processing. All inputs to the Exec node will be processed, unless the corresponding "Active" button for that input entry is disabled (unchecked) in the Exec panel entry list. For example, if a Disk Output node is connected to the Exec, the Execute Finals command will process the image data and write the file sequence to disk as specified in the Finals Output tab of the Disk Output node. Validate FinalsThe Validate Finals button allows you to verify that all files referenced by the nodes in the network are present and accessible to the system and that there are no procedural errors in the network. It is generally a good idea to validate a network before you attempt execution. When you press the Validate button, the Exec node will perform the validation operation; however, no data will be calculated or processed. Execute OrderUse the Execution Order popup menu to choose between Sequential or Interleaved execution. The Sequential option indicates that all the frames in the first Exec sequence entry will be processed before Chalice continues with the next Exec sequence entry. The Interleaved option indicates that Chalice will process the first specified frame from each Exec sequence entry, then the second frame from each Exec sequence entry, and so on. Temps ExecuteThe Temps Execute button enables you to render "temp comps" to disk, as specified in the Temps Output parameter of the Disk Output Node (see chapter 12, "I/O Nodes "). The size and quality of the output are determined by the Temps Res and Temps Quality parameters of the Exec node (see below). Higher quality and resolution may require considerably more processing time. Temps ResThe Temps Res menu allows you select a lower resolution for the Temps Execute output. You can choose from 1/8, 1/4, 1/2, and Full. The default is half of full resolution. Temps QualityThe Temps Quality menu allows you to set the quality of the Temps Execute output to Low, Medium, or High. Exec Panel EntriesEach time a node is connected to the Exec node, a corresponding entry is created in the Exec panel. It includes the name of the input node, parameters to specify start and end frames and the increment, a "local" validate option, a slicing option, and a checkbox to turn the entry on or off. Key in a value for the Start parameter to specify the first frame to process. Key in a value for the End parameter to specify the last frame to process. Key in a value for the Increment parameter to specify the frame increment of the sequence to be processed. For example, if you key in 1 (for the Start value), 50 (for the End value), and 2 (for the Increment value), this specifies the following values: 1, 3, 5, ..., 49. ![]() Use FileThere are two ways to specify frames that you wish to execute. You can key values into the Start, End, and Increment parameters, which is the default, or you can specify an ASCII text file that contains a list of numbers. When you click the Use File button (the file folder icon), the parameter changes to display a path field and plus button, which accesses a standard Chalice Choose File dialog box. The file you choose should be an ASCII text file that contains a list of numbers delimited by carriage returns. These numbers represent a list of frames and are sent upstream to the nodes connected to the Exec sequence as an alternative way of specifying the frames you wish to execute. Select the Use File icon again to toggle back to the Start, End, and Increment fields. ValidateThe Validate button enables you to validate only the associated Exec sequence entry. (If you wish to validate all entries connected to the Exec, use the Validate Finals button at the top of the node panel.) SlicesThe execution of a complex Chalice network requires a substantial amount of memory. Depending on your system configuration and the imagery and complexity of a particular Chalice network, you may need to divide the processing into smaller chunks to work within with the memory constraints of your system. The Slices parameter enables you to "slice" image processing into smaller chunks. Unfortunately, you cannot tell how much slicing your network will require until you attempt execution. If possible, avoid slicing altogether. If slicing is required, use the minimum that enables Chalice to successfully process the network. For example, begin with four slices. If this fails, try eight slices, and so on. For more information about slicing, see Memory Usage in Chalice in chapter 4. ActiveThis checkbox is used to specify whether or not to execute the associated sequence during the next execution cycle. By default, the box is checked, indicating that the entry layer is active and will be processed. To disable processing for the layer, uncheck the box . |