Forums PDG/TOPs @pdg_index not starting at 1

@pdg_index not starting at 1

   1951   1   1
User Avatar
smbell
Member
75 posts
Joined: Feb. 2017
Offline
 
I've got an HDA processor with iterations set to 16 and if I set the output geometry name to $PDG_DIR/geo/$OS.`@pdg_index`.bgeo.scthe numbers come out 16-31. Is this supposed to happen?

I've fixed it with $PDG_DIR/geo/$OS.`@pdg_index - (chs("iterations") - 1)`.bgeo.scbut seems buggy.
Edited by smbell - July 12, 2019 02:09:18
 Report
User Avatar
chrisgreb
Member
603 posts
Joined: Sept. 2016
Offline
 
Work Item indexes generated by a node will usually range from 0 to N-1, this is so that each workitem in the node has a unique index. If you are generating from upstream items I would expect the second set to be indexed 16-31. In what way does your fix seem buggy?
 Report
  • Quick Links