CollectionCreate

Collections are used to store a CEL statement. They are stored as attributes in the location given by the location parameter (see below). As they are simply attributes within the scene graph, collections can be included within Katana look files.

Note:  Similar to Katana’s CEL, USD’s Pattern-Based Collections (PBC) was introduced in USD 23.11 and is now fully integrated in Katana’s USD framework, with the addition of a Pattern-Based Collection (PBC) widget and the UsdCollection node, available as of Katana 7.5. See Pattern-Based Collections with USD.

You can see a list of the CEL and USD (PBC) Collections in your project in the Collections panel at the top of the Scene Explorer and via the Collection working set indicators . See The Scene Explorer.

Connection Type	Connection Name	Function
Input	in	The place in the node graph where you want to create a collection.

 

Control (UI)	Default Value	Function
location	N/A	The scene graph location where the collection is saved. The location parameter options are available in either the scene graph widget or dropdown menu to the right of the parameter. For more information, refer to the Scene Graph Location Widget Type in the Common Parameter Widgets.
name	N/A	Sets the name of the collection.
CEL	N/A	Specifies scene graph locations to store as part of this collection. The scene graph locations are specified using the Collection Expression Language (CEL). The CEL parameter options are available by clicking Add Statements. For more information, refer to the CEL Reference document found on the documentation HTML page (accessed through Help > Documentation) or the CEL Statement Widget Type in Common Parameter Widgets.
stripDisabledBlocks	No	When set to Yes, this removes parts of a collection expression that have been disabled by pressing the D key over a CEL editor panel. CEL statement parts that are disabled are normally wrapped in #IGNORE(...) statements. When stripDisabledBlocks is set to Yes, #IGNORE(...) blocks are removed from the resulting collection expression. This optional optimization means extra work upfront, but results in CEL statements that are potentially much shorter.