creating an "index" command that the postprocessor will interpret
creating an "index" command that the postprocessor will interpret
(OP)
We are currently outputting a CLSF and posting through GPM. we use a user defined event for creating an idex of operations:
Index/000 - name of index
Index/000,transl,0,0,0,0 - gives x and y coordinates and number of copies of the operations.
Now, we are moving away from generating the clsf and utilizing a postprocessor. Is there a way to create an array of operations without instancing them? Instances just clutter up the navigator and are not parametric to the initial operation. If I change my array of features, I have to delete the instanced operations and create new ones.
Index/000 - name of index
Index/000,transl,0,0,0,0 - gives x and y coordinates and number of copies of the operations.
Now, we are moving away from generating the clsf and utilizing a postprocessor. Is there a way to create an array of operations without instancing them? Instances just clutter up the navigator and are not parametric to the initial operation. If I change my array of features, I have to delete the instanced operations and create new ones.





RE: creating an "index" command that the postprocessor will interpret
John Joyce
N.C. Programming Supervisor
Barnes Aerospace, Windsor CT
NX6.0.5.3
RE: creating an "index" command that the postprocessor will interpret
Dave