×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

To publish or not

To publish or not

To publish or not

(OP)
Maybe someone can set me straight on this one.  Is there an advantage to publish bodies, surfaces, points, etc?  If so, where is it better than just a straight copy and paste with link.

Thanks.
Ross.

RE: To publish or not

A publication is like a stake in the ground.

It gives you the ability to redefine the object it is pointed at. As does copy with link

However it orders the data in a manner that makes it easy to manage and select by some sensible name.

Regards

Nev

RE: To publish or not

The biggest benefit is when the linked parent geometry is modified or replaced.

If the linked body,surface,plane,point is modified or if it's replaced with a new element, the copied (child) geometry must be replaced manually. This can take lots of time, especially if this copied geometry is the parent to many other elements.

But if the parent geometry is published, then all the children are automatically replaced.  

RE: To publish or not

Another benefit is the published elements appear 'higher' in the tree, so you don't have to expand the tree as much to select something.

RE: To publish or not

(OP)
Jackk, agreed that the linked data is better.  I do that now but I have been picking an unpublished element and the pasted special> copy w/ link.  That seems to do the same thing.  What Nev was saying, it give the next user an organized look. ie it puts all the data that was copied to other parts in a tidy area.  

What I am feeling is that publishing does not offer any extra modeling benifits but it helps organize you data.  Which is a VERY good thing.  Is that a correct statement?

Thanks guys.
Ross.

RE: To publish or not

Can you put a price tag on assembly stability?  If you replace components that use identical published names, the contextual links that are used in the assembly are also replaced with the new items.

RE: To publish or not

Ross,

Yes - Linked data is better, but Published Linked data is best.

you asked: "What I am feeling is that publishing does not offer any extra modeling benefits but it helps organize you data.   Is that a correct statement?"

Well... yes, it is a correct statement. Publishing does not help make better solid or surface geometry.

The only benefit Publish provides to the creator of the Published data is it provides a convenient way to communciate which data should be used by those who are making the links to their children parts.

  


RE: To publish or not

Reiteration:
Publishing allows you to create a stable external reference.  This is especially useful when creating complex Knowledge Templates.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources