Search - User list
Full Version: @pdg_index not starting at 1
Root » PDG/TOPs » @pdg_index not starting at 1
smbell
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.
chrisgreb
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?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Powered by DjangoBB