Download presentation
Presentation is loading. Please wait.
1
Mastering Layers Glenn Beer Photon Science & Applications
Lawrence Livermore National Laboratory UCRL-CONF This work was performed under the auspices of the U.S. Department of Energy by the University of California, Lawrence Livermore National Laboratory, under Contract No. W-7405-Eng-48.
2
Poster Child AXIS_TAG CG_POINT CG_POINTS CHAMFER COPY_GEOM COSMETIC
COSMETIC_THDS COSM_SKETCH COSM_THDS COSM_THRDS CSYS CURVER CURVES CURVE_ENT DATUM LAY0002 LOCATION LOCATION2 MAP NOTES PHANTOM_GEOM PLANES POINTS QUILTS ROUND SECTION SET_DATUM SET_DATUMS SKELETON SLOTDTMS SURFACES THREADS THREADS-PIPE THREAD_FEAT VIEW_TXT XSEC_DATUMS _1_CHAMFER _1_HOLE _1_ROUND _2_AXIS _2_COSM_SKETCH _2_CSYS _2_CURVE _2_GTOL _2_NOTE _2_NOTES_COL_1 _2_PLANE _2_POINT _2_START_ASSY_PLANES _2_THREAD _3_ALL_DATUMS _3_ALL_HARDWARE5 16_ALL_ROUNDS 17_ALL_CHAMFERS 1_ALL_PLANES 2_ALL_CSYS 3_ALL_AXES 4_ALL_POINTS 5_ALL_CURVES 6_ALL_SURFS 7_ALL_FEATURES ALL_FEAT ANNOTATIONS ASSY_CSYS ASSY_PLANES ASSY_POINTS AXIS 04__ASM_ALL_DTM_PNT 04___PRT_ALL_DTM_PNT 05_ALL_DTM_CSYS 05__ASM_ALL_DTM_CSYS 05__ASM_DEF_DTM_CSYS 05___PRT_ALL_DTM_CSYS 05___PRT_DEF_DTM_CSYS 06_ALL_SURFS 06__ASM_ALL_SURFS 06___PRT_ALL_SURFS 07__ASM_ALL_SKELETONS 1001_COSM_THRDS 1002_MBM_NOTES 10_ALL_DIMENSIONS 11_DRAWING_NOTES 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 01_ELEVATIONS 01_FLOOR_PLANS 01_PUB_GEOM 01_STATIONS 01__ASM_ALL_DTM_PLN 01__ASM_DEF_DTM_PLN 01___PRT_ALL_DTM_PLN 01___PRT_DEF_DTM_PLN 02_ALL_AXES 02__ASM_ALL_AXES 02___PRT_ALL_AXES 03_ALL_CURVES 03__ASM_ALL_CURVES 03___PRT_ALL_CURVES 04_ALL_DTM_PNT 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 0000_EMPTY 0010_SKELS 0020_PARTS 0021_SUBASSEMBLIES 0022_HARDWARE 0030_UNASSIGNED 0099_START_FEATURES 00_OCD 00_OCD_BEAMPATH_CL 00_OCD_BEAMPATH_SURFS 00_OCD_CSYS 00_OCD_PROFILES 01_ALL_DTM_PLN So who hasn’t seen a model, or a layer tree, that looks like this on retrieval. If you count every layer in every unique model, there’s something like 13,000 layers.
3
I Intend to show… How to easily predict the visibility of items, depending on the layer status. (Isolate, Hidden, Unhidden) How to make effective use of putting items onto multiple layers. And, I’ll demonstrate some cool mapkeys, that are based the info presented. They allow the quick and easy clean up of the layers of an entire assembly and it’s components. 1st point – an example -
4
So What Does Mastering Layers Involve?
Understanding exactly what has been put onto the layers. Knowing “Invisibility Rule #1”. Knowing how layer status impacts visibility. The effective use of placing items onto multiple layers. This makes it easier to choose what you want to see, instead of everything you don’t. Crowd example, big crowd example
5
All Features Have Entities…
Datum Features - Axis, Csys, Curves, Planes, Quilts, Tag Names… FEATURES Sketch Plane Copy Geom DTM1 P3 P2 Entities are the geometrical representation of the feature. Unless you have good reason, you should not put entities on layers. I’d like to point out that when using query select that it is very easy to select entities instead of features. I’ll visit that again a little later. P1 GEOMETRIC ENTITIES
6
* This is a fundamental in Pro/Engineer.
Invisibility Rule #1 Once an item is rendered invisible; every sub item, in that branch of the model, is rendered invisible. Assembly Part Feature Entity Coarse Fine Level of Control Once an item is rendered invisible, every sub item, in that branch of the model, is rendered invisible. It doesn’t matter how the item is made invisible * This is a fundamental in Pro/Engineer.
7
Layer Status Diagram (Parts)
Isolate Hidden Unhidden This VIN diagram distills MANY pages of info out of the user guides Each circle represents all the layers with particular layer status. The circles overlap because layer items can be on multiple layers.
8
Layer Status Diagram (Parts)
Isolate Hidden Unhidden * You can plot all layered items on this diagram Items that are on multiple layers fall into overlapping regions depending on the status of the layers.
9
Layer Status Diagram (Parts)
Isolate Hidden Unhidden Items not on layers are nominally visible V * I Items on isolated layers will “nominally” be visible. Remember that word Nominally. Items on hidden layers but not on Isolated layers will nominally be invisible. Items only on unhidden layers have no fixed status. They flip-flop between visible and invisible depending on the status of other layers. Remember that work Nominally.
10
Layer Status Diagram (Parts)
Isolate Hidden Unhidden Items not on layers are nominally visible V * I Assembly Part Feature Entity Visibility rule #1 overrules layer status. Remember, Invisibility Rule #1 still applies.
11
Layer Status Diagram (Parts)
Isolate Hidden Unhidden Items not on layers are nominally visible Feature Entity V * I Assembly Part Feature Entity If you have a feature that is invisible and you put an entity from that feature onto an isolated layer. Rule 1 will keep it invisible. In this particular case, it doesn’t matter if the positions are swapped. The item will remain invisible. Remember, Invisibility Rule #1 still applies.
12
Choosing What You Want to See (Isolate)
CURVES SURFACES PLANES SET-DATUMS CSYS I V I V I V I I I Isolate, BEAM-CENTERLINE LAYER BEAMPATH LAYER OPTIC-LOCATIONS LAYER Hidden 5X Isolated 3X
13
Layer Status Diagram (Assemblies)
Isolate Hidden Unhidden V * I Items not on layers are nominally visible Remember, Visibility Rule #1 still applies. Feature Entity All of the rules that apply to parts, apply equally to assemblies… Until a component (subassy, part) is added to a layer Every aspect of layers in an assembly is the same as in parts, until a component is added to a layer – then things change, boy do they!
14
Layer Status (Assemblies)
About putting components on layers… My Advice: Don’t do it! Simplified Reps are better for managing component visibilities Items out side of the branch that has been isolated become invisible. Advice: Don’t do it It’s much easier to use simplified reps to control visibility of components, and none of the above apply
15
Putting It Together Use Isolate in place of Unhidden.
Putting items on multiple layers becomes useful. Creating new layers need not disturb existing layers. Choose what you want to see, instead of everything you don’t. Create, all inclusive, default layers only for the items found in the majority of your models. Don’t remove items from them, with Isolate, it isn’t necessary. Create layers that suit your needs. Save all layers with the status Hidden. Make exceptions only for things that need to be seen in ALL upper assemblies. If you’re not willing to do this… Click --- Keep all layers saved with hidden status. Click --- Don’t inflict a default layer on all of your models when only a few require it. Mapkeys to create those layers when needed work wonders. Click --- Splitting layers – An ugly thing that happens when isolate is not used.
16
Demo: Config.pro, Drawing.dtl & Mapkeys
no def_layer options add_lower_level_comps_to_layer no Make the environment display options on by default. Drawing.dtl ignore_model_layer_status yes draw_layer_overrides_model yes
17
Demo’s Cleaning an Assembly Drawings & Parts Skeletons
Using find to create layers. Using the extend function to create layers, with rules, recursively. Searching for items in the layer tree. Using the selector to manipulate the layer tree. How to distinguish between entities and features. The quick cleanup demo. Drawings & Parts Create drawing layers, use them to keep changes to the model from impacting the drawing. Skeletons Layers to fit special requirements. Why put items on more than one layer? Why does the layer status column in the model tree say something is displayed when it is invisible? Why haven’t the items on this layer become visible when I made it Isolated? I added someone else’s assembly to mine, why did all my stuff vanish?
Similar presentations
