[QUOTE=PierpaoloPau;68469]That's great!
About 'transfer pipe model to equiment model' I was thinking to do the same few month ago.
Me too I'm massively into PML programming.
I modelled some Flares with pipe then I was thinking it would be useful to convert them to equi.
I can see from the image that you translated PIPE with EQUI and branch with SUBE, that is the same I was thinking to do.
How did you manege coordinates and orientation? This is the main problem in my mind.
All branch member primitives has local coordinetes and orientation.
And what about torus? The definition of this primitive is quite different in paragon.
For each piping element, in gmref of its catref, position, orientation and other properties of all the primitives are defined in expression of parameters.
The same catref could have many instances in desigen.in order to get the position, orientation and other properties, you have to evaluate each expression basing on the instance(piping element) in design, then you will get what you want.
[QUOTE=PierpaoloPau;68469]That's great!
About 'transfer pipe model to equiment model' I was thinking to do the same few month ago.
Me too I'm massively into PML programming.
I modelled some Flares with pipe then I was thinking it would be useful to convert them to equi.
I can see from the image that you translated PIPE with EQUI and branch with SUBE, that is the same I was thinking to do.
How did you manege coordinates and orientation? This is the main problem in my mind.
All branch member primitives has local coordinetes and orientation.
And what about torus? The definition of this primitive is quite different in paragon.
For each piping element, in gmref of its catref, position, orientation and other properties of all the primitives are defined in expression of parameters.
The same catref could have many instances in desigen.in order to get the position, orientation and other properties, you have to evaluate each expression basing on the instance(piping element) in design, then you will get what you want.
