Ok, so after sieving about in the TOPS/PDG documentation, I got this working using a Python processor and some attributes. Not sure if this is a good way to do this or anyone can share some better (I'd really appreciate it!)
- first I use a wedge TOP just to create some work items, 3 in this case for testing purposes.
- Next, I used the python processor to create an instance of the HDA for each work item and create 2 attributes (a path to each hda created and a string to use in the output filename). I also adjust a parameter on the HDA (trunk_height) to give each HDA a different trunk height as a test to see if it works.
- Next, I use the partition by attribute TOP to make sure that the work items complete by attribute before moving on (at least I think that's what it does)
- Then I use the hda_path attribute as the soppath in the ROP geometry TOP and use the save_name attribute somewhere in the output file name. Also I set the frame range here to 2 so I only get 2 Frames per HDA instance for testing purposes. (see images)
In the final setup, I'm using the wedge to actually generate the values for the attributes as you would with the HDA processor TOP, then I'm referencing those attributes in the python processor.
With this, I get varied HDA instances caching to disk with the procedural animation that's built into the HDA. Thoughts?