Taylor Petrick


About Me

Not Specified


Recent Forum Posts

Utilising @wedgenum[] in file output for nested wedges Jan. 14, 2020, 5:28 p.m.

The parm expressions don't have syntax for accessing the entire array. You can only access the components of the attribute using a particular index such as @wedgenum.0, @wedgenum.1, etc. Alternatively, you can use the function equivalent – pdgattribute(“wedgenum”, 2) to access the element at index 2 for example.

Wedgenum is also not an array by default - you'll need to toggle the “Preserve Wedge Numbers” option on each of the wedge node(s). Each wedge will append the wedgenum value on the end of the existing array when that option is on, rather than overwriting the single, scalar value.

For a file path, you might do something like $HIP/$OS.`@wedgenum.0`.`@wedgenum.1`.$F4.bgeo.sc.

Accessing the ROP Fetches Expect Output through Python Dec. 13, 2019, 1:10 p.m.

I've attached an example that uses a Python Processor to access upstream expected outputs. I've also includes an example of evaluating a Houdini parameter (the ROP Geo's sopoutput) against a particular work item.

Note that per-work item Houdini parm evaluation portion will only work in Houdini 18.0.307 or later. If you're using an older build, including any build of 17.5, you'll need to use a channel reference.

Python Script problems Dec. 13, 2019, 11:43 a.m.

I've fixed your .hip file so it works in process. You can use the Geometry Import to fetch your Prepare_Geometry and have it evaluate against the work item attributes. This will give you a work item per point, which you can then partition and dump to JSON.