Skip to main content
1-Visitor
September 9, 2009
Question

Merge, Inheritence, Copy Geometry and Publish Geometry

  • September 9, 2009
  • 2 replies
  • 28790 views
I am always confused that what is difference between Merge, Inheritence, Copy Geometry and Publish Geometry features. It seems the function of all three are same. When we should use which feature? Thanks!
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

2 replies

1-Visitor
September 10, 2009
Publish Geometry is a way to bundle together geometry in one part for easy reference by another part. It is used for Copy Geometry features, to re-use geometry in another part as reference. By using Published Geometry, you make it simple and fast for others to select the correct items when using Copy Geometry. Otherwise, there is the possibility that different people could grab different (incorrect) reference geometry. Copy Geometry allows you to grab features and refrences from one part to use in another part. It is indispensible in Top-Down design, where you want separate parts to share common references. In my case, I can use Copy Geometry to grab the internal surfaces of a cast part and incorporate them into a separate part that represents the 'core'. Once the surfaces of the inside are in my new part, I can close them and 'Solidify' to make a representation of the 'core'. Merge/Inheritance is the way you incorporate one complete solid part into another solid part. Merge inserts a monolithic solid feature representing one part in another part -- no changes allowed in the new part. Inheritance does almost the same thing, except the solid feature is not monolithic, you have access to the individual features and therefore you can alter the Inheritance feature in your new part. We use Merge/Inheritance to handle cast and machined parts. Part 'A' is modeled as a casting. Part 'B' is created to represent the "as machined" version of the casting. Inside Part 'B' insert a Merge from Part 'A'. Once done, we can now make cuts to represent the machining operations. If we then change the casting (Part 'A') those changes ripple into the machined casting (Part 'B'). Merge also allows you to make a mirrored copy of a solid part. This came in handy once when we had a design with a left-half and a right-half. We modeled the left-half then used the Merge (with mirror) to make the opposite. Merge will also allow you to make Cut Outs. We have used this functionality to make assembly nests or other such fixtures. Simply make a block of material in Part 'B', then Merge/Cut out Part 'A'. Inheritance is relatively new. I haven't used it. But it seems ideal for cases where you want to to model a part that is a lot like a previous part, but you want to make subtle changes in dimension. I can imagine this would be the case if you were making a new pistol and wanted hand grips almost like another model. You could inherit the grips, and then alter dimensions to make the new grips fit a wider hand (for example). I'm sure PTC can offer other, better examples.
1-Visitor
September 10, 2009
Thanks John for such a detailed explanation. Can u plz give example where we can use Publish geometry.
1-Visitor
September 10, 2009
Great post John, I hope I don't mess this up and confuse the issue. I think I'm correct in saying that you don't directly use Publish. What you do with publish is set up what you want to use, both for other users and yourself. Then when you want to use that particular configuration you can copy geom --> use published geometry
1-Visitor
January 8, 2014

Hi, this may seem like a trivial question, but how do I know if the published geometry needs updating? There aren't any prompts or symbols that tell me if the geometry has changed.

This instance arises when a colleage may be working on a component that I am using as my copied geometry references from on a different part.

Thanks

Steve

21-Topaz II
January 9, 2014

You need to have the source part (with the public) in session and then regen the target (with the copy). This assumes it's an external copy geom, if it's a standard you'd need the parent assembly in session too.