Officers and Committees of the IGES/PDES Organization September 17, 1991 Officers Chair William Conroy IGES Project Manager J. C. Kelly PDES Project Manager Anthony Day Testing Project Manager Constance Bracken Associated Staff IPO Editor Joan Wellington Executive Assistant Melissa Andrews Clerk Typist Mona Randall Administrative Coordinator, NCGA Nancy Flower IGES Editor Kent Reed IGES Change Control Secretary Jim Johnson IGES Ballot Coordinator Melissa Andrews Configuration Control Admin. Gaylen Rinaudot iii Technical Committee Chairs Application Validation Methodology Mark Palmer Joel Petersen, deputy Architecture, Engineering, & Construction Joseph Halford Burt Gischner, IGES Coordinator PDES Composites Glen Ziolko Dictionary/Methodology Peter Eirich Drafting Robert Parks Greg Morea, deputy (IGES) Electrical Applications Larry O'Connell Bob Owens, deputy (IGES) Rob Fletcher, deputy (PDES) Finite Element Analysis Keith Hunten Form Features Mark Dunn Tom Kramer, deputy Geometry Tracy Whelan Noel Christensen, deputy Implementation Specifications Jim Fowler Implementors Bill Turcotte George Baker, co-chair Interoperability Testing Methodology Nellie Morack Gary Conkol, deputy Manufacturing Technology Greg Paul Dan Small, deputy Materials John Rumble Mechanical Product Definition Bill Cain PDES Development Methods Bill Danner PDES Presentation Neal Appel Product Life Cycle Support Rick Bsharah Shirley Goodman, deputy Product Structure Buzz Bloom (a) Qualification & Integration Yuhwei Yang David Sanford, deputy Recommended Practices George Baker Software Products Tom Baker George Coletta, deputy Standard Parts Bob Meagher co-chair (a) Ron Bale co-chair Technical Publications Camillo Marziani, deputy Test Case Design Jim Felt Ken Erman, deputy Testing Methodologies Alan Peltzman Tolerances William Burkett Martin Holland, deputy iv Steering Committee Officers Chair Jim Snyder Credentials Mike Nolan Liason Jim Nell Special Interest Groups CALS/IGES Lisa Deeds Ben Kassel, deputy CALS/PDES Shirley Goodman, co-chair Tamera Terrell, co-chair Related Organizations ISO/SC4 Brad Smith ISO/PMAG Jerry Weiss National PDES Testbed Chuck McLean PDES, Inc. Bob Kiggans U.S. TAG to ISO/SC4 Kal Brauner v Members of the IGES/PDES Organization The following individuals participated in the balloting process to develop this Specification. Altemueller, Jeff McDonnell Douglas Corporation Anderson, Bill D. Battelle Anderson, Robert E. Naval Aviation Depot Assiff, Thomas C. Electronic Data Systems Baker, George W. International TechneGroup Inc. Bares, Peter Intentia AB Barker, Raymond E. Caterpillar, Inc. Bartlett, Sue Mentor Graphics Corporation Beazley, William CALS Report Berenyi, Tibor A. Deere and Company Bernstein, Joe Boeing Computer Services Billingsley, Dan Naval Sea Systems Command Blaney, David H. United Technologies Bloom, Buzz Prime Computer Bracken, Constance L. Electronic Data Systems Bradford, James E. Allied Signal Brainin, Jack David Taylor Research Center Brauner, Kalman Boeing Co. Briggs, David D. Boeing Co. Bronder, Clare M. Adra Systems, Inc. Brooks, Richard J. McDonnell Douglas Corporation Burkett, William C. Lockheed Aeronautical Systems, Co. Burns, Bernard J. Naval Surface Warfare Cain, William D. Martin Marietta Energy Systems Calkins, Bruce SEACOSD Carpenter, Vickie Electronic Data Systems Casey, Eva W. Schlumberger Technologies CAD/CAM Chamberlain, Mark T. Hughes Aircraft Cheever, Richard W. Martin Marietta Chi, Kelly McDonnell Douglas Corporation Christensen, Noel C. Allied Signal, Inc. Clapp, Edward Autodesk, Inc. Cochran, Richard McDonnell Douglas Corporation Colsher, Robert IGES Data Analysis Conroy, William NIST/EDS Corn, Earleen Newport News Shipbuilding vi MEMBERS OF THE IGES/PDES ORGANIZATION Costello, Helen D. Lockheed Aeronautical Systems Co. Cox, Margery J. Newport News Shipbuilding Crusey, Jesse L. NIST Dai, Losheng Sikorsky Aircraft Danielson, Pamela R. General Dynamics Dawson, Laurel C. IBM Deeds, Lisa V. David Taylor Research Center Dellinger, David L. Boeing Commercial Airplanes DePauw, Spencer Caterpillar Inc. Downer, Ron CAD/CAE Consulting Services Dragoo, Alan E. IGES Data Analysis Corporation Dvorak, Andrew Bath Iron Works Easley, Preston Northrop Corporation Erman, Ken CADKEY, Inc. Fallon, Kristine K. Computer Technology Management, Inc. Farrell, Jill M. Lawrence Livermore National Laboratory Faulkner, John C. SDRC Fleming, Jim Cummins Engine Co., Inc. Fong, Henry H. MARC Analysis Research Corporation Fox, Mike A. O. GRN Technology Ltd. Francis, Ray M. Naval Weapons Center Freund, Kevin D. Appleton Co. Inc. Frimer, Morris Boeing Electronics Company Gauntlett,Clifford J. Autodesk, Inc. Genseal, Steve Caterpillar, Inc. Giguere, Marshall E. Data Exchange Associates Gilbert, Mitchell Grumman Aircraft Systems Gilbert, Chip Martin Marietta Corporation Gischner, Burton General Dynamics - Electric Boat Golish, Mike US Army CECERL - FS Goodman, Shirley A. NAVORDSTA Goosen, Ted General Dynamics Goult, Ray J. Cranfield Institute of Technology Gray, W. Harvey Martin Marietta Corporation Green, Ronald D. Boeing Grout, Steven J. Martin Marietta Gurga, Eugene F. J I Case Gygi, Michael McDonnell Douglas Corporation Haines, Mark International TechneGroup, Inc. Halford, Joseph D. EI Du Pont de Nemours Co. Hamilton, C.H. PDA Engineering Hanson, Eric International TechneGroup, Inc. Harrison, Randy J. Sandia National Laboratories Harrod, Jr., Dennette A. Computervision Harrow, Pat Harrow Associates Ltd. Hart, John R. Boeing Advanced Systems Company Harvie, Andrew Nova Scotia CAD/CAM Centre Hebert, Charles T. Boeing Hemmelgarn, Don International TechneGroup Inc. Hooper, Richard Eastman Kodak vii MEMBERS OF THE IGES/PDES ORGANIZATION Humphrey, Darrell Martin Marietta Data Systems Hunten, Keith General Dynamics Hussong, William A. Honeywell, Inc. Ippolito, Greg General Dynamics Isenberg, Madeleine R. Northrop Corporation Ivey, Robert L. Westinghouse Electric Corporation Jaeger, Dwight L. Los Alamos National Laboratory Jensen, David EDS - BOC Headquarters Johnson, Jim General Dynamics Jones, Alan K. Boeing Computer Services Jones, Douglas Accugraph Corporation Judd, Jon L. General Dynamics Jurrens, Kevin NIST Kamvar, Estandiar AT & T Bell Laboratories Kassel, Ben David Taylor Research Center Kato, Toru Toyota Motor Corporation Keith, Greg Automation Technology Products Kelly, J. C. Sandia National Laboratories Kemmerer, Sharon NIST Kennedy, Philip J. Electronic Data Systems Kenngott, Debbie AutoTrol Technology Corporation Kennicott, Philip Sandia National Laboratories Ker, Kenneth R. McDonnell Douglas Kohler, Rick XL Engineering Kontry, Karen L. Electronic Data Systems Krishnaswami, Ravi Electronic Data Systems Kromarek, Darrel V. Boeing Aerospace & Electronics Kshirsagar, Sudhir Proctor & Gamble Kuan, L. P. NET Inc. Ladd, Harry E. Du Pont Engineering Development Laboratory Larsen, Larry J. Boeing Commercial Airplanes Lazo, Pete L. Newport News Shipbuilding Lee, Kaiman NAVFAC DSO-1A Leung, Richard AT & T Lichten, Olga IBM Linsner, James D. Boeing Computer Services Little, Maureen Naval Civil Engineering Laboratory Lodewijks, Bart Philips Losinski, Mark Control Data Corporation Lovdahl, Richard H. Lovdahl & Associates Loye, William CADnetix Lucke, Virgil General Electric Company MacLatchie, Robert PlanPrint Company Magoon, Gary CADKEY, Inc. Makoski, Thomas International TechneGroup Inc. Martino, Linda IBM Marz, Steven D. Integraph Corporation Marziani, Camillo Boeing Helicopters Mathew, Abraham Integraph Corporation Mays, James L. Naval Supply Systems Command viii MEMBERS OF THE IGES/PDES ORGANIZATION Messcher, Walter US Dept. of Transportation Miller, Rex D. Xerox Corporation Miller, Darin General Dynamics Mindel, Carolyn F. SDRC Montano, Allan M. Electronic Data Systems Morack, Nellie CDI Transportation Group Morea, Gregory General Dynamics - Electric Boat Morgan, Donald E. General Electric Aircraft Engines Morrill, Charles B. IBM Motz, Philip Cincinnati Milacron Murphy, James NAVSEA/NIDDESC Mylavarapu, Rao S. Electronic Data Systems Nairn, Bill CAD-CAM Data Exchange Technical Centre/UK Nelson, Paul A. Hughes Aircraft Company Nguyen, Hakim CADKEY, Inc. Nolan, Michael F. Rosetta Technology, Inc. O'Connell, Larry Sandia National Laboratories Oakes, Jr., William R. Los Alamos National Laboratories Overbeek, Michael D. International TechneGroup Inc. Owens, Bob Martin Marietta Paine, Louis C. Electronic Data Systems Palmer, Mark NIST Panzica, Connie General Motors Parker, Lawrence O. GM/Hughes Electronics Parks, Curtis H. NIST Parks, Robert E. Sandia National Laboratories Paschelke, Robert Point Control Company Paul, Greg A. General Dynamics Pearson, Mark CAD-CAM Data Exchange Technical Centre/UK Peltzman, Alan Peltzman Associates Petersen, Joel S. IBM Corporation Phelps, Freda Sun Microsystems Pilkenton, Stephen General Dynamics Prince, Anthony Integraph Corporation Purdon, James C. Schlumberger Technologies CAD/CAM Ranke, Guus Nederlandse Philips Bedryven BV Rau, Timothy R. NASA Space Station Freedom Program Reed, Kent NIST Rehg, Ed Texas Instruments Reid, E. A. Caterpillar, Inc. Remington, David O. NOVA University Rinaudot, Gaylen R. NIST Robinson, Gloria R. Electronic Data Systems Rodenberger, C. Mark General Dynamics Roth, Gloria R. Electronic Data Systems Sabine, Anne Newport News Shipbuilding Sadler, David Randolph NAVSEACOMBATSYSTENGSTA Sasser, Vickie Electronic Data Systems Schachtner, Steven R. Martin Marietta Scheets, William R. Caterpillar, Inc. ix MEMBERS OF THE IGES/PDES ORGANIZATION Schilli, Bruno University of Karlsruhe RPK Schmid, Randy CADAM Inc. Schroeter, Dirk J. Martin Marietta Schwander, Chris M. EI Du Pont de Nemours Co. Scott, Gladys E. Newport News Shipbuilding Scott, Ronald McDonnell Douglas Corporation Sherwood, Kenneth CADAM Inc. Siemon, Mark US Navy Skidmore, Lindsay Naval Weapons Support Center Slack, Francine Electronic Data Systems Small, Daniel H. Boeing Computer Systems Smith, Bradford M. NIST Smith, Robert E. Boeing Defense & Space Group Stark, Chuck South Carolina Research Authority/NIST Stoddard, Charles L. Pratt and Whitney Stone, Donald D. Hughes Aircraft Company Szmrecsanyi, Emery Chrysler Motor Corporation Taylor, Herb AutoTrol Technology Corporation Thompson, Jr., C. B. Southern Company Services, Inc. Tittle, Fremont Control Data Corporation Tompkins, Edwin B. Johns Hopkins University Torossian, Julie A. Electronic Data Systems Turcotte, William IGES Data Analysis Corporation Turner, James A. University of Michigan APRL Weideman, Christian IVF Wellington, Joan NIST Wells, Michael Rosetta Technologies, Inc. Wester, Ronald O. General Electric Company Whelan, Tracy M. CAMAX Systems, Inc. Williams, Anne McDonnell Douglas Corporation Wilson, Peter R. Rensselaer Polytechnic Institute Winfrey, R. C. Digital Equipment Company Wooley, Daniel Newport News Shipbuilding Wright, Debora J. Sikorsky Aircraft Yang, Sheree Ford Aerospace Corporation x Foreword This version of the Specification differs from its predecessors more in form than in content. A complete reorganization of the sections, to place the entity type definitions in an ascending numerical order, has been a long-standing goal of the IGES/PDES Organization (IPO). The major changes are the result of approximately 75 Request For Change submissions, developed by the various technical committees and approved as technical Edit Change Orders (ECOs) through mail ballots by the General Assembly, and approximately 20 editorial Edit Change Orders issued by the IGES Project Committee. The majority of the new entity types and form numbers introduced in this version of the Specification were created to improve the quality and robustness of data exchange in the application disciplines of Drafting, Electrical, and AEC. Numerous technical clarifications and technical additions have been made to geometry entities. The single most significant change is the addition of unambiguous requirements on the Directory Entry (DE) fields as applied to each of the individual entity types and form numbers. Most of the changes have been highlighted by the placement of the relevant ECO numbers in the margins. Some ECOs were so all-encompassing (e.g., providing consistent nomenclature in Parame- ter Data descriptions) that it was impractical to indicate each occurrence. Some ECOs superseded others and some removed sections in their entirety, so it was simply not possible to include highlights for all of the ECOs. When comparing this version with the previous one, sections highlighted by an ECO number should be examined very carefully because the change may consist of the addition or deletion of a single word (e.g., "not"), but this change could radically alter the technical content of the data representation. This version also marks a milestone in demonstrating the utility of the Specification. All of the technical illustrations were generated from data files that conform to the Specification. That is to say, the text and graphics in this document exist entirely in electronic form, and the pages were produced on a laser-imaging printer using device driver software that combines the output of a LaTEX document preparation system and the raster image output of an IGES postprocessing system. Use of this technology has resulted in a harmonization of the illustrations (consistent text and line font appearance) and the highest possible resolution, which in this case is 300 dots per inch. Several entities have been moved from the Untested Entities Appendix into the body of the Speci- fication, and most new entities and forms appear in that appendix. The MACRO Entity has been moved from the body of the Specification to the Untested Entities Appendix. The Binary Form has been deprecated and moved to a new appendix. This Specification is being published as a NIST report to provide the baseline technical document for standardization by the American National Standards Institute and to provide the document with greater exposure to the user community. The format differs from that of a normal NIST report to facilitate the standardization process. xi This page intentionally left blank. xii Contents Officers and Staff of the IGES/PDES Organization iii Members of the IGES/PDES Organization vi Foreword xi 1 General 1 1.1 Purpose : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 1 1.2 Field of Application : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 1 1.3 Conformance to the Specification : : : : : : : : : : : : : : : : : : : : : : : : : : : : 1 1.3.1 Conformance rules for data files. : : : : : : : : : : : : : : : : : : : : : : : : 2 1.3.2 Conformance rules for preprocessors. : : : : : : : : : : : : : : : : : : : : : 2 1.3.3 Conformance rules for postprocessors. : : : : : : : : : : : : : : : : : : : : : 2 1.4 Untested Entities : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 2 1.5 Concepts of Product Definition : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 2 1.6 Concepts of the File Structure : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 3 1.7 Concepts of Information Structures for Geometric Models : : : : : : : : : : : : : : 4 1.7.1 Property Entity. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 4 1.7.2 Associativity Entities. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 5 1.7.3 View Entity. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 5 1.7.4 Drawing Entity. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 5 1.7.5 Transformation Matrix Entity. : : : : : : : : : : : : : : : : : : : : : : : : : 5 1.7.6 Implementor-Defined Entities. : : : : : : : : : : : : : : : : : : : : : : : : : 5 1.8 Appendices : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 6 2 Data Form 7 2.1 General : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 2.1.1 Defaults. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 xiii CONTENTS 2.2 ASCII Form : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 2.2.1 Sequence Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 7 2.2.2 Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 8 2.2.2.1 Integer Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : 8 2.2.2.2 Real Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : : 9 2.2.2.3 String Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : 9 2.2.2.4 Pointer Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : 10 2.2.2.5 Language Statement Constants. : : : : : : : : : : : : : : : : : : : 10 2.2.2.6 Logical Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : 10 2.2.3 Rules for Forming and Interpreting Free Formatted Data. : : : : : : : : : : 10 2.2.3.1 Parameter and Record Delimiter Combinations. : : : : : : : : : : 11 2.2.4 File Structure. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 11 2.2.4.1 Start Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 12 2.2.4.2 Global Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : 12 2.2.4.3 Directory Entry Section. : : : : : : : : : : : : : : : : : : : : : : : 17 2.2.4.4 Parameter Data Section. : : : : : : : : : : : : : : : : : : : : : : : 25 2.2.4.5 Terminate Section. : : : : : : : : : : : : : : : : : : : : : : : : : : 28 2.3 Compressed ASCII Format : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 29 2.3.1 File Structure. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 29 3 Classes of Entities 31 3.1 General : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 31 3.2 Curve and Surface Geometry Entities : : : : : : : : : : : : : : : : : : : : : : : : : 31 3.2.1 Entity Type/Type Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : 31 3.2.2 Coordinate Systems. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 32 3.2.3 Multiple Transformation Entities. : : : : : : : : : : : : : : : : : : : : : : : 33 3.2.4 Directionality. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 33 3.3 Constructive Solid Geometry Entities : : : : : : : : : : : : : : : : : : : : : : : : : 36 3.3.1 Entity Type/Type Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : 36 3.3.2 Constructive Solid Geometry Models. : : : : : : : : : : : : : : : : : : : : : 36 3.4 B-Rep Solid Entities : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 38 3.4.1 Entity Type/Type Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : 38 3.4.2 Topology for B-Rep Solid Models. : : : : : : : : : : : : : : : : : : : : : : : 38 3.4.3 Analytical Surfaces for B-Rep Solid Models. : : : : : : : : : : : : : : : : : 39 3.4.3.1 Entity Type/Type Numbers. : : : : : : : : : : : : : : : : : : : : : 40 xiv CONTENTS 3.4.3.2 Parameterization of Analytical Surfaces. : : : : : : : : : : : : : : 40 3.5 Annotation Entities : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 41 3.5.1 Entity Type/Type Number. : : : : : : : : : : : : : : : : : : : : : : : : : : 41 3.5.2 Construction. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 41 3.5.3 Definition Space. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 41 3.5.4 Dimension Attributes : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 43 3.5.4.1 General. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 43 3.5.4.2 Usage Rules. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 43 3.6 Structure Entities : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 46 3.6.1 Entity Type/Type Number. : : : : : : : : : : : : : : : : : : : : : : : : : : 46 3.6.2 Subfigures. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 46 3.6.3 Connectivity. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 47 3.6.3.1 Connectivity Entities. : : : : : : : : : : : : : : : : : : : : : : : : : 47 3.6.3.2 Entity Relationships. : : : : : : : : : : : : : : : : : : : : : : : : : 47 3.6.3.3 Information Display. : : : : : : : : : : : : : : : : : : : : : : : : : 49 3.6.3.4 Additional Considerations. : : : : : : : : : : : : : : : : : : : : : : 49 3.6.4 External Reference Linkage. : : : : : : : : : : : : : : : : : : : : : : : : : : 49 3.6.5 Drawings and Views. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 52 3.6.6 Finite Element Modeling. : : : : : : : : : : : : : : : : : : : : : : : : : : : : 53 3.6.7 Attribute Tables. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 53 4 Entity Types 57 4.1 General : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 57 4.2 Null Entity (Type 0) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 58 4.3 Circular Arc Entity (Type 100) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 59 4.4 Composite Curve Entity (Type 102) : : : : : : : : : : : : : : : : : : : : : : : : : : 62 4.5 Conic Arc Entity (Type 104) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 67 4.6 Copious Data Entity (Type 106) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 73 4.7 Centerline Entity (Type 106, Form 20-21) : : : : : : : : : : : : : : : : : : : : : : : 77 4.8 Section Entity (Type 106, Forms 31-38) : : : : : : : : : : : : : : : : : : : : : : : : 79 4.9 Witness Line Entity (Type 106, Form 40) : : : : : : : : : : : : : : : : : : : : : : : 82 4.10 Plane Entity (Type 108) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 84 4.11 Line Entity (Type 110) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 88 4.12 Parametric Spline Curve Entity (Type 112) : : : : : : : : : : : : : : : : : : : : : : 90 4.13 Parametric Spline Surface Entity (Type 114) : : : : : : : : : : : : : : : : : : : : : 94 xv CONTENTS 4.14 Point Entity (Type 116) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 98 4.15 Ruled Surface Entity (Type 118) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 100 4.16 Surface of Revolution Entity (Type 120) : : : : : : : : : : : : : : : : : : : : : : : : 104 4.17 Tabulated Cylinder Entity (Type 122) : : : : : : : : : : : : : : : : : : : : : : : : : 107 4.18 Direction Entity (Type 123) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 110 4.19 Transformation Matrix Entity (Type 124) : : : : : : : : : : : : : : : : : : : : : : : 111 4.20 Flash Entity (Type 125) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 119 4.21 Rational B-Spline Curve Entity (Type 126) : : : : : : : : : : : : : : : : : : : : : : 122 4.22 Rational B-Spline Surface Entity (Type 128) : : : : : : : : : : : : : : : : : : : : : 124 4.23 Offset Curve Entity (Type 130) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 127 4.24 Connect Point Entity (Type 132) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 129 4.25 Node Entity (Type 134) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 132 4.26 Finite Element Entity (Type 136) : : : : : : : : : : : : : : : : : : : : : : : : : : : 135 4.27 Nodal Displacement and Rotation Entity (Type 138) : : : : : : : : : : : : : : : : 149 4.28 Offset Surface Entity (Type 140) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 152 4.29 Boundary Entity (Type 141) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 155 4.30 Curve on a Parametric Surface Entity (Type 142) : : : : : : : : : : : : : : : : : : 156 4.31 Bounded Surface Entity (Type 143) : : : : : : : : : : : : : : : : : : : : : : : : : : 158 4.32 Trimmed (Parametric) Surface Entity (Type 144) : : : : : : : : : : : : : : : : : : 159 4.33 Nodal Results Entity (Type 146) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 161 4.34 Element Results Entity (Type 148) : : : : : : : : : : : : : : : : : : : : : : : : : : : 162 4.35 Block Entity (Type 150) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 163 4.36 Right Angular Wedge Entity (Type 152) : : : : : : : : : : : : : : : : : : : : : : : 165 4.37 Right Circular Cylinder Entity (Type 154) : : : : : : : : : : : : : : : : : : : : : : 167 4.38 Right Circular Cone Frustum Entity (Type 156) : : : : : : : : : : : : : : : : : : : 169 4.39 Sphere Entity (Type 158) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 171 4.40 Torus Entity (Type 160) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 173 4.41 Solid of Revolution Entity (Type 162) : : : : : : : : : : : : : : : : : : : : : : : : : 175 4.42 Solid of Linear Extrusion Entity (Type 164) : : : : : : : : : : : : : : : : : : : : : 178 4.43 Ellipsoid Entity (Type 168) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 180 4.44 Boolean Tree Entity (Type 180) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 182 4.45 Selected Component Entity (Type 182) : : : : : : : : : : : : : : : : : : : : : : : : 185 4.46 Solid Assembly Entity (Type 184) : : : : : : : : : : : : : : : : : : : : : : : : : : : 186 4.47 Manifold Solid B-Rep Object Entity (Type 186) : : : : : : : : : : : : : : : : : : : 187 xvi CONTENTS 4.48 Plane Surface Entity (Type 190) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 188 4.49 Right Circular Cylindrical Surface Entity (Type 192) : : : : : : : : : : : : : : : : 189 4.50 Right Circular Conical Surface Entity (Type 194) : : : : : : : : : : : : : : : : : : 190 4.51 Spherical Surface Entity (Type 196) : : : : : : : : : : : : : : : : : : : : : : : : : : 191 4.52 Toroidal Surface Entity (Type 198) : : : : : : : : : : : : : : : : : : : : : : : : : : 192 4.53 Angular Dimension Entity (Type 202) : : : : : : : : : : : : : : : : : : : : : : : : : 193 4.54 Curve Dimension Entity (Type 204) : : : : : : : : : : : : : : : : : : : : : : : : : : 196 4.55 Diameter Dimension Entity (Type 206) : : : : : : : : : : : : : : : : : : : : : : : : 197 4.56 Flag Note Entity (Type 208) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 199 4.57 General Label Entity (Type 210) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 203 4.58 General Note Entity (Type 212) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 205 4.59 New General Note Entity (Type 213) : : : : : : : : : : : : : : : : : : : : : : : : : 223 4.60 Leader (Arrow) Entity (Type 214) : : : : : : : : : : : : : : : : : : : : : : : : : : : 224 4.61 Linear Dimension Entity (Type 216) : : : : : : : : : : : : : : : : : : : : : : : : : : 229 4.62 Ordinate Dimension Entity (Type 218) : : : : : : : : : : : : : : : : : : : : : : : : 231 4.63 Point Dimension Entity (Type 220) : : : : : : : : : : : : : : : : : : : : : : : : : : 233 4.64 Radius Dimension Entity (Type 222) : : : : : : : : : : : : : : : : : : : : : : : : : 235 4.65 General Symbol Entity (Type 228) : : : : : : : : : : : : : : : : : : : : : : : : : : : 237 4.66 Sectioned Area Entity (Type 230) : : : : : : : : : : : : : : : : : : : : : : : : : : : 239 4.67 Associativity Definition Entity (Type 302) : : : : : : : : : : : : : : : : : : : : : : 245 4.68 Line Font Definition Entity (Type 304) : : : : : : : : : : : : : : : : : : : : : : : : 248 4.69 Subfigure Definition Entity (Type 308) : : : : : : : : : : : : : : : : : : : : : : : : 254 4.70 Text Font Definition Entity (Type 310) : : : : : : : : : : : : : : : : : : : : : : : : 255 4.71 Text Display Template Entity (Type 312) : : : : : : : : : : : : : : : : : : : : : : : 260 4.71.1 Absolute Text Display Template (Form 0). : : : : : : : : : : : : : : : : : : 261 4.71.2 Incremental Text Display Template (Form 1). : : : : : : : : : : : : : : : : 262 4.72 Color Definition Entity (Type 314) : : : : : : : : : : : : : : : : : : : : : : : : : : : 263 4.73 Units Data Entity (Type 316) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 264 4.74 Network Subfigure Definition Entity (Type 320) : : : : : : : : : : : : : : : : : : : 265 4.75 Attribute Table Definition Entity (Type 322) : : : : : : : : : : : : : : : : : : : : : 267 4.75.1 Attribute Table Definition (Form 0). : : : : : : : : : : : : : : : : : : : : : : 268 4.75.2 Attribute Table Definition (Form 1). : : : : : : : : : : : : : : : : : : : : : : 269 4.75.3 Attribute Table Definition (Form 2). : : : : : : : : : : : : : : : : : : : : : : 270 4.76 Associativity Instance Entity (Type 402) : : : : : : : : : : : : : : : : : : : : : : : 299 xvii CONTENTS 4.76.1 Predefined Associativities. : : : : : : : : : : : : : : : : : : : : : : : : : : : 301 4.76.1.1 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 301 4.76.1.2 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 303 4.76.1.3 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 304 4.76.1.4 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 306 4.76.1.5 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 308 4.76.1.6 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 310 4.76.1.7 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 311 4.76.1.8 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 312 4.76.1.9 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 313 4.76.1.10 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 314 4.76.1.11 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 315 4.76.1.12 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 316 4.76.1.13 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 317 4.76.1.14 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 320 4.76.1.15 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 321 4.76.1.16 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 322 4.76.1.17 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 324 4.76.1.18 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 328 4.76.1.19 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 329 4.76.1.20 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 330 4.77 Drawing Entity (Type 404) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 331 4.78 Property Entity (Type 406) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 335 4.78.1 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 336 4.78.2 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 337 4.78.3 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 339 4.78.4 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 340 4.78.5 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 341 4.78.6 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 343 4.78.7 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 344 4.78.8 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 345 4.78.9 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 346 4.78.10 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 347 4.78.11 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 348 xviii CONTENTS 4.78.12 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 377 4.78.13 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 378 4.78.14 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 379 4.78.15 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 380 4.78.16 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 381 4.78.17 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 382 4.78.18 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 383 4.78.19 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 384 4.78.20 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 385 4.78.21 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 386 4.78.22 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 387 4.78.23 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 388 4.78.24 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 389 4.78.25 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 390 4.78.26 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 391 4.78.27 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 392 4.78.28 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 393 4.78.29 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 394 4.78.30 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 395 4.78.31 : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 396 4.79 Singular Subfigure Instance Entity (Type 408) : : : : : : : : : : : : : : : : : : : : 397 4.80 View Entity (Type 410) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 399 4.81 Rectangular Array Subfigure Instance Entity (Type 412) : : : : : : : : : : : : : : 405 4.82 Circular Array Subfigure Instance Entity (Type 414) : : : : : : : : : : : : : : : : : 407 4.83 External Reference Entity (Type 416) : : : : : : : : : : : : : : : : : : : : : : : : : 409 4.84 Nodal Load/Constraint Entity (Type 418) : : : : : : : : : : : : : : : : : : : : : : 412 4.85 Network Subfigure Instance Entity (Type 420) : : : : : : : : : : : : : : : : : : : : 414 4.86 Attribute Table Instance Entity (Type 422) : : : : : : : : : : : : : : : : : : : : : : 416 4.86.1 Attribute Table Instance (Form 0). : : : : : : : : : : : : : : : : : : : : : : 416 4.86.2 Attribute Table Instance (Form 1). : : : : : : : : : : : : : : : : : : : : : : 417 4.87 Solid Instance Entity (Type 430) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 418 4.88 Vertex Entity (Type 502) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 419 4.89 Edge Entity (Type 504) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 420 4.90 Loop Entity (Type 508) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 421 xix CONTENTS 4.91 Face Entity (Type 510) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 422 4.92 Shell Entity (Type 514) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 423 A Part File Examples 425 B Spline Curves and Surfaces 447 B.1 Introduction : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 447 B.2 Spline Functions : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 447 B.3 Spline Curves : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 448 B.4 Rational B-spline Curves : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 449 B.5 Spline Surfaces : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 450 B.6 Rational B-spline Surfaces : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 451 C Conic Arcs 453 D Color-Space Mappings 455 E ASCII Form Conversion Utility 457 F Obsolete Entities 471 F.1 General : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 471 F.2 Obsolete Associativity Instance Entities (Type 402) : : : : : : : : : : : : : : : : : 472 F.2.1 (Type 402, Form 2) - External Logical Reference File Index : : : : : : : : : 472 F.2.2 (Type 402, Form 6) - View List : : : : : : : : : : : : : : : : : : : : : : : : 473 F.2.3 (Type 402, Form 8) - Signal String : : : : : : : : : : : : : : : : : : : : : : : 474 F.2.4 (Type 402, Form 10) - Text Node : : : : : : : : : : : : : : : : : : : : : : : 476 F.2.5 (Type 402, Form 11) - Connect Node : : : : : : : : : : : : : : : : : : : : : 478 F.3 Obsolete Property Entity (Type 406) : : : : : : : : : : : : : : : : : : : : : : : : : 480 F.3.1 (Type 406, Form 4) - Region Fill : : : : : : : : : : : : : : : : : : : : : : : : 480 F.4 Obsolete General Note FC Zero : : : : : : : : : : : : : : : : : : : : : : : : : : : : 481 F.5 Obsolete Use of Single Parent Associativity : : : : : : : : : : : : : : : : : : : : : : 483 G Untested Entities 485 G.1 Introduction : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 485 G.2 Direction Entity (Type 123) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 487 G.3 Finite Element Entity (Type 136) : : : : : : : : : : : : : : : : : : : : : : : : : : : 488 G.4 Boundary Entity (Type 141) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 491 xx CONTENTS G.5 Bounded Surface Entity (Type 143) : : : : : : : : : : : : : : : : : : : : : : : : : : 495 G.6 Nodal Results Entity (Type 146) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 498 G.7 Element Results Entity (Type 148) : : : : : : : : : : : : : : : : : : : : : : : : : : : 501 G.8 Selected Component Entity (Type 182) : : : : : : : : : : : : : : : : : : : : : : : : 504 G.9 Manifold Solid B-Rep Object Entity (Type 186) : : : : : : : : : : : : : : : : : : : 505 G.10 Plane Surface Entity (Type 190) : : : : : : : : : : : : : : : : : : : : : : : : : : : : 511 G.11 Right Circular Cylindrical Surface Entity (Type 192) : : : : : : : : : : : : : : : : 514 G.12 Right Circular Conical Surface Entity (Type 194) : : : : : : : : : : : : : : : : : : 518 G.13 Spherical Surface Entity (Type 196) : : : : : : : : : : : : : : : : : : : : : : : : : : 521 G.14 Toroidal Surface Entity (Type 198) : : : : : : : : : : : : : : : : : : : : : : : : : : 524 G.15 Curve Dimension Entity (Type 204) : : : : : : : : : : : : : : : : : : : : : : : : : : 527 G.16 Additional General Note FCs : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 529 G.17 New General Note Entity (Type 213) : : : : : : : : : : : : : : : : : : : : : : : : : 531 G.17.1 Field Descriptions : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 531 G.17.2 Control Codes : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 533 G.17.2.1 Control Codes Which Cannot Be Nested : : : : : : : : : : : : : : 533 G.17.2.2 Control Codes Which Can Be Nested : : : : : : : : : : : : : : : : 534 G.18 Linear Dimension Entity (Type 216, Forms 0,1,2) : : : : : : : : : : : : : : : : : : 542 G.19 Ordinate Dimension Entity (Type 218, Form 1) : : : : : : : : : : : : : : : : : : : : 543 G.20 Radius Dimension Entity (Type 222, Form 1) : : : : : : : : : : : : : : : : : : : : : 545 G.21 General Symbol Entity (Type 228, Forms 1,2,3) : : : : : : : : : : : : : : : : : : : 547 G.22 Sectioned Area Entity (Type 230) : : : : : : : : : : : : : : : : : : : : : : : : : : : 550 G.23 Sectioned Area Entity (Type 230, Form 1) : : : : : : : : : : : : : : : : : : : : : : 556 G.24 MACRO Capability : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 559 G.24.1 General : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 559 G.24.2 MACRO Syntax : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 559 G.24.3 MACRO Definition Entity (Type 306) : : : : : : : : : : : : : : : : : : : : : 563 G.24.3.1 Language Statements. : : : : : : : : : : : : : : : : : : : : : : : : : 564 G.24.4 MACRO Instance Entity : : : : : : : : : : : : : : : : : : : : : : : : : : : : 574 G.24.4.1 Examples of MACRO Usage : : : : : : : : : : : : : : : : : : : : : 575 G.25 Units Data Entity (Type 316) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 584 G.26 Segmented Views Visible Associativity : : : : : : : : : : : : : : : : : : : : : : : : : 587 G.27 Piping Flow Associativity : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 589 G.28 Dimensioned Geometry Associativity : : : : : : : : : : : : : : : : : : : : : : : : : 593 xxi CONTENTS G.29 Drawing Entity (Type 404, Form 1) : : : : : : : : : : : : : : : : : : : : : : : : : : 599 G.30 Intercharacter Spacing Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : 601 G.31 Line Font Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 602 G.32 Highlight Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 607 G.33 Pick Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 608 G.34 Uniform Rectangular Grid Property : : : : : : : : : : : : : : : : : : : : : : : : : : 609 G.35 Associativity Group Type Property : : : : : : : : : : : : : : : : : : : : : : : : : : 610 G.36 Level to PWB Layer Map Property : : : : : : : : : : : : : : : : : : : : : : : : : : 612 G.37 PWB Artwork Stackup Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : 615 G.38 PWB Drilled Hole Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 616 G.39 Generic Data Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 618 G.40 Dimension Units Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 620 G.41 Dimension Tolerance Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 622 G.42 Dimension Display Data Property : : : : : : : : : : : : : : : : : : : : : : : : : : : 625 G.43 Basic Dimension Property : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 629 G.44 Perspective View Entity (Type 410, Form 1) : : : : : : : : : : : : : : : : : : : : : 630 G.45 External Reference Entity (Type 416, Form 3) : : : : : : : : : : : : : : : : : : : : 633 G.46 External Reference Entity (Type 416, Form 4) : : : : : : : : : : : : : : : : : : : : 634 G.47 Vertex Entity (Type 502) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 635 G.47.1 Vertex List Entity (Type 502, Form 1) : : : : : : : : : : : : : : : : : : : : 635 G.48 Edge Entity (Type 504) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 637 G.48.1 Edge List Entity (Type 504, Form 1) : : : : : : : : : : : : : : : : : : : : : 637 G.49 Loop Entity (Type 508) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 639 G.50 Face Entity (Type 510) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 641 G.51 Shell Entity (Type 514) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 643 H Parallel Projections from Perspective Views 645 I Deprecated Binary Form 647 I.1 Constants : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 647 I.1.1 Integer Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 647 I.1.2 Real Numbers. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 649 I.1.3 String Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 649 I.1.4 Pointers. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 649 I.1.5 Language Constants. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 649 xxii CONTENTS I.2 File Structure : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 652 I.2.1 Binary Flag Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 652 I.2.2 Start Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 654 I.2.3 Global Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 655 I.2.4 Directory Entry Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : 656 I.2.5 Parameter Data Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : 656 I.2.6 Terminate Section. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 658 J List of References 660 K Glossary 663 L Index of Entities 677 xxiii List of Figures 1 Categories of Product Definition : : : : : : : : : : : : : : : : : : : : : : : : : : : : 3 2 Format of the Start section in the ASCII Form : : : : : : : : : : : : : : : : : : : : 12 3 Format of the Directory Entry (DE) Section in the ASCII Form : : : : : : : : : : 18 4 Format of the Parameter Data (PD) section in the ASCII Form : : : : : : : : : : 27 5 Format of the Terminate section in the ASCII Form : : : : : : : : : : : : : : : : : 28 6 General file structure in the Compressed ASCII Format : : : : : : : : : : : : : : : 30 7 Multiple Transformation Cases : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 34 8 Interpretation of ZT Displacement (Depth) for Annotation Entities : : : : : : : : 42 9 Entity Usage According to System Category. : : : : : : : : : : : : : : : : : : : : : 45 10 Subfigure Structures : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 48 11 General Connectivity Pointer Diagram : : : : : : : : : : : : : : : : : : : : : : : : : 50 12 External Linkages : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 51 13 Finite Element Modeling File Structure : : : : : : : : : : : : : : : : : : : : : : : : 54 14 Finite Element Modeling Logical Structure : : : : : : : : : : : : : : : : : : : : : : 55 15 Examples Defined Using the Circular Arc Entity : : : : : : : : : : : : : : : : : : : 61 16 Parameterization of the Composite Curve : : : : : : : : : : : : : : : : : : : : : : : 64 17 Example Defined Using the Composite Curve Entity : : : : : : : : : : : : : : : : : 66 18 Examples Defined Using the Conic Arc Entity : : : : : : : : : : : : : : : : : : : : 69 19 Examples Defined Using the Centerline Entity : : : : : : : : : : : : : : : : : : : : 78 20 Definition of Patterns for the Section Entity : : : : : : : : : : : : : : : : : : : : : 81 21 Examples Defined Using the Witness Line Entity : : : : : : : : : : : : : : : : : : : 83 22 Examples Defined Using the Plane Entity : : : : : : : : : : : : : : : : : : : : : : : 85 23 Examples Defined Using the Line Entity : : : : : : : : : : : : : : : : : : : : : : : : 89 24 Parameters of the Parametric Spline Curve Entity : : : : : : : : : : : : : : : : : : 91 25 Examples Defined Using the Parametric Spline Curve Entity : : : : : : : : : : : : 91 26 Parameters of the Parametric Spline Surface Entity : : : : : : : : : : : : : : : : : 95 xxiv LIST OF FIGURES 27 Examples Defined Using the Point Entity : : : : : : : : : : : : : : : : : : : : : : : 99 28 Examples Defined Using the Ruled Surface Entity : : : : : : : : : : : : : : : : : : 101 29 Parameters of the Ruled Surface Entity : : : : : : : : : : : : : : : : : : : : : : : : 102 30 Examples Defined Using the Surface of Revolution Entity : : : : : : : : : : : : : : 105 31 Parameters of the Surface of Revolution Entity : : : : : : : : : : : : : : : : : : : : 105 32 Parameters of the Tabulated Cylinder Entity : : : : : : : : : : : : : : : : : : : : : 108 33 Example of the Transformation Matrix Coordinate Systems : : : : : : : : : : : : : 112 34 Notation for FEM-specific Forms of the Transformation Matrix Entity : : : : : : : 117 35 Definition of Shapes for the Flash Entity : : : : : : : : : : : : : : : : : : : : : : : 120 36 Nodal Displacement Coordinate Systems : : : : : : : : : : : : : : : : : : : : : : : 133 37 Finite Element Topology Set : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 137 38 Offset Surface in 3-D Euclidean Space : : : : : : : : : : : : : : : : : : : : : : : : : 153 39 Parameters of the CSG Block Entity : : : : : : : : : : : : : : : : : : : : : : : : : : 164 40 Parameters of the CSG Right Angular Wedge Entity : : : : : : : : : : : : : : : : : 166 41 Parameters of the CSG Right Circular Cylinder Entity : : : : : : : : : : : : : : : 168 42 Parameters of the CSG Right Circular Cone Frustum Entity : : : : : : : : : : : : 170 43 Parameters of the CSG Sphere Entity : : : : : : : : : : : : : : : : : : : : : : : : : 172 44 Parameters of the CSG Torus Entity : : : : : : : : : : : : : : : : : : : : : : : : : : 174 45 Parameters of the CSG Solid of Revolution Entity : : : : : : : : : : : : : : : : : : 177 46 Parameters of the CSG Solid of Linear Extrusion Entity : : : : : : : : : : : : : : : 179 47 Parameters of the CSG Ellipsoid Entity : : : : : : : : : : : : : : : : : : : : : : : : 181 48 Construction of Leaders for the Angular Dimension Entity : : : : : : : : : : : : : 194 49 Examples Defined Using the Angular Dimension Entity : : : : : : : : : : : : : : : 195 50 Examples Defined Using the Diameter Dimension Entity : : : : : : : : : : : : : : 198 51 Parameters of the Flag Note Entity : : : : : : : : : : : : : : : : : : : : : : : : : : 201 52 Examples Defined Using the Flag Note Entity : : : : : : : : : : : : : : : : : : : : 202 53 Examples Defined Using the General Label Entity : : : : : : : : : : : : : : : : : : 204 54 General Note Font Specified by FC 19 : : : : : : : : : : : : : : : : : : : : : : : : : 207 55 General Note Font Specified by FC 1001 : : : : : : : : : : : : : : : : : : : : : : : : 208 56 General Note Font Specified by FC 1002 : : : : : : : : : : : : : : : : : : : : : : : : 209 57 General Note Font Specified by FC 1003 : : : : : : : : : : : : : : : : : : : : : : : : 210 58 Examples Defined Using the General Note Entity : : : : : : : : : : : : : : : : : : 215 59 General Note Text Construction : : : : : : : : : : : : : : : : : : : : : : : : : : : : 216 60 General Note Example of Text Operations : : : : : : : : : : : : : : : : : : : : : : 217 xxv LIST OF FIGURES 61 Examples of Drafting Symbols That Exceed Text Box Height : : : : : : : : : : : : 218 62 Examples Defined Using the Leader Entity : : : : : : : : : : : : : : : : : : : : : : 226 63 Structure of Leaders Internal to a Dimension : : : : : : : : : : : : : : : : : : : : : 227 64 Definition of Arrowhead Types for the Leader (Arrow) Entity : : : : : : : : : : : : 228 65 Examples Defined Using Form 0 of the Linear Dimension Entity : : : : : : : : : : 230 66 Examples Defined Using the Ordinate Dimension Entity : : : : : : : : : : : : : : : 232 67 Examples Defined Using the Point Dimension Entity : : : : : : : : : : : : : : : : : 234 68 Examples Defined Using the Radius Dimension Entity : : : : : : : : : : : : : : : : 236 69 Examples Defined Using the General Symbol Entity : : : : : : : : : : : : : : : : : 238 70 Predefined Fill Patterns for the Sectioned Area Entity : : : : : : : : : : : : : : : : 242 71 Examples of Nested Definition Curves : : : : : : : : : : : : : : : : : : : : : : : : : 243 72 Examples of Illegal Definition Curves : : : : : : : : : : : : : : : : : : : : : : : : : 243 73 Example of Illegal Relationship for Definition Curves : : : : : : : : : : : : : : : : 244 74 Example of Two Ways to Define an Area : : : : : : : : : : : : : : : : : : : : : : : 244 75 Relationships Between Entities in an Associativity : : : : : : : : : : : : : : : : : : 247 76 Line Font Definition Using Form Number 1 (Template Subfigure) : : : : : : : : : 252 77 Line Font Definition Using Form Number 2 (Visible-Blank Pattern) : : : : : : : : 253 78 Example of a Character Definition : : : : : : : : : : : : : : : : : : : : : : : : : : : 258 79 Example of a Character Definition : : : : : : : : : : : : : : : : : : : : : : : : : : : 259 80 Dimensioned Geometry Associativity : : : : : : : : : : : : : : : : : : : : : : : : : 319 81 Using Clipping Planes with a View in a Drawing : : : : : : : : : : : : : : : : : : : 333 82 Parameters of the Drawing Entity : : : : : : : : : : : : : : : : : : : : : : : : : : : 334 83 Measurement of the Line Widening Property Values : : : : : : : : : : : : : : : : : 342 84 Relationship Between Properties Used to Represent a Composite Material : : : : : 357 ___ 85 Use of the Vector D to Define the Element Material Coordinate System : : : : : : 362 86 Internal Load and Strain Sign Convention : : : : : : : : : : : : : : : : : : : : : : : 364 87 Relationship Between Subfigure Definition and Subfigure Instance : : : : : : : : : 398 88 Orthographic Parallel Projection of AB on a View Plane : : : : : : : : : : : : : : 403 89 View Coordinate System : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 403 90 Planes Defining the View Volume : : : : : : : : : : : : : : : : : : : : : : : : : : : 404 91 Relationship Between the Nodal Load/Constraint Entity and Tabular Data Properties413 A1 Electrical Part Example : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 426 A2 Mechanical Part Example : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 429 A3 Drawing and View Example : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 437 xxvi LIST OF FIGURES F1 Obsolete General Note Font specified by FC 0 : : : : : : : : : : : : : : : : : : : : 482 G1 Finite Element Topology Set : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 489 G2 Hierarchical nature of the MSBO : : : : : : : : : : : : : : : : : : : : : : : : : : : : 509 G3 Construction of the MSBO : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 510 G4 Defining data for unparameterized plane surface (Form Number = 0). : : : : : : : 513 G5 Defining data for parameterized plane surface (Form Number = 1). : : : : : : : : 513 G6 Defining data for unparameterized right circular cylindrical surface (Form Number = 0). : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 516 G7 Defining data for parameterized right circular cylindrical surface (Form Number = 1). : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 517 G8 Defining data for unparameterized right circular conical surface (Form Number = 0).520 G9 Defining data for parameterized right circular conical surface (Form Number = 1). 520 G10 Defining data for unparameterized spherical surface (Form Number = 0). : : : : : 523 G11 Defining data for parameterized spherical surface (Form Number = 1). : : : : : : 523 G12 Defining data for unparameterized toroidal surface (Form Number = 0). : : : : : : 526 G13 Defining data for parameterized toroidal surface (Form Number = 1). : : : : : : : 526 G14 Examples Defined Using the Curve Dimension Entity : : : : : : : : : : : : : : : : 528 G15 General Note Font (OCR-B) Specified by FC 19 : : : : : : : : : : : : : : : : : : : 530 G16 Text Containment Area : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 537 G17 Character Height, Inter-line Spacing : : : : : : : : : : : : : : : : : : : : : : : : : : 537 G18 Character Width, Interspace, Box Width : : : : : : : : : : : : : : : : : : : : : : : 538 G19 Examples of Fixed Width Character Interspace : : : : : : : : : : : : : : : : : : : : 538 G20 Rotation, Slant and Character Angle : : : : : : : : : : : : : : : : : : : : : : : : : : 539 G21 Text Containment Area : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 539 G22 Character Height, Width, Interspace, Box Width : : : : : : : : : : : : : : : : : : : 540 G23 Character Height, Width, Interspace, Box Width : : : : : : : : : : : : : : : : : : : 541 G24 Example Defined Using the Ordinate Dimension Entity : : : : : : : : : : : : : : : 544 G25 Example Defined Using the Radius Dimension Entity : : : : : : : : : : : : : : : : 546 G26 Examples of Symbols Defined Using New Form Numbers of the General Symbol Entity : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 549 G27 Predefined Fill Patterns for the Sectioned Area Entity : : : : : : : : : : : : : : : : 551 G28 Examples of Standard and Inverted Crosshatching. : : : : : : : : : : : : : : : : : : 558 G29 Parameters of the Isoceles Triangle Macro in Example 1 in Text : : : : : : : : : : 576 G30 Repeated Parallelograms Created by Macro Example 2 in Text : : : : : : : : : : : 578 G31 Concentric Circles Created by Macro Example 3 in Text : : : : : : : : : : : : : : : 580 xxvii LIST OF FIGURES G32 Ground Symbol Created by Macro Example 4 in Text : : : : : : : : : : : : : : : : 582 G33 Use of DOF with Angular Dimensions. : : : : : : : : : : : : : : : : : : : : : : : : 597 G34 Use of DOF with Linear and Ordinate Dimensions. : : : : : : : : : : : : : : : : : 597 G35 Use of DLF. : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 598 G36 Illustrations of Line Font Patterns for Different Values of LFPC : : : : : : : : : : 604 G37 Examples of tolerance formats (UTOL = 0.01, LTOL = -0.02) : : : : : : : : : : : 624 G38 Placement of Text Using TP and TL. : : : : : : : : : : : : : : : : : : : : : : : : : 628 G39 Definition of a Perspective View : : : : : : : : : : : : : : : : : : : : : : : : : : : : 632 I40 Format of the Control Byte Used in the Binary Form : : : : : : : : : : : : : : : : 648 I41 Format of an Integer Number in the Binary Form : : : : : : : : : : : : : : : : : : 648 I42 Format of a Real Number in the Binary Form : : : : : : : : : : : : : : : : : : : : 650 I43 Structure of a String Constant in the Binary Form : : : : : : : : : : : : : : : : : : 651 I44 General File Structure in the Binary Form : : : : : : : : : : : : : : : : : : : : : : 651 I45 Format of the Binary Flag Section in the Binary Form : : : : : : : : : : : : : : : : 653 I46 Format of the Start Section in the Binary Form : : : : : : : : : : : : : : : : : : : 655 I47 Format of the Global Section in the Binary Form : : : : : : : : : : : : : : : : : : : 655 I48 Format of the Directory Entry (DE) Section in the Binary Form : : : : : : : : : : 657 I49 Format of the Parameter Data (PD) Section in the Binary Form : : : : : : : : : : 658 I50 Format of the Terminate Section in the Binary Form : : : : : : : : : : : : : : : : : 659 xxviii List of Tables 1 Parameters in the Global Section : : : : : : : : : : : : : : : : : : : : : : : : : : : : 13 2 Directory Entry (DE) Section : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 19 3 Examples of Physical Parent-Child Relationships : : : : : : : : : : : : : : : : : : : 35 4 Finite Element Topology Set : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 136 5 Character Names for the Symbol and Drafting Fonts : : : : : : : : : : : : : : : : : 211 6 Electrical Attribute List (ALT=2) : : : : : : : : : : : : : : : : : : : : : : : : : : : 271 7 AEC Attribute List (ALT=3) : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 285 8 Process Plant Attribute list (ALT=4) : : : : : : : : : : : : : : : : : : : : : : : : : 287 9 Electrical and PWA Manufacturing Attribute List (ALT=5) : : : : : : : : : : : : 291 G1 Finite Element Topology Set : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 488 G2 Description of TYPE Numbers for the Nodal and Element Results Entities : : : : 500 xxix 1. General 1.1 Purpose This Specification establishes information structures to be used for the digital representation and communication of product definition data. Use of this Specification permits the compatible ex- change of product definition data used by various Computer-Aided Design and Computer-Aided Manufacturing (CAD/CAM) systems. 1.2 Field of Application This Specification defines a file structure format, a language format, and the representation of geo- metric, topological, and nongeometric product definition data in these formats. Product definition data represented in these formats will be exchanged through a variety of physical media. The specific features and protocols for the communications media are the subject of other standards. The methodology for representing product definition data in this Specification is extensible and independent of the modeling methods used. Chapter 1 is general in nature and defines the overall purpose and objectives of this Specification. Chapter 2 defines the communications file structure and format. It explains the function of each of the sections of a file. Chapter 3 introduces the four classes of entities: curve and surface geometry, constructive solid geometry, annotation, and structure. Chapter 4 describes the details of each individual entity. In Chapter 4, the product is described in terms of geometric and nongeometric information, with nongeometric information being divided into annotation, definition, and organization. The geometry category consists of elements such as points, curves, surfaces, and solids that model the product. The annotation category consists of those elements which are used to clarify or enhance the geometry, including dimensions, drafting notation, and text. The definition category provides the ability to define specific properties or characteristics of individual entities or collections of data entities. The organization category identifies groupings of elements from geometric, annotation, or property data which are to be evaluated and manipulated as single items. 1.3 Conformance to the Specification ECO588 The conformance rules given here are based on three principles. First, conformance is defined in terms of a conforming data file. Second, conformance is defined for a single processor in isolation (i.e., not in terms of interoperability). Third, conformance is defined separately for preprocessor and postprocessor. This section details the minimum conformance criteria for processors. All processors claiming con- formance to this version of the Specification must adhere to the general rules below. In addition, 1 1. GENERAL conforming processors must adhere to the rules appropriate to specific features such as entities. 1.3.1 Conformance rules for data files. A conforming data file shall be syntactically and structurally correct as defined by this (or a previous) version of the Specification. This applies to all sections of the data file. 1.3.2 Conformance rules for preprocessors. A preprocessor which claims conformance to this specification must satisfy the following rule: o A conforming preprocessor shall create conforming data files. 1.3.3 Conformance rules for postprocessors. A postprocessor which claims conformance to this specification must satisfy the following rules: o A conforming postprocessor shall be capable of reading (though not necessarily translating) any conforming data file. o A conforming postprocessor shall not halt or abort because it encounters a conforming data file containing some feature or entity which it was not designed to translate. 1.4 Untested Entities It is the policy of the organization to ensure that entities are tested before being introduced into the Specification. In cases where this testing is not yet complete, the entity is included in Appendix G. A prospective implementor is warned that, despite the fact that Appendix G entities represent the best judgment of the organization, there is a chance that changes will be required before these entities are introduced into the body of the Specification. If these entities are judged useful and implementation is attempted, the results of the attempt will be useful to the IGES/PDES Organization. Contact the IGES/PDES Administration Office at the National Institute of Standards and Technology to report problems and successes. 1.5 Concepts of Product Definition This Specification is concerned with the data required to describe and communicate the essential engineering characteristics of physical objects such as manufactured products. Such products are described in terms of their physical shape, dimensions, and information which further describes or explains the product. The processes which generate or utilize the product definition data typically include design, engineering analysis, production planning, fabrication, material handling, assembly, inspection, marketing, and field service. The requirements for a common data communication format for product definition can be understood in terms of today's CAD/CAM environment. Traditionally, engineering drawings and associated documentation are used to communicate product definition data. Commercial interactive graph- ics systems, originally developed as aids to producing these two-dimensional drawings, are rapidly developing sophisticated three-dimensional solid modeling. In parallel, extensive research work is being conducted in advanced geometric modeling techniques (e.g., parametric representations and solid primitives) and in CAM applications utilizing product definition data in manufacturing (e.g., NC machining and computer-controlled coordinate measurement). The result is rapid growth of 2 1.6 CONCEPTS OF THE FILE STRUCTURE o ADMINISTRATIVE Product Identification Product Structure o DESIGN/ANALYSIS Idealized Models o BASIC SHAPE Geometric Topological o AUGMENTING PHYSICAL CHARACTERISTICS Dimensions and Tolerances Intrinsic Properties o PROCESSING INFORMATION o PRESENTATIONAL INFORMATION Figure 1. Categories of Product Definition CAD/CAM applications, allowing exchange of product definition data, which usually employ in- compatible data representations and formats. In addressing this compatibility problem, this Spec- ification is concerned with needs and capabilities of current and advanced methods of CAD/CAM product definition development. Product definition data may be categorized by their principal roles in defining a product. An example of such a categorization is presented in Figure 1. This Specification specifies communication formats (information structures) for subsets of the product definition. 1.6 Concepts of the File Structure A format to allow the exchange of a product definition between CAD/CAM systems must, as a minimum, support the communication of geometric data, annotation, and organization of the data. The file format defined by this Specification treats the product definition as a file of entities. Each entity is represented in an application-independent format, to and from which the native represen- tation of a specific CAD/CAM system can be mapped. The entity representations provided in this Specification include forms common to the CAD/CAM systems currently available and forms which support the system technologies currently emerging. The fundamental unit of data in the file is the entity. Entities are categorized as geometry and nongeometry. Geometry entities represent the definition of the physical shape and include points, curves, surfaces, solids, and relations which are collections of similarly structured entities. Nonge- ometry entities typically serve to enrich the model by providing a viewing perspective in which a 3 1. GENERAL planar drawing may be composed and by providing annotation and dimensioning appropriate to the drawing. Nongeometry entities further serve to provide specific attributes or characteristics for individual entities or groups of entities and to provide definitions and instances for groupings of entities. The definitions of these groupings may reside in another file. Typical nongeometry entities for drawing definition, annotation, and dimensioning are the view, drawing, general note, witness line, and leader. Typical nongeometry entities for attributes and groupings are the property and the associativity entities. A file consists of five or six sections: Flag (in the case of the binary or compressed ASCII form), Start, Global, Directory Entry, Parameter Data, and Terminate. A file may include any number of entities of any type as required to represent the product definition. Each entity occurrence consists of a directory entry and a parameter data entry. The directory entry provides an index and includes descriptive attributes about the data. The parameter data provides the specific entity definition. The directory data are organized in fixed fields and are consistent for all entities to provide simple access to frequently used descriptive data. The parameter data are entity-specific and are variable in length and format. The directory data and parameter data for all entities in the file are organized into separate sections, with pointers providing bidirectional links between the directory entry and parameter data for each entity. The Specification provides for groupings whose definitions will be found in a file other than the one in which they are used (see Section 3.6.4). Each entity defined by the file structure in Chapter 2 has a specific assigned entity type number. While not all are assigned at this time, entity type numbers 0000 through 0599 and 0700 through 5000 are allocated for specific assignment. Entity type numbers 0600 through 0699 and 10000 ECO532 through 99999 are for implementor-defined (i.e., macro) entities. For implementor-defined entities, see Section 1.7.6. Some entity types include a form number as an attribute. The form number serves to further define or classify an entity within its specific type. The entity set includes a provision for associativities and properties. The Associativity Entity provides a mechanism to establish relationships among entities and to define the meaning of the relationship. The Property Entity allows specific characteristics, such as line widening, to be as- signed to an entity or collection of entities. Each entity format includes a structure for an arbitrary number of pointers to associativities and properties. The file structure provides for both predefined associativities and properties to be included in the Specification and unique definitions which will ECO532 be defined by the implementor. 1.7 Concepts of Information Structures for Geometric Models The geometric model refers to the entity set defined in Chapter 4, and comprises an entity-based product definition file. The entity types, as described above, are categorized as geometry and nongeometry. In general, the geometry entities are defined independently of one another (surfaces are an exception). Features have been provided to define and compose relationships among entities to enhance the model. The nongeometry entities include structures in which an entity may be defined by a collection of other entities and structures which are independent. Several entity types which are used to provide relations or definitions are essential to the file structure methodology of this Specification and are described below. 1.7.1 Property Entity. The Property Entity (Type 406) allows nongeometric numeric or tex- tual information to be related to any entity. Any entity occurrence may reference one or more property entity occurrences as required. In addition, a value which is contained in a property may 4 1.7 CONCEPTS OF INFORMATION STRUCTURES FOR GEOMETRIC MODELS be displayed as text when an additional pointer (See Section 2.2.4.4.2) of the property points to a Text Display Template Entity (Type 312). Property Entities may exist independently of other entities. In this case, the property is defined to be a property of the level indicated in the Level Field of the Directory Entry (DE) of the property. This allows a property to apply to all entities of a given level or for the assignment of an application's function to a level. Because the Level Field in a DE is also allowed to point to a Definition Levels Property Entity (Type 406, Form 1), properties may be applied to multiple levels. 1.7.2 Associativity Entities. The Associativity Entities are designed for use when several en- tities must be logically related to one another. In the case of implementor-defined associativities, two types of entities are involved: Associativity Definition and Associativity Instance. The Asso- ciativity Definition Entity (Type 302) is used to specify the structure of the logical relationship, and the Associativity Instance Entity (Type 402) is used to specify the information involved in a particular occurrence of the relationship. Some associativities are specifically defined as part of this Specification in Section 4.76.1. 1.7.3 View Entity. A drawing or equivalent human-readable representation of the geometric model of a product is a two-dimensional projection of a selected subset of the model, together with nongeometric information such as text. The View Entity (Type 410) and Views Visible Associativity Entities (Type 402, Forms 3 and 4) control such representations. These provide information for orientation, clipping, line removal, and other characteristics associated with individual views rather than with the model itself. 1.7.4 Drawing Entity. The Drawing Entity (Type 404) allows a set of views to be identified and arranged for human presentation. Note that the View and Drawing Entities contain only the rules and parameters for extracting drawings from the geometric model. The actual product definition is not duplicated in various views, eliminating risk of conflicting or ambiguous information. 1.7.5 Transformation Matrix Entity. The Transformation Matrix Entity (Type 124) allows translation and rotation to be applied as needed to any entity in the construction of the model and to the development of views and drawings of the model. 1.7.6 Implementor-Defined Entities. This Specification allows implementors to include enti- ties in their files that are not defined in this document but which have specific implementor meanings. ECO532 This feature supports the objective of the Specification to act as an archiving format where the re- ceiving system is the same as the sending system. In this way, the implementor is able to archive those data forms which may be unique to a particular system. From time to time, files with such implementor-defined entities are used with applications which attempt to edit the file. In this situation, processing problems can arise because, without an entity definition, the editor cannot know which parameter values are pointers that have to be updated, and which are simply data values that should not be updated. This problem can be avoided by using macro definitions and instances of Macro Entities with entity type numbers in the range of 5001 to 9999 inclusively. (See Section G.24 for information on how to use the macro capabilities of the Specification.) This means that for each different implementor- defined entity type, there will be a Macro Definition Entity (Type 306). In order to accomplish the desired result, all that needs to be present in the parameter data for these macro definitions is the 5 1. GENERAL first MACRO statement which defines the parameter list, and an ENDM statement to terminate the definition. 1.8 Appendices As an aid to the implementor/user, a series of appendices is included with this Specification. Ap- pendix A gives three part file examples. Appendix B explains spline representation and approaches for conversion techniques. Appendix C discusses the numerical stability of conic arcs. Appendix D provides mappings between color spaces. Appendix E provides a set of FORTRAN utilities to con- vert physical file structures in the ASCII Form from the regular ASCII Format to the Compressed ASCII Format and back. Appendix F itemizes entities from previous versions which have been made obsolete by this version. Appendix G includes new entities which have not received sufficient implementation testing for inclusion in the main body of the Specification. Appendix H presents ancillary information about perspective views. For reference, Appendix I provides the deprecated binary representation of data. In addition, a List of References, a Glossary, and an Index of Entities are included. 6 2. Data Form 2.1 General An ASCII [ANSI68, ANSI77] form is defined in this Specification to represent data. (A now depre- ECO529 cated Binary Form is described in Appendix I.) ECO531 2.1.1 Defaults. A specific interpretation of an omitted item has been provided in some cases. ECO502 Such defaults tend to reduce the redundancy of the file, but may reduce legibility. Caution should be exercised in generalizing the interpretation of any default beyond that explicitly provided in the Specification. Furthermore, distinctions may be needed among empty fields, blank fields, and a zero field. The appearance of consecutive field delimiters or a field delimiter immediately followed by a record delimiter is an empty field. Notice that empty fields are possible only in free formatted data. The field containing only blanks will be referred to as a blank field. The numeric field with only one digit, where that digit is a zero will be said to have the value 0 and will be called a zero field. A pointer constant represented by any of the three following strings: an empty field; a blank field; or a zero field; requires an explicit interpretation for this single default condition. 2.2 ASCII Form The ASCII Form has two format types: a fixed (80 character) line length format and a compressed format. In the fixed line length ASCII format, the entire file is partitioned into 80 character units beginning with the first character in the file. These units are called lines. The term "column" refers to the character position in a line. The file is divided into sections. The section identification character shall occupy Column 73 of each line. Columns 74 through 80 are specified for the section sequence number of each line. Every line in the file must have a sequence number, i.e., completely blank ECO500 lines are not permitted. For the Compressed ASCII Format, the Directory Entry and Parameter Data Sections are excepted from the above three rules, and will be defined in a later section. The remaining columns are assigned to fields as defined in the file section description. The term "record" refers to the set of parameters for one entity within one file section. A record consists of one or more lines. 2.2.1 Sequence Numbers. A sequence number is a string of from one to seven digits and is the means of indexing lines within the various sections of the data file. The sequence numbers for each section begin with 1 (0000001) and continue sequentially without interruption to the value corresponding to the number of lines in the section. A sequence number may have either leading zeros or leading blanks and is right-justified in its field in the line (Columns 74-80). The sequence number is preceded in the line by a single letter code in Column 73 identifying the section in which the line resides: 7 2.2 ASCII FORM _______________________________________________ |___________Section___________|__Letter_Code__|_ | Flag (not always present) | B or C | | Start | S | | Global | G | | Directory Entry | D | | Parameter Data | P | |__Terminate__________________|_______T________| Letter codes "B" and "C" are used to signify binary (see Appendix I) and compressed ASCII (see Section 2.3.1) information, respectively. 2.2.2 Constants. This Specification defines six types of constants: integer (or fixed point), real (or floating point), string, pointer, language statement, and logical. Regardless of whether the constants appear in a fixed or free format, certain rules apply to their formation, interpretation, and display as text: o Blanks are only significant in string and language statement constants. A numeric field of all ECO502 blanks is considered to denote the default value for that field where a meaning for that default value has been defined in the Specification. No blanks are allowed between the beginning of a numeric constant (i.e., its sign, first numeric digit, or decimal point) and the end of that constant (i.e., the last character position allocated in fixed format or the delimiter character in free format). Leading blanks in the parameters containing numeric constants are ignored. Blanks between the end of any constant and the delimiter following the constant are not allowed. o Numeric constants shall not contain embedded commas. o The absolute magnitude of an integer constant may not exceed the value 2**(N-1)-1, where N is the number of bits used to represent the integer value (Global Parameter 7). Similarly, the absolute magnitude and precision of a real constant may not exceed that indi- cated by Global Parameters 8-9 (for single precision) and 10-11 (for double precision). o Only string and language statement constants may cross field/line boundaries. When such a constant does cross a boundary, it is considered to extend to the last usable column on the current line and then to continue with the first column on the succeeding line. The last usable column on lines in the Parameter Data Section is Column 64; on lines in all other sections it is Column 72. A string constant may not be broken before the Hollerith delimiter (H). o A numeric constant may be either signed or unsigned. If signed, the leading plus or minus determines the sense of the constant. If unsigned, the sense is assumed to be non-negative. 2.2.2.1 Integer Constants. An integer constant (sometimes called a fixed point constant) is always an exact representation of an integer value. It may assume a positive, negative, or zero value. It may assume only an integral value. The form of an integer constant is an optional sign followed by a non-empty string of digits. The digit string is interpreted as a decimal number. The following are examples of valid integer constants (assuming the value of Global Parameter 7 is 32): 8 2.2 ASCII FORM 1 150 2147483647 +3451 0 -10 -2147483647 2.2.2.2 Real Constants. A real constant (sometimes called a floating point constant) is a pro- cessor approximation of the value of a real number. It may assume a positive, negative, or zero value. The following rules and examples apply to real constants as parameter data or as processed for text display. o A real constant may be a basic real constant, a basic real constant followed by an exponent, or an integer constant followed by an exponent. o A real constant may be of either single or double precision. The distinction is in the precision of the processor's representation of the real number which is specified in Global Parameters 8 through 11. A double precision constant may be either a basic real constant followed by a double precision exponent or an integer constant followed by a double precision exponent. o The form of a basic real constant is, in order, an optional sign, an integer part, a decimal point, and a fractional part. Both the integer part and the fractional part are strings of digits; either of these parts may be omitted but not both. A basic real constant is interpreted as a decimal number. o The form of a real exponent is the letter E followed by an optionally signed integer constant. A real exponent denotes a decimal power of ten by which the preceding constant is multiplied. o The form of a double precision exponent is the letter D followed by an optionally signed integer constant. A double precision exponent denotes a decimal power of ten by which the preceding constant is multiplied. The following are examples of valid real constants: 256.091 0. -0.58 +4.21 1.36E1 -1.3E-02 0.1E-3 1.E+4 145.98763D4 -2145.980001D-5 0.123456789D+09 -.43E2 2.2.2.3 String Constants. String constants are represented in the Hollerith form as specified in Appendix C of the current FORTRAN Standard [ANSI78]. A string constant is an arbitrary sequence of ASCII characters. Blanks, parameter delimiters, and record delimiters are treated simply as characters within the string. There is no limit on the length of a string constant. The form of a string constant is a nonzero, unsigned integer constant (character count), followed by the letter H, followed by a string of characters consisting of the number of contiguous characters specified by the character count. No ASCII control characters, i.e., hexadecimal 00 through 1F and ECO531 hexadecimal 7F, may appear in the string of characters. The following are examples of valid string constants: 3H123 10HABC.,;ABCD 8H0.457E03 12H HELLO THERE 9 2.2 ASCII FORM 2.2.2.4 Pointer Constants. A pointer constant is represented by a string of zero to seven ECO502 characters. An empty field, a blank field, and a zero value are all equivalent. However, such null pointers are valid only where the meaning of the null value for that pointer has been specifically provided. Furthermore, a negative integer in the field is valid only where the interpretation of a negative field has been explained. Pointer constants are used to identify a line in either the same or a different section of the data file. The magnitude of the pointer constant corresponds to the sequence number of the referenced line, and the referenced file section is determined by the context of the reference. Pointer constants are unsigned except where they are alternative parameters in a field. Pointer constants whose magnitude requires fewer than seven digits may use leading zeros or leading blanks in fixed format fields. 2.2.2.5 Language Statement Constants. The language statement constant is an arbitrary character string made up of alphanumeric, punctuation, and blank characters from the ASCII char- acter set. The language statement constant is not preceded by the character count and the Hollerith delimiter, H, as is the string constant. Section G.24 defines the syntax of the language statement constant as used for the Macro Entity. The length of the language statement constant is determined by means of the Parameter Data line count in the Directory Entry record for the entity (see Directory Entry Parameter 14). 2.2.2.6 Logical Constants. A logical constant has only two values. These values are specified in the current FORTRAN standard [ANSI78]. In exchange files, where logical constants are expected, the unsigned integer 0 will denote the logical value .FALSE. and the unsigned integer 1 will denote the value .TRUE. . The form of a logical constant is an unsigned integer consisting of a single digit. The digits 2 through 9 may not be used as logical constants. The digit is interpreted as a logical value. 2.2.3 Rules for Forming and Interpreting Free Formatted Data. The data in several sections of a file may be entered in free format. The free format will apply to a range of columns of a line in the section and to the same range of columns of successive lines as needed. This free format feature allows the specification of parameters in the prescribed order without restricting the placement of the parameter to a particular location on a line. When free format is permitted, the following rules apply (in addition to those in Section 2.2.2): o The parameter delimiter (Global Parameter 1_defaulting to a comma) is used to separate parameters. o The record delimiter (Global Parameter 2_defaulting to a semicolon) is used to terminate the record (i.e., to terminate a list of parameters). o When two parameter delimiters, or a parameter and record delimiter, appear adjacent to each other, or are separated by only blanks, the delimited parameter is considered not to have been specified in the file and should be given its default value. Unless specifically noted, the default value for a numeric parameter is zero, and the default value for a string parameter is null ECO540 (see NULL STRING in Appendix K). Pointer constants can be defaulted only when a specific ECO502 definition of the meaning of the default field has been provided in this Specification. It is the responsibility of the preprocessor to ensure that these default values are reasonable for the particular parameter in question. o When a record delimiter appears before the list of parameters is complete, all remaining pa- rameters should be given their default values (see above for a discussion of assigning default 10 2.2 ASCII FORM values). In the case of early termination of a Parameter Data record, either or both groups ECO502 of the additional parameters of Section 2.2.4.4.2 need not be present. This is valid because the pointer count in the parameter preceding the unused pointers has been defaulted to zero. Thus, the unused pointers are not expected. o The end of the data portion of the physical line (i.e., Column 72 in the Global Section, and Column 64 in the Parameter Data Section) is not to be construed to act as either a parameter delimiter or a record delimiter. o The parameter delimiter and record delimiter characters do not maintain their special signifi- cance when included within a string constant. o A numeric constant, including its trailing delimiter, cannot extend across a line boundary. 2.2.3.1 Parameter and Record Delimiter Combinations. The following ASCII characters are prohibited from being used as either Global Parameter 1 (Parameter Delimiter) or Global Pa- rameter 2 (Record Delimiter) because they will cause parsing difficulties in the postprocessor. ______________________________________________ | || Hexadecimal | |__________Name__________|______Range______|__ | The Control Symbols | 0-1F, 7F | | The Space Character | 20 | | The Digits 0 through 9 | 30-39 | | The Characters + - . | 2B, 2D, 2E | |__The_Letters_D_E_H______|__44,_45,_48_______| Only four forms of legitimate syntax are allowed for the first characters of the Global Section defining the two delimiters. They are (where ff and fi represent ASCII characters): _________________________________________________________________ | Form | Interpretation | | |Parameter Delimiter Record Delimiter | |___________________|______Character_____________Character_____|_ | 1. ,, | , ; | | 2. 1Hffff1Hfiff | ff fi | | 3. 1Hffffff | ff ; | |__4._,1Hfi,________|___________,_____________________fi_________ | 2.2.4 File Structure. The file contains six subsections which must appear in order as follows: a. Flag Section (Not always present) b. Start Section c. Global Section d. Directory Entry Section e. Parameter Data Section f. Terminate Section 11 2.2 ASCII FORM These sections are contiguous with no intervening blank lines. The Flag Section of the file is used, ECO500 when present, to indicate that the file is in the Binary Form (see Appendix I) or in the Compressed ASCII Format (see Section 2.3.1). 2.2.4.1 Start Section. The Start Section of the file is designed to provide a human-readable prologue to the file. There must be at least one start record. All records in the section shall have the letter S in Column 73 and a sequence number in Column 74 through 80 (see Section 2.2.1). The information in Columns 1 through 72 need not be formatted in any special way except that the ASCII character set shall be used. An example of a Start Section is shown in Figure 2. 2.2.4.2 Global Section. The Global Section of the file contains the information describing the preprocessor and information needed by the postprocessor to handle the file. All records in the Global Section shall contain the letter G in Column 73 and a sequence number (see Section 2.2.1). The first two global parameters are used to define the parameter delimiter and record delimiter characters if necessary. The default characters are "comma" and "semicolon" respectively. The parameters for the Global Section are input in free format as described in Section 2.2.3. As implied in Section 2.2.3, the global parameters will end with the record delimiter. If the Global Section specifies new delimiter characters, they take over immediately and are used in the Global Section as well as the rest of the file. This is possible because the comma and semicolon delimiter specifications are the first two global parameters. The parameters in the Global Section are described in Table 1 and the paragraphs that follow. Unless explicitly stated, no defaults are provided. |1| 72 |73| 80|| ________________________________________________________________________________________________________ |This section is a human readable prologue to the file. | | | |S0000001 | |It can contain an arbitrary number of lines |S0000002 | | . |S0000003 | | .. | .. | | | . | |using ASCII characters in columns 1-72. |S000000N | | | | Figure 2. Format of the Start section in the ASCII Form 12 2.2 ASCII FORM Table 1. Parameters in the Global Section Index__ Type___ Description___ 1 String Parameter delimiter character (default is comma) 2 String Record delimiter character (default is semicolon) 3 String Product identification from sending system 4 String File name 5 String System ID 6 String Preprocessor version 7 Integer Number of binary bits for integer representation 8 Integer Maximum power of ten representable in a single precision floating point number on the sending system 9 Integer Number of significant digits in a single precision floating point number on the sending system 10 Integer Maximum power of ten representable in a double precision floating point number on the sending system 11 Integer Number of significant digits in a double precision floating point number on the sending system 12 String Product identification for the receiving system 13 Real Model space scale (example: .125 indicates a ratio of 1 unit model space to 8 units real world) 14 Integer Unit flag 15 String Units. 16 Integer Maximum number of line weight gradations (1-32768). Refer to the Directory Entry Parameter 12 (see Section 2.2.4.3.12) for use of this parameter. (Default = 1) ECO544 17 Real Width of maximum line weight in units. Refer to the Directory Entry Parame- ECO545 ter 12 (see Section 2.2.4.3.12) for use of this parameter. 18 String Date & time of exchange file generation 13HYYMMDD.HHNNSS where: ECO565 YY is last 2 digits of year HH is hour (00-23) MM is month (01-12) NN is minute (00-59) DD is day (01-31) SS is second (00-59) 19 Real Minimum user-intended resolution or granularity of the model expressed in units defined by Parameter 15 (example .0001) 20 Real Approximate maximum coordinate value occurring in the model expressed in units defined by Parameter 15. (Example: 1000.0 means for all coordinates |X|; |Y |; |Z| 1000:) 21 String Name of author 22 String Author's organization 23 Integer Integer value corresponding to the version of the Specification used to create this file. 24 Integer Drafting standard in compliance to which the data encoded in this file was generated. 25 String Date and time the model was created or last modified, whichever occurred last, ECO565 13HYYMMDD.HHNNSS (see index 18) 13 2.2 ASCII FORM 2.2.4.2.1 Parameter Delimiter Character. This parameter indicates which character is used to separate parameter values in the Global and Parameter Data sections. Each occurrence of this character denotes the end of the current parameter and the start of the next parameter. Two exceptions exist: (1) string constants in which the delimiter character may be part of the string; (2) language statements in which the delimiter character may be a part of the language syntax. The default value is a comma. See Section 2.2.3. 2.2.4.2.2 Record Delimiter. This parameter indicates which character is used to denote the end of a list of parameters in the Global Section and each Parameter Data Section Entry. Each occurrence of this character denotes the end of the current parameter and of the current parameter list. Two exceptions exist: (1) string constants in which the delimiter character may be part of the string; (2) language statements in which the delimiter character may be a part of the language syntax. The default value is a semicolon. See Section 2.2.3. 2.2.4.2.3 Product Identification From Sender. This is the name or identifier which is used by the sender to reference this product. 2.2.4.2.4 File Name. This is the name of the exchange file. 2.2.4.2.5 System ID. This parameter is an identification code which should uniquely identify the system software which generated this file. It includes the complete vendor's name, the name by which the system is marketed, and the product ID/version number and/or release date of software. 2.2.4.2.6 Preprocessor Version. This parameter identifies the version and/or release date of the preprocessor which created this file. 2.2.4.2.7 Number of Binary Bits for Integer Representation. This parameter indicates how many bits are present in the integer representation of the sending system. This parameter sets limits on the range of values for integer parameters in the file. 2.2.4.2.8 Single Precision Magnitude. This parameter indicates the maximum power of ten which may be represented as a single precision floating point number on the sending system. 2.2.4.2.9 Single Precision Significance. This parameter indicates the number of decimal dig- its of significance which can be accurately represented in the single precision floating point repre- sentation on the sending system. 2.2.4.2.10 Double Precision Magnitude. This parameter indicates the maximum power of ten which may be represented as a double precision floating point number on the sending system. 2.2.4.2.11 Double Precision Significance. This parameter indicates the number of decimal digits of significance which can be accurately represented in the double precision floating point repre- sentation on the sending system. Example: For an IEEE floating point representation (see [IEEE85]) with 32 bits, the magnitude and significance parameters have the values 38 and 6, respectively; for a representation with 64 bits, the values are 308 and 15, respectively. 14 2.2 ASCII FORM 2.2.4.2.12 Product Identification for the Receiver. This is the name or identifier which is intended to be used by the receiver to reference this product. 2.2.4.2.13 Model Space Scale. The ratio of model space to real world space. 2.2.4.2.14 Unit Flag. An integer value denoting the measuring system used in the file. The values in the file are assumed to be: ____________________________________________________ |__Value__|_________Measuring_System__________|_____ | 1 |Inches | | 2 |Millimeters | | 3 |(See Parameter 15 for name of units) | | 4 |Feet | | 5 |Miles | | 6 |Meters | | 7 |Kilometers | | 8 |Mils (i.e., 0.001 inch) | | 9 |Microns | | 10 |Centimeters | |____11____|Microinches____________________________|_ This is the controlling definition of units. A value of 3 should only be used when it is intended to transfer data to a system using the same units, in which case Parameter 15 must be used to provide additional information as to those units. 2.2.4.2.15 Units. A string constant naming the model units in the system: ______________________________________ |_____Constant_____|__Model_Units__|__ | 2HIN or 4HINCH | Inches | | 2HMM | Millimeters | | 2HFT | Feet | | 2HMI | Miles | | 1HM | Meters | | 2HKM | Kilometers | | 3HMIL | Mils | | 2HUM | Microns | | 2HCM | Centimeters | |_______3HUIN_______|__Microinches___|_ When the unit flag is given a value of 3, the string constant naming the desired unit should conform to [MIL12] or [IEEE260]. 2.2.4.2.16 Maximum Number of Line Weight Gradations. This is the number of equal subdivisions of line thickness. The default value is 1. ECO544 2.2.4.2.17 Width of Maximum Line Weight in Units. This is the actual width of the ECO545 thickest line possible in the (scaled) file. 15 2.2 ASCII FORM ECO565 2.2.4.2.18 Date and Time of Exchange File Generation. This is a time stamp indicating when the exchange file was generated. 2.2.4.2.19 Minimum User-Intended Resolution. This parameter indicates the smallest dis- tance in model space units that the system should consider as discernable. Coordinate locations in the file which are less than this distance apart should be considered to be coincident. 2.2.4.2.20 Approximate Maximum Coordinate Value. This is the upper bound on the values of all coordinate data actually occurring in this model. The absolute magnitude of each of the coordinates in this model is less than or equal to this value. 2.2.4.2.21 Name of Author. The name of the person responsible for the creation of the data contained in this file. 2.2.4.2.22 Author's Organization. The organization or group with whom the author is asso- ciated. ECO609 2.2.4.2.23 Version Number. Each version of this Specification is assigned a unique integer value corresponding to that version. This field contains the integer value corresponding to the version of the Specification used to create this file. The values in the table below are valid for this Specification version, and will be added to for each successive version or ANSI Specification. If no valid integer number is entered in this field, the default value of 3 (corresponding to Version 2.0 [NBS83]) should be assumed. See the List of References for a full citation for each version. _______________________________________________________________ |__Value__|___________Version_____________|____Reference____|__ | 1 | 1.0 | [NBS80] | | 2 | ANSI Y14.26M - 1981 | [ANSI81] | | 3 | 2.0 | [NBS83] | | 4 | 3.0 | [NBS86] | | 5 |ASME/ANSI Y14.26M - 1987 | [ASME87] | | 6 | 4.0 | [NBS88] | | 7 | ASME Y14.26M - 1989 | [ASME89] | | 8 | 5.0 | [NIST90] | |____9____|______________5.1________________|This_document__|__ 2.2.4.2.24 Drafting Standard Code. The drafting standard according to which the data in this file was generated. _________________________________________________________________________ |__Code__|____________________Drafting_Standard_____________________|____ | 0 |None No standard specified | | 1 |ISO International Organization for Standardization | | 2 |AFNOR French Association for Standardization | | 3 |ANSI American National Standards Institute | | 4 |BSI British Standards Institute | | 5 |CSA Canadian Standards Association | | 6 |DIN German Institute for Standardization | |____7____|JIS________Japanese_Institute_for_Standardization__________|__ 16 2.2 ASCII FORM 2.2.4.2.25 Date and Time Model was Created/Modified. This is a time stamp indicating ECO565 when the model was created or last modified, whichever occurred last. If this information is not available, then this field should be defaulted by preprocessors. If no valid string is entered, then this field should be ignored by postprocessors. 2.2.4.3 Directory Entry Section. The Directory Entry Section has one directory entry for each entity in the file. The directory entry for each entity is fixed in size and contains twenty fields of eight characters each, spread across two consecutive eighty character lines. Data are right justified in each field. With the exception of the fields numbered 10, 16, 17, 18, and 20, entries in all fields in this section will be either integer constants or pointer constants. In this section, the word "number" is sometimes used in place of the phrase "integer constant." The purposes of the Directory Entry Section are to provide an index for the file and to contain attribute information for each entity. The order of the directory entries within the Directory Entry Section is arbitrary with the exception that a definition entity must precede all of its instances. Within the Directory Entry Section, a field consisting wholly of blanks is to be considered to have not been specified and should be given a default value where possible. Default values are not allowed in Fields 1, 2, 10, 11, 14, and 20. The actual values to be assigned as defaults will vary depending on the entity type. This rule does not apply to compressed ASCII. Some of the fields in the directory entry can contain either an attribute value or a pointer to an entity containing a set of such values. In these fields a positive value indicates an integer constant while for a negative value the absolute value should be taken and the result interpreted as a pointer constant. Since valid files have sequence numbers increasing from one, zero is a valid pointer value only when ECO502 a specific interpretation for a 0 value has been defined for that field in this Specification. In such cases, an empty field or a blank field is equivalent to the zero field. See Section 2.2.4.3.7 for one such instance involving the default instead of a pointer to a Transformation Matrix Entity. Figure 3 gives an abbreviated listing of the fields making up the directory entry for each entity. Table 2 and the following paragraphs describe each directory entry field. Note that Table 2 contains references to entities and form numbers defined in Appendix G. Elsewhere in this specification, figures similar to Figure 3 are used with individual entity definitions.ECO580 The same nomenclature is used, with the following additions and exceptions: o If the field is blank, it is defaulted, and the postprocessor will interpret it as a 0. (Exception: Fields 16, 17, which are undefined, and 18, which is treated as an empty text string.) o Explicit values in fields are the only allowed values, e.g., the Entity Type Number and the Form Number. o The symbol < n:a: > is used to indicated that the field has no meaning for this entity. A preprocessor must set the field to either 0 or blank. A postprocessor will ignore the value altogether. o In the Status Number Field, the following symbols are used: . The symbol (**) has the same meaning as < n:a: >; a preprocessor must set this field to 00. . The symbol (??) means that an appropriate value from the defined range for this field must be used for each instance of the entity. 17 2.2 ASCII FORM .An explicit numeric value (e.g., 00 or 02) is the only value that may be used in the field. The value 00 will often be used in place of ** for clarity, i.e., **??01** and 00??0100 are equivalent. o Footnotes are used to indicate that the values of some fields should be ignored under certain conditions. |1|| 8 9||| 16 17||| 24 |25|| 32|33|| 40 41||| 48 |49|| 56|57|| 64 65||| 72 |73|| 80||| |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | | Entity | Para- |Structure| Line | Level | View |Transfor-| Label | Status |Sequence | | Type | meter | | | | | | Display | | | | | | | Font | | | mation | |Number |Number | |Number | Data | |Pattern | | | Matrix | Assoc. | | | | # | ) | #; ) | #; ) | #; ) | 0; ) | 0; ) | 0; ) | # | D # | | | | | | | | | | | | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | | Entity | | | | | | | Entity | Entity |Sequence | | | Line | Color | Para- | Form |Reserved |Reserved | | | | | Type |Weight |Number | meter |Number | | | Label |Subscript|Number | |Number |Number | | Line | | | | |Number | | | | | | Count | | | | | | | | | | | | | | | | | | | # | # | #; ) | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Nomenclature: (n) - Field number n # - Integer ) - Pointer #; ) - Integer or pointer (pointer has negative sign) 0; ) - Zero or pointer Figure 3. Format of the Directory Entry (DE) Section in the ASCII Form 18 2.2 ASCII FORM Table 2. Directory Entry (DE) Section No.__ Field_Name____ Meaning_and_Notes_______ 1 Entity Type Number Identifies the entity type. 2 Parameter Data Pointer to the first line of the parameter data record for the entity. The letter P is not included. 3 Structure Negated pointer to the directory entry of the definition entity that specifies this entity's meaning. The letter D is not included. The integer values 0, 1, and 2 are permissible in this field but should be disregarded. 4 Line Font Pattern Line font pattern or negated pointer to the directory entry of a Line Font Definition Entity (Type 304). 5 Level Number of the level upon which the entity resides, or a negated pointer to the directory entry of a Definition Levels Property Entity (Type 406, Form 1) which contains a list of levels upon which the entity resides. 6 View Pointer to the directory entry of a View Entity (Type 410), or pointer to a Views Visible Associativity Instance (Type 402, Form 3 or 4), or integer zero (default). 7 Transformation Matrix Pointer to the directory entry of a Transformation Matrix Entity (Type 124) used in defining this entity; zero (de- fault) implies the identity transformation matrix and zero translation vector will be used. 8 Label Display Associativity Pointer to the directory entry of a label Display Associa- tivity (Type 402, Form 5). The value of zero indicates no label display associativity. 9 Status Number Provides four two-digit status values which are entered from left to right in the status number field in the order given below. 1-2 Blank Status 00 Visible 01 Blanked 3-4 Subordinate Entity Switch 00 Independent 01 Physically Dependent 02 Logically Dependent 03 Both (01) and (02) 5-6 Entity Use Flag 00 Geometry 01 Annotation 02 Definition 03 Other 04 Logical/Positional 05 2D Parametric 7-8 Hierarchy 00 Global top down 01 Global defer 02 Use hierarchy property 10 Section Code and Sequence Physical count of this line from the beginning of the Direc- Number tory Entry Section, preceded by the letter D (odd number). 11 Entity Type Number (Same as Field 1.) 19 2.2 ASCII FORM 12 Line Weight Number System display thickness; given as a gradation value in the range of 0 to the maximum (Parameter 16 of the Global Section). 13 Color Number Color number or negated pointer to the directory entry of a Color Definition Entity (Type 314). 14 Parameter Line Count Number of lines in the parameter data record for this en- Number tity. 15 Form Number Certain entities have different interpretations. These in- terpretations are uniquely identified by a form number. Possible form numbers are listed within each entity de- scription. 16 Reserved for future use 17 Reserved for future use 18 Entity Label Up to eight alphanumeric characters (right justified). 19 Entity Subscript Number 1 to 8 digit unsigned number associated with the label. 20 Section Code and Sequence Same meaning as Field 10 (even number). Number ECO580 2.2.4.3.1 Entity Type Number. The integer number indicating the type of entity. This num- ber must agree with the entity type number in the corresponding PD record. 2.2.4.3.2 Parameter Data. This is the sequence number of the first parameter data record for ECO580 this entity. The letter P is not included. This number must be in the range indicated by Field 4 on the Terminate Section (see Section 2.2.4.5). 2.2.4.3.3 Structure. Non-negative integer values are permitted in this field, but should be dis- regarded. (In versions prior to Version 3.0, non-negative integers were used in this field to designate version numbers.) For a negative value, the absolute value of this field is interpreted as a pointer to the structure definition entity which specifies the schema for this entity type number. ECO580 This field has meaning only for the Macro Instance Entity (see Appendix G), the Implementor- Defined Associativity Instance Entity (Type 402, Forms 5001-9999) and the Attribute Table Instance Entity (Type 422, Forms 0 and 1). 2.2.4.3.4 Line Font Pattern. This indicates a display pattern to be used to display a geometric entity. A positive value indicates that the receiving system's corresponding version of the solid, dashed, phantom, centerline, and dotted fonts should be used. A negative value indicates that the absolute value should be interpreted as a pointer to a Line Font Definition Entity (Type 304) which provides the information specifying the display pattern. __________________________________ |__Value__|______Pattern________|_ | 0 |No pattern specified | | 1 | Solid | | 2 | Dashed | | 3 | Phantom | | 4 | Centerline | |____5____|_______Dotted_________|_ 20 2.2 ASCII FORM Additional line font patterns may be assigned by using the Line Font Property Entity (Type 406, ECO530 Form 19) (see Section G.31). 2.2.4.3.5 Level. This value specifies a graphic display level or levels to be associated with this entity. A positive value indicates the graphic level on which this entity exists. A negative value indicates the absolute value is a pointer to a Definitions Level Property Entity (Type 406, Form 1) which contains a list of levels to be associated with the entity. This feature allows an entity to exist on multiple graphic levels. 2.2.4.3.6 View. Three options exist. This value is a pointer to the directory entry of a View Entity (Type 410), a pointer to an Associativity Instance (Type 402, Form 3 or 4, Views Visible), or the integer zero (default). The first option applies when the entity is visible in a single view. The second option applies when the entity is visible in more than one view. (Type 402, Form 4 applies when the display characteristics of the entity are view dependent.) The third option applies when the entity is displayed with the same characteristics in all views. 2.2.4.3.7 Transformation Matrix. This value is either a pointer to the directory entry of a Transformation Matrix Entity (Type 124) or the integer zero (default). Zero implies the identity rotation matrix and zero translation vector will be used. The Transformation Matrix Entity provides form numbers according to the form of the transformation matrix. See Section 4.19. 2.2.4.3.8 Label Display Associativity. This is a pointer to the directory entry of a Label Display Associativity (Type 402, Form 5) which defines how the entity's label and subscript are to be displayed in different views. A zero value indicates no Label Display Associativity is specified. 2.2.4.3.9 Status Number. This value contains four pieces of information which are concate- nated into a single integer number. The four two-digit values are concatenated from left to right in the order given below. 2.2.4.3.9.1 Blank Status. This value defines whether the entity is meant to be visible on the output device of the receiving system. A value of 00 implies the entity is to be displayed and a value of 01 implies the entity is not to be displayed. 2.2.4.3.9.2 Subordinate Entity Switch. This value indicates whether or not the entity is referenced by other entities in the file; and, if so, what type of relationship exists. An entity can be independent, physically dependent, logically dependent, or both physically and logically dependent. The values are defined as follows: 00: Independent. The entity is not referenced (i.e., pointed to) by any other entities in the file. It can exist alone in the native database. 01: Physically Dependent. This entity (the child) is referenced by another entity (the parent) in the file. The child cannot exist unless the parent exists. The matrix pointed to by the entity (as a child) must be applied to the entity's definition in order to determine its location in the parent's definition space (see Section 3.2.3). Entity A is subordinate to entity B if, and only if, the parameter data entry of entity B contains a pointer to entity A. The additional pointers as defined in Section 2.2.4.4.2 are ignored for 21 2.2 ASCII FORM the purposes of this definition. This implies that entities are NOT subordinate to the View (or Views Visible Associativity) Entity that defines the view within which the entity is displayed. The structure formed by a parent entity and its physically subordinate components is indivis- ible and may therefore be considered to form a single entity. The following are examples of physically subordinate entities: o A Leader Line Entity pointed to by a Linear Dimension Entity. o A Circular Arc Entity pointed to by a Plane Entity. o A Circular Arc Entity pointed to by a Composite Curve Entity. o A Composite Curve Entity pointed to by a Subfigure Definition Entity (note that the subfigure definition would NOT point to the constituent entities of the composite curve). Consider the following example: o Entity A is physically subordinate to entity B. o Entity A points to a Transformation Matrix M1. o Transformation Matrix M1 points to a Transformation Matrix M2. o Entity B is subordinate to a Subfigure Definition Entity C. o Entity B points to a Transformation Matrix M3. o Entity C is instanced in a Subfigure Instance D. o The parameter data of entity D specifies its scale factor as Sd and position as (Xd,Yd,Zd). o Entity D points to a Transformation Matrix M4. o Entity D points to a View Entity E. o The view scale factor defined in the parameter data of entity E is Se. o Entity E occurs within a drawing F at drawing coordinates (Fx,Fy). o Entity E points to a Transformation Matrix M5. In order to obtain the drawing space coordinates of entity A, the following operations are performed: 1. The coordinates of entity A are transformed by M1. 2. The coordinates resulting from the preceding step are transformed by M2. 3. The coordinates resulting from the preceding step are transformed by M3. 4. The coordinates resulting from the preceding step are scaled by Sd. 5. The coordinates resulting from the preceding step are transformed by M4. 6. The coordinates resulting from the preceding step are translated by the vector (Xd,Yd,Zd). The coordinates resulting from this step are the model space coordinates of entity A. 22 2.2 ASCII FORM 7. The coordinates resulting from the preceding step are transformed by M5. 8. The coordinates resulting from the preceding step are scaled by the scale factor Se. 9. The coordinates resulting from the preceding step are translated by the vector (Fx,Fy). 02: Logically Dependent. This entity (the child) can exist alone in the native database, but is referenced by some sort of logical grouping entity, or entities (the parents), such as Asso- ciativities. The matrix pointed to by the parent entity has no effect on the location of the child. An example of a logically subordinate entity is that of a Line Entity pointed to by a Group Associativity Entity. 03: Both Physically and Logically Dependent. This entity is physically dependent upon an- other entity in the file and is subject to the physical dependency rules described above. This entity is also referenced by one or more logical grouping entities, and is also subject to the logical dependency rules described above. Additionally, an entity cannot be physically and logically dependent upon the same parent entity. The case of an entity being both logically and physically subordinate refers to the fact that the Transformation Matrix pointed to by a parent entity is not applied to its logically subordinate children. An example of a logically and physically subordinate entity is that of a Line Entity occurring in a subfigure definition and pointed to by a Group Associativity Entity. 2.2.4.3.9.3 Entity Use Flag. This value indicates the intent of the entity. It classifies the entity as intending to serve in the following manners: 00: Geometry. This is the default value. The entity is used to define the geometry of the structure of the product. 01: Annotation. The entity is used to add annotation or description to the file. This includes geometric entities used to form annotation or description. 02: Definition. The entity is used in definition structures of the file. It is not intended to be valid outside of the other entities which reference the definition structure. An example is the entities in a Subfigure Definition which are intended to be valid in the Subfigure Instances that reference the Subfigure Definition. This class includes all entities in the 300 entity type number range. 03: Other. The entity is being used for other purposes such as defining structural features in the file. This category corresponds roughly to the 400 range, but there are exceptions. For example, a Subfigure Instance (Type 408) could define geometry, thus having an entity use flag = 00 or it could define a drawing format, thus having an entity use flag = 01. An Associativity Instance would ordinarily have the value 03. Exceptions include Associativities concerned with display where it would have the value 01. The View and Drawing Entities have value 01 (annotation). Transformation depends on its use: If used only for annotation (e.g., defining a view), the value is 01; if used for defining geometry or for defining geometry and annotation, value is 00. 04: Logical/Positional. The entity is used as a logical and/or positional reference by other enti- ties. This usage does not prevent the entity from referencing other entities or having its own attributes. Some entities which may be instanced in this way are Node, Connect Point, and Point when their primary use is as a reference. 23 2.2 ASCII FORM 05: 2-D Parametric. The entity takes its values in two-dimensional XY parameter space consid- ered as a subset of three dimensional XYZ space by ignoring the Z coordinate. The transfor- mation matrix from definition space to parameter space must be 2-dimensional (i.e., in Entity 124, Section 4.19, T3 = R13 = R31 = R32 = R23 = 0:0 and R33 = 1:0). In addition, the coordinates do not have units of length (i.e., the model space scale and units conversion do not apply). This is intended for use in defining curves on surfaces. 2.2.4.3.9.4 Hierarchy. This value indicates the relationship between entities in a hierarchical structure and is used to determine which entity's directory entry attributes should be applied. It applies to line font, view, entity level, blank status, line weight, and color number. Three values are provided: 00: All the above directory entry attributes will apply to entities physically subordinate to this entity. 01: None of the above directory entry attributes of this entity will apply to physically subordinate entities. The physically subordinate entities will use their own directory entry attributes. 02: Individual setting of each of above direct entry attributes are allowed. A Hierarchy Property Entity (Type 406, Form 10) (see Section 4.78.10) specifies whether 00 or 01 is applied for each directory entry attribute to physically subordinate entities. Example: If an entity A has 00 in its DE status digits 7 and 8, all entities subordinate to A will have the attributes assigned to A. Consequently, the attributes assigned to all entities subordinate to A are ignored. If an entity A has 01 in its DE status digits 7 and 8, the entities immediately subordinate to A will retain their own status. Consequently, the attributes assigned to A are ignored. 2.2.4.3.10 Sequence Number. A number which specifies the position of the DE line in the Directory Entry Section. The sequence number of the first DE line for any entity is always odd and the sequence number of the second line is always even. 2.2.4.3.11 Entity Type Number. This is the same as Field 1. 2.2.4.3.12 Line Weight Number. This value denotes the thickness (or width) with which an entity should be displayed. A specific series of possible thicknesses are specified by Global Parameters 16 and 17. The largest thickness possible is that specified in Global Parameter 17 and is denoted by setting the Line Weight Number equal to the value in Global Parameter 16. The smallest thickness possible is equal to the result of dividing Global Parameter 17 by Global Parameter 16 and is denoted by setting the Line Weight Number equal to 1. Thicknesses between the smallest and largest thickness are available in increments equal to the smallest possible thickness and are denoted by setting the Line Weight Number equal to the integer number of (adjacent) increments required. Thus, display thickness is: Line Weight Number * (Global Parameter 17/Global Parameter 16). A value of 0 indicates that the default line weight display of the receiving system is to be used. 24 2.2 ASCII FORM 2.2.4.3.13 Color Number. Field 13 either is a color number used for specifying color when the precise shade is unimportant or is a pointer to a more precise color definition. It is up to the receiving system to generate colors which approximately fit the following description. _______________________________________ |__Color_No.__|________Color_________|_||| | 0 |No color assigned | | 1 |Black | | 2 |Red | | 3 |Green | | 4 |Blue | || 5 |Yellow| || || 6 |Magenta| || | 7 |Cyan | |_______8_______|White________________|_ If the color number is negative, its absolute value is a pointer to the directory entry of a Color Definition Entity (Type 314). 2.2.4.3.14 Parameter Line Count Number. This is the number of lines in the Parameter Data Section which contain the parameter data record for this entity. This number must be greater ECO580 than zero, except for the Null Entity (Type 0). 2.2.4.3.15 Form Number. This value indicates an individual interpretation of the entity to be used when processing the parameter data for this entity. Some entity types allow multiple interpretations of their parameter data. This parameter along with the entity type number uniquely identify the interpretation of the parameter data. 2.2.4.3.16 Reserved Field. This field is reserved for future use and should be left blank. 2.2.4.3.17 Reserved Field. Same as Field 16. 2.2.4.3.18 Entity Label. This is the application-specified alphanumeric identifier or name for this entity. It is used in conjunction with the entity subscript number (Field 19) to provide the application-specified alphanumeric identifier for the entity. 2.2.4.3.19 Entity Subscript Number. This is a numeric qualifier for the entity label (Field 18). 2.2.4.3.20 Sequence Number. See Section 2.2.4.3.10. 2.2.4.4 Parameter Data Section. The Parameter Data Section of the file contains the param- eter data associated with each entity. The following information is true for all parameter data. 25 2.2 ASCII FORM 2.2.4.4.1 Parameter data are placed in free format (see Section 2.2.3) with the first field always containing the entity type number. Therefore, the entity type number and a parameter delimiter (default is comma) precede parameter one of each entity. The free format part of a parameter line ends in Column 64. Column 65 shall contain a blank. Columns 66 through 72 on all parameter lines contain the sequence number of the first line in the directory entry of the entity for which parameter data is being presented. Column 73 of all lines in the parameter section shall contain the letter P and Columns 74 through 80 shall contain the sequence number (see Section 2.2.1). 2.2.4.4.2 Two groups of parameters are defined at the end of the specified parameters for each entity. The first group of parameters may contain pointers to Associativity Instance, General Note, and/or Text Template Entities. The pointers to associativity instances are "back pointers" in that they point back from a member of an associativity instance to the associativity instance. These pointers may be required by the associativity definition. If the given entity references associated text, a pointer to the General Note (Type 212) may be included in the first group of pointers. If so, the indicated General Note specifies the string constant and the indicated display parameters. If instead, the given entity contains a string constant to be displayed, a pointer to a Text Template Entity (Type 312) may be included in the first group of pointers. The Text Template entities provide display parameters for text supplied by the entity which points to the template. The second group of parameters may contain pointers to one or more properties or attribute tables. Either group of parameters, or both, may be empty or may be defaulted to no pointers. When present, the pointers comprising these parameters are added after all the other specified (or defaulted) parameters, but ahead of the record delimiter as follows: Index__ Name____ Type___ Description___ .. . . . . .. .. .. Let NV = last parameter number NV+1 NA Integer Number of pointers to the DEs of Associativity Instances/Text Entities NV+2 DE1 Pointer Pointer to the DE of the first Associativity Instance/Text Entity .. . . . . .. .. .. NV+NA+1 DENA Pointer Pointer to the DE of the last Associativity Instance/Text Entity NV+NA+2 NP Integer Number of pointers to the DEs of Property or Attribute Table Entities NV+NA+3 DE Pointer Pointer to the DE of the the first Property or Attribute Table Entity .. . . . .. .. NV+NA+NP+2 DENP Pointer Pointer to the DE of the the last Property or Attribute Table Entity 2.2.4.4.3 Any desired comment may be added after the record delimiter. Note that additional lines may be used for this purpose by keeping the directory entry pointer in Columns 65-72 constant and including them in the count of parameter lines for the entity (DE Field 14). Figure 4 shows a Parameter Data Section. 26 2.2 ASCII FORM 1|| 64 ||66|| 72 73|| 80 || |_________________________________________________________________________________||_________|_________|_ |Entity type number followed by parameter delimiter followed by || DE | | |parameters separated by parameter delimiters ||Pointer |P0000001 | |_________________________________________________________________________________||_________|_________|_ |Parameters separated by parameter delimiters || DE | | |followed by record delimiter ||Pointer |P0000002 | |_________________________________________________________________________________||_________|_________|_ | || | | | .. || .. | .. | | . || . | . | | || | | Note: The DE pointer is the sequence number of the first directory entry line for this entity Figure 4. Format of the Parameter Data (PD) section in the ASCII Form 27 2.2 ASCII FORM ECO500 2.2.4.5 Terminate Section. There is only one line in the Terminate Section of the file. It is divided into ten fields of eight columns each. The Terminate Section must be the last line of the file. Note that there may be blank lines or other data after the file to "pad" a physical block or sector. This data is not part of the file. The Terminate Section has a "T" in Column 73 and Columns 74 through 80 contain the sequence number with a value of one (1). ECO518 Each field in the Terminate record contains a section identifier, left-justified in the field, and the last sequence number used in that section, right-justified in the field. The fields are defined in the table below and are shown in Figure 5. Note that leading zeroes are not required in sequence numbers. __________________________________________ |__Field__|Columns__|_______Section______|_ | 1 | 1-8 | Start | | 2 | 9-16 | Global | | 3 | 17-24 | Directory Entry | | 4 | 25-32 | Parameter Data | | 5-9 | 33-72 | (not used) | |___10___|___73-80____|_Terminate________|_ |1| 8 9|| 16 17|| 24 |25| 32|33| 40 41|| 48 |49| 56|57| 64 65|| 72 |73| 80|| ________________________________________________________________________________________________________ | | | | | | | |S0000020 |G0000003 |D0000500 |P0000261 | Not Used |T0000001 | | | | | | | | Figure 5. Format of the Terminate section in the ASCII Form 28 2.3 COMPRESSED ASCII FORMAT 2.3 Compressed ASCII Format The format described here is intended to serve as an alternative to the fixed line-length ASCII Format when the size of a file is a problem. The Compressed ASCII Format is intended to be simply converted to and from the fixed line length ASCII Format. An example of software to perform such conversions is presented in Appendix E. 2.3.1 File Structure. A single Flag Section record shall precede the Start Section and shall ECO517 contain the character "C" in character position 73 to identify the file as being in the Compressed ASCII Format. The Start, Global and Terminate Sections remain the same as those for the regular ASCII Format, while the Directory Entry Section and the Parameter Data Section are combined into a single Data Section. A record in the Data Section contains the data from the entity's Directory Entry record followed immediately by the data from its Parameter Data record. The first line of the Data record begins with the letter "D" followed without intervening blanks by an unsigned integer whose value is that of the sequence number of the corresponding Directory Entry record (see Figure 6). The "D" group of characters is followed by zero or more Directory Entry field specifiers. The field specifier consists of the symbol "@" (commercial at) followed by an unsigned inte- ger identifying the field being specified. The "@" group is followed by the character "_" (underscore) which is in turn followed by the value of the field ("@_"). No delimiter is used between the Directory Entry field specifiers, but the collection of field specifi- cations is terminated by a record delimiter character (default: ";"). The Directory Entry field numbers are the same as those used to identify the Directory Entry fields in the regular ASCII Format. Fields 2, 10, 11, and 20 are not specified because they are either redundant or meaningless in the Compressed ASCII Format. When several Directory Entry fields are being specified additional lines may be used. The sequence of field specifiers may be broken only between complete specifications, thus assuring that new lines will begin with the character "@". The Directory Entry field values need be specified only when they change. Thus a field retains its value from entity to entity unless a new value is explicitly stated. Only the first entity in a file is assured of containing a complete set of field specifications. The Directory Entry portion of the Data Section record is followed immediately by the Parameter Data portion. The data from the Parameter Data record begins on a new line and is the same in the Compressed ASCII Format as it is in the regular ASCII Format. Each line is of variable length, and terminates before character position 65, thus assuring that character position 65, if it existed (i.e., if the line were read into a fixed-length, 80-character buffer), would always contain a blank character. 29 2.3 COMPRESSED ASCII FORMAT |1|| 64 || 72 |73| 80|| |_______________________________________________________________________________________________________ | | |_____________________________________________________________________________________________C_________| | | |Start Section as it appears in the fixed line length ASCII Format S | |_______________________________________________________________________________________________________| |Global Section as it appears in the fixed line length ASCII Format G | |______________________________________________________________________________________________________|_ |D1@1_100 . .a.dditional field descriptions . . . | |__________________________________________________________________________________________| | |. .u.sing as many lines of up to 72 characters each . . . | |______________________________________________________________________________________| |. .a.s needed . . .; | |______________________________________|___________________________________________ |PD record belonging to DE #1 . . . | |__________________________________________________________________________________| | | |._.o.n_lines_of_up_to_64_characters_each_._._.;____|________________________________________ | |D3@ . . .; | |____________________________________________________________________________________________| |PD record belonging to DE #3 . . .; | |____________________________________________________________________|_ .. ._Remaining_Data_Section_entries_._._.___________________________________________________________________ |Terminate|Section_as_it_appears_in_the_fixed_line_length_ASCII_Format________________________T________||_ Note: Default record delimiter assumed Figure 6. General file structure in the Compressed ASCII Format 30 3. Classes of Entities 3.1 General This Chapter contains information pertaining generally to the classes of entities and their structures that occur in the product data exchange file. The four classes of entities defined in this Specification are curve and surface geometry entities, constructive solid geometry entities, annotation entities, and structure entities. Entity type numbers from 100 through 199 are generally reserved for geometry entities. 3.2 Curve and Surface Geometry Entities 3.2.1 Entity Type/Type Numbers. The following curve and surface geometry entities are defined in this Specification: ____________________________________________________________ | Entity | | |__Type_Number__|________________Entity_Type_____________|__ | 100 |Circular Arc | | 102 |Composite Curve | | 104 |Conic Arc | | 106 |Copious Data | | | Linear Path | | | Simple Closed Planar Curve | | 108 |Plane | | 110 |Line | | 112 |Parametric Spline Curve | | 114 |Parametric Spline Surface | | 116 |Point | | 118 |Ruled Surface | | 120 |Surface of Revolution | | 122 |Tabulated Cylinder | | 124 |Transformation Matrix | | 125 |Flash | | 126 |Rational B-Spline Curve | | 128 |Rational B-Spline Surface | | 130 |Offset Curve | | 140 |Offset Surface | | 141 |Boundary (see Appendix G) | | 142 |Curve on a Parametric Surface | | 143 |Bounded Surface (see Appendix G) | |________144________|Trimmed_Parametric_Surface________|____ 31 3.2 CURVE AND SURFACE GEOMETRY ENTITIES 3.2.2 Coordinate Systems. This section introduces a model space concept and a definition space concept. Model space is three-dimensional Euclidean space, the space in which the "model" (or product) being represented resides. The model space X, Y, Z coordinate system is a right-handed Cartesian coordinate system. It is fixed relative to the model. Definition space is also three-dimensional Euclidean space, but has its own right-handed Cartesian XT, YT, ZT coordinate system. In contrast to model space where a single fixed coordinate system exists, the definition space coordinate system may vary from entity to entity. The origin of a definition space coordinate system may be any point in model space, and the orientation may be arbitrary with respect to model space. It is assumed that the unit of length is always the same in both the model space and the definition space coordinate systems. The definition space concept allows the use of a temporary coordinate system in positioning certain geometric entities into model space. This concept plays a simplifying role that is most apparent in connection with those entities which can be contained within a single plane. Use of definition space entails initially describing an entity in definition space, and then converting this to a model space description. Thus, an orthogonal matrix and a translation vector are used to generate model space coordinates from definition space coordinates. The orthogonal matrix used for this purpose is called the defining matrix; both it and the translation vector are treated in the description of the Transformation Matrix Entity (see Section 4.19). The value of the determinant of an orthogonal matrix is always plus or minus one. In the case that the determinant is one, there are two equivalent points of view that can be taken concerning how the geometric entity is related to model space from its definition space description. In order to simplify the discussion that follows, the translation vector is assumed to be the zero vector. This implies that the origin of the definition space coordinate system coincides with the origin in the model space coordinate system. The first point of view imagines that the two coordinate systems are initially coincident (that is, X axis to XT axis, etc.), but that the XT, YT, ZT coordinate frame is free to rotate relative to the X, Y, Z frame. The geometry entity is then considered to be defined relative to the XT, YT, ZT frame, and the defining matrix then rotates this frame, geometry included, so that the geometry entity is positioned as desired relative to the X, Y, Z frame. The second point of view imagines that the XT, YT, ZT frame is initially situated so that the geometry entity within definition space is positioned in the desired manner relative to model space. The defining matrix then leaves the geometry entity fixed, but rotates the XT, YT, ZT frame. At the completion of the rotation, the XT, YT, ZT frame becomes the X, Y, Z frame. The result is that the geometry entity is then positioned as desired relative to the X, Y, Z frame. It is to be emphasized that the discussion here pertains to a single defining matrix whose action in transforming coordinates can be viewed intuitively in two ways. Each point of view stresses the temporary nature of the XT, YT, ZT system, insofar as what is ultimately of interest is the relationship of the geometry entity to the X, Y, Z frame. In a case when the geometry entity to be located within model space can be contained within a single plane, it can be seen that the definition space concept can be used in such a way that the geometry entity as initially described in definition space can be considered to lie in the XT, YT-plane (i.e., the plane ZT=0). From this, it is then convenient to also allow entities to be situated in definition space in any plane parallel to the XT, YT plane (i.e., ZT=arbitrary constant). Each entity is acted upon by a transformation matrix. This implies that each entity makes use of the definition space concept, i.e., is defined initially in definition space, and then transformed into model space. Thus the complete definition of a geometry entity, with respect to model space, involves the Transformation Matrix Entity. However, in some instances, it may very well be that the 32 3.2 CURVE AND SURFACE GEOMETRY ENTITIES transformation matrix will leave all coordinates unchanged. This will be the case exactly when the defining matrix is the identity rotation matrix and the translation vector is the zero vector. (In this situation, a convention is provided to prevent unnecessary processing. See the explanation given in Section 2.2.4.3.7 for Field 7 of the directory entry.) 3.2.3 Multiple Transformation Entities. There are only two cases in which entities can be operated on by multiple transformation entities. The first is the explicit case in which an entity points to a transformation entity through its Directory Entry Field 7, and that transformation entity, in turn, points to an additional transformation entity through its Directory Entry Field 7. This structure is illustrated in Figure 7(a). In the case illustrated by Figure 7(a), the points represented by entity XXX are first operated on ECO519 by matrix 1. The transformed points resulting from application of matrix 1 are then operated on by matrix 2. The other case is an implicit one in which two entities are in a parent/child relationship, and each points to a transformation entity through its respective Directory Entry Field 7. A parent/child relationship occurs when one entity (the parent) is pointing to another entity (the child). This structure is illustrated in Figure 7(b). In the case illustrated by Figure 7(b) the points represented by entity XXX are operated upon by matrix 2 and from that point on are transformed like the points in entity YYY, using matrix 1. A parent/child relationship between entities may also be created with a Single Parent Associativity Instance Entity (Type 402, Form 9). When the specific parent/child relationships shown in Table 3 occur, the implicit relation rule shall apply. Each of the relationships in Table 3 ordinarily results in the subordinate entity switch of the child entity being set to 01 (physically dependent). The exception is the case in which a preprocessor wishes to actually instance the child entity. In this case the child's subordinate entity switch is set to 02 (logically dependent), and the matrix pointed to by the parent has no effect on the location of the child (see Section 2.2.4.3.9.2). 3.2.4 Directionality. Within model space, all curves are directed. Such curves have associated end points; i.e., start point and terminate point. For each entity type, the manner of assigning direction is discussed within the description of each individual entity. Within the entity descriptions that follow, some refer to a "counterclockwise direction" with respect to a sense of rotation in the XT, YT plane. Since the XT, YT plane is located within three dimensional XT, YT, ZT space, this phrase is ambiguous unless a viewing direction is specified from which to view the rotation within the plane. The viewing direction is taken to be from the positive ZT axis looking "down" upon the XT, YT plane. Then, if a clock were imagined to be lying "face up" in the XT, YT plane, i.e., so as to be readable from the chosen viewing direction along the ZT axis - the phrase "counterclockwise direction" refers to the sense of rotation which is opposite the sense of rotation of the hands of the clock. This same notion of the meaning of counterclockwise carries over to any plane that is parallel to the XT, YT plane. 33 3.2 CURVE AND SURFACE GEOMETRY ENTITIES Figure 7. Multiple Transformation Cases 34 3.2 CURVE AND SURFACE GEOMETRY ENTITIES Table 3. Examples of Physical Parent-Child Relationships ____________________________________________________________________________________ |_______________Parent_______________|___________________Child____________________|_||| || Composite Curve |all|constituents || || Plane |bounding|curve || | Point |display symbol | || Ruled Surface |rail|curves || || Flash |defining|entity || || Surface of Revolution |axis,|generatrix || | Tabulated Cylinder |directrix | | Offset Curve |base curve | | Offset Surface |surface | || Trimmed Surface |surface| || | Angular Dimension |all subordinate entities | || Diameter Dimension |all|subordinate entities || | Flag Note |all subordinate entities | | General Label |all subordinate entities | | Linear Dimension |all subordinate entities | | Ordinate Dimension |all subordinate entities | | Point Dimension |all subordinate entities | || Radius Dimension |all|subordinate entities || || General Symbol |all|subordinate entities || || Sectioned Area |all|boundary curves || || Entity Label Display |all|leaders || || Connect Point |display|symbol, Text Display Templates || || Drawing |all|annotation entities || | Subfigure Definition |all associated entities | | Network Subfigure Definition |all associated entities, Text Display Tem- | | |plates and Connect Points | || || || || Nodal Display and Rotation |all|General Notes and Nodes || || Any entity with Entity Use |all|General Notes in text pointer field || |__Flag_=_00_or_01____________________|____________________________________________|_ 35 3.3 CONSTRUCTIVE SOLID GEOMETRY ENTITIES 3.3 Constructive Solid Geometry Entities 3.3.1 Entity Type/Type Numbers. The CSG Primitive Entities are a defined set of solid modeling primitive constructs to be used in all solid modelers_either directly in CSG modelers or in other types of modelers after conversion. CSG primitive entities include the following: _____________________________________________________ | Entity | | |__Type_Number__|____________Entity_Type_________|___ || 150 |Block| || || 152 |Right|Angular Wedge || || 154 |Right|Circular Cylinder || || 156 |Right|Circular Cone Frustum || | 158 |Sphere | | 160 |Torus | | 162 |Solid of Revolution | || 164 |Solid|of Linear Extrusion || |________168________|Ellipsoid_______________________| These primitive entities can be combined into more complex CSG solids using the following entities: _____________________________________________________ | Entity | | |__Type_Number__|____________Entity_Type_________|___ | 180 |Boolean Tree | | 182 |Selected Component (see Ap- | | |pendix G) | || || || | 184 |Solid Assembly | |________430________|Solid_Instance__________________| 3.3.2 Constructive Solid Geometry Models. The Constructive Solid Geometry (CSG) enti- ties support a standard format for one of the two mostly widely used solid model representations_ ECO610 CSG. The CSG entities in this section can be thought of as being one of two types_geometric or struc- tural. The geometric entities are volumetric primitives. These primitives include a block, wedge, cylinder, cone, sphere, torus, ellipsoid, solid of revolution and solid of linear extrusion. The model information for a primitive contains dimensions that define the shape of the primitive, point and vector coordinates that define the local coordinate system of the primitive, and an optional Directory Entry pointer to a transformation matrix which may be used to further position the primitive. If the point and vector coordinates defining the local coordinate system are not given values, the local coordinate system defaults to the global coordinate system. For the Solid of Revolution and Solid of Linear Extrusion Entities, the shape is partly defined indirectly, via a pointer to a planar boundary curve. The structural entities are the Boolean Tree, Solid Instance, and Solid Assembly Entities. The Boolean Tree Entity contains pointers to the elements of the tree, and operations such as union, difference, and intersection to be performed on these elements. Elements may be primitives, other boolean trees or solid instances. There may also be a Directory Entry pointer to a transformation matrix to relocate the entire boolean resultant. 36 3.3 CONSTRUCTIVE SOLID GEOMETRY ENTITIES The Solid Instance Entity contains a pointer to an entity representing a solid and a Directory Entry pointer to a transformation matrix by which the entity is to be transformed. It is a copy of the solid entity relocated in global space. The solid entity may be a primitive, boolean tree, another solid instance, or an assembly. A solid assembly is a collection of items that share a fixed geometric relationship. The relationship is a logical one and is not to be confused with a boolean union. If the faces of different items in an assembly touch, they are not removed, as they would be in a boolean union. The items of an assembly may include primitives, boolean trees, other assemblies, and solid instances. Corresponding to each item pointed to by the assembly is an optional pointer to a transformation matrix to be applied to that item. Thus, each item of the assembly can be moved independently. There is also an optional directory entry pointer to a global transformation matrix to be applied to the entire assembly of items. This global transformation matrix is applied after each of the individual transformation matrices are applied. The description of a solid model is an acyclic directed graph. The nodes in the graph are the various geometric and structural entities. This type of graph is like a tree structure, except that the branches of this graph may reconvene as a move is made down the graph, where down is the general direction from root to terminal node. There may be any number of root nodes, which represent the actual solid models. A root may even be within the branches of another root's graph. The terminal nodes are the primitives_the geometric entities. All the other nodes are structural entities. The structural entities are all able to point to each of the other structural entities as well as to primitives, with one exception. The boolean tree cannot point to an assembly. A CSG solid model is thus represented by appropriately combining geometric entities with structural entities to create a graph structure. 37 3.4 B-REP SOLID ENTITIES 3.4 B-Rep Solid Entities ECO603 3.4.1 Entity Type/Type Numbers. The Boundary Representation (B-Rep) Solid Model En- tities consist of a set of topological entities, a set of surface entities, and a set of curve entities. The following topological entities for B-Rep Solid Models are defined in this Specification: _________________________________________________________________________ | Entity | | |__Type_Number__|______________________Entity_Type___________________|___ | 186 |Manifold Solid B-Rep Object (see Appendix G) | | 502 |Vertex (see Appendix G) | | 504 |Edge (see Appendix G) | | 508 |Loop (see Appendix G) | | 510 |Face (see Appendix G) | |________514________|Shell_(see_Appendix_G)___________________________|__ Only the following surface entities may be used in the construction of B-Rep Solid Models: ___________________________________________________________ | Entity | | |__Type_Number__|_______________Entity_Type____________|___ | 114 |Parametric Spline Surface | | 118/1 |Ruled Surface | | 120 |Surface of Revolution | | 122 |Tabulated Cylinder | | 128 |Rational B-Spline Surface | | 140 |Offset Surface | | 190 |Plane Surface | | 192 |Right Circular Cylindrical Surface | | 194 |Right Circular Conical Surface | | 196 |Spherical Surface | |________198________|Toroidal_Surface____________________|_ Only the following curve entities may be used in the construction of B-Rep Solid Models: _________________________________________________ | Entity | | |__Type_Number__|__________Entity_Type_______|___ | 100 |Circular Arc | | 102 |Composite Curve | | 104 |Conic Arc | | 106/11 |2D Path | | 106/12 |3D Path | | 106/63 |Closed Planar Curve | | 110 |Line | | 112 |Parametric Spline Curve | | 126 |Rational B-Spline Curve | |________130________|Offset_Curve______________|_ 3.4.2 Topology for B-Rep Solid Models. In mechanical CAD systems the role of topology has been traditionally limited to its use in defining Boundary Representation (B-Rep) Solid Models. 38 3.4 B-REP SOLID ENTITIES Constraints have been placed on each topological entity with the intention that they be used in the specific application domain of B-Rep Solid Models. Should another application domain (e.g., AEC or FEM) require different constraints, then new form numbers of these entities should be created which limit the context or the utility of the entities. Each entity has its own set of constraints. A higher level entity (e.g., a loop) may impose constraints on a lower level entity (e.g., an edge). At the higher level, the constraints on the lower level entity are the sum of the constraints imposed by each entity in the chain between the higher and lower level entities. Several topological entities use an Orientation Flag (OF) to indicate whether the direction of a referenced entity agrees with or is opposed to the direction of the referencing entity. If the OF is TRUE then the direction of the referenced entity is correct but if the OF is FALSE then the direction of the referenced entity should be (conceptually) reversed. It can happen that there are several Orientation Flags in the chain of entities from the high level referencing entity to the low level referenced entity. 3.4.3 Analytical Surfaces for B-Rep Solid Models. The entities defined in this set encom- pass those commonly used for describing the surface geometry of B-Rep Solid Models. The surfaces specified here are defined in terms of point, vector and scalar quantities. In general, a point is used to provide positional information and a vector to provide directional information. One or more scalars provide dimensional data. The symbol convention used in the definition of these entities is shown in the following table. ____________Symbols_used_for_analytical_surfaces_____________ |__Symbol__|__Definition____________________________________|_ | a |Scalar quantity | | A | Vector quantity | | <> |Vector normalization | | a |Normalized vector (e.g., a = = A=|A|) | | * |Vector (cross) product | | . |Scalar product | | S(x; y; z) A|nalytic surface | | oe(u; v) P|arametric surface | |_____Sx_____|Partial_derivative_of_S_with_respect_to_x_____|_ 39 3.4 B-REP SOLID ENTITIES 3.4.3.1 Entity Type/Type Numbers. The following analytical surface entities for B-Rep Solid Models are defined in this Specification: ______________________________________________________________________________ | Entity | | |__Type_Number__|_________________________Entity_Type______________________|__ | 123 |Direction (see Appendix G) | | 190 |Plane Surface (see Appendix G) | | 192 |Right Circular Cylindrical Surface (see Appendix G) | | 194 |Right Circular Conical Surface (see Appendix G) | | 196 |Spherical Surface (see Appendix G) | |________198________|Toroidal_Surface_(see_Appendix_G)____________________|___ Note that the Plane Surface Entity (Type 190) may not be used as a clipping plane for a view, and several of these surfaces (plane, cylinder, and cone) are unbounded, i.e., they are infinite surfaces. With the exception of the Plane Surface, these surfaces shall only be used in conjunction with B-Rep Solid Models. 3.4.3.2 Parameterization of Analytical Surfaces. For those systems that use parameterized surfaces, a parameterization is defined for each surface. All the surfaces defined here include a point which forms the origin of a Local Coordinate System (LCS). Two direction vectors are used to complete the definition of the LCS. One is the local Z axis direction and the other is an approximation to the local X axis direction. Let z be the local Z axis direction and a be the approximate local X axis direction. The method for calculating the local X and Y axis directions is the following: o The vector a is projected onto the plane defined by the origin point P and the vector z to give the local X axis direction as x = . The local Y axis direction is then given by y = . 40 3.5 ANNOTATION ENTITIES 3.5 Annotation Entities 3.5.1 Entity Type/Type Number. The following annotation entities are defined in this Spec- ification: ______________________________________________________________ | Entity | | |__Type_Number__|________________Entity_Type______________|___ | 106 |Copious Data | | | Centerline | | | Section | | | Witness Line | | 202 |Angular Dimension | | 204 |Curve Dimension (see Appendix G) | | 206 |Diameter Dimension | | 208 |Flag Note | | 210 |General Label | | 212 |General Note | | 213 |New General Note (see Appendix G) | | 214 |Leader (Arrow) | | 216 |Linear Dimension | | 218 |Ordinate Dimension | | 220 |Point Dimension | | 222 |Radius Dimension | | 228 |General Symbol | |________230________|Sectioned_Area________________________|__ 3.5.2 Construction. Many annotation entities are constructed by using other entities. For example, the dimension entities may have 0, 1, or 2 pointers to Witness Line Entities (a form of Copious Data), 0, 1, or 2 pointers to Leader (Arrow) Entities and a pointer to a General Note Entity. For some annotation entities, a witness line or leader, although allowed, may not exist. For these cases the Parameter Data field pointer value can be set zero. If any constructive entity exists, but its display is suppressed, it can be set to blank status or, if allowed, the pointer value can be set to zero. 3.5.3 Definition Space. An annotation entity may be defined in XT, YT, ZT definition space (see the discussion in Section 3.2.2) or in a two-dimensional space associated with a Drawing Entity (Type 404). In the case of XT, YT, ZT definition space, a transformation matrix is applied to locate the annotation entity within model space. Within the XT, YT, ZT definition space, subordinate entities to an annotation entity may have different ZT displacements. For example, within the Linear Dimension, a different ZT value may be found in each of: General Note, Leader, and Witness Lines (which are pointed to in the Linear Dimension Parameter Data). An example showing the use of ZT displacement (DEPTH) is shown in Figure 8. While the option of having dimensions occupy different planes exists, it is expected that only a single plane will be used. The reason for its existence is due to the structure of annotation entities. As each dimension may comprise several subordinate entities, each subordinate entity by its definition has the ability to stand alone and may require its own ZT displacement; it is likely, though not necessary, that each ZT displacement is identical. 41 3.5 ANNOTATION ENTITIES Figure 8. Interpretation of ZT Displacement (Depth) for Annotation Entities 42 3.5 ANNOTATION ENTITIES 3.5.4 Dimension Attributes 3.5.4.1 General. Most of the dimension entities defined by this specification provide only enough data for the receiving system to restore a visually equivalent representation of the original; additional information (e.g., the geometry being dimensioned) is lost. Dimension attributes enable exchanging this added data to maximize the potential of functionally equivalent entity transfer between systems which support them. Receiving systems lacking CAD entities to contain all attribute data may find some portions useful, or they may ignore the attributes without losing the visual data. CAD system dimensioning capabilities can be grouped into one of three categories: 1. MANUAL - dimensions are constructed using lines, arcs, and text. 2. GENERATIVE - dimensions are generated automatically from selected geometry, but the association with the geometry is not maintained after creation. 3. ASSOCIATIVE - dimensions are generated automatically from selected geometry,and the as- sociation is maintained so that subsequent geometric change will cause a corresponding change in the dimension value; some associative systems with parametric design capabilities also can alter geometry if the dimension value is changed. Usage of dimension attribute entities will directly correspond to the CAD system's category. Cat- egory 1 systems will be unable to send any attributes, and will probably ignore them in received files. Category 2 systems will be able to send and receive the dimension properties: Dimension Units (Type 406, Form 28), Dimension Tolerance (Type 406, Form 29), Dimension Display Data (Type 406, Form 30), and Basic Dimension (Type 406, Form 31). Category 3 systems will be able to send and receive the Dimensioned Geometry Associativity (Type 402, Form 21); this entity groups the dimensioned geometry with the necessary dimension properties. Figure 9 illustrates category usage for a diameter dimension. 3.5.4.2 Usage Rules. Dimension properties may not be independent; they must be logically subordinate to at least one dimension entity; in some cases (e.g., the Dimension Units Property), more than one dimension can reference one property instance. Properties may be used in any combination which is consistent with dimension entity data; thus, the same dimension will never point to both the Dimension Tolerance and Basic Dimension properties because basic dimensions aren't toleranced. Property data must correspond to the data stored in the dimension(s) which reference the property. If the Dimensioned Geometry Associativity is used, the dimension entity and geometry will be logically subordinate to it, and any dimension properties will have logically subordinate status. The Dimensioned Geometry Associativity will always have only physically subordinate status; it will always be referenced only by one dimension entity's backpointer. Refer to Figure 9, category 3. Some systems maintain additional information about dimensions that is of a global nature, and some that is specific to a particular instance of a dimension. Some systems are able to associate a dimension with geometry in such a way that if the geometry is changed, the dimension value is automatically updated to reflect the new values. To support the variety of functionality available for dimensions, several Form Numbers of the Property Entity (Type 406) and a Dimensioned Geometry Associativity (Type 402, Form 21) are provided. All of these properties are optional, but none may exist independently in a file; each instance must be referenced by at least one dimension entity as described in Section 2.2.4.4.2. For example, in the 43 3.5 ANNOTATION ENTITIES case of the Dimension Units Property (Type 406, Form 28), it is possible that one instance of the property is sufficient for all of the dimensions in the drawing, or all Angular Dimensions (Type 202) may reference one instance while all Linear Dimensions (Type 216) reference another instance. A similar situation exists for the Dimension Tolerance Property (Type 406, Form 29). Some of the properties are unique to a particular dimension. For example, the Basic Dimension Property (Type 406, Form 31) contains the coordinates of the corners of a box to be drawn around the dimension text, so an instance of this property may be referenced by only one dimension. The same restriction applies to the Dimension Display Data Property (Type 406, Form 30). There is no restriction on the order in which these properties are referenced; any or all of them may be present in any combination. If present, some contain numeric values that are intended to replace the text string(s) in the General Note Entity (Types 212 and 213) that is referenced by the dimension in its PD section, or they may provide information for the interpretation of the text string(s). Several Form Numbers of the General Note Entity (Type 212) have been provided to indicate dimension types. Specifically, Form Numbers 1, 2, 3, 4, and 5 communicate information about text placement for dual and tolerance dimensions. The dimension attribute properties and the Form Numbers of the General Note should be used in a logically consistent, non-conflicting manner. 44 3.5 ANNOTATION ENTITIES Figure 9. Entity Usage According to System Category. 45 3.6 STRUCTURE ENTITIES 3.6 Structure Entities 3.6.1 Entity Type/Type Number. The following structure entities are defined in this Speci- fication: _____________________________________________________________________________________ | Entity | | |__Type_Number__|____________________________Entity_Type_________________________|___ | 0 |Null | | 132 |Connect Point | | 134 |Node | | 136 |Finite Element | | 138 |Nodal Displacement and Rotation | | 146 |Nodal Results (see Appendix G) | | 148 |Element Results (see Appendix G) | | 302 |Associativity Definition | | 304 |Line Font Definition | | 306 |MACRO Definition (see Appendix G) | | 308 |Subfigure Definition | | 310 |Text Font Definition | | 312 |Text Display Template | | 314 |Color Definition | | 316 |Units Data (see Appendix G) | | 320 |Network Subfigure Definition | | 322 |Attribute Table Definition | | 402 |Associativity Instance | | 404 |Drawing | | 406 |Property | | 408 |Singular Subfigure Instance | | 410 |View | | 412 |Rectangular Array Subfigure Instance | | 414 |Circular Array Subfigure Instance | | 416 |External Reference | | 418 |Nodal Load/Constraint | | 420 |Network Subfigure Instance | | 422 |Attribute Table Instance | | 600-699 |Implementor specified MACRO Instance (see Appendix G) | |____10000-99999____|Implementor_specified_MACRO_Instance_(see_Appendix_G)__|________ The following sections describe some of the uses of the structure entities. 3.6.2 Subfigures. Subfigures have been provided to enable the use of a collection of entities many times within the model at various locations, orientations, and scales. In some cases, the collection itself is specified by a Subfigure Definition Entity (Type 308) and each placement of the collection is specified by a Singular Subfigure Instance Entity (Type 408). The Network Subfigure Definition (Type 320) and Instance (Type 420) Entity pair is similar in concept but has some special features to accommodate the notion of connect point in a network. (Section 3.6.3 provides additional information about network subfigures.) In other cases, a Rectangular Array (Type 412) or a Circular Array (Type 414) Subfigure Instance Entity specifies a base entity to be copied according to one of these two overall patterns. 46 3.6 STRUCTURE ENTITIES Subfigures may be nested. For example, a Subfigure Definition Entity may include a Singular Subfigure Instance Entity as one entity in its collection. The notion of Depth of the Subfigure Definition Entity is used to convey nesting information. Figure 10 illustrates two instances of a Subfigure Definition having a Depth value of N. That Subfigure Definition Entity consists of two geometry entities and one Subfigure Instance Entity. The Subfigure Definition Entity corresponding to this instance entity then has a Depth value of N-1. A similar interpretation of Depth applies also to the Network Subfigure Definition and Instance Entity pair. In these cases, the X,Y,Z location and the scale factor(s) in the Subfigure Instance Entity help locate the Subfigure Definition Entity into the definition space of the referring Subfigure Definition Entity instead of into model space. Thus, the processing sequence in these cases is as follows: Each entity in the Subfigure Definition is operated upon by its defining matrix and translation vector. Each entity is now located within the definition space of the Subfigure Definition Entity. Then, the defining matrix and translation vector of the Subfigure Definition Entity are applied. The entity collection of the Subfigure Definition Entity is now located in the definition space of the Subfigure Instance Entity. Next, the scale factor(s) located in the parameter data of the Subfigure Instance Entity is (are) applied. This results in a scaling about the origin of the definition space of the Subfigure Instance Entity. Next, the defining matrix and translation vector of the Subfigure Instance Entity are applied. This locates the scaled entities either in model space or in the definition space of another Subfigure Definition Entity. Finally, the X,Y,Z translation data located in the parameter data of the Subfigure Instance Entity is applied. Note that this translation data can be relative to either model space or to the definition space of a Subfigure Definition Entity. It will be relative to a definition space exactly when the Subfigure Instance Entity is pointed to by another entity to which it is physically subordinate. 3.6.3 Connectivity. The following file structure shall be used to define logical (and the location for physical) connections between objects. A formed connection between two or more objects requires the data to represent the following: 1. the exact location of each connection point 2. the flow path formed and its identification (if any) 3. the physical connection between the objects (if any). These objects may include electrical or mechanical components such as transistors, pipes and valves, and air conditioning ductwork. Each connection formed defines a flow path between the objects, allowing a fluid (electricity, water, or air) to flow from one object to another. The Network Subfigure (Definition and Instance) Entities are used to represent the objects to be connected. The Connect Point Entity (Type 132) is used to represent the exact location of connection. The term "link" will refer to the logical representation of the flow path (signal) formed, and "flow-name" will refer to the flow path identifier. The term "join" will refer to the file entity or entities which represent the physical connection (geometries between the items). 3.6.3.1 Connectivity Entities. The entities used to implement connectivity include the Net- work Subfigure Definition (Type 320) and Network Subfigure Instance (Type 420) Entities, the Flow Associativity (Type 402, Form 18), the Connect Point Entity (Type 132), and the Text Display Tem- plate (Type 312; absolute = Form 0, incremental = Form 1). 3.6.3.2 Entity Relationships. A flow path (signal) may be formed between items by a link which references the items' connect points (entities) to be related. This creates an associativity 47 3.6 STRUCTURE ENTITIES Figure 10. Subfigure Structures 48 3.6 STRUCTURE ENTITIES among the connect points and thus the entities connected. The flow-name may be used to uniquely identify the particular signal formed. The join may be used to provide a graphical representation of the flow path. In electrical applications the join will be represented by geometric entities such as line, arc, subfigure, copious data, etc. In a piping application, an example of a join represented might be the section of pipe between a valve and a tank. The logical constructs (link and flow-name) shall be implemented by the Flow Associativity Entity which in turn identifies (by pointer) the entities which form the join. In electrical applications, for example, the items to be connected are components (i.e., resistor, 16-pin dual in-line package, etc.), or integrated circuit cells, represented and instanced by Network Subfigures. Each pin (or signal port) is a potential connection point in a flow path, thus each Network Subfigure has a Connect Point for each pin (or port). When such a subfigure is instanced, its connect points must also be instanced. An instanced Connect Point, when added to a flow path, is different from its definition which shall not be a member of any flow path. See Figure 11 for the basic entity relationships. 3.6.3.3 Information Display. The Network Subfigures, representing electrical components for example, often contain text describing the component and its pins. The Text Display Template (Type 312) allows text embedded in another entity to be displayed without redundant specification of the text string. The Text Display Template may be used to display reference designators and pin numbers. The absolute form, within a network subfigure, is recommended for the reference designator text. Each instance of the subfigure need only supply the text string. The pin number can be represented in the incremental form. All the pin numbers on a given side of a package outline having the same X, Y, and Z offsets relative to the pin whose number is to be displayed may use the same Text Display Template definition. 3.6.3.4 Additional Considerations. The situation is exactly the same for both logical and physical product representations. The only differences arise in the subfigure and join entities used. One file may contain both schematic and physical representations of a product. The Flow Associa- tivity Entity (Type 402, Form 18) contains a type flag to indicate the connection type (logical or physical). In this case, one Flow Associativity would represent the logical connection and a second the physical connection. The two associativities would be related by the pointers provided in the Flow Associativity. 3.6.4 External Reference Linkage. Linkages between entities can occur not only within a file, but also between entities in different files. Two entities shall be used in a referencing file to establish this linkage: the External Reference Entity (Type 416) which provides the actual linkage to the referenced file, and the External Reference File List Property Entity (Type 406, Form 12) which provides a list of the names of all the files referenced. Further, only directly referenced files shall be in this property's parameter list. Each file name listed in the parameter data of this property must match the name in the fourth global parameter of a referenced file. An External Reference File Index Associativity (Type 402, Form 12) is required in the referenced file when the Type 416, Form 0 or 2 is used (i.e., more than one referenced entity in the referenced file). This associativity provides a directory to the referenced entities within its file, and both relate a symbolic name to the directory entry of an entity within the file (see Figure 12). All symbolic names used within a set of files linked by references must be unique. Definitions may be nested, and a symbolic name used need be unique only on the nesting level on which it is used. 49 3.6 STRUCTURE ENTITIES Figure 11. General Connectivity Pointer Diagram 50 3.6 STRUCTURE ENTITIES Figure 12. External Linkages 51 3.6 STRUCTURE ENTITIES Because of the intricacy of the linkages, an example follows (refer to Figure 12). Consider a file containing a Subfigure Instance Entity (Type 408). The first item in its parameter data record is a pointer to the subfigure definition entry in the DE Section of the file. In the case that the Subfigure Definition Entity (Type 308) is to be contained in a library file, this first parameter is a pointer to an External Reference Entity (Type 416). That External Reference Entity will have in its parameter data record the name of the file which is to contain the definition and the symbolic name of the definition itself. The file name is the fourth global parameter in the referenced file. The symbolic name is a string which identifies the appropriate referenced definition. In the case of a library file which contains several definitions, each of which are expected to be referenced by other files, the External Reference Associativity (Type 402, Form 12) provides a "table of contents" of the available definitions in the file. The parameter data record of this associativity contains pairs of data: the symbolic name associated with the definition (the same one used in the Type 416 entity's parameter data record), and a pointer to the directory entry record which contains the desired definition. In the case that the entire external file is to be included (i.e., a super-subfigure), Form 1 of the Type 416 entity is used which does not contain a symbolic name in the parameter data record. In a similar manner, the referenced file does not contain an associativity Type 402, Form 12 entity; it is unneeded since the entire file is to be used. In either case, the External Reference File List Property (Type 406, Form 12) will be found in the referencing file. The parameter data record contains a simple list of the file names of the various external files referenced by this file. Once again, the file name used is that in the fourth global parameter of the referenced file. Note that this list contains only those file names that are directly referenced; it gives no information about files which may be referenced in turn by those files used by this file. A limitation of external referencing is that the backpointers (in the "backpointers to associativities" addition to an entity's parameters) cannot be used. If a pointer is required in each direction, separate external reference mechanisms must exist in each file (e.g., the double linkage between files A and B in Figure 12). A preprocessor implementor should use the external reference mechanism with care because of the burden placed on the postprocessor. 3.6.5 Drawings and Views. This Specification provides a mechanism for associating models and drawings so that there is consistency between them. The mechanism is based on the existing practices of some CAD/CAM graphic systems to define the views of a part on a drawing in terms of a single 3-dimensional (3-D) model. The Drawing Entity (Type 404) specifies a drawing of a given size within a special drawing space coordinate system. This entity can refer to one or more View Entities (Type 410) which will specify the projection from 3-D model space to the two-dimensional drawing space. Annotation Entities such as dimensioning can be defined directly in the drawing coordinate system, or can be defined in the 3-D model space and then be included in individual views. More than one drawing entity may be included in a file. In addition to being used in conjunction with the Drawing Entity, the view-specific display of parts of the model can be used to communicate hidden lines, phantom lines, etc. Graphic systems which do not have the ability to define drawing and views of models in this manner are not required to preprocess this construct into a file, but all systems with postprocessors must be able to process the drawing and View Entities in received files. 52 3.6 STRUCTURE ENTITIES 3.6.6 Finite Element Modeling. This section defines the entities and their relationships (point- ers) required to support the Finite Element Modeling (FEM) application and to display results of analysis on those systems which support finite element analysis postprocessing. The entities available for exchanging FEM data are illustrated in Figures 13 and 14. The left side of Figure 13 illustrates the relationships between the entities that define the model's parametric attributes. The right side illustrates the addition of the analysis results. Figure 14 illustrates the FEM entities used to define an example beam structure with accompanying material properties, a load, and a constraint. The entities defined in support of such analysis are the Element Entity (Type 136), Node Entity (Type 134), Load/Constraint Entity (Type 418), Tabular Data Property Entity (Type 406, Form 11), Nodal Results Entity (Type 146) and Element Results Entity (Type 148). The Nodal Results Entity is intended to supercede the Nodal Displacement and Rotation Entity (Type 138). Element (Type 136) defines a finite element to be used in the finite element model. Several finite elements are defined in the specification. Examples of an element are: BEAM, CTRIA, and DAMP. Specifically, the element entity specifies the topology type, number of nodes, and the element type name. Pointers locate the defining nodes and the material properties of the element. The connec- tivity of the nodes is implied in the order of the contained pointers and topology type. Node (Type 134) defines the grid points or nodes of the element. It contains the spatial values that define the node and a pointer to the coordinate system upon which it is defined. Load/Constraint (Type 418) is an entity that points to a node. It defines either a load or a constraint as applied to that node. It also contains a pointer to General Note Entities that define the load case. Property pointers point to the Tabular Data Entity that contains the values of the load or constraint vector. Tabular Data Property Entity (Type 406, Form 11) contains the material property data of the elements and the load/constraint data as required. The Nodal Results Entity is used to communicate nodal finite element analysis results data. It contains analysis results at FEM nodes that are independent of the FEM elements that are attached to them. (The Element Results Entity should be used if the analysis results data are dependent on FEM elements.) It is intended to supercede the old Nodal Displacement and Rotation Entity, as it permits far greater flexibility in the transfer of nodal results. The Element Results Entity is used to communicate FEM element results that vary within a FEM element. The data communicated may be results at various layers within the FEM element: at the FEM element/nodes, at the FEM centroid, at the FEM element gauss points, or any combination of these locations. For example, consider the extrapolated stress values at the nodes of several quadratic, plane-stress FEM elements. There is no guarantee that the nodal values of stress will be identical for adjacent FEM elements at common nodes. There are at least as many possible FEM element result values as there are finite elements that contain common nodes in their topologies. These data are different from the results data expressed at the same node in the Nodal Results Entity. 3.6.7 Attribute Tables. An attribute table (see Sections 4.75 and 4.86) is a collection of at- tribute definitions and values in the form of a single row or table. The structure consists of an Attribute Table Definition Entity (Type 322), where each attribute is defined by a name, a data- type, and a count. The attribute values are either supplied immediately after the attribute definition, or "instanced" via the Attribute Table Instance Entity (Type 422). One or more Attribute Table Instance Entities may point to the Attribute Table Definition Entity using the third field of their Directory Entry. 53 3.6 STRUCTURE ENTITIES Figure 13. Finite Element Modeling File Structure 54 3.6 STRUCTURE ENTITIES Figure 14. Finite Element Modeling Logical Structure 55 3.6 STRUCTURE ENTITIES Three types of Attribute Table Definition Entities and two types of Attribute Table Instance Entities are defined. The Attribute Table Definition Entity can have: (1) attribute definitions only, (2) attribute definitions followed immediately by the attribute values, or (3) attribute definitions followed by attribute values with each value followed by a Text Display Template. The Attribute Table Instance Entity can store: (1) a single row of attribute values, or (2) a table of rows of attribute values, stored in row-major order. 56 4. Entity Types 4.1 General This Chapter defines the entity types available to be used in the entity-based product definition file. Descriptions of the various Directory Entry fields were given in Section 2.2.4.3. The meanings of these fields remain the same across all entities. In this Chapter, those entities making extended use of Field 15 in the Directory Entry (Form Number) are indicated and the various options are listed. The Parameter Data record for each entity is also described in this Chapter. The fields for this record vary from entity to entity. Beginning with Version 4.0 of this Specification, those entities whose testing is not yet complete are included in the Appendix of Untested Entities (Appendix G in this document) rather than here in the body of the Specification (see Section 1.4). 57 4.2 NULL ENTITY (TYPE 0) 4.2 Null Entity (Type 0) ECO583 The Null Entity (Type 0) is intended to be ignored by a processor. It may contain an arbitrary amount of data in its PD data. When encountered by a processor, this entity should be skipped over and not processed. This entity is useful when editing a file. By changing the entity type number of an entity in a file to 0, one ensures that the entity will not be processed. Thus, the replacement of an entity in a file can easily be done by adding the replacement entity to the end of the DE and PD Sections and changing the replaced entity type number to 0. When editing a file to create a Null Entity, care should be taken to change both Entity Type Number Fields in the DE Section, as well as the first field of the first PD line. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 0 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |******** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 0 |< n:a: > |< n:a: > |< n:a: > |< n:a: > | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ 58 4.3 CIRCULAR ARC ENTITY (TYPE 100) 4.3 Circular Arc Entity (Type 100) A circular arc is a connected portion of a parent circle which consists of more than one point. The definition space coordinate system is always chosen so that the circular arc lies in a plane either coincident with or parallel to the XT , Y T plane. A circular arc determines unique arc end points and an arc center point (the center of the parent circle). By considering the arc end points to be enumerated and listed in an ordered manner, start point first, followed by terminate point, a direction with respect to definition space can be associated with the arc. The ordering of the end points corresponds to the ordering necessary for the arc to be traced out in a counterclockwise manner. This convention serves to distinguish the desired circular arc from its complementary arc (complementary with respect to the parent circle). Refer to Section 3.2.4 for information relating to use of the term counterclockwise. The direction of the arc with respect to model space is determined by the original counterclockwise direction of the arc within definition space, in conjunction with the action of the transformation matrix on the arc. In the event that a parameterization is required but not given, the default parameterization is: C(t) = (X1 + R * cos t; Y1 + R * sin t; ZT ) for t2 t t3 where; for i = 2 and 3; q ____________________________ (i) R = (Xi - X1)2 + (Yi - Y1)2 (ii) ti is such that (R * cos ti; R * sin ti) = (Xi - X1; Yi - Y1) and 0 t2 < 2 * ss 0 t3 - t2 2 * ss Examples of the Circular Arc Entity are shown in Figure 15. In Example 2 of Figure 15, the solid arc is defined using point A as the start point and point B as the terminate point. If the complementary dashed arc were desired, the start point listed in the parameter data entry would be B, and the terminate point would be A. 59 4.3 CIRCULAR ARC ENTITY (TYPE 100) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 100 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 100 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 ZT Real Parallel ZT displacement of arc from XT, YT plane 2 X1 Real Arc center abscissa 3 Y1 Real Arc center ordinate 4 X2 Real Start point abscissa 5 Y2 Real Start point ordinate 6 X3 Real Terminate point abscissa 7 Y3 Real Terminate point ordinate Additional pointers as required (see Section 2.2.4.4.2). 60 4.3 CIRCULAR ARC ENTITY (TYPE 100) Figure 15. Examples Defined Using the Circular Arc Entity 61 4.4 COMPOSITE CURVE ENTITY (TYPE 102) 4.4 Composite Curve Entity (Type 102) A composite curve is a continuous curve that results from the grouping of certain individual con- stituent entities into a logical unit. ECO510 A composite curve is defined as an ordered list of entities consisting of point, connect point, and parameterized curve entities (excluding the Composite Curve Entity). The list of entities appears in the parameter data entry. There, each entity to appear in the defining list is indicated by means of a pointer to the directory entry of that entity. The order within the defining list is derived from the order of the listing of these pointers. Each constituent entity has its own transformation matrix and display attributes. Each constituent entity may have text or properties associated with it. Because the constituent entities are subordinate to the composite entity, the Subordinate Entity Switch (digits 3-4 in Directory Entry Field 9) of each constituent entity should indicate a physical dependency. A composite curve is a directed curve, having a start point and a terminate point. The direction of the composite curve is induced by the direction of the constituent curve entities (i.e., those constituent entities other than the point entity) in the following way: The start point for the composite curve is the start point of the first curve entity appearing in the defining list. The terminate point for the composite curve is the terminate point of the last curve entity appearing in the defining list. Within the defining list itself, the terminate point of each constituent curve entity has the same coordinates as the start point of the succeeding curve entity. The Point and Connect Point Entities are included as allowable entity types so that properties or general notes can be attached to either the start point or the terminate point of any constituent curve entities in the defining list. A logical connection relationship can be indicated by having two composite curves or a composite curve and a network subfigure reference the Connect Point Entity. For the special case of the logical connection of a connect point on one subfigure instance to a connect point on another subfigure instance, a composite curve is allowed whose list contains only two Connect Point Entities with no ECO524 intervening curve entity. In this case, the instance of the Composite Curve Entity is not a curve in the normal sense; it is not continuous and has no arc length. This usage is permitted in certain applications (i.e., FEM and AEC). There are certain restrictions regarding the use of the point entity in a composite entity. They are: 1. Two Point or Connect Point Entities cannot appear consecutively in the defining list unless they are the only entities in the composite curve. 2. If a Point or Connect Point Entity and a curve entity are adjacent in the defining list, then the coordinates of the Point or Connect Point Entity must agree with the coordinates of the terminate point of the curve entity whenever the curve entity precedes the Point or Connect Point Entity, and must agree with the coordinates of the start point of the curve entity whenever the curve entity follows the Point or Connect Point Entity. 3. A composite curve cannot consist of a Point Entity alone or a single Connect Point Entity. In the event that a parameterization is required but not given, the default parameterization of the composite curve is obtained from the parameterization of the constituent curves as defined below. As point and connect point entities do not contribute to the parameterization of a composite curve, they are not considered in this definition. 62 4.4 COMPOSITE CURVE ENTITY (TYPE 102) Let C be the composite curve; N be the number of constituent curves (N 1); CC(i) be the i-th constituent curve, for each i such that 1 i N ; P S(i) be the parametric value of the start of CC(i); P E(i) be the parametric value of the end of CC(i); T (0) be 0.0; P i T (i) be j=1(P E(j) - P S(j)), for each i such that 1 i N Then 1. The parametric values of C range from T (0) to T (N ) ; and 2. C(u) = CC(i)(u-T (i-1)+P S(i)) where u is a parametric value such that T (i-1) u T (i). A composite curve consisting solely of Point and/or Connect Point Entities will not be given a parameterization. As an example of a parameterization of a Composite Curve Entity, let N = 3, and for each i such that 1 i 3, let CC(i) be the i-th constituent curve of the composite curve C. Assume the parametric values of the start and end points of each CC(i) are given by the table: _______________________ |__i__|P_S(i)__|P_E(i)_ | | 1 |0.0 | 0.4 | | 2 |3.3 | 3.5 | |__3__|0.0___|__0.3___|_ Then T (0) = 0.0, T (1) = 0.4, T (2) = 0.6, T (3) = 0.9, and the composite curve C is defined from 0.0 to 0.9. This situation is illustrated in Figure 16. The curve combining CC(1), CC(2), and CC(3) represents the composite curve C. An example of a composite curve and its parameterization is shown in Figure 17. 63 4.4 COMPOSITE CURVE ENTITY (TYPE 102) Figure 16. Parameterization of the Composite Curve 64 4.4 COMPOSITE CURVE ENTITY (TYPE 102) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 102 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 102 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of entities 2 DE1 Pointer Pointer to the DE of the first constituent entity .. . . . .. .. 1+N DEN Pointer Pointer to the DE of the last constituent entity Additional pointers as required (see Section 2.2.4.4.2). 65 4.4 COMPOSITE CURVE ENTITY (TYPE 102) Figure 17. Example Defined Using the Composite Curve Entity 66 4.5 CONIC ARC ENTITY (TYPE 104) 4.5 Conic Arc Entity (Type 104) A conic arc is a bounded connected portion of a parent conic curve which consists of more than one point. The parent conic curve is either an ellipse, a parabola, or a hyperbola. The definition space coordinate system is always chosen so that the conic arc lies in a plane either coincident with or parallel to the XT , Y T plane. Within such a plane, a conic is defined by the six coefficients in the following equation. A * XT 2 + B * XT * Y T + C * Y T 2 + D * XT + E * Y T + F = 0 Each coefficient is a real number. The definitions of ellipse, parabola, and hyperbola in terms of these six coefficients are given below. A conic arc determines unique arc endpoints. A conic arc is defined within definition space by the six coefficients above and the two endpoints. By considering the conic arc endpoints to be enumerated and listed in an ordered manner, start point followed by terminate point, a direction with respect to definition space can be associated with the arc. In order for the desired elliptical arc to be distinguished from its complementary elliptical arc, the direction of the desired elliptical arc must be counterclockwise. In the case of a parabola or hyperbola, the parameters given in the parameter data section uniquely define a portion of the parabola or a portion of a branch of the hyperbola; therefore, the concept of a counterclockwise direction is not applied. (Refer to Section 3.2.4 for information concerning use of the term "counterclockwise.") The direction of the conic arc with respect to model space is determined by the original direction of the arc within definition space, in conjunction with the action of the transformation matrix on the arc. The definitions of the terms ellipse, parabola, and hyperbola are given in terms of the quantities Q1, Q2, and Q3. These quantities are: 2 3 A B=2 D=2 Q1 = determinant of 64 B=2 C E=2 75 D=2 E=2 F " # A B=2 Q2 = determinant of B=2 C Q3 = A + C A parent conic curve is: An ellipse if Q2 > 0 and Q1 * Q3 < 0. A hyperbola if Q2 < 0 and Q1 6= 0. A parabola if Q2 = 0 and Q1 6= 0. An example of each type of conic arc is shown in Figure 18. Those entities which can be represented as various degenerate forms of a conic equation (Point and Line) must not be put into the Entity Type 104, more appropriate entity types exist for these forms. 67 4.5 CONIC ARC ENTITY (TYPE 104) Because of the numerical sensitivity of the implicit form of the conic description, a receiving system not using that form as its internal representation for conics need not be expected to correctly process conics in this form unless they are put into a standard position in definition space. A Conic Arc Entity is said to be in a standard position in definition space provided each of its axes is parallel to either the XT axis or Y T axis and provided it is centered about the ZT axis. For a parabola, use the vertex as the origin. The conic is moved from this position in definition space to the desired position in space with a transformation matrix (Entity Type 124). The form number is regarded as purely informational by such a postprocessor. Further details may be found in Appendix C. 68 4.5 CONIC ARC ENTITY (TYPE 104) Figure 18. Examples Defined Using the Conic Arc Entity 69 4.5 CONIC ARC ENTITY (TYPE 104) In the event that a parameterization is required but not given, the default parameterization is: Parabola____ case A and E 6= 0:0 ifX1 < X2 C(t) = (t; -(A=E) * t2; ZT ) for t1 t t2 where; for i = 1 and 2; ti = Xi: ifX2 < X1 C(t) = (-t; -(A=E) * t2; ZT ) for t1 t t2 where; for i = 1 and 2; ti = -Xi: case C and D 6= 0:0 ifY1 < Y2 C(t) = (-(C=D) * t2; t; ZT ) for t1 t t2 where; for i = 1 and 2; ti = Yi: ifY2 < Y1 C(t) = (-(C=D) * t2; -t; ZT ) for t1 t t2 where; for i = 1 and 2; ti = -Yi: Ellipse__ C(t) = (a * cos t; b * sint; ZT ) for t1 t t2 where p ________ a = p -F=A____ b = -F=C and; for i = 1 and 2; ti is such that (i) (a * cos ti; b * sinti; ZT ) = (Xi; Yi; ZT ) (ii) 0 t1 2 * ss (iii) 0 t2 - t1 2 * ss 70 4.5 CONIC ARC ENTITY (TYPE 104) Hyperbola_____ case F * A < 0:0 and F * C > 0:0 let p ________ a = p -F=A__ b = F=C and, for i = 1; 2; ti is such that (i) (a * sec ti; b * tan ti; ZT ) = (Xi; Yi; ZT ) (ii) -ss=2 < t1; t2 < ss=2 if t1 < t2 C(t) = (a * sec t; b * tan t; ZT ) for t1 t t2 if t2 < t1 C(t) = (a * sec(-t); b * tan (-t); ZT ) for - t1 t -t2 case F * A > 0:0 and F * C < 0:0 let p ______ a = p F=A_____ b = -F=C and, for i = 1; 2 ti is such that (i) (a * tan ti; b * sec ti; ZT ) = (Xi; Yi; ZT ) (ii) -ss=2 < t1; t2 < ss=2 if t1 < t2 C(t) = (a * tan t; b * sec t; ZT ) for t1 t t2 if t2 < t1 C(t) = (a * tan (-t); b * sec(-t); ZT ) for - t1 t -t2 71 4.5 CONIC ARC ENTITY (TYPE 104) Field 15 of the directory entry accommodates a form number. For this entity, the options are as follows: __________________________________________________________________________________________ |__Form__|______________________________Meaning__________________________________________|_ | 0 |Form of parent conic curve must be determined from the general equation | | 1 |Parent conic curve is an ellipse (See Figure 18) | | 2 |Parent conic curve is a hyperbola (See Figure 18) | |____3____|Parent_conic_curve_is_a_parabola_(See_Figure_18)_____________________________|_ Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 104 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 104 | # | #; ) | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0-3. Parameter Data Index__ Name____ Type___ Description___ 1 A Real Conic Coefficient 2 B Real Conic Coefficient 3 C Real Conic Coefficient 4 D Real Conic Coefficient 5 E Real Conic Coefficient 6 F Real Conic Coefficient 7 ZT Real ZT Coordinate of plane of definition 8 X1 Real Start Point Abscissa 9 Y1 Real Start Point Ordinate 10 X2 Real Terminate Point Abscissa 11 Y2 Real Terminate Point Ordinate Additional pointers as required (see Section 2.2.4.4.2). 72 4.6 COPIOUS DATA ENTITY (TYPE 106) 4.6 Copious Data Entity (Type 106) This entity stores data points in the form of pairs, triples, or sextuples. An interpretation flag value signifies which of these forms is being used. This value is one of the parameter data entries. The interpretation flag is abbreviated below by the letters IP. Data points within definition space which lie within a single plane are specified in the form of XT, YT coordinate pairs. In this case, the common ZT value is also needed. Data points arbitrarily located within definition space are specified in the form of XT, YT, ZT coordinate triples. Data points within definition space which have an associated vector are specified in the form of sextuples; the XT, YT, ZT coordinates are specified first, followed by the i, j, k coordinates of the vector associated with the point. (Note that, for an associated vector, no special meaning is implicit.) Field 15 of the Directory Entry accommodates a Form Number. For this entity, the options are as follows: ________________________________________________________________________________________________________ |__Form__||__________________________________________Meaning__________________________________________|_ | 1 |Data points in the form of coordinate pairs. All data points lie in a plane ZT= constant. | | |(IP=1) | | | | | 2 |Data points in the form of coordinate triples (IP=2) | | | | | 3 |Data points in the form of sextuples (IP=3) | | | | | 11 |Data points in the form of coordinate pairs which represent the vertices of a planar, | | | | | |piecewise linear curve (piecewise linear string is sometimes used). All data points lie in | | |a plane ZT=constant. (IP=1) | | | | | 12 |Data points in the form of coordinate triples which represent the vertices of a piecewise | | |linear curve (piecewise linear string is sometimes used) (IP=2) | | | | | 13 |Data points in the form of sextuples. The first triple of each sextuple represents the | | | | | |vertices of a piecewise linear curve (piecewise linear string is sometimes used). The | | |second triple is an associated vector. (IP=3) | | | | | 20 |Centerline Entity through points (IP=1) | | | | | 21 |Centerline Entity through circle centers (IP=1) | | | | | 31 |Section Entity Form 31 (IP=1) | | | | | 32 |Section Entity Form 32 (IP=1) | | | | | 33 |Section Entity Form 33 (IP=1) | | | | | 34 |Section Entity Form 34 (IP=1) | | | | | 35 |Section Entity Form 35 (IP=1) | | | | | 36 |Section Entity Form 36 (IP=1) | | | | | 37 |Section Entity Form 37 (IP=1) | | | | | 38 |Section Entity Form 38 (IP=1) | | | | | 40 |Witness Line Entity (IP=1) | | | | | 63 |Simple Closed Planar Curve Entity (IP=1) | |__________|___________________________________________________________________________________________|_ The linear path is an ordered set of points in either 2- or 3-dimensional space. These points define a series of linear segments along the consecutive points of the path. The segments may cross or be coincident with each other. Paths may close, i.e., the first path point may be identical to the last. 73 4.6 COPIOUS DATA ENTITY (TYPE 106) ECO526 The linear path is implemented as three forms of the Copious Data Entity (Type 106). Form 11 is for 2-dimensional paths, Form 12 is for 3-dimensional paths, and Form 63 is for 2-dimensional closed paths. This entity will be closely associated with properties indicating functionality and fabrication parameters, such as Line Widening. ECO501 In the event that a parameterization is required but not given for these linear path form numbers, the default parameterization is as defined below. It is consistent with the 0-1 parameterization of the Line Entity (Type 110) in that it results in local 0-1 parameterizations for each of the line segments of the path. Let C be the composite curve; P (i) be the i-th point in the definition of the path; N be the number of points in the definition of the path. Then 1. The parametric values, u, of C range from 0 to N - 1; and 2. C(u) = P (i + 1) + s * (P (i + 2) - P (i + 1)) where i u i + 1 0 i N - 1 s = u - i. Refer to the Centerline and Witness Line Entities for examples of Form Numbers 20, 21 and 40. Each of these annotation entities contains a description of how the associated copious data are to be interpreted. Forms 31-38 provide for the transfer of graphical information and are defined here for compatibility with previous versions of this Specification. The Sectioned Area Entity (Type 230) provides a more compact method for transferring this information. ECO526 A simple closed planar curve (Form 63) defines the boundary of a region in XY coordinate space. This entity must meet the constraints of a simple closed curve (see Appendix K) that lies in a plane ZT = constant. Parameterization for this entity may be provided; the default parameterization is the same as defined for the planar linear path (Form 11). The simple closed planar curve will be closely related to entities that require the functionality of a closed region. The simple closed planar curve is implemented as Form 63 of the Copious Data Entity (Type 106). 74 4.6 COPIOUS DATA ENTITY (TYPE 106) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 106 | ) |< n:a: > |< n:a: > | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 106 |< n:a: > | #; ) | # | 1-3 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 IP Integer Interpretation Flag 1 = x,y pairs, common z 2 = x,y,z coordinates 3 = x,y,z coordinates and i,j,k vectors 2 N Integer Number of n-tuples For IP=1 (x,y pairs, common z), i.e., for Form 1: 3 ZT Real Common z displacement 4 X1 Real First data point abscissa 5 Y1 Real First data point ordinate .. . . . .. .. 3+2*N YN Real Last data point ordinate For IP=2 (x,y,z triples), i.e., for Form 2: 3 X1 Real First data point x value 4 Y1 Real First data point y value 5 Z1 Real First data point z value .. . . . .. .. 2+3*N ZN Real Last data point z value For IP=3 (x,y,z,i,j,k sextuples), i.e., for Form 3: 3 X1 Real First data point x value 4 Y1 Real First data point y value 5 Z1 Real First data point z value 6 I1 Real First data point i value 7 J1 Real First data point j value 8 K1 Real First data point k value .. . . . .. .. 2+6*N KN Real Last data point k value Additional pointers as required (see Section 2.2.4.4.2). 75 4.6 COPIOUS DATA ENTITY (TYPE 106) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 106 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 106 | # | #; ) | # |11-13, 63 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 IP Integer Interpretation Flag 1 = x,y pairs, common z 2 = x,y,z coordinates 3 = x,y,z coordinates and i,j,k vectors 2 N Integer Number of n-tuples For IP=1 (x,y pairs, common z), i.e., for Forms 11, 63: 3 ZT Real Common z displacement 4 X1 Real First data point abscissa 5 Y1 Real First data point ordinate .. . . . .. .. 3+2*N YN Real Last data point ordinate For IP=2 (x,y,z triples), i.e., for Form 12: 3 X1 Real First data point x value 4 Y1 Real First data point y value 5 Z1 Real First data point z value .. . . . .. .. 2+3*N ZN Real Last data point z value For IP=3 (x,y,z,i,j,k sextuples), i.e., for Form 13: 3 X1 Real First data point x value 4 Y1 Real First data point y value 5 Z1 Real First data point z value 6 I1 Real First data point i value 7 J1 Real First data point j value 8 K1 Real First data point k value .. . . . .. .. 2+6*N KN Real Last data point k value Additional pointers as required (see Section 2.2.4.4.2). 76 4.7 CENTERLINE ENTITY (TYPE 106, FORM 20-21) 4.7 Centerline Entity (Type 106, Form 20-21) The Centerline Entity takes one of two forms. The first, as illustrated in Example 1 of Figure 19 appears as crosshairs and is normally used in conjunction with circles. The second type (Example 2) is a construction between 2 positions. The Centerline entities are defined as Form 20 or 21 of the Copious Data Entity. The associated matrix transforms the XT-YT plane of the centerline into model space. The coordinates of the centerline points describe the centerline display symbol. The display symbol is described by line segments where each line is from (Xn ; Yn ; Zn ) to (Xn+1 ; Yn+1 ; Zn+1 ) where n = 1; 3; 5; :::; N - 1: See Section 4.6 for more information about the Copious Data Entity (Type 106). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 106 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 106 | # | #; ) | # | 20-21 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 IP Integer Interpretation Flag: IP = 1 2 N Integer Number of data points: N is even ECO605 3 ZT Real Common z displacement 4 X1 Real First data point abscissa 5 Y1 Real First data point ordinate .. . . . .. .. 3+2*N YN Real Last data point ordinate Additional pointers as required (see Section 2.2.4.4.2). 77 4.7 CENTERLINE ENTITY (TYPE 106, FORM 20-21) Figure 19. Examples Defined Using the Centerline Entity 78 4.8 SECTION ENTITY (TYPE 106, FORMS 31-38) 4.8 Section Entity (Type 106, Forms 31-38) A Section Entity is defined as a Copious Data Entity (Type 106, Forms 31 to 38). The form number describes how the data are to be interpreted. These descriptions are included for compatibility with previous versions of the Specification. The Sectioned Area Entity (Type 230) provides a more compact method for transferring this information. The point data contains a list of points (Xn , Yn ), n=1, 2, . . ., N, (The Z value is constant and N is an even integer.) The display of the lines consists of solid line segments between the points (Xn ,Yn ,Z) and (Xn+1 ,Yn+1 ,Z) where n = 1,3,5, . . ., N-1. A portion of collinear line segments which appear to be a dashed line shall consist of point pairs for each dash. The defined line patterns are described below and illustrated in Figure 20. _______________________________________________________________________________________________________ |__Form__|______________________________Description_(see_[ANSI79])_______________________________|_____ | 31 |Parallel line segments from section edge to edge (Cast or malleable iron and general use | | |for all materials) | | | | | 32 |Parallel line segments in pairs with a gap between pairs (Steel) | | | | | 33 |Alternating pattern of a solid line and a set of collinear dash segments (Bronze, brass, | | |copper, and compositions) | | | | | 34 |Parallel lines in quadruples with a gap between groups (Rubber, plastic, and electrical | | |insulation) | | | | | 35 |Triples of parallel lines consisting of two solid lines and a set of collinear dash segments| | |between them with a gap between triples (Titanium and refractory material) | | | | | 36 |Parallel sets of collinear dash segments (Marble, slate, glass, porcelain) | | | | | 37 |Two perpendicular sets of parallel lines (White metal, zinc, lead, babbitt, and alloys) | | | | | 38 |Two perpendicular sets of lines with the principal set solid from edge to edge and the | | | | | |second set consisting of collinear dash segments alternating on the solid lines (Magne- | | |sium, aluminum, and aluminum alloys) | |__________|__________________________________________________________________________________________|_ See Section 4.6 for more information about the Copious Data Entity. 79 4.8 SECTION ENTITY (TYPE 106, FORMS 31-38) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 106 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 106 | # | #; ) | # | 31-38 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 IP Integer Interpretation Flag: IP = 1 2 N Integer Number of data points: N is even 3 ZT Real Common z displacement 4 X1 Real First data point abscissa 5 Y1 Real First data point ordinate .. . . . .. .. 3+2*N YN Real Last data point ordinate Additional pointers as required (see Section 2.2.4.4.2). 80 4.8 SECTION ENTITY (TYPE 106, FORMS 31-38) Figure 20. Definition of Patterns for the Section Entity 81 4.9 WITNESS LINE ENTITY (TYPE 106, FORM 40) 4.9 Witness Line Entity (Type 106, Form 40) A Witness Line Entity is a Form Number 40 of a Copious Data Entity that contains one or more straight line segments associated with drafting entities of various types. Each line segment may be visible or invisible. Refer to Figure 21 for examples. Within the copious data, there will be the location from which the witness line gap must be main- tained. This point is indicated in the figure as P1. The location will be the first point in the copious data. P1 will be coincident with the geometry being dimensioned or equal to P2 when the location of the geometry is unknown. (Note: for those annotation methods that do not allow drafting entities to be displaced from the plane of annotation, "coincident with the geometry" indicates that a line normal to the plane of annotation connects P1 and the point on the geometry being dimensioned. Note that all points must be collinear, and that the number of points will be odd and at least 3 (i.e., 3, 5, 7, . .)., with alternating blank and displayed segments. The examples in Figure 21 show the blanking of segments and the order of points stored in the copious data.) See Section 4.6 for more information about the Copious Data Entity (Type 106). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 106 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 106 | # | #; ) | # | 40 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 IP Integer Interpretation Flag: IP = 1 ECO605 2 N Integer Number of data points: N 3 and odd 3 ZT Real Common z displacement 4 X1 Real First data point abscissa 5 Y1 Real First data point ordinate .. . . . .. .. 3+2*N YN Real Last data point ordinate Additional pointers as required (see Section 2.2.4.4.2). 82 4.9 WITNESS LINE ENTITY (TYPE 106, FORM 40) Figure 21. Examples Defined Using the Witness Line Entity 83 4.10 PLANE ENTITY (TYPE 108) 4.10 Plane Entity (Type 108) The plane entity can be used to represent an unbounded plane, as well as a bounded portion of a plane. In either of the above cases, the plane is defined within definition space by means of the coefficients A, B, C, D, where at least one of A, B, and C is nonzero and A * XT + B * Y T + C * ZT = D for each point lying in the plane, and having definition space coordinates (XT; Y T; ZT ). The definition space coordinates of a point, as well as a size parameter, can be specified in order to assist in defining a system-dependent display symbol. These values are parameter data entries six through nine, respectively. This information, together with the four coefficients defining the plane, provides sufficient information relative to definition space in order to be able to position the display symbol. (In the unbounded plane example of Figure 22, the curves and the crosshair together constitute the display symbol.) Setting the size parameter to zero indicates that a display symbol is not intended. ECO591 The case of a bounded portion of a fixed plane requires the existence of a pointer to a closed curve lying in the plane. This is parameter five. The only allowed coincident points for this curve are the start point and the terminate point. The case of an unbounded plane requires this pointer to be zero. ECO590 Use of the Single Parent Associativity has been deprecated (see Appendix F). This functionality should be implemented using the Trimmed (Parametric) Surface Entity (Type 144) or the Bounded Surface Entity (Type 143). Field 15 of the Directory Entry accommodates a form number. For this entity, the options are as follows: ____________________________________________________________________ |__Form__|_______________________Meaning____________________________| | +1 | Bounded planar portion is considered positive. | | |PTR must not be zero. | | | | | 0 |Plane is unbounded. PTR must be zero. | | | | | -1 |Bounded planar portion is considered negative (hole). | | |PTR must not be zero. | |_________|______________________________________________________|__ 84 4.10 PLANE ENTITY (TYPE 108) Figure 22. Examples Defined Using the Plane Entity 85 4.10 PLANE ENTITY (TYPE 108) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 108 | ) |< n:a: > |< n:a: > | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 108 |< n:a: > | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When used as a view clipping plane, Entity Use Flag shall be Annotation (01), and Subor- dinate Entity Switch shall be Physically Dependent (01). Parameter Data Index__ Name____ Type___ Description___ 1 A Real Coefficients of Plane 2 B Real Coefficients of Plane 3 C Real Coefficients of Plane 4 D Real Coefficients of Plane 5 PTR Pointer Must be zero 6 X Real XT coordinate of location point for display symbol 7 Y Real YT coordinate of location point for display symbol 8 Z Real ZT coordinate of location point for display symbol 9 SIZE Real Size parameter for display symbol Additional pointers as required (see Section 2.2.4.4.2). 86 4.10 PLANE ENTITY (TYPE 108) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 108 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 108 | # | #; ) | # |-1 or +1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 A Real Coefficients of Plane 2 B Real Coefficients of Plane 3 C Real Coefficients of Plane 4 D Real Coefficients of Plane 5 PTR Pointer Pointer to the DE of the closed curve entity 6 X Real XT coordinate of location point for display symbol 7 Y Real YT coordinate of location point for display symbol 8 Z Real ZT coordinate of location point for display symbol 9 SIZE Real Size parameter for display symbol Additional pointers as required (see Section 2.2.4.4.2). 87 4.11 LINE ENTITY (TYPE 110) 4.11 Line Entity (Type 110) A line is a bounded, connected portion of a parent straight line which consists of more than one point. A line is defined by its end points. Each end point is specified relative to definition space by triple coordinates. With respect to definition space, a direction is associated with the line by considering the start point to be listed first and the terminate point second. The direction of the line with respect to model space is determined by the original direction of the line within definition space, in conjunction with the action of the transformation matrix on the line. Examples of the line entity are shown in Figure 23. In the event that a parameterization is required, the default parameterization is: C(t) = P1 + t * (P2 - P1) for 0 t 1 Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 110 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 110 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 X1 Real Start Point P 1 2 Y1 Real 3 Z1 Real 4 X2 Real Terminate Point P 2 5 Y2 Real 6 Z2 Real Additional pointers as required (see Section 2.2.4.4.2). 88 4.11 LINE ENTITY (TYPE 110) Figure 23. Examples Defined Using the Line Entity 89 4.12 PARAMETRIC SPLINE CURVE ENTITY (TYPE 112) 4.12 Parametric Spline Curve Entity (Type 112) The parametric spline curve is a sequence of parametric polynomial segments. The CTYPE value in Parameter 1 indicates the type of curve as it was represented in the sending (preprocessing) system before conversion to this entity. The N polynomial segments are delimited by the breakpoints T (1), T (2), ...,T (N + 1). The coor- dinates of the points in the i-th segment of the curve are given by the following cubic polynomials (the coefficients D, or C and D will be zero if the polynomials are of degrees 2 or 1, respectively): X(u) = AX(i) + BX(i) * s + CX(i) * s2 + DX(i) * s3 Y (u) = AY (i) + BY (i) * s + CY (i) * s2 + DY (i) * s3 Z(u) = AZ(i) + BZ(i) * s + CZ(i) * s2 + DZ(i) * s3 where T (i) u T (i + 1); i = 1; :::; N s = u - T (i) In order to avoid degeneracy, for each i at least one of the following nine real coefficients must be ECO557 nonzero: BX(i), CX(i), DX(i), BY (i), CY (i), DY (i), BZ(i), CZ(i), and DZ(i). If the spline is planar, it must be parameterized in terms of the X and Y polynomials only. The coefficient of the Z- polynomial will then be zero except, for each i , the AZ(i) term which indicates the Z-depth in definition space. The parameter H is used as an indicator of the smoothness of the curve. If H=0, the curve is continuous at all breakpoints. If H=1, the curve is continuous and has slope continuity (see Section 6.3 of [FAUX79]) at all breakpoints. If H=2, the curve is continuous and has both slope and curvature continuity at all breakpoints (see Section 6.3 of [FAUX79]). To enable determination of the terminate point and derivatives without computing the polynomials, the N -th polynomials and their derivatives are evaluated at u = T (N + 1). These data are divided by appropriate factorials and stored following the polynomial coefficients. For example, the name TPY3 will be used to designate 1/3! times the third derivative of the Y -polynomial for the N -th segment evaluated at u = T (N + 1) , the parameter value corresponding to the terminate point. Note that these data are redundant as they are derived from the data defining the N -th polynomial segment. Examples of a parametric spline are shown in Figure 24 and Figure 25; see Appendix B for additional mathematical details. 90 4.12 PARAMETRIC SPLINE CURVE ENTITY (TYPE 112) Figure 24. Parameters of the Parametric Spline Curve Entity Figure 25. Examples Defined Using the Parametric Spline Curve Entity 91 4.12 PARAMETRIC SPLINE CURVE ENTITY (TYPE 112) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 112 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 112 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 CTYPE Integer Spline Type: 1=Linear 2=Quadratic 3=Cubic 4=Wilson-Fowler 5=Modified Wilson-Fowler 6=B Spline 2 H Integer Degree of continuity with respect to arc length 3 NDIM Integer Number of dimensions: 2=planar 3=nonplanar 4 N Integer Number of segments 5 T(1) Real First break point of piecewise polynomial .. . . . .. .. 5+N T(N+1) Real Last break point of piecewise polynomial 6+N AX(1) Real X coordinate polynomial 7+N BX(1) Real 8+N CX(1) Real 9+N DX(1) Real 10+N AY(1) Real Y coordinate polynomial 11+N BY(1) Real 12+N CY(1) Real 13+N DY(1) Real 14+N AZ(1) Real Z coordinate polynomial 15+N BZ(1) Real 16+N CZ(1) Real 17+N DZ(1) Real .. . . . .. .. Subsequent X, Y, Z polynomials concluding with the twelve coefficients of the Nth polynomial segment. The parameters that follow comprise the evaluations of the polynomials of the N -th segment and their derivatives at the parameter value u = T (N + 1) corresponding to the terminate point. Sub- sequently, these evaluations are divided by appropriate factorials. 6+13*N TPX0 Real X value 7+13*N TPX1 Real X first derivative 92 4.12 PARAMETRIC SPLINE CURVE ENTITY (TYPE 112) 8+13*N TPX2 Real X second derivative/2! 9+13*N TPX3 Real X third derivative/3! 10+13*N TPY0 Real Y value 11+13*N TPY1 Real Y first derivative 12+13*N TPY2 Real Y second derivative/2! 13+13*N TPY3 Real Y third derivative/3! 14+13*N TPZ0 Real Z value 15+13*N TPZ1 Real Z first derivative 16+13*N TPZ2 Real Z second derivative/2! 17+13*N TPZ3 Real Z third derivative/3! ECO605 Additional pointers as required (see Section 2.2.4.4.2). 93 4.13 PARAMETRIC SPLINE SURFACE ENTITY (TYPE 114) 4.13 Parametric Spline Surface Entity (Type 114) The parametric spline surface is a grid of parametric polynomial patches. PTYPE in the Parameter Data Section indicates the type of patch under consideration. The M x N grid of patches is defined by the u breakpoints T U (1), . . ., T U (M + 1) and the v breakpoints T V (1), . .,.T V (N + 1). The coordinates of the points in each of the patches are given by the general bicubic polynomials (given here for the (i, j ) patch). X(u; v) = AX(i; j) + BX(i; j) * s + CX(i; j) * s2 + DX(i; j) * s3 + EX(i; j) * t + F X(i; j) * t * s + GX(i; j) * t * s2 + HX(i; j) * t * s3 + KX(i; j) * t2 + LX(i; j) * t2 * s + M X(i; j) * t2 * s2 + N X(i; j) * t2 * s3 + P X(i; j) * t3 + QX(i; j) * t3 * s + RX(i; j) * t3 * s2 + SX(i; j) * t3 * s3 Y (u; v) = ::: Z(u; v) = ::: where T U (i) u T U (i + 1); i = 1; :::; M s = u - T U (i) and T V (j) v T V (j + 1); j = 1; :::; N t = v - T V (j) Postprocessors shall ignore parameters with the indices 7+M+N+48*(k*N+(k-1)) through 6+M+N+48* (k*(N+1)), where k=1,2,3,...,M (i.e., the (N+1)-th row of patches) as well as 7+M+N+48*(M*(N+1)) through 6+M+N+48*(M+1)*(N+1) (i.e., the (M+1)-th column of patches). To maintain upward compatibility with previous versions of this Specification, the preprocessors must either enter a real number for each of these parameters or a series of parameter delimiters (see Section 2.2.3). These values act as placeholders in the parameter list. These parameters were intended to handle first, second, and third partial derivatives of the N -th row and M -th column of patches along the outer edge or boundary. However, these parameters can be computed by the receiving system, as needed, from the other parameter values contained in this entity, and therefore are not needed. An example of the bicubic surface is shown in Figure 26; consult Appendix B for additional details. 94 4.13 PARAMETRIC SPLINE SURFACE ENTITY (TYPE 114) Figure 26. Parameters of the Parametric Spline Surface Entity 95 4.13 PARAMETRIC SPLINE SURFACE ENTITY (TYPE 114) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 114 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 114 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 CTYPE Integer Spline Boundary Type: 1 = Linear 2 = Quadratic 3 = Cubic 4 = Wilson-Fowler 5 = Modified Wilson-Fowler 6 = B-spline 2 PTYPE Integer Patch Type: 1 = Cartesian Product 0 = Unspecified 3 M Integer Number of u segments 4 N Integer Number of v segments 5 TU(1) Real First breakpoint in u (u values of grid lines) .. . . . .. .. 5+M TU(M+1) Real Last breakpoint in u 6+M TV(1) Real First breakpoint in v (v values of grid lines) .. . . . .. .. 6+M+N TV(N+1) Real Last breakpoint in v 7+M+N AX(1,1) Real First X Coefficient of (1,1) Patch .. . . . .. .. 22+M+N SX(1,1) Real Last X Coefficient of (1,1) Patch 23+M+N AY(1,1) Real First Y Coefficient of (1,1) Patch .. . . . .. .. 38+M+N SY(1,1) Real Last Y Coefficient of (1,1) Patch 39+M+N AZ(1,1) Real First Z Coefficient of (1,1) Patch .. . . . .. .. 54+M+N SZ(1,1) Real Last Z Coefficient of (1,1) Patch 55+M+N AX(1,2) Real First X Coefficient of (1,2) Patch .. . . . .. .. 102+M+N SZ(1,2) Real Last Z Coefficient of (1,2) Patch .. . . . .. .. 7+M+N+48*(N-1) AX(1,N) Real First X Coefficient of (1,N) Patch 96 4.13 PARAMETRIC SPLINE SURFACE ENTITY (TYPE 114) .. . . . .. .. 6+M+N+48*N SZ(1,N) Real Last Z Coefficient of (1,N) Patch 7+M+N+48*N < n:a: > Real Beginning of Arbitrary Values .. . . . .. .. 6+M+N+48*(N+1) < n:a: > Real End of Arbitrary Values 7+M+N+48*(N+1) AX(2,1) Real First X Coefficient of (2,1) Patch .. . . . .. .. 6+M+N+48*(N+2) SZ(2,1) Real Last Z Coefficient of (2,1) Patch .. . . . .. .. 7+M+N+48*(2*N) AX(2,N) Real First X Coefficient of (2,N) Patch .. . . . .. .. 6+M+N+48*(2*N+1) SZ(2,N) Real Last Z Coefficient of (2,N) Patch 7+M+N+48*(2*N+1) < n:a: > Real Beginning of Arbitrary Values .. . . . .. .. 6+M+N+48*(2*N+2) < n:a: > Real Arbitrary Value .. . . . .. .. 7+M+N+48*[(J-1)*(N+1)+K-1] AX(J,K) Real First X Coefficient of (J,K) Patch .. . . . .. .. 6+M+N+48*[(J-1)*(N+1)+K] SZ(J,K) Real Last Z Coefficient of (J,K) Patch .. . . . .. .. 7+M+N+48*[(M-1)*(N+1)+N-1] AX(M,N) Real First X Coefficient of (M,N) Patch .. . . . .. .. 6+M+N+48*[(M-1)*(N+1)+N] SZ(M,N) Real Last Z Coefficient of (M,N) Patch 7+M+N+48*[(M-1)*(N+1)+N] < n:a: > Real Beginning of Arbitrary Values .. . . . .. .. 6+M+N+48*[(M-1)*(N+1)+(N+1)]< n:a: > Real Arbitrary Value 7+M+N+48*[M*(N+1)] < n:a: > Real Arbitrary Value .. . . . .. .. 6+M+N+48*[M*(N+1)+(N+1)] < n:a: > Real End of Arbitrary Values Additional pointers as required (see Section 2.2.4.4.2). 97 4.14 POINT ENTITY (TYPE 116) 4.14 Point Entity (Type 116) A point is defined by its coordinates in definition space. Examples of the Point Entity are shown in Figure 27. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 116 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 116 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: If PD Index 4 (Pointer to Display Geometry) is 0 or defaulted, then Line Font Pattern, Line Weight, and Hierarchy are ignored. Parameter Data Index__ Name____ Type___ Description___ 1 X Real Coordinates of point 2 Y Real 3 Z Real ECO564 4 PTR Pointer Pointer to the DE of the Subfigure Definition Entity specifying the display symbol or zero. If zero, no display symbol specified. Additional pointers as required (see Section 2.2.4.4.2). 98 4.14 POINT ENTITY (TYPE 116) Figure 27. Examples Defined Using the Point Entity 99 4.15 RULED SURFACE ENTITY (TYPE 118) 4.15 Ruled Surface Entity (Type 118) A ruled surface is formed by moving a line connecting points of equal relative arc length (Form 0) or equal relative parametric value (Form 1) on two parametric curves from a start point to a terminate point on the curves. The parametric curves may be points, lines, circles, conics, parametric splines, rational B-splines, composite curves, or any parametric curves defined in this specification (both planar and nonplanar). Form 0: In this case, DE1 and DE2 specify the defining rail curves, but their given parameterizations are not the ones used to generate the ruled surface. In- stead, their arc length reparameterizations, C1 and C2 (respectively), are used. Form 1: In this case, DE1 and DE2 specify the defining rail curves, C1 and C2 (respectively). Moreover, their given parameterizations are the ones used to generate the ruled surface. Both Forms: In either case, if two curves are expressed parameterically by the functions (C1x(t); C1y(t); C1z(t)) and (C2x(s); C2y(s); C2z(s)), where a t b and c s d, then the coordinates of the points on the ruled surface can be written as: X(u; v) = (1 - v) * C1x(t) + v * C2x(s) Y (u; v) = (1 - v) * C1y(t) + v * C2y(s) Z(u; v) = (1 - v) * C1z(t) + v * C2z(s) where 0 u 1; 0 v 1; t = a + u * (b - a) s = c + u * (d - c); if DIRF LG = 0 s = d + u * (c - d); if DIRF LG = 1 C1(t) and C2(s) are said to be of equal relative parametric value if t and s are evaluated at the same u value. In case DIRFLG=0, then the first point of curve 1 is joined to the first point of curve 2 and the last point of curve 1 to last point of curve 2. If DIRFLG=1, then the first point of curve 1 is joined to the last point of curve 2, the last point of curve 1 to the first point of curve 2. If DEVFLG=1, then the surface is a developable surface (see [DOCA76]); if DEVFLG=0, the surface may or may not be a developable surface. Field 15 of the directory entry accommodates a form number. For this entity, the options are as follows: ______________________________________________ |__Form__|____________Meaning_____________|___ | 0 |Equal relative arc length | |____1____|Equal_relative_parametric_values__|_ The default is Form 0. Examples of the Ruled Surface Entity are shown in Figures 28 and 29. 100 4.15 RULED SURFACE ENTITY (TYPE 118) Figure 28. Examples Defined Using the Ruled Surface Entity 101 4.15 RULED SURFACE ENTITY (TYPE 118) Figure 29. Parameters of the Ruled Surface Entity 102 4.15 RULED SURFACE ENTITY (TYPE 118) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 118 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 118 | # | #; ) | # | # | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Valid values of the Form Number are 0, 1. Parameter Data Index__ Name____ Type___ Description___ 1 DE1 Pointer Pointer to the DE of the first curve entity 2 DE2 Pointer Pointer to the DE of the second curve entity 3 DIRFLG Integer Direction flag: 0=Join first to first, last to last 1=Join first to last, last to first 4 DEVFLG Integer Developable surface flag: 1=Developable 0=Possibly not Additional pointers as required (see Section 2.2.4.4.2). 103 4.16 SURFACE OF REVOLUTION ENTITY (TYPE 120) 4.16 Surface of Revolution Entity (Type 120) A surface of revolution is defined by an axis of rotation (which must be a Line Entity), a generatrix, and start and terminate rotation angles. The surface is created by rotating the generatrix about the axis of rotation through the start and terminating angles. Since the axis of rotation is a Line Entity (Type 110), it contains in its parameter data section the coordinates of its start point first, followed by the coordinates of its terminate point. The angles of rotation are measured counterclockwise while looking in the direction of the start point of the Line Entity defining the axis of revolution from the terminate point of this line. The generatrix curve may be any curve entity to which a parameterization has been assigned. Examples of surfaces of revolution are given in Figure 30. The various parameters defining the Surface of Revolution Entity are illustrated in Figure 31. The Line Entity L defines a unique straight line. This straight line defines the axis of revolution. The axis is given the same direction as the direction assigned to the Line Entity L . Let R be the unique rigid motion leaving each point of the axis of revolution fixed and rotating each point in three dimensional Euclidean space, radians counterclockwise about the axis of revolution. R assigns to each element of three dimensional Euclidean space another element of three dimensional Euclidean space. The curve C is the generatrix of the surface of revolution. For each real number in the interval [a,b] that defines its domain, C assigns an element of three dimensional Euclidean space. SA and TA denote the start angle and terminate angle, measured in radians, of the surface of revolution to be defined. SA and TA are constrained so that 0 < T A - SA 2ss. The surface of revolution S defined by this entity is the surface that is swept by rotating the generatrix curve C from the angle SA to the angle TA, counterclockwise about the directed axis of revolution. The default parameterization for the surface of revolution S shall be given by S(x; ) = R (C(x)) for each pair of real numbers (x; ) such that a x b and SA T A. 104 4.16 SURFACE OF REVOLUTION ENTITY (TYPE 120) Figure 30. Examples Defined Using the Surface of Revolution Entity Figure 31. Parameters of the Surface of Revolution Entity 105 4.16 SURFACE OF REVOLUTION ENTITY (TYPE 120) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 120 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 120 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 L Pointer Pointer to the DE of the Line Entity (axis of revolution) 2 C Pointer Pointer to the DE of the generatrix entity 3 SA Real Start angle in radians 4 TA Real Terminate angle in radians Additional pointers as required (see Section 2.2.4.4.2). 106 4.17 TABULATED CYLINDER ENTITY (TYPE 122) 4.17 Tabulated Cylinder Entity (Type 122) A tabulated cylinder is a surface formed by moving a line segment called the generatrix parallel to itself along a curve called the directrix. This curve may be a line, circular arc, conic arc, parametric spline curve, rational B-spline curve, or composite curve. It must be pointed out that different parameterizations of the generating curves will produce differ- ent parameterized surfaces, but the underlying point set surface will still be the same. Assuming a parameterization u on the directrix and v on the generatrix, both of which run from 0 to 1, we can express the points on the surface by: X(u; v) = CX(u) + v * (LX - CX(0)) Y (u; v) = CY (u) + v * (LY - CY (0)) Z(u; v) = CZ(u) + v * (LZ - CZ(0)) where 0 u 1; 0 v 1 and CX; CY; CZ represent the X; Y; Z components, respectively, along the di- rectrix curve, while (CX(0); CY (0); CZ(0)) and (LX; LY; LZ) represent the coordinates of the start and terminate points, respectively, of the gen- eratrix. An example of the tabulated cylinder is shown in Figure 32. 107 4.17 TABULATED CYLINDER ENTITY (TYPE 122) Figure 32. Parameters of the Tabulated Cylinder Entity 108 4.17 TABULATED CYLINDER ENTITY (TYPE 122) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 122 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 122 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DE Pointer Pointer to the DE of the directrix curve entity 2 LX Real Coordinates of the terminate point of the generatrix. The start point of the generatrix is identical with the start point of the directrix. 3 LY Real 4 LZ Real Additional pointers as required (see Section 2.2.4.4.2). 109 4.18 DIRECTION ENTITY (TYPE 123) 4.18 Direction Entity (Type 123) ECO603 The definition of this entity can be found in Appendix G (see Section G.2). 110 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) 4.19 Transformation Matrix Entity (Type 124) The Transformation Matrix Entity transforms three-row column vectors by means of a matrix mul- tiplication and then a vector addition. The notation for this transformation is: 2 3 2 3 2 3 2 3 R11 R12 R13 XIN P U T T1 XOU T P U T 4 R21 R22 R23 5 4 Y IN P U T 5 + 4 T2 5 = 4 Y OU T P U T 5 R31 R32 R33 ZIN P U T T3 ZOU T P U T Here, col [ XINPUT, YINPUT, ZINPUT ] (i.e., the column vector) is the vector being transformed, and col [ XOUTPUT, YOUTPUT, ZOUTPUT ] is the column vector resulting from this transfor- mation. R = [Rij] is a 3 row by 3 column matrix of real numbers, and T = col [ T1,T2,T3 ] is a three-row column vector of real numbers. Thus, 12 real numbers are required for a Transformation Matrix Entity. This entity can be considered to be an "operator" entity in that it starts with the input vector, operates on it as described above, and produces the output vector. Frequently, the input vector lists the coordinates of some point in one coordinate system, and the output vector lists the coordinates of that same point in a second coordinate system. The matrix R and the translation vector T then express a general relationship between the two coordinate systems. By considering special input vectors such as col [ 1,0,0 ], col [ 0,1,0 ], and col [ 0,0,1 ] and computing the corresponding output results, a geometric appreciation of the spatial relationship between the two coordinate systems can be gained. For example, for 2 3 2 3 0 0 1 0 R = 4 0 1 0 5 ; T = 4 0 5 -1 0 0 0 the spatial relationship of the input and output coordinate systems is given in Figure 33. All coordinate systems are assumed to be orthogonal, Cartesian, and right-handed unless specifically noted otherwise. Following are three specific areas where the Transformation Matrix Entity is used to transform coordinates between coordinate systems. Each example area illustrates a specific choice of input and output coordinate systems. Other choices of coordinate systems may be appropriate in other application areas. The usual situation for this type of use of the Transformation Matrix Entity is when the input vector refers to the definition space coordinate system for a certain entity, and the output vector refers to the model space coordinate system (See Section 3.2.2). In this case, the matrix R is referred to as the defining matrix, and the Transformation Matrix Entity defining R and T is pointed to in field seven (transformation matrix field) of the directory entry of the entity (See Section 2.2.4.3.7). In this use of the Transformation Matrix Entity, the matrix R is subject to the restrictions given in Form 0 and Form 1 below. A second situation is the case when the input vector refers to the model space coordinate system and the output vector refers to a viewing coordinate system. In this case, the matrix R is referred to as a view matrix, and is subject to the restrictions given in Form 0 below. Note that when a planar entity is viewed at true length (i.e., the viewing plane is parallel to the plane containing the entity) then the rotation matrix pointed to by DE Field 7 of the Planar Entity will be the inverse (=matrix transpose) of the matrix pointed to by DE Field 7 of the View Entity (See Section 4.80). 111 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) A third situation involves finite element modeling applications. Here, it may be the case that an input coordinate system is related to an output coordinate system by a particular R and T , and, in turn, the output coordinate system is then taken as an input coordinate system for a second R and T combination, and so on. These coordinate systems are frequently called local coordinate systems. Model space is frequently called the reference system. For example, the location of a finite element node may be given in one local coordinate system, which may serve as the input coordinate system for a second local coordinate system, which in turn serves as the input coordinate system for the model space coordinate system which is the reference system. Allowable forms of the matrix R for these applications are detailed in Forms 10, 11, and 12 below. Whenever coordinate systems are related successively to each other as described above, a basic result is that the combined effect of the individual coordinate system changes can be expressed in terms of a single matrix R and a single translation vector T . For example, if the coordinate system change involving the matrix R2 and the translation vector T 2 is to be applied following the coordinate system change involving the matrix R1 and the translation vector T 1, then the matrix R and the translation vector T expressing the combined changes are R=(R2) (R1) and T = (R2) (T 1) + T 2. Here, (R2) (R1) denotes matrix multiplication of 3x3 matrices, where multiplication order is impor- tant. The matrix R and the translation vector T are computed similarly whenever more than two coordinate system changes are to be applied successively. Successive coordinate system changes are specified by allowing a Transformation Matrix Entity to reference another Transformation Matrix Entity through Field 7 of the directory entry. In the ex- ample above, the Transformation Matrix Entity containing R1 and T 1 would contain in its directory entry field 7 a pointer to the Transformation Matrix Entity containing R2 and T 2. The general rule is that Transformation Matrix Entities applied earlier in a succession will reference Transformation Figure 33. Example of the Transformation Matrix Coordinate Systems 112 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) Matrix Entities applied later. Note that the matrix product (R2) (R1) in the example above does not appear explicitly in the data, but, if needed, must be computed according to the usual rules of matrix multiplication. A second example of coordinate systems being related successively (or "concatenated" or "stacked"), in addition to the finite element example mentioned above, involves one manner of locating into model space a conic arc that is in standard position in definition space. In this case, R1 and T 1 move the conic arc from its standard position to an arbitrary location in any plane in definition space satisfying ZT=constant. (Therefore, R133 = 1:0; R131 = R132 = R113 = R123 = 0:0. T 1 can be an arbitrary translation vector.) R2 and T 2 then position the relocated conic arc into model space. (R2 can be an arbitrary defining matrix and T 2 can be an arbitrary translation vector.) Note that for R1 and T 1, both the input vector and the output vector refer to the same coordinate system, namely, the definition space for the conic arc. A 3x3 matrix R is called orthogonal provided its transpose, Rt, yields a matrix inverse for R. The columns of an orthogonal matrix considered as vectors form an orthogonal collection of unit vectors. As (Rt)t = R, the transpose of an orthogonal matrix is again an orthogonal matrix. The determinant of an orthogonal matrix is equal to either plus one or minus one. In the event R is an orthogonal matrix with determinant equal to positive one, R can be expressed as a rotation about an axis passing through the origin. In this event, R is referred to as a rotation matrix. In the event R is an orthogonal matrix with determinant equal to negative one, R can be expressed as a rotation about an axis passing through the origin followed by a reflection about a plane passing through the origin perpendicular to the axis of rotation. Allowable Form Numbers The defining matrix of an entity must use either Form 0 or Form 1. A defining matrix associated with a View Entity (Type 410) must use Form 0. Special matrices representing Node Entity (Type 134) local coordinate systems must use Forms 10, 11, or 12. Form 0: (default) R is an orthogonal matrix with determinant equal to positive one. T is arbitrary. The columns of R taken in order form a right-handed triple in the output coordinate system. Form 1: R is an orthogonal matrix with determinant equal to negative one. T is arbitrary. The columns of R taken in order form a left-handed triple in the output coordinate system. Form 10: This form number conveys special information when used in conjunction with the Node Entity (Type 134) in Finite Element Applications. Refer to Figure 34(a) for notation. The matrix R and the vector T are used to transform coordinate data from the u1, u2, u3 coordinate system to the x,y,z local system. The u1,u2,u3 coordinate system has its origin at an arbitrary fixed point col [XOFF- SET, YOFFSET, ZOFFSET] in the x,y,z coordinate system and is assumed to be displaced parallel to that reference coordinate system. Thus, 2 3 2 3 1 0 0 XOF F SET R = 4 0 1 0 5 ; T = 4 Y OF F SET 5 0 0 1 ZOF F SET 113 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) so that 2 3 2 3 2 3 2 3 1 0 0 u1 XOF F SET XLOCAL 4 0 1 0 5 4 u2 5 + 4 Y OF F SET 5 = 4 Y LOCAL 5 0 0 1 u3 ZOF F SET ZLOCAL Note that the orientation of the two coordinate systems can be described by saying that the u1,u2,u3 coordinate system is the system obtained by imposing orthogo- nal curvilinear coordinates onto the x,y,z space and then constructing unit tangent vectors to the three curvilinear coordinate curves at the given fixed point to serve as basis vectors. In this special case of parallel displacement, the curvilinear coor- dinates imposed are identical to the existing x,y,z coordinates. Form 11: This form number conveys special information when used in conjunction with the Node Entity (Type 134) in Finite Element applications. Refer to Figure 34(b) for notation. The matrix R and the vector T are used to transform coordinate data from the u1, u2, u3 (node point) coordinate system to the x,y,z (local system) coordinate system. The u1, u2, u3 coordinate system has its origin at an arbitrary fixed point XOF F SET = r0 cos 0 r0 > 0 Y OF F SET = r0 sin 0 0 0 3600 ZOF F SET = z0 -1 < z0 < 1 for r0 = 0; take = 00 in the x,y,z coordinate system. The u1,u2,u3 system is the system obtained by im- posing orthogonal curvilinear coordinates onto the x,y,z space which are the cylin- drical coordinates (r,,z) with x = r cos y = r sin z = z; and then constructing unit tangent vectors to the three curvilinear coordinate curves at the given fixed point to serve as basis vectors. Thus, the relationship between the u1, u2, u3 and the x,y,z local coordinate system is given by: 114 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) 2 3 2 3 2 3 2 3 cos 0 - sin0 0 u1 XOF F SET XLOCAL 4 sin0 cos 0 0 5 4 u2 5 + 4 Y OF F SET 5 = 4 Y LOCAL 5 0 0 1 u3 ZOF F SET ZLOCAL Form 12: This form number conveys special information when used in conjunction with the Node Entity (Type 134) in Finite Element applications. Refer to Figure 34(c) for notation. The matrix R and the vector T are used to transform coordinate data from the u1, u2, u3 coordinate system to the x,y,z local system. The u1, u2, u3 coordinate system has its origin at an arbitrary fixed point XOF F SET = r0 sin0 sinOE0 r0 0 Y OF F SET = r0 sin0 cosOE0 0 0 1800 ZOF F SET = r0 cos0 0 OE0 < 3600 for r0 = 0; take 0 = OE0 = 00 for 0 = 00 or 1800; take OE0 = 00 in the x,y,z coordinate system. The u1, u2, u3 system is the system obtained by imposing orthogonal curvilinear coordinates onto the x,y,z space which are the spherical coordinates (r,,OE) with x = r sin cosOE y = r sin sinOE z = r cos and then constructing unit tangent vectors to the three curvilinear coordinate curves at the given fixed point to serve as basis vectors. Thus, the relationship between the u1, u2, u3 and the x,y,z local coordinate systems is given by: 2 3 2 3 2 3 2 3 sin 0 * cosOE0 cos0 * cosOE0 - sinOE0 u1 XOF F SET XLOCAL 4 sin 0 * sinOE0 cos0 * sinOE0 cos OE0 5 4 u2 5 + 4 Y OF F SET 5 = 4 Y LOCAL 5 cos 0 - sin0 0 u3 ZOF F SET ZLOCAL 115 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) See, Kaplan [KAPL52] or Hildebrand [HILD76] for a discussion of orthogonal curvilinear coordinate systems. 116 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) Figure 34. Notation for FEM-specific Forms of the Transformation Matrix Entity 117 4.19 TRANSFORMATION MATRIX ENTITY (TYPE 124) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 124 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |< n:a: > |******** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 124 |< n:a: > |< n:a: > | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0, 1, 10, 11, 12. Parameter Data Index__ Name____ Type___ Description___ 1 R11 Real Top Row 2 R12 Real . 3 R13 Real . 4 T1 Real . 5 R21 Real Second Row 6 R22 Real . 7 R23 Real . 8 T2 Real . 9 R31 Real Third Row 10 R32 Real . 11 R33 Real . 12 T3 Real . Additional pointers as required (see Section 2.2.4.4.2). 118 4.20 FLASH ENTITY (TYPE 125) 4.20 Flash Entity (Type 125) A Flash Entity is a point in the ZT=0 plane that locates a specific instance of a particular closed area. That closed area can be defined in one of two ways. First, it can be an arbitrary closed area defined by any entity capable of defining a closed area. The points of this entity must all lie in the ZT=0 plane. Second, it can be a member of a predefined set of flash shapes. In the latter case, Parameters 3 through 5 of the Flash Entity control the final size of the flash. Figure 35 indicates the usage of those parameters for the specific flash forms. Parameters 3 through 5 are ignored for Form 0. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: __________________________________________ |__Form__|__________Meaning___________|___ | 0 |Defined by referenced entity | | 1 |Circular | | 2 |Rectangle | | 3 |Donut | |____4____|Canoe________________________|_ Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 125 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |??????00 | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 125 | # | #; ) | # | # | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Valid values of the Form Number are 0, 1, 2, 3, 4. Parameter Data Index__ Name____ Type___ Description___ 1 X Real X reference of flash 2 Y Real Y reference of flash 3 DIM1 Real First flash sizing parameter 4 DIM2 Real Second flash sizing parameter 5 ROT Real Rotation of flash about reference point in radians 6 DE Pointer Pointer to the DE of the referenced entity or zero Additional pointers as required (see Section 2.2.4.4.2). 119 4.20 FLASH ENTITY (TYPE 125) Figure 35. Definition of Shapes for the Flash Entity 120 4.20 FLASH ENTITY (TYPE 125) Figure 35. Definition Shapes for the Flash Entity (continued) 121 4.21 RATIONAL B-SPLINE CURVE ENTITY (TYPE 126) 4.21 Rational B-Spline Curve Entity (Type 126) The rational B-spline curve may represent analytic curves of general interest. This information is important to both the sending and receiving systems. The Directory Entry Form Number Pa- rameter is provided to communicate this information. It should be emphasized that use of this curve form should be restricted to communications between systems operating directly on rational ECO522 B-spline curves and not used as a replacement for the analytic forms for communication. For a brief description and a precise definition of rational B-spline curves, see Appendix B. If the rational B-spline curve represents a preferred curve type, the form number corresponds to the most preferred type. The preference order is from 1 through 5 followed by 0. For example, if the curve is a circle or circular arc, the form number is set to 2. If the curve is an ellipse with unequal major and minor axis lengths, the form number is set to 3. If the curve is not one of the preferred types, the form number is set to 0. If the curve lies entirely within a unique plane, the planar flag (PROP1) is set to 1, otherwise it is set to 0. If it is set to 1, the plane normal (Parameters 14+A+4*K through 16+A+4*K) contain a unit vector normal to the plane containing the curve. These fields exist but are ignored if the curve is nonplanar. ECO582 If the beginning and ending points on the curve, as defined by evaluating the curve at the starting and ending parameter values (i.e., V(0) and V(1)), are identical, then the curve is closed and PROP2 is set to 1. If they are not equal, PROP2 is set to 0. If the curve is rational (does not have all weights equal), PROP3 is set to 0. If all weights are equal to each other, the curve is polynomial and PROP3 is set to 1. The curve is polynomial since in this case all weights cancel and the denominator sums to 1 (see Appendix B). The weights must be positive real numbers. If the curve is periodic with respect to its parametric variable, set PROP4 to 1; otherwise set PROP4 to 0. The periodic flag is to be interpreted as purely informational. The curves which are flagged to be periodic are to be evaluated exactly the same as in the nonperiodic case. ECO522 Note that the control points are in the definition space of the curve. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________________________ |__Form__|________________Meaning_________________|___ | 0 |Form of curve must be determined from | | |the rational B-spline parameters | | 1 |Line | | 2 |Circular arc | | 3 |Elliptical arc | | 4 |Parabolic arc | |____5____|Hyperbolic_arc____________________________|_ 122 4.21 RATIONAL B-SPLINE CURVE ENTITY (TYPE 126) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 126 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 126 | # | #; ) | # | # | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Valid values of the Form Number are 0-5. Parameter Data Index__ Name____ Type___ Description___ 1 K Integer Upper index of sum. See Appendix B 2 M Integer Degree of basis functions 3 PROP1 Integer 0 = nonplanar, 1 = planar 4 PROP2 Integer 0 = open curve, 1 = closed curve 5 PROP3 Integer 0 = rational, 1 = polynomial 6 PROP4 Integer 0 = nonperiodic, 1 = periodic Let N = 1+K-M and A = N+2*M 7 T(-M) Real First value of knot sequence .. . . . .. .. 7+A T(N+M) Real Last value of knot sequence 8+A W(0) Real First weight .. . . . .. .. 8+A+K W(K) Real Last weight 9+A+K X0 Real First control point 10+A+K Y0 Real 11+A+K Z0 Real .. . . . .. .. 9+A+4*K XK Real Last control point 10+A+4*K YK Real 11+A+4*K ZK Real 12+A+4*K V(0) Real Starting parameter value 13+A+4*K V(1) Real Ending parameter value 14+A+4*K XNORM Real Unit normal (if curve is planar) 15+A+4*K YNORM Real 16+A+4*K ZNORM Real Additional pointers as required (see Section 2.2.4.4.2). 123 4.22 RATIONAL B-SPLINE SURFACE ENTITY (TYPE 128) 4.22 Rational B-Spline Surface Entity (Type 128) The rational B-spline surface represents various analytical surfaces of general interest. This in- formation is important to both the generating and receiving system. The Directory Entry Form ECO522 Number Parameter is provided to communicate such information. For a brief description and a precise definition of rational B-spline surfaces, see Appendix B. If the rational B-spline surface represents a preferred surface type, the form number corresponds to the most preferred type. The preference order is from 1 through 9 followed by 0. For example, if the surface is a right circular cylinder, the form number is set to 2. If the surface is a surface of revolution and also a torus, the form number is set to 5. If the surface is not one of the preferred types, the form number is set to 0. If, for each fixed value of the second parametric variable the resulting curves which are functions of the first parametric variable are closed, set PROP1 to 1; otherwise, set PROP1 to 0. Similarly, if for each fixed value of the first parametric variable the resulting curves which are functions of the ECO582 second parametric variable are closed, set PROP2 to 1; otherwise, set PROP2 to 0. Mathematically, this is described as follows: PROP1 shall be set to 1, if and only if, for each value of V (0) V V (1), the surface at (U (0); V ) evaluates to the same point as it does for (U (1); V ). Correspondingly, PROP2 shall be set to 1, if and only if, for each value of U (0) U U (1), the surface at (U; V (0)) evaluates to the same point as it does for (U; V (1)). If the surface is rational (does not have all weights equal), set PROP3 to 0. If all weights are equal to each other, the surface is polynomial and PROP3 is set to 1. The surface is polynomial since in this case all weights cancel and the denominator sums to one (see Appendix B). The weights must be positive real numbers. If the surface is periodic with respect to the first parametric variable, set PROP4 to 1; otherwise, set PROP4 to 0. If the surface is periodic with respect to the second parametric variable, set PROP5 to 1; otherwise, set PROP5 to 0. The periodic flags are to be interpreted as purely informational. The surfaces which are flagged to be periodic are to be evaluated exactly the same as in the nonperiodic case. ECO522 Note that the control points are in the definition space of the surface. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________________________ |__Form__|_________________Meaning_________________|__ | 0 |Form of the surface must be determined | | |from the rational B-spline parameters | | 1 |Plane | | 2 |Right circular cylinder | | 3 |Cone | | 4 |Sphere | | 5 |Torus | | 6 |Surface of revolution | | 7 |Tabulated cylinder | | 8 |Ruled surface | |____9____|General_quadric_surface___________________|_ 124 4.22 RATIONAL B-SPLINE SURFACE ENTITY (TYPE 128) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 128 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 128 | # | #; ) | # | # | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Valid values of the Form Number are 0-9. Parameter Data Index__ Name____ Type___ Description___ 1 K1 Integer Upper index of first sum. See Appendix B 2 K2 Integer Upper index of second sum. See Appendix B 3 M1 Integer Degree of first set of basis functions 4 M2 Integer Degree of second set of basis functions 5 PROP1 Integer 1 = Closed in first parametric variable direction 0 = Not closed 6 PROP2 Integer 1 = Closed in second parametric variable direction 0 = Not closed 7 PROP3 Integer 0 = Rational 1 = Polynomial 8 PROP4 Integer 0 = Nonperiodic in first parametric variable direction 1 = Periodic in first parametric variable direction 9 PROP5 Integer 0 = Nonperiodic in second parametric variable direction 1 = Periodic in second parametric variable direction Let N1 = 1+K1-M1, N2 = 1+K2-M2, A = N1+2*M1, B = N2+2*M2, C = (1+K1)*(1+K2) 10 S(-M1) Real First value of first knot sequence .. . . . .. .. 10+A S(N1+M1) Real Last value of first knot sequence 11+A T(-M2) Real First value of second knot sequence .. . . . .. .. 11+A+B T(N2+M2) Real Last value of second knot sequence 12+A+B W(0,0) Real First Weight 13+A+B W(1,0) Real .. . . . .. .. 11+A+B+C W(K1,K2) Real Last Weight 12+A+B+C X(0,0) Real First Control Point 13+A+B+C Y(0,0) Real 14+A+B+C Z(0,0) Real 125 4.22 RATIONAL B-SPLINE SURFACE ENTITY (TYPE 128) 15+A+B+C X(1,0) Real 16+A+B+C Y(1,0) Real 17+A+B+C Z(1,0) Real .. . . . .. .. 9+A+B+4*C X(K1,K2) Real Last Control Point 10+A+B+4*C Y(K1,K2) Real 11+A+B+4*C Z(K1,K2) Real 12+A+B+4*C U(0) Real Starting value for first parametric direction 13+A+B+4*C U(1) Real Ending value for first parametric direction 14+A+B+4*C V(0) Real Starting value for second parametric direction 15+A+B+4*C V(1) Real Ending value for second parametric direction Additional pointers as required (see Section 2.2.4.4.2). 126 4.23 OFFSET CURVE ENTITY (TYPE 130) 4.23 Offset Curve Entity (Type 130) The Offset Curve Entity contains the data necessary to determine the offset of a given curve C. This entity points to the base curve to be offset and contains the offset distance and additional pertinent information. No restriction is placed on the entity types of curves. Any parametric curve may be offset. It is the intent of this Specification to limit the applicability of offsets to curves which are planar and slope continuous. The offset curve lies in the plane which contains the base curve as follows: Let C denote a curve in definition space which is defined by r = r(t): Let T (t) denote the unit tangent at r(t) (See [FAUX79]). Let V be a unit vector normal to the plane which contains C. Then the offset curve is a curve defined as: O(t) = r(t) + f (s) * (V x T (t)); T T 1 t T T 2 a) if FLAG = 1, a uniform offset distance, f (s) = D1 b) if FLAG = 2, an offset distance varying linearly, f (s) = D1 + (D2 - D1) * (s - T D1)=(T D2 - T D1) with Case (i) PTYPE = 1 s = arc length along r from r(T T 1) to r(t), D1 = the offset at arc length value T D1, D2 = the offset at arc length value T D2 Case (ii) PTYPE = 2 s = t, D1 = the offset at parametric value T D1, D2 = the offset at parametric value T D2 c) if FLAG = 3, an offset distance defined by a function, f (s) is the NDIM-th coordinate function of the curve pointed to by DE2, with Case (i) PTYPE = 1 s = arc length along r from r(T T 1) to r(t), Case (ii) PTYPE = 2 s = t Note that T T 1 and T T 2 must be chosen to be in the domain of the base curve r(t). 127 4.23 OFFSET CURVE ENTITY (TYPE 130) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 130 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 130 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DE1 Pointer Pointer to the DE of the curve entity to be offset. 2 FLAG Integer Offset distance flag: 1 = Single value offset, uniform distance 2 = Offset distance varying linearly 3 = Offset distance as a specified function. 3 DE2 Pointer Pointer to the DE of the curve entity, one coordinate of which describes the offset as a function of its parameter. or 0 (0 unless FLAG = 3) 4 NDIM Integer Pointer of particular coordinate of DE2 which describes offset as a function of its parameter. (only used if FLAG = 3) 5 PTYPE Integer Tapered offset type flag: 1 = Function of arc length 2 = Function of parameter (only used if FLAG=2 or 3) 6 D1 Real First offset distance. (only used if FLAG=1 or 2) 7 TD1 Real Arc length or parameter value, depending on PTYPE, of first offset distance. (only used if FLAG=2) 8 D2 Real Second offset distance. 9 TD2 Real Arc length or parameter value, depending on PTYPE, of second offset distance. (only used if FLAG=2) 10 VX Real X-component of unit vector normal to plane containing curve to be offset. 11 VY Real Y-component of unit vector normal to plane containing curve to be offset. 12 VZ Real Z-component of unit vector normal to plane containing curve to be offset. 13 TT1 Real Offset curve starting parameter value. 14 TT2 Real Offset curve ending parameter value. Additional Pointers as required (see Section 2.2.4.4.2). Parameter data not required for a particular case should be given zero values. For example, if the value of Parameter 2 is not 3, then Parameters 3 and 4 should be given zero values. 128 4.24 CONNECT POINT ENTITY (TYPE 132) 4.24 Connect Point Entity (Type 132) A Connect Point Entity describes a point of connection for zero, one or more entities. These entities include those required in piping diagrams, electrical and electronic schematics, and physical designs (e.g., printed wiring boards). The Connect Point Entity is referenced from either the Composite Curve (Type 102), Network Subfigure Definition (Type 320), Network Subfigure Instance (Type 420), or the Flow Associativity Instance (Type 402, Form 18); or it may stand alone in a file. The connect point may be displayed by the receiving system using default display parameters and/or symbols. Also see Section 3.6.3. TF. The Type Flag (TF) is an enumerated list that specifies a particular type of connection: ECO576 ___________________________________________________________ |__TF_Value__|_________________Meaning_________________|___ | 0 |Not Specified (default) | | 1 |Nonspecific logical point of connection | | 2 |Nonspecific physical point of connection | | 101 | Logical component pin | | 102 | Logical port connector | | 103 | Logical offpage connector | | 104 | Logical global signal connector | | 201 | Physical PWA surface mount pin | | 202 | Physical PWA blind pin | | 203 | Physical PWA thru-pin | |__5001-9999__|_Implementor_defined______________________|_ 129 4.24 CONNECT POINT ENTITY (TYPE 132) ECO576 FC. The Function Code (FC) is an enumerated list that specifies a particular function for the connection: ______________________________________________________________________________ |__FC_Value__|_______Meaning_______|_|___FC_Value__|_________Meaning_______|__ | 0 |Unspecified (default) | | 30 | Reset | | 1 |Input | | 31 | Blanking | | 2 |Output | | 32 | Test | | 3 |Input and Output | | 33 | Address | | 4 |Power (VCC) | | 34 | Control | | 5 |Ground | | 35 | Carry | | 6 |Anode | | 36 | Sum | | 7 |Cathode | | 37 | Write | | 8 |Emitter | | 38 | Sense | | 9 |Base | | 39 | V+ | | 10 |Collector | | 40 | Read | | 11 |Source | | 41 | Load | | 12 |Gate | | 42 | SYNC | | 13 |Drain | | 43 | Tri-State Output | | 14 |Case | | 44 | VDD | | 15 |Shield | | 45 | V- | | 16 |Inverting Input | | 46 | VEE | | 17 |Regulated Input | | 47 | Reference | | 18 |Booster Input | | 48 | Reference Bypass | | 19 |Unregulated Input | | 49 | Reference Supply | | 20 |Inverting Output | | 98 | Deferred | | 21 |Regulated Output | | 99 | No Connection | | 22 |Booster Output | | 5001-9999 | Implementor defined | | 23 |Unregulated Output | | | | | 24 |Sink | | | | | 25 |Strobe | | | | | 26 |Enable | | | | | 27 |Data | | | | | 28 |Clock | | | | |______29______|Set____________________|_|___________|________________________| 130 4.24 CONNECT POINT ENTITY (TYPE 132) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 132 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????04?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 132 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: If PD Index 4 (Pointer to Display Geometry) is 0 or defaulted, then Line Font Pattern, Line Weight, and Hierarchy are ignored. Parameter Data ECO546 Index__ Name____ Type___ Description___ 1 X Real X coordinate of the connection point 2 Y Real Y coordinate of the connection point 3 Z Real Z coordinate of the connection point 4 PTR Pointer Pointer to the DE of the display symbol geometry entity, or null. If null, no display symbol specified. 5 TF Integer Type flag 6 FF Integer Function Flag: 0 = not specified 1 = electrical signal 2 = fluid flow path 7 CID String Connect Point Function Identifier (e.g., Pin Number or Nozzle Label) 8 PTTCID Pointer Pointer to the DE of the Text Display Template Entity for CID, or null. If null, no Text Display Template specified. 9 CFN String Connection Point Function Name 10 PTTCFN Pointer Pointer to the DE of the Text Display Template Entity for CFN, or null. If null, no Text Display Template specified. 11 CPID Integer Unique Connect Point Identifier 12 FC Integer Connect Point Function Code 13 SF Integer Swap Flag 0 = Connect point may be swapped (default) 1 = Connect point may not be swapped 14 PSFI Pointer Pointer to the DE of the "owner" Network Subfigure Instance Entity, or Network Subfigure Definition Entity, or zero. Additional pointers as required (see Section 2.2.4.4.2). 131 4.25 NODE ENTITY (TYPE 134) 4.25 Node Entity (Type 134) The Node Entity is a geometric point used in the definition of a finite element. Directory Entry field 7 points to a labeled definition coordinate system Transformation Matrix. The form number of the Transformation Matrix indicates the definition coordinate system type. Coordinate angles for the cylindrical and spherical coordinate systems are specified in degrees. Every node has a nodal displacement coordinate system associated with it. This is Form 10, 11, or 12 of the Transformation Matrix Entity which locates translational and rotational directions for load, restraint and displacement results. Again, the form number of the Transformation Matrix indicates the coordinate system type. The origin of the nodal displacement coordinate system is always the location of the node. However, the orientation of the nodal displacement axes depends on the location of the node and the type of displacement coordinate system being referenced. Cartesian (rectangular), cylindrical, and spherical are the three possible types. Figure 36 illustrates the definition of a node in the three coordinate systems. If the displacement coordinate system is Cartesian, then the nodal displacement axes are parallel to the respective referenced coordinate system. This is illustrated in Figure 36(a) Cartesian. For the cylindrical type displacement coordinate system, the orientation of the nodal displacement axes depends on the coordinate value of the node as defined in the referenced displacement coordinate system. The nodal displacement axes are respectively in the radial, tangential and axial directions as illustrated in Figure 36(b) Cylindrical. Finally, for spherical, the orientation of the nodal displacement axes depend on both the and OE coordinates of the node as defined in the referenced displacement coordinate system. The nodal displacement axes are respectively in the radial, meridional, and azimuthal directions as indicated in Figure 36(c) Spherical. If a node lies on the polar axis of either the cylindrical or spherical coordinate system, the nodal displacement axes are defined parallel to the referenced displacement coordinate system axes. For a cylindrical system the first axis is the = 0 axis and the third axis is the z axis. For a spherical system the first axis is the OE = 0 axis while the third axis is the = 0 axis. The remaining axis of both systems is defined by the appropriate cross product of the previously defined axes. 132 4.25 NODE ENTITY (TYPE 134) Figure 36. Nodal Displacement Coordinate Systems 133 4.25 NODE ENTITY (TYPE 134) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 134 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > | ) |< n:a: > |????04** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 134 |< n:a: > | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Entity Subscript shall contain the Node Number. The Entity Label optionally may contain the Node Label. Parameter Data Index__ Name____ Type___ Description___ 1 X/R/R Real First nodal coordinate 2 Y// Real Second nodal coordinate 3 Z/Z/OE Real Third nodal coordinate 4 NDCSP Pointer Pointer to the DE of the Transformation Matrix Entity Form 10, 11 or 12 which defines the Nodal Displacement Coordinate System Entity. Default (zero) is Global Cartesian Coordinate System. Additional pointers as required (see Section 2.2.4.4.2). 134 4.26 FINITE ELEMENT ENTITY (TYPE 136) 4.26 Finite Element Entity (Type 136) A finite element is defined by an element topology (i.e., node connectivity) along with physical and material properties. Table 4 lists the data to define the element topology. Additional element topologies are defined in ECO515 Appendix G (see Section G.3). Figure 37 illustrates the node connectivity for each element topology. In Table 4 the element name is an English abbreviation or acronym describing the element. The element topology type is an integer number which will appear as the first parameter of the parameter data. The order is an integer identifying the order of an edge where: ______________________________ |__Value__|Order_of_Edge__|___ | 0 |Not applicable | | 1 |Linear | | 2 |Parabolic | |____3____|Cubic_____________|_ The number of nodes from Table 4 will appear as the second parameter of the finite element pa- rameter data. A missing node in the connectivity sequence will have its corresponding pointer value equal to zero. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 136 | ) |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > | 0; ) |******** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 136 |< n:a: > | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Entity Subscript shall contain the Element Number. The Entity Label optionally may contain the Element Label. Parameter Data Index__ Name____ Type___ Description___ 1 ITOP Integer Topology type 2 N Integer Number of nodes defining element (See Section 4.25). 3 DE1 Pointer Pointer to the DE of the first node defining element entity (See Section 4.25). .. . . . .. .. 2+N DEN Pointer Pointer to the DE of the last node defining element entity 3+N ETYP String Element type name Additional pointers as required (see Section 2.2.4.4.2). 135 4.26 FINITE ELEMENT ENTITY (TYPE 136) Table 4. Finite Element Topology Sety _____________________________________________________________________________ | Element | Element | Order | Number | Number | Number | | Name | Topology | | of Nodes | of Edges | of Faces | |______________|__Type____|__________|_____________|____________|____________| | BEAM | 1 | 1 | 2 | 1 | 0 | | LTRIA | 2 | 1 | 3 | 3 | 1 | | PTRIA | 3 | 2 | 6 | 3 | 1 | | CTRIA | 4 | 3 | 9 | 3 | 1 | | LQUAD | 5 | 1 | 4 | 4 | 1 | | PQUAD | 6 | 2 | 8 | 4 | 1 | | CQUAD | 7 | 3 | 12 | 4 | 1 | | PTSW | 8 | 2 | 12 | 9 | 5 | | CTSW | 9 | 3 | 18 | 9 | 5 | | PTS | 10 | 2 | 16 | 12 | 6 | | CTS | 11 | 3 | 24 | 12 | 6 | | LSOT | 12 | 1 | 4 | 6 | 4 | | PSOT | 13 | 2 | 10 | 6 | 4 | | LSOW | 14 | 1 | 6 | 9 | 5 | | PSOW | 15 | 2 | 15 | 9 | 5 | | CSOW | 16 | 3 | 24 | 9 | 5 | | LSO | 17 | 1 | 8 | 12 | 6 | | PSO | 18 | 2 | 20 | 12 | 6 | | CSO | 19 | 3 | 32 | 12 | 6 | | ALLIN | 20 | 1 | 2 | 1 | 0 | | APLIN | 21 | 2 | 3 | 1 | 0 | | ACLIN | 22 | 3 | 4 | 1 | 0 | | ALTRIA | 23 | 1 | 3 | 3 | 0 | | APTRIA | 24 | 2 | 6 | 3 | 0 | | ALQUAD | 25 | 1 | 4 | 4 | 0 | | APQUAD | 26 | 2 | 8 | 4 | 0 | | SPR | 27 | 0 | 2 | 0 | 0 | | GSPR | 28 | 0 | 1 | 0 | 0 | | DAMP | 29 | 0 | 2 | 0 | 0 | | GDAMP | 30 | 0 | 1 | 0 | 0 | | MASS | 31 | 0 | 1 | 0 | 0 | | RBDY | 32 | 0 | 2 | 0 | 0 | |__TBEAM___|_______33______|____1_____|_____3______|_____1______|_____0______| yAdditional element topologies are defined in Appendix G (see Section G.3). 136 4.26 FINITE ELEMENT ENTITY (TYPE 136) 1. BEAM E1=1,2 2. LTRIA - Linear Triangle E1=1,2 F1=1,2,3 E2=2,3 E3=3,1 3. PTRIA - Parabolic Triangle E1=1,2,3 F1=1,2,3,4,5,6 E2=3,4,5 E3=5,6,1 4. CTRIA - Cubic Triangle E1=1,2,3,4 F1=1,2,3,4,5,6,7,8,9 E2=4,5,6,7 E3=7,8,9,1 5. LQUAD - Linear Quadrilateral E1=1,2 F1=1,2,3,4 E2=2,3 E3=3,4 E4=4,1 6. PQUAD - Parabolic Quadrilateral E1=1,2,3 F1=1,2,3,4,5,6,7,8 E2=3,4,5 E3=5,6,7 E4=7,8,1 Figure 37. Finite Element Topology Set 137 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 138 4.26 FINITE ELEMENT ENTITY (TYPE 136) 7. CQUAD - Cubic Quadrilateral E1=1,2,3,4 F1=1,2,3,4,5,6,7,8,9,10,11,12 E2=4,5,6,7 E3=7,8,9,10 E4=10,11,12,1 8. PTSW - Parabolic Thick Shell Wedge E1=1,2,3 E4=7,8,9 E7=1,7 F1=1,2,3,4,5,6 E2=3,4,5 E5=9,10,11 E8=3,9 F2=7,8,9,10,11,12 E3=5,6,1 E6=11,12,7 E9=5,11 F3=1,2,3,9,8,7 F4=3,4,5,11,10,9 F5=5,6,1,7,12,11 9. CTSW - Cubic Thick Shell Wedge E1=1,2,3,4 E4=10,11,12,13 E7=1,10 E2=4,5,6,7 E5=13,14,15,16 E8=4,13 E3=7,8,9,1 E6=16,17,18,10 E9=7,16 F1=1,2,3,4,5,6,7,8,9 F2=10,11,12,13,14,15,16,17,18 F3=1,2,3,4,13,12,11,10 F4=4,5,6,7,16,15,14,13 F5=7,8,9,1,10,18,17,16 10. PTS - Parabolic Thick Shell E1=1,2,3 E5=9,10,11 E9=1,9 E2=3,4,5 E6=11,12,13 E10=3,11 E3=5,6,7 E7=13,14,15 E11=5,13 E4=7,8,1 E8=15,16,9 E12=7,15 F1=1,2,3,4,5,6,7,8 F4=3,4,5,13,12,11 F2=9,10,11,12,13,14,15,16 F5=5,6,7,15,14,13 F3=1,2,3,11,10,9 F6=7,8,1,9,16,15 11. CTS - Cubic Thick Shell E1=1,2,3,4 E5=13,14,15,16 E9=1,13 E2=4,5,6,7 E6=16,17,18,19 E10=4,16 E3=7,8,9,10 E7=19,20,21,22 E11=7,19 E4=10,11,12,1 E8=22,23,24,13 E12=10,22 F1=1,2,3,4,5,6,7,8,9,10,11,12 F2=13,14,15,16,17,18,19,20,21,22,23,24 F3=1,2,3,4,16,15,14,13 F4=4,5,6,7,19,18,17,16 F5=7,8,9,10,22,21,20,19 F6=10,11,12,1,13,24,23,22 Figure 37. Finite Element Topology Set (continued) 139 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 140 4.26 FINITE ELEMENT ENTITY (TYPE 136) 12. LSOT - Linear Solid Tetrahedron E1=1,2 E4=1,4 F1=1,2,3 E2=2,3 E5=2,4 F2=1,2,4 E3=3,1 E6=3,4 F3=2,3,4 F4=3,1,4 13. PSOT - Parabolic Solid Tetrahedron E1=1,2,3 E4=1,7,10 F1=1,2,3,4,5,6 E2=3,4,5 E5=3,8,10 F2=1,2,3,8,10,7 E3=5,6,1 E6=5,9,10 F3=3,4,5,9,10,8 F4=5,6,1,7,10,9 14. LSOW - Linear Solid Wedge E1=1,2 E4=4,5 E7=1,4 F1=1,2,3 E2=2,3 E5=5,6 E8=2,5 F2=4,5,6 E3=3,1 E6=6,4 E9=3,6 F3=1,2,5,4 F4=2,3,6,5 F5=3,1,4,6 15. PSOW - Parabolic Solid Wedge E1=1,2,3 E4=10,11,12 E7=1,7,10 E2=3,4,5 E5=12,13,14 E8=3,8,12 E3=5,6,1 E6=14,15,10 E9=5,9,14 F1=1,2,3,4,5,6 F2=10,11,12,13,14,15 F3=1,2,3,8,12,11,10,7 F4=3,4,5,9,14,13,12,8 F5=5,6,1,7,10,15,14,9 16. CSOW - Cubic Solid Wedge E1=1,2,3,4 E4=16,17,18,19 E7=1,10,13,16 E2=4,5,6,7 E5=19,20,21,22 E8=4,11,14,19 E3=7,8,9,1 E6=22,23,24,16 E9=7,12,15,22 F1=1,2,3,4,5,6,7,8,9 F2=16,17,18,19,20,21,22,23,24 F3=1,2,3,4,11,14,19,18,17,16,13,10 F4=4,5,6,7,12,15,22,21,20,19,14,11 F5=7,8,9,1,10,13,16,24,23,22,15,12 Figure 37. Finite Element Topology Set (continued) 141 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 142 4.26 FINITE ELEMENT ENTITY (TYPE 136) 17. LSO - Linear Solid E1=1,2 E5=5,6 E9=1,5 F1=1,2,3,4 E2=2,3 E6=6,7 E10=2,6 F2=5,6,7,8 E3=3,4 E7=7,8 E11=3,7 F3=1,2,6,5 E4=4,1 E8=8,5 E12=4,8 F4=2,3,7,6 F5=3,4,8,7 F6=4,1,5,8 18. PSO - Parabolic Solid E1=1,2,3 E7=17,18,19 E2=3,4,5 E8=19,20,13 E3=5,6,7 E9=1,9,13 E4=7,8,1 E10=3,10,15 E5=13,14,15 E11=5,11,17 E6=15,16,17 E12=7,12,19 F1=1,2,3,4,5,6,7,8 F2=13,14,15,16,17,18,19,20 F3=1,2,3,10,15,14,13,9 F4=3,4,5,11,17,16,15,10 F5=5,6,7,12,19,18,17,11 F6=7,8,1,9,13,20,19,12 19. CSO - Cubic Solid E1=1,2,3,4 E7=27,28,29,30 E2=4,5,6,7 E8=30,31,32,21 E3=7,8,9,10 E9=1,13,17,21 E4=10,11,12,1 E10=4,14,18,24 E5=21,22,23,24 E11=7,15, 19, 27 E6=24,25,26,27 E12=10,16,20,30 F1=1,2,3,4,5,6,7,8,9,10,11,12 F2=21,22,23,24,25,26,27,28,29,30,31,32 F3=1,2,3,4,14,18,24,23,22,21,17,13 F4=4,5,6,7,15,19,27,26,25,24,18,14 F5=7,8,9,10,16,20,30,29,28,27,19,15 F6=10,11,12,1,13,17,21,32,31,30,20,16 Figure 37. Finite Element Topology Set (continued) 143 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 144 4.26 FINITE ELEMENT ENTITY (TYPE 136) 20. ALLIN - Axisymmetric Linear Line E1=1,2 No Faces 21. APLIN - Axisymmetric Parabolic Line E1=1,2,3 No Faces 22. ACLIN - Axisymmetric Cubic Line E1=1,2,3,4 No Faces 23. ALTRIA - Axisymmetric Linear Triangle E1=1,2 E2=2,3 No Faces E3=3,1 24. APTRIA - Axisymmetric Parabolic Triangle E1=1,2,3 E2=3,4,5 No Faces E3=5,6,1 25. ALQUAD - Axisymmetric Linear Quadrilateral E1=1,2 E2=2,3 E3=3,4 No Faces E4=4,1 26. APQUAD - Axisymmetric Parabolic Quadrilateral E1=1,2,3 E2=3,4,5 E3=5,6,7 No Faces E4=7,8,1 Figure 37. Finite Element Topology Set (continued) 145 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 146 4.26 FINITE ELEMENT ENTITY (TYPE 136) 27. SPR - Spring No edges or faces 28. GSPR - Grounded Spring 29. DAMP - Damper 30. GDAMP - Grounded damper 31. MASS - Mass 32. RBDY - Rigid Body 33. TBEAM - three noded beam (no faces) E1 = 1,2 Figure 37. Finite Element Topology Set (continued) 147 4.26 FINITE ELEMENT ENTITY (TYPE 136) Figure 37. Finite Element Topology Set (continued) 148 4.27 NODAL DISPLACEMENT AND ROTATION ENTITY (TYPE 138) 4.27 Nodal Displacement and Rotation Entity (Type 138) The Nodal Displacement and Rotation Entity is used to communicate finite element postprocessing data. It contains the incremental displacements and rotations (expressed in radians) for each load case and each node in the model. It also contains a pointer to a General Note Entity (Type 212) for a description of the load cases. For each node it contains the node number identifier and the node DE pointer. The node number identifier is equivalent to the node number in the Directory Entry subscript field of the Node Entity (Type 134). 149 4.27 NODAL DISPLACEMENT AND ROTATION ENTITY (TYPE 138) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 138 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 138 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NC Integer Number of analysis cases 2 GP1 Pointer Pointer to the DE of the general note that describes the first analysis case .. . . . .. .. 1+NC GPNC Pointer Pointer to the DE of the general note that describes the last analysis case 2+NC NN Integer Number of nodes 3+NC NO1 Integer Node number identifier for first node 4+NC NP1 Pointer Pointer to the DE of the Node Directory Entry 5+NC X11 Real X-Incr. translation, first analysis case 6+NC Y11 Real Y-Incr. translation 7+NC Z11 Real Z-Incr. translation 8+NC RX11 Real RX-Incr. rotation 9+NC RY11 Real RY-Incr. rotation 10+NC RZ11 Real RZ-Incr. rotation .. . . . .. .. -1+7*NC X1NC Real X-Incr. translation, last analysis case 7*NC Y1NC Real Y-Incr. translation 1+7*NC Z1NC Real Z-Incr. translation 2+7*NC RX1NC Real RX-Incr. rotation .. . . . .. .. 3+NC+(-1+NN)*(2+6*NC) NONN Integer Node number identifier for NNth node 4+NC+(-1+NN)*(2+6*NC) NPNN Pointer Pointer to the DE of the Node Directory Entry 5+NC+(-1+NN)*(2+6*NC) XNN1 Real X-Incr. translation, first analysis case 6+NC+(-1+NN)*(2+6*NC) YNN1 Real Y- " " 7+NC+(-1+NN)*(2+6*NC) ZNN1 Real Z- " " 8+NC+(-1+NN)*(2+6*NC) RXNN1 Real RX-Incr. rotation, first analysis case 9+NC+(-1+NN)*(2+6*NC) RYNN1 Real RY- " " 10+NC+(-1+NN)*(2+6*NC) RZNN1 Real RZ- " " .. . . . .. .. -3+NC+NN*(2+6*NC) XNNNC Real X-Incr. translation, last analysis case -2+NC+NN*(2+6*NC) YNNNC Real Y- " " -1+NC+NN*(2+6*NC) ZNNNC Real Z- " " NC+NN*(2+6*NC) RXNNNC Real RX-Incr. rotation, last analysis case 150 4.27 NODAL DISPLACEMENT AND ROTATION ENTITY (TYPE 138) 1+NC+NN*(2+6*NC) RYNNNC Real RY- " " 2+NC+NN*(2+6*NC) RZNNNC Real RZ- " " Additional pointers as required (see Section 2.2.4.4.2). 151 4.28 OFFSET SURFACE ENTITY (TYPE 140) 4.28 Offset Surface Entity (Type 140) The offset surface is a surface defined in terms of an already existing surface. 1. Let S = S(u; v) be a regular surface defined by this specification parameterized and oriented by N (u; v), a differentiable field of unit normal vectors defined on the whole surface, and d a fixed nonzero real number. An offset surface to S is a parameterized surface S(u; v) given by: O(u; v) = S(u; v) + d * N (u; v); u1 u u2 v1 v v2: The base surface S(u; v) is referenced by a pointer in the parameter data section, while N (u; v) is found from S(u; v) as defined below. The value of d is provided as a parameter value in the parameter data section. 2. To determine which one of the two orientations of the orientable regular surface S(u; v) the offset surface will be used to define O, define N (u; v) = _@S=@u__x__@S=@v_____||@S=@u|:x @S=@v| In order to avoid confusion connecting the orientation of the base surface S(u; v), an additional offset indicator is included. That indicator, shown in Figure 38, consists of the vector (N x; N y; N z) defined by: (N x; N y; N z) = N (U m; V m)=||N (U m; V m)||: (This is the unit normal vector at the parameter values (U m; V m).) where, if the surface is bounded, U m = (u1 + u2)=2 and V m = (v1 + v2)=2 or, if the surface is unbounded, U m = 0:0 and V m = 0:0: This indicates the direction in which the offset distance, d, is measured positive at (U m; V m). CAUTION: The vector (N x; N y; N z) is just an indicator of the direction with respect to the base surface S(u; v) where the offset distance, d, is measured positively. This vector does not participate in the evaluation of the offset surface as is evident from the formula for O that defines the offset surface. 152 4.28 OFFSET SURFACE ENTITY (TYPE 140) Figure 38. Offset Surface in 3-D Euclidean Space 153 4.28 OFFSET SURFACE ENTITY (TYPE 140) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 140 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 140 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NX Real The x-coordinate of the offset indicator N (U m; V m) 2 NY Real The y-coordinate of the offset indicator N (U m; V m) 3 NZ Real The z-coordinate of the offset indicator N (U m; V m) 4 D Real The distance by which the surface is normally offset on the side of the offset indicator if d > 0 and on the opposite side if d < 0 5 DE Pointer Pointer to the DE of the surface entity to be offset Additional pointers as required (see Section 2.2.4.4.2). 154 4.29 BOUNDARY ENTITY (TYPE 141) 4.29 Boundary Entity (Type 141) ECO511 The definition of this entity can be found in Appendix G (see Section G.4). 155 4.30 CURVE ON A PARAMETRIC SURFACE ENTITY (TYPE 142) 4.30 Curve on a Parametric Surface Entity (Type 142) The Curve on a Parametric Surface Entity associates a given curve with a surface and identifies the curve as lying on the surface. Let S = S(u; v) = (x(u; v); y(u; v); z(u; v) ) be a regular parameterized surface whose domain is a rectangle defined by D = { (u; v) | u1 u u2 and v1 v v2}: Let B = B(t) be a curve defined by B(t) = (u(t); v(t)) for a t b taking its values in D. A curve C(t) on the surface S(u; v) is the composition of two mappings, S and B defined as follows: C(t) 4= S O B(t) 4= S(B(t)) 4= S(u(t); v(t)) 4= ( x(u(t); v(t)); y(u(t); v(t)); z(u(t); v(t)) ) a t b: The curve B lies in the two dimensional space which is the domain of the surface S. Therefore, the representation used for B which has been derived from a curve defined in this Specification must be two dimensional: the X and Y coordinates of this curve pointed to by BPTR are used. The Entity Use Flag (DE Field 9) of the entity B is set to 05, indicating that B is in the parameter space of the surface. Consequently, B cannot be scaled, and, if a transformation matrix is to be applied on B, it has to map it within the parameter space D in which it resides. A curve on a parametric surface is given by: (a) the mapping C and an indication that the curve lies on the surface S(u; v) (b) the mappings B and S whose composition gives the curve C. A curve on a surface may have been created in one of a number of various ways: (a) as the projection on the surface of a given curve in model space in a prescribed way, for example, parallel to a given fixed vector (b) as the intersection of two given surfaces (c) by a prescribed functional relation between the surface parameters "u" and "v" (d) by a special curve, such as a geodesic, emanating from a given point in a certain direction, a principal curve (line of curvature) emanating from a certain point, an asymptotic curve emanation from a certain point, an isoparametric curve for a given value, or any other kind of special curve. 156 4.30 CURVE ON A PARAMETRIC SURFACE ENTITY (TYPE 142) The Parameter Data section contains three pointers: (a) a pointer to the curve from which B(t) is derived (b) a pointer to the surface S(u; v) (c) a pointer to the mapping C(t). It also contains: (d) a flag to indicate how the curve was created (e) a flag to indicate which of the two alternate representations was preferred by the sending system. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 142 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????05** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 142 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 CRTN Integer Indicates the way the curve on the surface has been created: 0 = Unspecified 1 = Projection of a given curve on the surface 2 = Intersection of two surfaces 3 = Isoparametric curve, i.e., either a u-parametric or a v-parametric curve 2 SPTR Pointer Pointer to the DE of the surface on which the curve lies 3 BPTR Pointer Pointer to the DE of the entity that contains the definition of the curve B in the parametric space (u; v) of the surface S 4 CPTR Pointer Pointer to the DE of the curve C 5 PREF Integer Indicates preferred representation in the sending system: 0 = Unspecified 1 = S O B is preferred 2 = C is preferred 3 = C and S O B are equally preferred Additional pointers as required (see Section 2.2.4.4.2). 157 4.31 BOUNDED SURFACE ENTITY (TYPE 143) 4.31 Bounded Surface Entity (Type 143) ECO511 The definition of this entity can be found in Appendix G (see Section G.5). 158 4.32 TRIMMED (PARAMETRIC) SURFACE ENTITY (TYPE 144) 4.32 Trimmed (Parametric) Surface Entity (Type 144) A simple closed curve in the Euclidean plane divides the plane into two disjoint open connected components; one bounded and one unbounded. The bounded one is called the interior region to the curve (herein called `interior'). The unbounded component is called the exterior region to the curve (herein called `exterior'). The domain of the trimmed surface is defined as the common region of the interior of the outer boundary and the exterior of each of the inner boundaries and includes the boundary curves. Note that the trimmed surface has the same mapping S(u; v) as the original (untrimmed surface) but different domain. The curves that delineate either the outer or the inner boundary of the trimmed surface are curves on the surface S, and are to be exchanged by means of the Curve on a Parametric Surface Entity (Type 142). Let S(u; v) be a regular parameterized surface, whose untrimmed domain is a rectangle D consisting of those points (u; v) such that a u b and c v d for given constants a, b, c, and d with a < b and c < d. Assume that S takes its values in three dimensional Euclidean space so that it can be expressed as: 2 3 x(u; v) S = S(u; v) = 64 y(u; v) 75 for each ordered pair (u; v) in D. z(u; v) Also let the mapping S be subject to the following regularity conditions: - It has continuous normal vector in the interior of D. - It is one-to-one in D. - There are no singular points in D, i.e., the vectors of the first partial derivatives of S at any point in D are linearly independent. Two types of simple closed curves are utilized to define the domain of the trimmed (parametric) surface. 1. Outer boundary: there is exactly one. It lies in D, and in particular, it can be the boundary curve of D. 2. Inner boundary: there can be any number of them including zero. The set of inner boundaries satisfies two criteria: (a) The curves as well as their interiors are mutually disjoint. (b) Each curve lies in the interior of the outer boundary. If the outer boundary of the surface being defined is the boundary of D and there are no inner boundaries, the trimmed surface being defined is untrimmed. 159 4.32 TRIMMED (PARAMETRIC) SURFACE ENTITY (TYPE 144) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 144 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 144 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 PTS Pointer Pointer to the DE of the surface entity that is to be trimmed 2 N1 Integer 0 = the outer boundary is the boundary of D 1 = otherwise 3 N2 Integer This number indicates the number of simple closed curves which constitute the inner boundary of the trimmed surface. In case no inner boundary is introduced, this is set equal to zero. 4 PTO Pointer Pointer to the DE of the simple closed curve entity (Curve on a Parametric Surface Entity), that constitutes the outer boundary of the trimmed surface or zero 5 PTI1 Pointer Pointer to the DE of the first simple closed inner boundary curve entity (Curve on a Parametric Surface Entity) according to some arbitrary ordering of these entities .. . . . .. .. 4+N2 PTIN2 Pointer Pointer to the DE of the last simple closed inner boundary curve entity (Curve on a Parametric Surface Entity) Additional pointers as required (see Section 2.2.4.4.2). 160 4.33 NODAL RESULTS ENTITY (TYPE 146) 4.33 Nodal Results Entity (Type 146) The definition of this entity can be found in Appendix G (see Section G.6). 161 4.34 ELEMENT RESULTS ENTITY (TYPE 148) 4.34 Element Results Entity (Type 148) The definition of this entity can be found in Appendix G (see Section G.7). 162 4.35 BLOCK ENTITY (TYPE 150) 4.35 Block Entity (Type 150) The block is a rectangular parallelepiped, defined with one vertex at (X1,Y1,Z1) and three edges lying along the local +X, +Y, and +Z axes. The local X-axis is defined by the unit vector (I1,J1,K1) and the local Z-axis by (I2,J2,K2). The local Y-axis is derived by taking the cross product of Z into X. The resulting local system must be orthogonal, with (I1,J1,K1) values having the highest accuracy precedence. The block is specified by the positive lengths (LX,LY,LZ) along these axes as shown in Figure 39. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 150 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 150 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 LX Real Length in the local X-direction 2 LY Real Length in the local Y-direction 3 LZ Real Length in the local Z-direction 4 X1 Real Corner point coordinates (default (0,0,0)) 5 Y1 Real 6 Z1 Real 7 I1 Real Unit vector defining local X-axis (default (1,0,0)) 8 J1 Real 9 K1 Real 10 I2 Real Unit vector defining local Z-axis (default (0,0,1)) 11 J2 Real 12 K2 Real Must be orthogonal (see above) to (I1,J1,K1) Additional pointers as required (see Section 2.2.4.4.2). 163 4.35 BLOCK ENTITY (TYPE 150) Figure 39. Parameters of the CSG Block Entity 164 4.36 RIGHT ANGULAR WEDGE ENTITY (TYPE 152) 4.36 Right Angular Wedge Entity (Type 152) The right angular wedge is defined with one vertex at (X1,Y1,Z1) and three orthogonal edges lying along the local +X, +Y, and +Z axes. Figure 40 shows one example. A triangular/trapezoidal face lies in the local XY-plane. The local X-axis is defined by the unit vector (I1,J1,K1) and the local Z- axis by (I2,J2,K2). The local Y-axis is derived by taking the cross product of Z into X. The resulting local system must be orthogonal, with (I1,J1,K1) values having the highest accuracy precedence. The wedge is specified by the positive lengths LX, LY, LZ along these axes and the length LTX (where LTX | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 152 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 LX Real Length in the local X-direction at Y=0 2 LY Real Length in the local Y-direction 3 LZ Real Length in the local Z-direction 4 LTX Real Length in the local X-direction at distance LY from local X-axis 5 X1 Real Corner point coordinates (default (0,0,0)) 6 Y1 Real 7 Z1 Real 8 I1 Real Unit vector defining local X-axis (default (1,0,0)) 9 J1 Real 10 K1 Real 11 I2 Real Unit vector defining local Z-axis (default (0,0,1)) 12 J2 Real 13 K2 Real Must be orthogonal (see above) to (I1,J1,K1) Additional pointers as required (see Section 2.2.4.4.2). 165 4.36 RIGHT ANGULAR WEDGE ENTITY (TYPE 152) Figure 40. Parameters of the CSG Right Angular Wedge Entity 166 4.37 RIGHT CIRCULAR CYLINDER ENTITY (TYPE 154) 4.37 Right Circular Cylinder Entity (Type 154) The right circular cylinder is defined by the center of one circular cylinder face, a unit vector, a height, and a radius as shown in Figure 41. The faces are perpendicular to the unit vector in the axis direction (I1,J1,K1) and are circular discs with the specified radius R (where R>0). The height H (where H> 0) is the distance from the first circular face center in the positive direction of the unit vector to the second circular face center. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 154 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 154 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 H Real Cylinder height 2 R Real Cylinder radius 3 X1 Real First face center coordinates (default (0,0,0)) 4 Y1 Real 5 Z1 Real 6 I1 Real Unit vector in axis direction (default (0,0,1)) 7 J1 Real 8 K1 Real Additional pointers as required (see Section 2.2.4.4.2). 167 4.37 RIGHT CIRCULAR CYLINDER ENTITY (TYPE 154) Figure 41. Parameters of the CSG Right Circular Cylinder Entity 168 4.38 RIGHT CIRCULAR CONE FRUSTUM ENTITY (TYPE 156) 4.38 Right Circular Cone Frustum Entity (Type 156) The right circular cone frustum is defined by the center of the larger circular face of the frustum (X1,Y1,Z1), its radius R1, a unit vector in the axis direction (I1,J1,K1), a height H in this direction, and a second circular face with radius R2, where R1 > R2 0 and H > 0. As shown by Figure 42, the circular faces are perpendicular to the unit vector (I1,J1,K1). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 156 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 156 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 H Real Height 2 R1 Real Larger face radius 3 R2 Real Smaller face radius (zero for cone apex - default) 4 X1 Real Larger face center coordinates (default (0,0,0)) 5 Y1 Real 6 Z1 Real 7 I1 Real Unit vector in axis direction (default (0,0,1)) 8 J1 Real 9 K1 Real Additional pointers as required (see Section 2.2.4.4.2). 169 4.38 RIGHT CIRCULAR CONE FRUSTUM ENTITY (TYPE 156) Figure 42. Parameters of the CSG Right Circular Cone Frustum Entity 170 4.39 SPHERE ENTITY (TYPE 158) 4.39 Sphere Entity (Type 158) The sphere is defined with its center coordinates at (X1,Y1,Z1) and a radius R, where R > 0. Figure 43 shows one example. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 158 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 158 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 R Real Radius 2 X1 Real Center coordinates (default (0,0,0)) 3 Y1 Real 4 Z1 Real Additional pointers as required (see Section 2.2.4.4.2). 171 4.39 SPHERE ENTITY (TYPE 158) Figure 43. Parameters of the CSG Sphere Entity 172 4.40 TORUS ENTITY (TYPE 160) 4.40 Torus Entity (Type 160) The torus is the solid formed by revolving a circular disc about a specified coplanar axis. R1 is the distance from the axis to the center of the defining disc, and R2 is the radius of the defining disc, where R1 > R2 > 0. The torus is located with its center at (X1, Y1,Z1), and its axis is oriented in the (I1,J1,K1) direction, as shown in Figure 44. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 160 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 160 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 R1 Real Distance from center of torus to center of circular disc to be revolved (perpendicular to axis) 2 R2 Real Radius of circular disc 3 X1 Real Torus center coordinates (default (0,0,0)) 4 Y1 Real 5 Z1 Real 6 I1 Real Unit vector in axis direction (default (0,0,1)) 7 J1 Real 8 K1 Real Additional pointers as required (see Section 2.2.4.4.2). 173 4.40 TORUS ENTITY (TYPE 160) Figure 44. Parameters of the CSG Torus Entity 174 4.41 SOLID OF REVOLUTION ENTITY (TYPE 162) 4.41 Solid of Revolution Entity (Type 162) The solid of revolution is defined by revolving the area determined by a planar curve about a specified axis (which must be in the same plane) through a given fraction of full rotation F (0 < F 1), using the right hand rule (counterclockwise when viewed from the positive direction). The curve must not intersect itself. It must not cross the axis but may touch it. Figure 45 shows one example. Two form numbers are used to indicate how the area is determined from the curve. If the curve is closed, the form number shall be set to 1, and the area enclosed by the curve is used. If the curve is not closed and the form number = 0, projections are made from the ends of the curve to the rotation axis and the area enclosed by the curve, the projections, and the axis is used. In this case, the curve must be such that it does not intersect the projections, except at the end points. If the curve is not closed and the form number = 1, the curve is closed by adding a line connecting its end points and the area enclosed by the curve and the added line is used. In this case, the curve must not intersect the added line, except at the end points. Field 15 of the Directory Entry accommodates a form number. For this entity, the options are as follows: __________________________________ |__Form__|_______Meaning_______|__ | 0 |Curve closed to axis | |____1____|Curve_closed_to_itself_ | 175 4.41 SOLID OF REVOLUTION ENTITY (TYPE 162) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 162 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 162 | # | #; ) | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0, 1. Parameter Data Index__ Name____ Type___ Description___ 1 PTR Pointer Pointer to the DE of the curve entity to be revolved. The curve must be coplanar with rotation axis. 2 F Real Fraction of full rotation through which the curve entity will be revolved (0 < F 1) - counterclockwise when viewed from the positive direction; default 1 3 X1 Real Coordinates of point on axis (default (0,0,0)) 4 Y1 Real 5 Z1 Real 6 I1 Real Unit vector in axis direction (default (0,0,1)) 7 J1 Real 8 K1 Real Additional pointers as required (see Section 2.2.4.4.2). 176 4.41 SOLID OF REVOLUTION ENTITY (TYPE 162) Figure 45. Parameters of the CSG Solid of Revolution Entity 177 4.42 SOLID OF LINEAR EXTRUSION ENTITY (TYPE 164) 4.42 Solid of Linear Extrusion Entity (Type 164) The solid of linear extrusion is defined by translating an area determined by a planar curve. The curve as indicated by PTR in Figure 46 must be closed and nonintersecting. The direction of the translation is defined by a unit vector (I1,J1,K1) and the length of the translation is defined by L, where L > 0. The vector (I1,J1,K1) must not be coplanar with the closed curve. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 164 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 164 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 PTR Pointer Pointer to the DE of the closed curve entity 2 L Real Length of extrusion along the vector positive direction 3 I1 Real Unit vector specifying direction of extrusion (default (0,0,1)) 4 J1 Real 5 K1 Real Additional pointers as required (see Section 2.2.4.4.2). 178 4.42 SOLID OF LINEAR EXTRUSION ENTITY (TYPE 164) Figure 46. Parameters of the CSG Solid of Linear Extrusion Entity 179 4.43 ELLIPSOID ENTITY (TYPE 168) 4.43 Ellipsoid Entity (Type 168) The ellipsoid is a solid bounded by the surface defined by: _X2__ + _Y_2_ + _Z2__ = 1 LX2 LY 2 LZ2 when centered at the origin and aligned with its major axis (LX) in the X direction and with the minor axis (LZ) in the Z direction. A major axis of an ellipsoid can be found by choosing a point on the surface farthest from the center and constructing the line from that point through the center. The plane through the center perpendicular to this major axis intersects the surface of the ellipsoid in an ellipse. The other two axes of the ellipsoid are the axes of this ellipse. The ellipsoid is defined with its center at (X1,Y1,Z1) and its three axes coincident with the local X, Y, Z axes, as shown in Figure 47. The local X-axis is defined by the unit vector (I1,J1,K1) and the local Z-axis by (I2,J2,K2). The local Y-axis is derived by taking the cross product of Z into X. The resulting local system must be orthogonal, with (I1,J1,K1) values having the highest accuracy precedence. The ellipsoid is specified by positive lengths (LX, LY, and LZ respectively, where LX LY LZ > 0) from the local origin to the surface along the local +X, +Y, +Z axes. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 168 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 168 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 LX Real Length in the local X-direction 2 LY Real Length in the local Y-direction 3 LZ Real Length in the local Z-direction 4 X1 Real Coordinates of point in center of ellipsoid 5 Y1 Real (default (0,0,0)) 6 Z1 Real 7 I1 Real Unit vector defining local X-axis (Ellipsoid major axis) 8 J1 Real (default (1,0,0)) 9 K1 Real 10 I2 Real Unit vector defining local Z-axis (Ellipsoid minor axis) 11 J2 Real (default (0,0,1)) Must be orthogonal (see above) to (I1,J1,K1) 12 K2 Real Additional pointers as required (see Section 2.2.4.4.2). 180 4.43 ELLIPSOID ENTITY (TYPE 168) Figure 47. Parameters of the CSG Ellipsoid Entity 181 4.44 BOOLEAN TREE ENTITY (TYPE 180) 4.44 Boolean Tree Entity (Type 180) The Boolean tree describes a binary tree structure composed of regularized Boolean operations and operands, in postorder notation. A regularized Boolean operation is defined as the closure of the interior of the result_of a Boolean set operation. Specifically, denote the interior of a set X by Xo, the closure of X by X , and use [*; \*; and -* to denote the regularized Boolean operations union, intersection, and difference, respectively. Then: ___________ X [* Y = (X__[_Y_)o_ X \* Y = (X__\_Y_)o__ X -* Y = (X - Y )o Since the topological space under consideration is a 3-dimensional space, all lower dimensional enti- ties resulting from these operations will disappear. A discussion of regularized Boolean operations can be found in [TILO80]. All operations are assigned integers as follows: ___________________________ |__Integer__|Operation__|__ | 1 | Union | | 2 |Intersection | |_____3_____|_Difference___| Allowable operands are: o Primitive entities o Boolean Tree Entities o Solid Instance Entities The parameter data entries for the Boolean Tree Entity can be operation codes (integers) or pointers to operands. A positive (or unsigned) value in a parameter data entry implies an operation code; a negative value implies the absolute value is to be taken as a pointer to an operand. A transformation matrix may be pointed to by Field 7 of the DE to position the resulting solid in any desired manner. 182 4.44 BOOLEAN TREE ENTITY (TYPE 180) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 180 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 180 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Length of post-order notation, including operations and operands (N > 2) 2 PTR(1) Pointer Negated pointer to the DE of the first operand 3 PTR(2) Pointer Negated pointer to the DE of the second operand 4 PTR(3) Pointer Negated pointer to the DE of the third operand or or or IOP(1) Integer Integer for the first operation .. . . . .. .. N PTR(M) Pointer Negated pointer to the DE of the last operand or or or IOP(L-1) Integer Integer for next-to-last operation N+1 IOP(L) Integer Integer for last operation Notes: Parameters 2 and 3 will always be operands and thus will be negative numbers. As L is the number of operations, and M is the number of operands, N = L+M. Additional pointers as required (see Section 2.2.4.4.2). 183 4.44 BOOLEAN TREE ENTITY (TYPE 180) The following is an example of a Boolean tree composed of five operands and four operations. [* j Q Ordinary infix notation: j Q -* \* (A -* (B [* C )) [* (D \* E) @ @ @ @ Postorder notation: A [* D E A B C [* -* D E \* [* J JJ B C Parameters: 9 A B C 1 3 D E 2 1 (A, B, C, D, & E are negative values representing pointers to operands.) For the preceding example, the values are: PARAMETER VALUE 1 9 2 PTRA (negative) 3 PTRB (negative) 4 PTRC (negative) 5 1 6 3 7 PTRD (negative) 8 PTRE (negative) 9 2 10 1 Additional pointers as required (see Section 2.2.4.4.2). 184 4.45 SELECTED COMPONENT ENTITY (TYPE 182) 4.45 Selected Component Entity (Type 182) ECO505 The definition of this entity may be found in Appendix G (see Section G.8). 185 4.46 SOLID ASSEMBLY ENTITY (TYPE 184) 4.46 Solid Assembly Entity (Type 184) A solid assembly is a collection of items which possess a shared fixed geometric relationship. It differs from a union of the items in that each item retains its own structure, even if the items touch. The transformation matrices are applied to the items individually before a matrix pointed to in Field 7 of the DE is applied to the collection. A value of zero in the pointer field indicates the identity matrix. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 184 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????02?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 184 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of items 2 PTR1 Pointer Pointer to the DE of the first item .. . . . .. .. 1+N PTRN Pointer Pointer to the DE of the last item 2+N PTRM1 Pointer Pointer to the DE of the Transformation Matrix Entity for the first item .. . . . .. .. 1+2*N PTRMN Pointer Pointer to the DE of the Transformation Matrix Entity for the last item Additional pointers as required (see Section 2.2.4.4.2). 186 4.47 MANIFOLD SOLID B-REP OBJECT ENTITY (TYPE 186) 4.47 Manifold Solid B-Rep Object Entity (Type 186) ECO603 The definition of this entity can be found in Appendix G (see Section G.9). 187 4.48 PLANE SURFACE ENTITY (TYPE 190) 4.48 Plane Surface Entity (Type 190) ECO603 The definition of this entity can be found in Appendix G (see Section G.10). 188 4.49 RIGHT CIRCULAR CYLINDRICAL SURFACE ENTITY (TYPE 192) 4.49 Right Circular Cylindrical Surface Entity (Type 192) ECO603 The definition of this entity can be found in Appendix G (see Section G.11). 189 4.50 RIGHT CIRCULAR CONICAL SURFACE ENTITY (TYPE 194) 4.50 Right Circular Conical Surface Entity (Type 194) ECO603 The definition of this entity can be found in Appendix G (see Section G.12). 190 4.51 SPHERICAL SURFACE ENTITY (TYPE 196) 4.51 Spherical Surface Entity (Type 196) ECO603 The definition of this entity can be found in Appendix G (see Section G.13). 191 4.52 TOROIDAL SURFACE ENTITY (TYPE 198) 4.52 Toroidal Surface Entity (Type 198) ECO603 The definition of this entity can be found in Appendix G (see Section G.14). 192 4.53 ANGULAR DIMENSION ENTITY (TYPE 202) 4.53 Angular Dimension Entity (Type 202) An Angular Dimension Entity consists of a general note; zero, one, or two witness lines; two leaders; and an angle vertex point. Figure 48 indicates the construction used. Refer to Figure 49 for examples of angular dimensions. If two witness lines are used, each is contained in its own Copious Data Entity. Each leader consists of at least one circular arc segment with an arrowhead at one end. The leader pointers are ordered such that the first circular arc segment of the first leader is defined in a counterclockwise manner from arrowhead to terminate point, and the first circular arc segment of the second leader is defined in a clockwise manner. (Refer to Section 3.2.4 for information relating to the use of the term counterclockwise). Section 4.60 contains a discussion of multi-segment leaders. For those leaders in Angular Dimension Entities consisting of more than one segment, the first two segments are circular arcs with a center at the vertex point. The second circular arc segment is defined in the opposite direction from the first circular arc segment. Remaining segments, if any, are straight lines. Any leader segment in which the start point is the same as the terminate point is to be ignored. This convention arises to facilitate the definition of the second circular arc segment such as in the bottom leader in Figure 48. The first example in Figure 49 illustrates a leader with three segments. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 202 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 202 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEWIT1 Pointer Pointer to the DE of the first Witness Line Entity or zero 3 DEWIT2 Pointer Pointer to the DE of the second Witness Line Entity or zero 4 XT Real Coordinates of vertex point 5 YT Real 6 R Real Radius of Leader arcs 7 DEARRW1 Pointer Pointer to the DE of the first Leader Entity 8 DEARRW2 Pointer Pointer to the DE of the second Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 193 4.53 ANGULAR DIMENSION ENTITY (TYPE 202) Figure 48. Construction of Leaders for the Angular Dimension Entity. The radius of the arc in the leader must be calculated between the vertex point and the start point of the leader. 194 4.53 ANGULAR DIMENSION ENTITY (TYPE 202) Figure 49. Examples Defined Using the Angular Dimension Entity 195 4.54 CURVE DIMENSION ENTITY (TYPE 204) 4.54 Curve Dimension Entity (Type 204) ECO566 The definition of this entity may be found in Appendix G (see Section G.15). 196 4.55 DIAMETER DIMENSION ENTITY (TYPE 206) 4.55 Diameter Dimension Entity (Type 206) A Diameter Dimension Entity consists of a general note, one or two leaders, and an arc center point. Refer to Figure 50 for examples of the Diameter Dimension Entity. The arc center coordinates are used as reference in constructing the diameter dimension but have no effect on the dimension components. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 206 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 206 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEARRW1 Pointer Pointer to the DE of the first Leader Entity 3 DEARRW2 Pointer Pointer to the DE of the second Leader Entity or zero 4 XT Real Arc center coordinates 5 YT Real Additional pointers as required (see Section 2.2.4.4.2). 197 4.55 DIAMETER DIMENSION ENTITY (TYPE 206) Figure 50. Examples Defined Using the Diameter Dimension Entity 198 4.56 FLAG NOTE ENTITY (TYPE 208) 4.56 Flag Note Entity (Type 208) A Flag Note Entity is label information formatted as shown in Figure 51. The rotation angle and location of the lower left corner coordinate in the Flag Note Entity override the General Note Entity (Type 212) rotation angle and placement. The Flag Note Entity may be defined with or without leaders. The flag note is constructed from information defined in the General Note Entity. This data is the character box height and character box width. For this reason, no geometric definition is explicit within the definition of the Flag Note Entity. The box containing the text (as defined in the General Note Entity) shall be centered in the flag note box of size (H x L). The general note may consist of multiple text strings; however, they must share a common baseline. The number of characters shall not be greater than 10. Variables: H = Height CH = Character Height (from General Note) L = Length TW = Text Width (from General Note) T = Tip Length A = Rotation Angle (in radians) Formulas: H = 2 * CH L = TW + 0.4 * CH T = 0.5 * H / tan 350 Restrictions: H shall never be less than 0.3 in. L shall never be less than 0.6 in. Examples defined using the Flag Note Entity are shown in Figure 52. 199 4.56 FLAG NOTE ENTITY (TYPE 208) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 208 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 208 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 XT Real Lower left corner coordinate of the Flag 2 YT Real 3 ZT Real 4 A Real Rotation angle in radians 5 DENOTE Pointer Pointer to the DE of the General Note Entity 6 N Integer Number of Arrows (Leaders) or zero 7 DEARRW1 Pointer Pointer to the DE of the first associated Leader Entity .. . . . .. .. 6+N DEARRWN Pointer Pointer to the DE of the last associated Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 200 4.56 FLAG NOTE ENTITY (TYPE 208) Figure 51. Parameters of the Flag Note Entity. Note that the box outlined within the flag illustrates the bounds of the text and is not a subsymbol. 201 4.56 FLAG NOTE ENTITY (TYPE 208) Figure 52. Examples Defined Using the Flag Note Entity 202 4.57 GENERAL LABEL ENTITY (TYPE 210) 4.57 General Label Entity (Type 210) A General Label Entity consists of a general note with one or more associated leaders. Examples of general labels are shown in Figure 53. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 210 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 210 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the associated General Note Entity 2 N Integer Number of Leaders 3 DEARRW1 Pointer Pointer to the DE of the first associated Leader Entity .. . . . .. .. 2+N DEARRWN Pointer Pointer to the DE of the last associated Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 203 4.57 GENERAL LABEL ENTITY (TYPE 210) Figure 53. Examples Defined Using the General Label Entity 204 4.58 GENERAL NOTE ENTITY (TYPE 212) 4.58 General Note Entity (Type 212) A General Note Entity consists of one or more text strings. Each text string contains text, a starting point, a text size, and an angle of rotation of the text. Examples of general notes are shown in Figure 58. The font code (FC) is an integer specifying the desired character set and its associated display characteristics. Positive values are predefined fonts. Negative values point to implementor-defined fonts or modifications to a predefined font, through the use of the Text Font ECO532 Definition Entity (Type 310). The following font codes are defined: ____________________________________________________ |__FC__||_______________Description_______________|_ | 0 |Symbol Font (no longer recommended) | | 1 |Default Style for ASCII Character Set | | 2 |LeRoy | | 3 |Futura | | 6 |Comp 80 | | 12 |News Gothic | | 13 |Lightline Gothic | | 14 |Simplex Roman | | 17 |Century Schoolbook | | 18 |Helvetica | | 19 |OCR-B [ISO1073] (see Appendix G) | | 1001 |Symbol Font 1 | | 1002 |Symbol Font 2 | | 1003 |Drafting Font | |__2001__|Kanji_[JIS6226]_(see_Appendix_G)_______|__ FC 0 specifies an old symbol font and should no longer be used. Figure F1 in Appendix F is a mapping symbol definition for FC 0. FC 1 does not specify a defined display. Use of Font 1 implies that the receiving system may use any font which displays the appropriate ASCII format characters. The intent of this font is for usage when the actual display of the characters is not critical for the application. FC 19 specifies a symbol font shown in Figure 54 and is defined in Appendix G (see Section G.16). Display symbols must be represented using 7-bit ASCII codes with FC-values in the 1000 series as ECO531 shown in Figures 55, 56 and 57. The 7-bit ASCII control characters, i.e., hexadecimal 00 through 1F and hexadecimal 7F, may not be used to represent display symbols. They do not specify a character display font. FC 2001 specifies a symbol font defined in Appendix G (see Section G.16). ECO547 If the predefined font codes are not sufficient to describe a desired character set or display charac- teristic, a Text Font Definition Entity (Type 310) may be used to define the font. If a text font definition is being used, the negative of the pointer value for the directory entry of the Text Font Definition Entity is placed in the font code (FC) parameter. The use of the values WT, HT, SL, A, and text start point are shown in Figure 59. Table 5 provides names for the graphical characters generated for each valid FC. 205 4.58 GENERAL NOTE ENTITY (TYPE 212) Within definition space, the parameters for the text block are applied in the following order (see Figure 60): 1. Define the box height (HT) and box width (WT). The rotate internal text flag indicates whether the text box is filled with horizontal text or vertical text. The box width is measured from the start of the left-most (first) text charac- ter/symbol in the positive XT direction along the text base line, and extends to the end of the right-most (last) character/symbol, extending N characters/symbols and N-1 intercharacter spaces. The box height is measured in the positive YT direction and is the height of capital letters. It is equivalent to the symbol "h" used in Appendix C of [ANSI82]. Special symbols, such as those appearing in Appendix C of [ANSI82], which exceed "h" in height are centered vertically. Descenders and portions of symbols exceeding "h" extend outside the lower and/or ECO549 upper borders of the box (see Figure 61). The box height and width are measured before the rotation angle (A) is applied. The text start point is defined as the lower left corner of the ECO579 first character/symbol box. 2. The slant angle is then applied to each individual character. For horizontal text, it is measured from the XT axis in a counterclockwise direction. For vertical text, the slant angle is measured from the YT axis. 3. The rotation angle is then applied to the text block. This rotation is applied in a counter- clockwise direction about the text start point. The plane of rotation is the XT, YT plane at the depth ZSn (where ZSn is the value given for the text start point). 4. The mirror operation is performed next. The value 1 indicates the mirror axis is the (rotated) line perpendicular to the text base line and through the text start point. The value 2 indicates the mirror axis is the (rotated) text base line. Finally, the Transformation Matrix Entity is used to specify the relative position of definition space within model space. The number of characters (NCn) must always be equal to the character count in its corresponding text string (TEXTn). 206 4.58 GENERAL NOTE ENTITY (TYPE 212) ________________________________________________________|| | | | | | | | The definition of this font can be found | | | | in Appendix G (see Section G.16). | | | | | |_______________________________________________________| Figure 54. General Note Font Specified by FC 19 207 4.58 GENERAL NOTE ENTITY (TYPE 212) ________________________________________________________________________________________________ | | BL | | |0 | 0 | | @ | @ | | P | P | | | | |p | iP | | |_|_________|____|_|_____|______|_|______|______|_|_____|_______|_|_____|_______|_|_____|______|_| | | ! |! | |1 | 1 | | A | A | | Q | Q | | a | ___ | |q | C|_ | | |_|________|_____|_|____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | " |" | | 2 | 2 | | B | B | | R | R | | b | _|_|_|||r | if | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_|_ | | # |# | | 3 | 3 | | C | C | | S | S | | c | ___ | |s | iS | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_|_ | | $ |$ | | 4 | 4 | | D | D | | T | T | | d | |_|_ | |t | ___||||| |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | % |% | | 5 | 5 | | E | E | | U | U | | e | i | |u | i| | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | & |& | | 6 | 6 | | F | F | | V | V | | f | | |v | ___|A| | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | | | | 7 | 7 | | G | G | | W | W | | g | f | |w | 3| | | |_|_______|____|_|______|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | ( |( | | 8 | 8 | | H | H | | X | X | | h | % | | x | 4| | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_|_ | | ) |) | | 9 | 9 | | I | I | | Y | Y | | i | _____| |y | @@ | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | * |* | | : | : | |J | J | | Z | Z | | j | _f|_ | |z | Y | | |_|________|____|_|_____|________|_|____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | + |+ | | ; | ; | |K | K | | [ | [ | |k | |_| | |{ | { | | |_|________|____|_|_____|________|_|____|______|_|______|________|_|____|_______|_|____|_______|_| | | , | , | |< | < | | L | L | | " | " | | l | ? | | _ | I | | |_|________|______|_|____|______|_|_____|_______|_|_____|______|_|______|______|_|_____|________| | | | - |- | |= | = | | M | M | | ] | ] | |m | Mi | |} | } | | |_|________|_____|_|____|_______|_|_____|______|_|______|________|_|____|_______|_|____|_______|_| | | . | . | |> | > | | N | N | | ^ | ^ | | n | i | |" | " | | |_|________|______|_|____|______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | / |/ | | ? | ? | | O | O | | _ | _ | | o | O | | |_|________|____|_|_____|_______|_|_____|______|_|______|_______|_|_____|______|_| Figure 55. General Note Font Specified by FC 1001 208 4.58 GENERAL NOTE ENTITY (TYPE 212) ________________________________________________________________________________________________ | | BL | | |0 | 0 | | @ | @ | | P | P | | | | |p | " | | |_|_________|____|_|_____|______|_|______|______|_|_____|_______|_|_____|_______|_|_____|______|_|_ | | ! |! | |1 | 1 | | A | A | | Q | Q | | a | ___@@| |q | # | | |_|________|_____|_|____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | " |" | | 2 | 2 | | B | B | | R | R | | b | | | r | ! | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_____|_|______|______|_| | | # | | | 3 | 3 | | C | C | | S | S | | c | | | s | | | |_|________|___|_|______|_______|_|_____|______|_|______|______|_|______|_____|_|______|______|_| | | $ | | | 4 | 4 | | D | D | | T | T | | d | | | t | OE | | |_|________|___|_|______|_______|_|_____|______|_|______|______|_|______|_____|_|______|________| | | | % |% | | 5 | 5 | | E | E | | U | U | | e | 4 | | u | | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|______|_|_____|______|_| | | & |& | | 6 | 6 | | F | F | | V | V | | f | p | |v | fl | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|________| | | | | | | 7 | 7 | | G | G | | W | W | | g | x | | w | | | |_|_______|____|_|______|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | ( |( | | 8 | 8 | | H | H | | X | X | | h | | | x | ! | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_____|_|______|_______|_| | | ) |) | | 9 | 9 | | I | I | | Y | Y | | i | 6= | |y | | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|______|_|R | | * |* | | : | : | |J | J | | Z | Z | | j | | |z | ff | | |_|________|____|_|_____|________|_|____|_______|_|_____|______|_|______|_______|_|____|________| | | | + |+ | | ; | ; | |K | K | | [ | [ | |k | | | { | ffi | | |_|________|____|_|_____|________|_|____|______|_|______|________|_|____|_____|_|______|________ | | | | , | , | |< | < | | L | L | | " | " | | l | _ | | _ | | | |_|________|______|_|____|______|_|_____|_______|_|_____|______|_|______|______|_|_____|______|_| | | - |- | |= | = | | M | M | | ] | ] | |m | ^ | | } | ss | | |_|________|_____|_|____|_______|_|_____|______|_|______|________|_|____|______|_|_____|________| | | | . | . | |> | > | | N | N | | ^ | ^ | | n | | | " | ___ | | |_|________|______|_|____|______|_|_____|______|_|______|______|_|______|_____|_|______|_______|_|P | | / |/ | | ? | ? | | O | O | | _ | _ | | o | | | |_|________|____|_|_____|_______|_|_____|______|_|______|_______|_|_____|_______| | Figure 56. General Note Font Specified by FC 1002 209 4.58 GENERAL NOTE ENTITY (TYPE 212) ________________________________________________________________________________________________ | | BL | | |0 | 0 | | @ | @ | | P | P | | | | |p | iP | | |_|_________|____|_|_____|______|_|______|______|_|_____|_______|_|_____|_______|_|_____|______|_| | | ! |! | |1 | 1 | | A | A | | Q | Q | | a | ___ | |q | C|_ | | |_|________|_____|_|____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | " |" | | 2 | 2 | | B | B | | R | R | | b | ? | | r | if | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_|_ | | # |# | | 3 | 3 | | C | C | | S | S | | c | ___ | |s | iS | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | $ |$ | | 4 | 4 | | D | D | | T | T | | d | |_|_ | |t | __ | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_| | | % |% | | 5 | 5 | | E | E | | U | U | | e | i | |u | ___ | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | & |& | | 6 | 6 | | F | F | | V | V | | f | | |v | ___||| | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | ' | | | 7 | 7 | | G | G | | W | W | | g | f | |w | _ | | |_|________|___|_|______|_______|_|_____|______|_|______|______|_|______|_______|_|____|_______|_|_ | | ( |( | | 8 | 8 | | H | H | | X | X | | h | % | | x | # | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | ) |) | | 9 | 9 | | I | I | | Y | Y | | i | _____| |y | _|>_ | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | * |* | | : | : | |J | J | | Z | Z | | j | _f|_ | |z | ___|@@|| |_|________|____|_|_____|________|_|____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | + |+ | | ; | ; | |K | K | | [ | [ | |k | |_| | |{ | { | | |_|________|____|_|_____|________|_|____|______|_|______|________|_|____|_______|_|____|_______|_| | | , | , | |< | < | | L | L | | " | " | | l | Li | |_ | I | | |_|________|______|_|____|______|_|_____|_______|_|_____|______|_|______|_______|_|____|________| | | | - |- | |= | = | | M | M | | ] | ] | |m | Mi | |} | } | | |_|________|_____|_|____|_______|_|_____|______|_|______|________|_|____|_______|_|____|_______|_| | | . | . | |> | > | | N | N | | ^ | _ | | n | i | |" | | | |_|________|______|_|____|______|_|_____|______|_|______|______|_|______|_______|_|____|______|_|_ | | / |/ | | ? | ? | | O | O | | _ | _ | | o | ___||| | |_|________|____|_|_____|_______|_|_____|______|_|______|_______|_|_____|_______| | Figure 57. General Note Font Specified by FC 1003 210 4.58 GENERAL NOTE ENTITY (TYPE 212) Table 5. Character Names for the Symbol and Drafting Fonts _______________________________________________________________ | | ||____________FCy____________| |_________Name_________||__Symbol_||__1_|_|1001_||_1002__|1003_ | | Space | | 20 | 20 | 20 | 20 | | Exclamation mark | ! |21 | 21 | 21 | 21 | | Quotation marks | " | 22 | 22 | 22 | 22 | | Pound sign | # | 23 | 23 | | 23 | | Plus/minus | | | | 23 | 60 | | Dollar sign | $O | 24 | 24 | | 24 | | Degree symbol | | | | 24 | 7E | | Percent sign | % | 25 | 25 | 25 | 25 | | Ampersand | & | 26 | 26 | 26 | 26 | | Apostrophe | | 27 | 27 | 27 | 27 | | Left parenthesis | ( | 28 | 28 | 28 | 28 | | Right parenthesis | ) | 29 | 29 | 29 | 29 | | Asterisk | * | 2A | 2A | 2A | 2A | | Plus sign | + | 2B | 2B | 2B | 2B | | Comma | , |2C | 2C | 2C | 2C | | Minus sign/hyphen | - |2D | 2D | 2D | 2D | | Period | . |2E | 2E | 2E | 2E | | Slash | / | 2F | 2F | 2F | 2F | | Numeric 0 | 0 | 30 | 30 | 30 | 30 | | Numeric 1 | 1 | 31 | 31 | 31 | 31 | | Numeric 2 | 2 | 32 | 32 | 32 | 32 | | Numeric 3 | 3 | 33 | 33 | 33 | 33 | | Numeric 4 | 4 | 34 | 34 | 34 | 34 | | Numeric 5 | 5 | 35 | 35 | 35 | 35 | | Numeric 6 | 6 | 36 | 36 | 36 | 36 | | Numeric 7 | 7 | 37 | 37 | 37 | 37 | | Numeric 8 | 8 | 38 | 38 | 38 | 38 | | Numeric 9 | 9 | 39 | 39 | 39 | 39 | | Colon | : |3A | 3A | 3A | 3A | | Semi-colon | ; |3B | 3B | 3B | 3B | | Less than | < | 3C | 3C | 3C | 3C | | Equal sign | = | 3D | 3D | 3D | 3D | | Greater than | > | 3E | 3E | 3E | 3E | | Question mark | ? | 3F | 3F | 3F | 3F | | Commercial at | @ | 40 | 40 | 40 | 40 | | Upper case letter A | A | 41 | 41 | 41 | 41 | | Upper case letter B | B | 42 | 42 | 42 | 42 | | Upper case letter C | C | 43 | 43 | 43 | 43 | | Upper case letter D | D | 44 | 44 | 44 | 44 | | Upper case letter E | E | 45 | 45 | 45 | 45 | | Upper case letter F | F | 46 | 46 | 46 | 46 | | Upper case letter G | G | 47 | 47 | 47 | 47 | |__Upper_case_letter_H__|___H_____|_48__|__48___|_48___|__48___| yEntries for each FC are hexadecimal ASCII equivalent 211 4.58 GENERAL NOTE ENTITY (TYPE 212) Table 5. Character Names for the Symbol and Drafting Fonts (continued) _________________________________________________________________ | | ||____________FCy____________| |__________Name__________||__Symbol_||__1_|_|1001_||_1002__|1003_ | | Upper case letter I | I |49 | 49 | 49 | 49 | | Upper case letter J | J |4A | 4A | 4A | 4A | | Upper case letter K | K | 4B | 4B | 4B | 4B | | Upper case letter L | L | 4C | 4C | 4C | 4C | | Upper case letter M | M | 4D | 4D | 4D | 4D | | Upper case letter N | N | 4E | 4E | 4E | 4E | | Upper case letter O | O | 4F | 4F | 4F | 4F | | Upper case letter P | P | 50 | 50 | 50 | 50 | | Upper case letter Q | Q | 51 | 51 | 51 | 51 | | Upper case letter R | R | 52 | 52 | 52 | 52 | | Upper case letter S | S | 53 | 53 | 53 | 53 | | Upper case letter T | T | 54 | 54 | 54 | 54 | | Upper case letter U | U | 55 | 55 | 55 | 55 | | Upper case letter V | V | 56 | 56 | 56 | 56 | | Upper case letter W | W | 57 | 57 | 57 | 57 | | Upper case letter X | X | 58 | 58 | 58 | 58 | | Upper case letter Y | Y | 59 | 59 | 59 | 59 | | Upper case letter Z | Z | 5A | 5A | 5A | 5A | | Left bracket | [ |5B | 5B | 5B | 5B | | Backward slash | \ |5C | 5C | 5C | 5C | | Right bracket | ] |5D | 5D | 5D | 5D | | Caret | ^ | 5E | 5E | 5E | | | Arc length | _ | | | | 5E | | Underscore | ___ | 5F | 5F | 5F | 5F | | Reverse quote | | 60 | 60 | 60 | | | Lower case letter a | a |61 | | | | | Angularity | ____ | | 61 | | 61 | | Marker/symbol | ___@@ | | | 61 | | | Lower case letter b | b_ | 62 | | | | | Marker/symbol | _|_|| | | 62 | | | | Division symbol | | | | 62 | | | Perpendicularity | ? | | | | 62 | | Lower case letter c | c__ |63 | | | | | Flatness | ___ | | 63 | | 63 | | Less than or equal | | | | 63 | | | Lower case letter d | d_ | 64 | | | | | Profile of a surface | |_|_ | | 64 | | 64 | | Greater than or equal | | | | 64 | | | Lower case letter e | ei |65 | | | | | Circularity | | | 65 | | 65 | |__Marker/symbol________|_____4____|______|_______|__65___|______| yEntries for each FC are hexadecimal ASCII equivalent 212 4.58 GENERAL NOTE ENTITY (TYPE 212) Table 5. Character Names for the Symbol and Drafting Fonts (continued) ECO605 _________________________________________________________________________ | | ||____________FCy____________| |______________Name______________||__Symbol_||__1_|_|1001|_|1002__|1003__| | Lower case letter f | f | 66 | | | | | Parallelism | p | | 66 | | 66 | | Radical | | | | 66 | | | Lower case letter g | gf | 67 | | | | | Cylindricity | | | 67 | | 67 | | Cross product | x | | | 67 | | | Lower case letter h | h | 68 | | | | | Circular Runout | % | | 68 | | 68 | | Congruence | | | | 68 | | | Lower case letter i | i___ | 69 | | | | | Symmetry | __ | | 69 | | 69 | | Not equal | 6= | | | 69 | | | Lower case letter j | jf_ |6A | | | | | Position | R| | | 6A | | 6A | | Integral | | | | 6A | | | Lower case letter k | k_ | 6B | | | | | Profile of a line | | | | | 6B | | 6B | | Implication | | | | 6B | | | Lower case letter l | l | 6C | | | | | Perpendicularity | ? | | 6C | | | | Union | _i | | | 6C | | | Least material condition | L | | | | 6C | | Lower case letter m | mi |6D | | | | | Maximum material condition | M | | 6D | | 6D | | Intersection | ^ | | | 6D | | | Lower case letter n | ni | 6E | | | | | Diameter | | | 6E | | 6E | | Approximately equal | | | | 6E | | | Lower case letter o | o | 6F | | | | | All around applicability | PO | | 6F | | | | Greek letter sigma (Sum) | | | | 6F | | | Square (shape) | 2 | | | | 6F | | Lower case letter p | pi | 70 | | | | | Projected tolerance zone | P | | 70 | | 70 | | Up arrow | " | | | 70 | | | Lower case letter q | q | 71 | | | | | Centerline | C|_ | | 71 | | 71 | | Down arrow | # | | | 71 | | | Lower case letter r | rif | 72 | | | | | Concentricity | | | 72 | | 72 | |__Right_arrow____________________|___!____|______|______|__72___|_______| yEntries for Each FC are hexadecimal ASCII equivalent 213 4.58 GENERAL NOTE ENTITY (TYPE 212) Table 5. Character Names for the Symbol and Drafting Fonts (continued) _____________________________________________________________________ | | ||____________FCy____________| |____________Name____________||__Symbol_||__1_|_|1001|_|1002__|1003__| | Lower case letter s | si | 73 | | | | | Regardless of feature size | S | | 73 | | 73 | | Left arrow | | | | 73 | | | Lower case letter t | _t_| | 74 | | | | | Marker/symbol | ___|| | | 74 | | | | Greek letter phi | OE | | | 74 | | | Total runout | __ | | | | 74 | | Lower case letter u | ui| | 75 | | | | | Marker/symbol | | | 75 | | | | Greek letter theta | ___ | | | 75 | | | Straightness | | | | | 75 | | Lower case letter v | v| | 76 | | | | | Marker/symbol | ___A | | 76 | | | | Greek letter gamma | fl | | | 76 | | | Counterbore | ___|| | | | | 76 | | Lower case letter w | w | 77 | | | | | Marker/symbol | 3| | | 77 | | | | Greek letter psi | | | | 77 | | | Countersink | _ | | | | 77 | | Lower case letter x | x | 78 | | | | | Marker/symbol | 4| | | 78 | | | | Greek letter omega | _!_ | | | 78 | | | Depth | # | | | | 78 | | Lower case letter y | _y_ | 79 | | | | | Marker/symbol | @@ | | 79 | | | | Greek letter lambda | | | | 79 | | | Conical taper | _|>_ | | | | 79 | | Lower case letter z | z |7A | | | | | Marker/symbol | Y | | 7A | | | | Greek letter alpha | ff | | | 7A | | | Slope | ___|@@ | | | | 7A | | Left brace | { |7B | 7B | | 7B | | Greek letter delta | ffi | | | 7B | | | Vertical bar | | |7C | 7C | | 7C | | Greek letter mu | | | | 7C | | | Right brace | } |7D | 7D | | 7D | | Greek letter pi | ss | | | 7D | | | Tilde | " |7E | 7E | | | |__Overscore__________________|_________|_____|______|__7E___|_______| yEntries for each FC are hexadecimal ASCII equivalent 214 4.58 GENERAL NOTE ENTITY (TYPE 212) Figure 58. Examples Defined Using the General Note Entity 215 4.58 GENERAL NOTE ENTITY (TYPE 212) Figure 59. General Note Text Construction 216 4.58 GENERAL NOTE ENTITY (TYPE 212) Figure 60. General Note Example of Text Operations 217 4.58 GENERAL NOTE ENTITY (TYPE 212) Figure 61. Examples of Drafting Symbols That Exceed Text Box Height 218 4.58 GENERAL NOTE ENTITY (TYPE 212) The graphical representation and recreation of notes with a special structure are handled by the use of the Form Number in Field 15 of the Directory Entry for this entity. A system to accommodate these notes is outlined below. Any strings after those specified by the form number are consid- ered additional, appended strings that are not related in any particular manner to the previously referenced strings. In the event that a string necessary for the defined structure is not present in the originating system's note, a null string (see NULL STRING in Appendix K) shall be inserted in the General Note Entity to take the place of the nonexistent string to maintain the structure of the data. Notes that contain fractional notation will be represented as mixed numerals. This is done through the use of four consecutive strings representing the whole number, the numerator, the denominator, and the divisor bar. These are examples of the divisor bar string: 1H/ 1H- 2H-- 1H_ The following form numbers for the general note are used to maintain the graphical representation of the originating system's note: Form 0: Simple Note (default) - A general note of one or more strings such that a text string is not related in any manner to another string in the same General Note Entity. Form 1: Dual Stack - A general note of two or more strings where the first two are related in a manner such that they are both left justified and the second string is displayed "below" the first. xxxxxx yyyyy Form 2: Imbedded Font Change - A general note of two or more strings that is intended as a single string but was divided to accommodate a font change in the string. xxxxxx xxxx Form 3: Superscript - A general note of two or more strings where the second string is a superscript of the first string. xxx yyy Form 4: Subscript - A general note of two or more strings where the second string is a subscript of the first string. xxx yyy 219 4.58 GENERAL NOTE ENTITY (TYPE 212) Form 5: Super-/Sub-script - A general note of three or more strings where the second string is a superscript of the first string and the third string is a subscript of the first string. xxx yyyzzz Form 6: Multiple Stack/Left Justified - A general note where all strings are left justified to a common margin. These strings originated as a "paragraphed" note. xxxxxxxxxx yyyyyyy zzzzzzzzzzz Form 7: Multiple Stack/Center Justified - A general note where all strings are center justified to a common axis. xxxxxxxx yyyy zzzzzzzz Form 8: Multiple Stack/Right Justified - A general note where all strings are right justified to a common margin. xxxxxxxxxx yyyyy zzzzzzzz Form 100: Simple Fraction - A general note of four or more strings where the first four strings define a mixed numeral as defined previously. yy xx -- zz Form 101: Dual Stack Fraction - A general note of eight or more strings which represent two mixed numerals as defined previously. These mixed numerals are related such that the fifth through the eighth strings are displayed below the first through the fourth strings respec- tively. 220 4.58 GENERAL NOTE ENTITY (TYPE 212) yy xx -- zz jj ii -- kk Form 102: Imbedded Font Change/Double Fraction - This general note originated as a single string but was split to accommodate a font change for a special character in the fifth string. This is a general note of nine or more strings where the first and sixth strings represent the whole number string of a mixed numeral as defined previously. The fifth string is a character (or characters) that was set apart to accommodate the font change. yy jj xx -- - ii -- zz kk Form 105: Super-/Subscript Fraction - A general note of twelve or more strings where the first, fifth, and ninth strings represent the whole number string of a mixed numeral as defined previously. The second and third mixed numerals are the superscript and subscript respectively of the first mixed numeral. 0 1 jj @ ii -- A 0 1 kk yy @ xx -- A zz 0 1 ss @ rr -- A tt Note: The large parentheses are added to help convey the intent of Form 105. They are not part of the General Note. 221 4.58 GENERAL NOTE ENTITY (TYPE 212) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 212 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 212 | # | #; ) | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0-8, 100-102, 105. Parameter Data Index__ Name____ Type___ Description___ 1 NS Integer Number of text strings in General Note 2 NC1 Integer Number of characters in first string (TEXT1) or zero. The num- ber of characters (NCn) must always be equal to the character count of its corresponding text string (TEXTn) 3 WT1 Real Box width 4 HT1 Real Box height 5 FC1 Integer Font code (default = 1) or Pointer Pointer to the DE of the Text Font Definition Entity if negative 6 SL1 Real Slant angle of TEXT1 in radians (ss=2 is the value for no slant angle and is the default value) 7 A1 Real Rotation angle in radians for TEXT1 8 M1 Integer Mirror flag: 0 = no mirroring 1 = mirror axis is perpendicular to text base line 2 = mirror axis is text base line 9 VH1 Integer Rotate internal text flag: 0 = text horizontal 1 = text vertical 10 XS1 Real First text start point 11 YS1 Real 12 ZS1 Real Z depth from XT, YT plane 13 TEXT1 String First text string 14 NC2 Integer Number of characters in second text string .. . . . .. .. -10+12*NS NCNS Integer Number of characters in last text string .. . . . .. .. 1+12*NS TEXTNS String Last text string Additional pointers as required (see Section 2.2.4.4.2). 222 4.59 NEW GENERAL NOTE ENTITY (TYPE 213) 4.59 New General Note Entity (Type 213) ECO567 The definition of this entity may be found in Appendix G (see Section G.17). 223 4.60 LEADER (ARROW) ENTITY (TYPE 214) 4.60 Leader (Arrow) Entity (Type 214) A Leader (Arrow) Entity consists of one or more line segments except when the leader is part of an angular dimension (see Section 4.53). The first segment begins with an arrowhead. Remaining segments successively link to a presumed text item. An individual segment is assumed to extend from the end point of its predecessor in the segment list to its defined end point. Examples of leaders are shown in Figure 62. In the use of angular, diameter, and linear dimension, there are instances where the text is exterior to the line or arc lying between the two arrows. In these situations, it remains the case that the appearance of two arrows implies the use of two leaders. These are formed by dividing the line or arc lying between the two arrows into two nonoverlapping segments. Refer to Figure 63. Some leaders (for example, the leader involved with the radius dimension in Figure 63) give the appearance of locating an arrow interior to a segment. There are two overlapping segments. The first segment begins at the arrow and, in the radius dimension example, ends at the center of the arc or circle being dimensioned. The second segment then retraces the first in the opposite direction and extends it. Leaders of this type for other types of dimensions are constructed similarly. For cases involving angular dimension, the first two segments are arcs. ECO584 There are twelve arrowhead types defined (see Figure 64) and selection is made by entering the form number in Directory Entry Field 15. 224 4.60 LEADER (ARROW) ENTITY (TYPE 214) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 214 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 214 | # | #; ) | # | # | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Valid values of the Form Number are 1-12. Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of segments 2 AD1 Real Arrowhead height 3 AD2 Real Arrowhead width 4 ZT Real Z depth 5 XH Real Arrowhead coordinates 6 YH Real 7 X1 Real First segment tail coordinate pair 8 Y1 Real .. . . . .. .. 5+2*N XN Real Last segment tail coordinate pair 6+2*N YN Real Additional pointers as required (see Section 2.2.4.4.2). 225 4.60 LEADER (ARROW) ENTITY (TYPE 214) Figure 62. Examples Defined Using the Leader Entity 226 4.60 LEADER (ARROW) ENTITY (TYPE 214) Figure 63. Structure of Leaders Internal to a Dimension 227 4.60 LEADER (ARROW) ENTITY (TYPE 214) Figure 64. Definition of Arrowhead Types for the Leader (Arrow) Entity 228 4.61 LINEAR DIMENSION ENTITY (TYPE 216) 4.61 Linear Dimension Entity (Type 216) A Linear Dimension Entity consists of a general note; two leaders; and zero, one or two witness lines. Refer to Figure 65 for examples of linear dimensions. Field 15 of the Directory Entry Section accomodates a form number. For this entity, the form ECO512 number is used to maintain the nature of the dimension on the originating system. The definition of the form numbers can be found in Appendix G (see Section G.18). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 216 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 216 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEARRW1 Pointer Pointer to the DE of the first Leader Entity 3 DEARRW2 Pointer Pointer to the DE of the second Leader Entity 4 DEWIT1 Pointer Pointer to the DE of the first Witness Line Entity, or zero if not defined 5 DEWIT2 Pointer Pointer to the DE of the second Witness Line Entity, or zero if not defined Additional pointers as required (see Section 2.2.4.4.2). 229 4.61 LINEAR DIMENSION ENTITY (TYPE 216) Figure 65. Examples Defined Using Form 0 of the Linear Dimension Entity 230 4.62 ORDINATE DIMENSION ENTITY (TYPE 218) 4.62 Ordinate Dimension Entity (Type 218) The Ordinate Dimension Entity is used to indicate dimensions from a common base line. Dimen- sioning is only permitted along the XT or YT axis. An Ordinate Dimension Entity consists of a general note and a witness line or leader. The values stored are pointers to the Directory Entry for the associated General Note and Witness Line or Leader Entities. A second form of the Ordinate Dimension Entity is defined in Appendix G (see ECO541 Section G.19). Examples of ordinate dimensions are shown in Figure 66. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 218 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 218 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEWIT Pointer Pointer to the DE of the Witness Line Entity or Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 231 4.62 ORDINATE DIMENSION ENTITY (TYPE 218) Figure 66. Examples Defined Using the Ordinate Dimension Entity 232 4.63 POINT DIMENSION ENTITY (TYPE 220) 4.63 Point Dimension Entity (Type 220) A Point Dimension Entity consists of a leader, text, and an optional circle or hexagon enclosing the text. The leader will always contain three segments, and its first and last segments are always horizontal or vertical. If a hexagon encloses the text, it will be described by either a Composite Curve Entity ECO520 (Type 102) or a Simple Closed Planar Curve Entity (Type 106, Form 63). If a circle or hexagon does not enclose the text, the last segment of the leader will be horizontal and it will underline the text. Examples are shown in Figure 67. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 220 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 220 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEARRW Pointer Pointer to the DE of the Leader Entity ECO520 3 DEGEOM Pointer Pointer to the DE of the Circular Arc Entity, Composite Curve Entity, or Simple Closed Planar Curve Entity, or zero Additional pointers as required (see Section 2.2.4.4.2). 233 4.63 POINT DIMENSION ENTITY (TYPE 220) Figure 67. Examples Defined Using the Point Dimension Entity 234 4.64 RADIUS DIMENSION ENTITY (TYPE 222) 4.64 Radius Dimension Entity (Type 222) A Radius Dimension Entity consists of a general note, a leader, and an arc center point, (XT, YT). Refer to Figure 68 for examples of radius dimensions. A second form of this entity accounts for the occasional need to have two Leader (Arrow) Entities referenced. The definition of this second form can be found in Appendix G (see Section G.20). The arc center coordinates are used as reference in constructing the radius dimension but have no effect on the dimension components. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 222 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 222 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEARRW Pointer Pointer to the DE of the Leader Entity 3 XT Real Arc center coordinates 4 YT Real Additional pointers as required (see Section 2.2.4.4.2). 235 4.64 RADIUS DIMENSION ENTITY (TYPE 222) Figure 68. Examples Defined Using the Radius Dimension Entity 236 4.65 GENERAL SYMBOL ENTITY (TYPE 228) 4.65 General Symbol Entity (Type 228) A General Symbol Entity consists of zero or one (Form 0) or one (all other forms) general note, one ECO607A or more geometry entities which define a symbol, and zero, one or more associated leaders. Examples of general symbols are shown in Figure 69. Any geometry entity used to create the symbol shall have a Subordinate Entity Switch of 01 and an Entity Use Flag of 01 in Field 9 of its Directory Entry Section. Field 15 of the Directory Entry Section accommodates a form number. For this entity, it is used to maintain the nature of the symbol on the originating system. The definition of the form numbers can be found in Appendix G (see Section G.21). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 228 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 228 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ ECO607A 1 DENOTE Pointer Pointer to the DE of the associated General Note Entity or zero (for Form 0 only) 2 N Integer Number of pointers to geometry 3 DEGEOM1 Pointer Pointer to the DE of the first defining geometry entity .. . . . .. .. 2+N DEGEOMN Pointer Pointer to the DE of the last defining geometry entity 3+N L Integer Number of Leaders or zero 4+N DEARRW1 Pointer Pointer to the DE of the first associated Leader Entity .. . . . .. .. 3+L+N DEARRWL Pointer Pointer to the DE of the last associated Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 237 4.65 GENERAL SYMBOL ENTITY (TYPE 228) Figure 69. Examples Defined Using the General Symbol Entity 238 4.66 SECTIONED AREA ENTITY (TYPE 230) 4.66 Sectioned Area Entity (Type 230) ECO569 A sectioned area is a portion of a design which is to be filled with a pattern of lines. Ordinarily this entity is used to reveal or expose shape or material characteristics defined by other entities. The Sectioned Area Entity consists of a pointer to an exterior definition curve, a specification of the pattern of lines, the coordinates of a point on a pattern line, the distance between the pattern lines, the angle between the pattern lines and the X-axis of the definition space, and the specification of any enclosed definition curves (commonly known as islands). A second form of this entity is defined in Appendix G (see Section G.23). This entity is commonly used for annotative purposes but may ECO570 be considered geometry if all definition curves are also part of the model geometry. A definition curve is a simple closed curve that defines an area on the plane. The list of curve entity types and form numbers that may be used is given below: ____________________________________________ |__Type__|_____________Name_____________|___ | 100 | Circular Arc (full circle only) | | 102 | Composite Curve | | 104/1 | Conic Arc (full ellipse only) | | 106/63 |Simple Closed Planar Curve | | 112 | Parameteric Spline Curve | |___126___|_Rational_B-Spline_Curve_______|_ In cases where the definition curve duplicates or projects model geometry into the definition space solely for the purpose of defining the sectioned area, the definition curve shall be flagged as an annotative entity and physically subordinate to the Sectioned Area Entity. In cases where the definition curve is the model geometry, the definition curves shall remain as geometric entities and are not physically subordinate to the Sectioned Area Entity. The XT and YT coordinates, which may be specified, indicate a location which is on one of the pattern lines. This point allows applications which require specific placements of the lines to con- strain them appropriately. This point explicitly defines a point interior to the filled portion of the Sectioned Area which may be used as an anchor point for those systems which must produce explicit ray traces to create the fill pattern. If not specified, i.e., indicated by default, the lines need only be within the exterior definition curve. The angle of the lines has a default value of ss=4, measured in radians. The fill pattern is specified by a fill pattern code according to predefined definitions illustrated in Figure 70. Where possible, the intention of the pattern is shown in the following table. 239 4.66 SECTIONED AREA ENTITY (TYPE 230) _____________________________________________________________________ |__Pattern__|____Description_/_Intention_(see_[ANSI79])_____|________ | 0 |(no fill pattern specified) | | 1 |Iron, brick, stone masonry | | 2 |Steel | | 3 |(no intended meaning) | | 4 |Rubber, plastic, electrical insulation | | 5 |Marble, slate, glass, porcelain | | 6 |(no intended meaning) | | 7 |(no intended meaning) | | 8 |(no intended meaning) | | 9 |Bronze, brass, copper, composition | | 10 |(no intended meaning) | | 11 |(no intended meaning) | | 12 |Titanium, refractory material | | 13 |(no intended meaning) | | 14 |(no intended meaning) | | 15 |(no intended meaning) | | 16 |White metal, zinc, lead, babbit, alloys | | 17 |Magnesium, aluminum, aluminum alloys | | 18 |Electrical windings, electromagnets, resistance, etc. | |_____19_____|Solid_fill_____________________________________________ | For the fill pattern code 0 and 19, the Parameter Data values for indices 3 through 7 are defaulted to 0.0 because they do not apply to the specified fill patterns. ECO509 Additional fill pattern codes are defined in Appendix G (see Section G.22). The specification of enclosed definition curves allows for the nesting of curves so long as they meet the criteria specified below. This specification makes it possible to identify closed areas which are alternately filled and not filled as the pattern lines trace inward from the exterior definition curve. Since no nesting levels are required, interior definition curves may be interior to or at the same level as another interior definition curve. (See Figure 71). All definition curves used to create a Sectioned Area must meet the following criteria: 1. The Sectioned Area Entity and all its constituent components must be defined in the same definition space (model or drawing). 2. A definition curve is a simple closed curve. The curve intersects itself only at its endpoints. A curve is called a simple closed curve if its start point and end point coincide and furthermore as one traverses the curve from start point to end point this common end point is occupied by no other point during the traversal. The definition curve separates a plane into two distinct ECO605 areas; the interior area and the exterior area. Figure 72 shows cases of illegal definition curves. 3. The interior areas defined by two or more definition curves will be related in one of two ways. The two areas will either be completely disjoint or one will completely enclose the other, in the sense that the interior area of the island or islands is a subset of the interior area of the outer definition curve. Figure 73 shows cases of illegal relationships for definition curves. 4. Pattern lines and all definition curves must be co-planar (i.e., the Sectioned Area Entity and all its constituent components must share the same plane). Figure 74 shows an example of how implementations may differ but still accomplish the same result. The example is a cross section detail of a T-slot. The T-slot may be represented as a single enclosed 240 4.66 SECTIONED AREA ENTITY (TYPE 230) area to be sectioned (Figure 74-A). The area not to be sectioned may be represented by a second definition curve (island Figure 74-B). Note that the interior and exterior curves in Figure 74-B have coincident edges. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 230 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 230 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 BNDP Pointer Pointer to the DE of the exterior definition curve - a closed planar curve 2 PATRN Integer Fill pattern code 3 XT Real X coordinate through which a line should pass 4 YT Real Y coordinate through which a line should pass 5 ZT Real Z depth of lines 6 DIST Real Normal distance between adjacent lines 7 ANGLE Real Angle measured in radians from the XT axis to the lines of the sectioning. Default = ss=4 8 N Integer Number of island curves or zero 9 ISLPT1 Pointer Pointer to the DE of the first interior definition curve for an island .. . . . .. .. 8+N ISLPTN Pointer Pointer to the DE of the last interior definition curve for an island Additional pointers as required (see Section 2.2.4.4.2). 241 4.66 SECTIONED AREA ENTITY (TYPE 230) Figure 70. Predefined Fill Patterns for the Sectioned Area Entity 242 4.66 SECTIONED AREA ENTITY (TYPE 230) Figure 71. Examples of Nested Definition Curves Figure 72. Examples of Illegal Definition Curves 243 4.66 SECTIONED AREA ENTITY (TYPE 230) Figure 73. Example of Illegal Relationship for Definition Curves Figure 74. Example of Two Ways to Define an Area 244 4.67 ASSOCIATIVITY DEFINITION ENTITY (TYPE 302) 4.67 Associativity Definition Entity (Type 302) The Associativity Definition Entity permits the preprocessor to define an associativity schema. That is, by using the associativity definition, the preprocessor defines the type of relationship. It is important to note that this mechanism specifies the syntax of such a relationship and not the semantics. The definition schema allows the specification of multiple groups of data which are called classes. A class is considered to be a separate list, and the existence of several classes implies an association among the classes as well as among the contents of each class. For each class, the schema has provision to specify whether or not back pointers are required. A back pointer being required implies that an entity which is a member of this associativity (when it is instanced) has a pointer to the directory entry of the associativity instance in its back pointer parameter section. The provision in the schema which specifies whether or not a class is ordered indicates if the order of appearance of entries in the class is significant. In the schema, "ENTRIES" are the members of the class. However, each entry could be composed of several items. If multiple items are required, they will be ordered. For example, if the entries were locations, each entry might have three items to specify X, Y, and Z values. The associativity definition will fix the number of classes for an associativity and the number of items per entry in a particular class. Each associativity instance will have a variable number of entries per class. In order to help decode instances of the definition, each item is specified as a pointer (to an entity directory entry) or a data value. Two kinds of associativity are permitted within the file. Predefined associativities will have form numbers in the range of 1 to 5000 and are defined in Section 4.76.1. (These definitions do not appear in the file). The second kind of associativity is defined in the file by a preprocessor and will have form numbers in the range of 5001-9999. These definitions appear once in the file for each form of associativity defined and allow the preprocessor to fill in the definition according to a schema which defines the details of the associativity. The definition includes the associativity form, the number of class definitions, the number and type of items in each entry, and whether back pointers (from the entity to the associativity) are required. Each set of values (BP, Order, N, and Item Type) is considered a class. See Figure 75 for a complete example of associativity. 245 4.67 ASSOCIATIVITY DEFINITION ENTITY (TYPE 302) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 302 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0002** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 302 |< n:a: > |< n:a: > | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 5001-9999. Parameter Data Index__ Name____ Type___ Description___ 1 K Integer Number of class definitions 2 BP1 Integer 1 = back pointers required 2 = back pointers not required 3 OR1 Integer 1 = ordered class 2 = unordered class 4 N1 Integer Number of items per entry 5 IT1(1) Integer 1 = pointer to a directory entry 2 = value 3 = parameter is a value or a pointer if parameter 0, it is a value if parameter < 0, it is a pointer .. . . . .. .. 4+N1 IT1(N1) Integer The items in parameters 2 through 4+N1 are repeated for each of the K classes. 246 4.67 ASSOCIATIVITY DEFINITION ENTITY (TYPE 302) Figure 75. Relationships Between Entities in an Associativity 247 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) 4.68 Line Font Definition Entity (Type 304) Two types of line fonts may be defined. One type considers a line font as a repetition of a basic pattern of visible-blank (or, on-off) segments superimposed on a line or a curve. The line or curve is then displayed according to the basic pattern. The other type considers a line font as a repetition of a template figure that is displayed at regularly spaced locations along a planar anchoring curve. The anchoring curve itself has no visual purpose. Any line or curve geometry entity type may reference a Line Font Definition Entity by inserting a pointer to that entity in its Directory Entry Field 4, the line font pattern field. The type of line font being specified is then indicated by a form number in the Line Font Definition Entity. The preprocessor must select one of the line font patterns (see Section 2.2.4.3.4) and place the value in Directory Entry Field 4 of the Line Font Definition Entity. This value should be the closest functional equivalent or the most visually similar. The value will be used by postprocessors which cannot support the Line Font Definition Entity. Form Number 1 in a Line Font Definition Entity specifies that the line font type is to be a repetition of template figure displays along the referencing anchoring curve. The template figure is specified as a Subfigure Definition Entity (Type 308). In this case, four values specify the entity as follows: The first parameter specifies the orientation of the template displays. This may remain constant, or it may vary with the direction of the anchoring curve at the point of each template figure display location. The second parameter is a pointer to the Subfigure Definition Entity containing the template display. The third parameter specifies display locations on the anchoring curve by giving the common arc length distance between corresponding points on successive template figure displays. The fourth parameter gives a scale factor to be applied to the template subfigure at each display location. Figure 76 illustrates two examples of a line font using Form Number 1. In each case, the anchoring curve is a straight line. Form Number 2 in a Line Font Definition Entity specifies that the line font type is to be a repetition of a basic visible-blank pattern superimposed on the referencing line or curve. An arbitrary number M of segments may be used in the basic pattern. When the basic pattern is laid out horizontally, the "first" segment is the leftmost one, the "M-th" segment is the rightmost one. The length (in the units of the curve on which the pattern is being superimposed) of each segment of the pattern may be specified individually. This allows the visible-blank sequence of the pattern to alternate between "visible" and "blank" regardless of the lengths of the segments but does not prohibit adjacent segments from being either both visible or both blanked when unequal lengths are employed. Another option for some patterns is to hold the length constant across segments, and achieve variation in the lengths of the visible and blanked segments by making the "visible" and/or the "blank" segments be adjacent as required. For example, a basic pattern whose left two-thirds is visible and whose right third is blanked, may be described either by the sequence "visible-blank" with the length of the first segment twice that of the second, or else by the sequence "visible-visible-blank", with the lengths of all three segments equal. The visible-blank sequence is specified by correlating it with the rightmost M bits in the binary representation of a string of hexadecimal digits, the Mth segment being associated with the units bit of the binary representation of the rightmost hexadecimal digit. A "0" represents a "blank", or "off" segment, a "1" represents a "visible", or "on" segment. For this line font type, the first parameter is the positive integer M giving the number of segments in the basic pattern. Then, parameter values 2 through M+1 give the lengths of the M segments. 248 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) Finally, parameter value M+2 is the minimal string of hexadecimal digits whose significance has been described above. Figure 77 shows an example of the Form Number 2. Shown is a font made up of five segments of unequal length. Two repetitions of the basic font are illustrated. ______________________________________________________________________ |__Form__||_________________________Meaning_________________________|_ | 1 |Line font specified by a repeating template subfigure | |____2____|Line_font_specified_by_a_repeating_visible-blank_pattern__|_ 249 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 304 | ) |< n:a: > | # |< n:a: > |< n:a: > | 0; ) |< n:a: > |**0002** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 304 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Line Font Pattern value must be in the range 1 through 5; 0 is not allowed. Parameter Data Index__ Name____ Type___ Description___ 1 M Integer M=0: Each template display is oriented by aligning the axes of the subfigure definition coordinate system with the axes of the definition space of the anchoring curve. M=1: Each template display is oriented by aligning the X axis of the subfigure definition coordinate system with the tangent vector of the anchoring curve at the point of incidence of the curve and the origin of the subfigure, and the Z axis of the subfigure definition coordinate system with the Z axis of the definition space of the anchoring curve. 2 L1 Pointer Pointer to the DE of the Subfigure Definition Entity for the template displays 3 L2 Real Common arc length distance between corresponding points on successive template figure displays 4 L3 Real Scale factor to be applied to the subfigure Additional pointers as required (see Section 2.2.4.4.2). 250 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 304 | ) |< n:a: > | # |< n:a: > |< n:a: > | 0; ) |< n:a: > |**0002** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 304 |< n:a: > |< n:a: > | # | 2 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Line Font Pattern value must be in the range 1 through 5; 0 is not allowed. Parameter Data Index__ Name____ Type___ Description___ 1 M Integer Number of segments in the basic pattern of visible-blank seg- ments 2 L1 Real Length of the first segment of the basic pattern .. . . . .. .. 1+M LM Real Length of the last segment of the basic pattern 2+M B String (((M-1)/4) + 1) hexadecimal digits indicating which segments of the basic pattern are visible and which are blanked, where the expression represents the greatest integer result. E.g., "5" indicates that segments 1 and 3 are visible. Bits are right jus- tified. Additional pointers as required (see Section 2.2.4.4.2). 251 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) Figure 76. Line Font Definition Using Form Number 1 (Template Subfigure) 252 4.68 LINE FONT DEFINITION ENTITY (TYPE 304) Figure 77. Line Font Definition Using Form Number 2 (Visible-Blank Pattern) 253 4.69 SUBFIGURE DEFINITION ENTITY (TYPE 308) 4.69 Subfigure Definition Entity (Type 308) The Subfigure Definition Entity is designed to support the concept of a subpicture (if one equates drawing creation with graphics picture processing). This entity permits a single definition of a detail to be utilized in multiple instances in the creation of the whole picture. The contents of the subfigure include a set of pointers to any combination of entities and other subfigures. DEPTH indicates the actual nesting of the subfigures. If DEPTH=0, the subfigure has no references to any subfigure instances. A subfigure cannot reference a subfigure instance that has equal or greater depth. A DEPTH=N indicates there is a reference to an instance of a subfigure definition with DEPTH N-1. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 308 | ) |< n:a: > | #; ) | #; ) |< n:a: > | 0; ) | 0; ) |**??02?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 308 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DEPTH Integer Depth of subfigure (indicating the amount of nesting) 2 NAME String Subfigure name 3 N Integer Number of entities in the subfigure 4 DE1 Pointer Pointer to the DE of the first associated entity .. . . . .. .. 3+N DEN Pointer Pointer to the DE of the last associated entity Additional pointers as required (see Section 2.2.4.4.2). 254 4.70 TEXT FONT DEFINITION ENTITY (TYPE 310) 4.70 Text Font Definition Entity (Type 310) This entity defines the appearance of characters in a text font. The data describing the appearance of a character may be located by the Font Code (FC) and the ASCII character code (AC). This entity may describe any or all the characters in a character set. Thus, this entity may be used to describe a complete font or a modification to a subset of characters in another font. Font Code (FC) and Font Name (FNAME) are the number and name used to reference the font on the originating system. When this entity is a modification to another font, the Supersedes Font (SF) value (Parameter 3) indicates which font the entity modifies. When it is not, this field is ignored. This value is an integer which indicates the font number to be modified or, if negative, is the pointer value to the Directory Entry of another Text Font Definition Entity. When this entity modifies another font, i.e., Parameter 3 references another font, the definitions in this entity supersede the definition in the original font. For example, a complete set of characters may have their font definition specified by this entity. Another Text Font Definition Entity could reference the first definition and modify a subset of the characters. Each character is defined by overlaying an equally spaced square grid over the character. The character is decomposed into straight line segments which connect grid points. Grid points are referenced by standard Cartesian coordinates. The position of the character relative to the grid is defined by two points. The character's origin point is placed at the origin (0,0) of the grid and defines the position of the character relative to the text origin of that character. The second point defines the origin point of the character following the character being defined. This allows the spacing between characters to be specified. Construction of text strings consists of placing the character origin of the first character at the text string origin and placing subsequent character origins at the location specified in the previous character as the location of the next character's origin. The parameterization of the character appearance is described by the motion of an imaginary pen moving between grid points. Commands to move the pen reference the grid location to which the pen is to move. The pen may be "lifted" such that its movement is not displayed. The representation of the movement of the pen is a sequence of pen commands and grid locations. Each movement of the pen is represented by a pen up/down flag and a pair of integer grid coordinates. The pen up/down flag defaults to pen down. A flag value of 1 means the pen is to be lifted (i.e., display off) and moved to the next location in the sequence. Upon arrival at this location the pen is returned to a "down" position (i.e., display on). The grid size is related to the text height through the scale parameter. This parameter defines how many grid units equal one text height unit. 255 4.70 TEXT FONT DEFINITION ENTITY (TYPE 310) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 310 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0002** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 310 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 FC Integer Font Code 2 FNAME String Font Name 3 SF Integer Number of the font which this definition supersedes or Pointer Pointer to the DE of the Text Definition Entity if negative 4 SCALE Integer Number of grid units which equal one text height unit 5 N Integer Number of characters in this definition 6 AC1 Integer ASCII code for first character 7 NX1 Integer Grid location of the next character's origin 8 NY1 Integer " 9 NM1 Integer Number of pen motions for first character 10 PF1(1) Integer Pen up/down flag: 0 = Down (default), 1 = Up 11 X1(1) Integer Grid location to which the pen is to move 12 Y1(1) Integer " .. . . . .. .. 8+3*NM1 Y1(NM1) Integer Last grid location of first character 9+3*NM1 AC2 Integer ASCII code for second character 10+3*NM1 NX2 Integer Grid location of the next character origin 11+3*NM1 NY2 Integer " 12+3*NM1 NM2 Integer Number of pen motions for second character .. . . . .. .. 5+4*N+P YN(NMN) Integer Last grid location of last character 3* NMi Additional pointers as required (see Section 2.2.4.4.2). Examples of character definitions are shown in Figures 78 and 79. The parameters for the first example are: FC 1 FNAME 8HSTANDARD SF SCALE 8 N 60 256 4.70 TEXT FONT DEFINITION ENTITY (TYPE 310) AC1 65 NX1 11 NY1 0 NM1 4 PF1 0 X1 4 Y1 8 PF2 0 X2 8 Y2 0 PF3 1 X3 2 Y3 4 PF4 0 X4 6 Y4 4 In the Parameter Data Section of the file, this definition would look like: 1,8HSTANDARD,,8,60,65,11,0,4,,4,8,,8,0,1,2,4,,6,4.... 257 4.70 TEXT FONT DEFINITION ENTITY (TYPE 310) Figure 78. Example of a Character Definition 258 4.70 TEXT FONT DEFINITION ENTITY (TYPE 310) Figure 79. Example of a Character Definition Including Descenders 259 4.71 TEXT DISPLAY TEMPLATE ENTITY (TYPE 312) 4.71 Text Display Template Entity (Type 312) The Text Display Template is used to set parameters for display of information which has been logically included in another entity as a parameter value. The text to be displayed is derived from the indicated parameter value of the entity which is pointing to the Text Display Template. In addition to string constants, the parameter values to be displayed may be integer, real or logical constants. The parameter value shall be processed into text as defined in Section 2.2.2 and according to the processing rules presented in the following. Furthermore, the pointer to the Text Display Template may be explicitly defined in the pointing entity description or it may be an implicitly defined additional pointer available with all entities (see Section 2.2.4.4.2). When the pointer is explicitly defined (e.g., Class 6 of the Flow Associativity (Type 402, Form 18)), the specified explicit parameter shall be processed for display. (In the example cited, the parameter to be displayed is the first flow name listed in Class 5.) When, on the other hand, the pointer to the template is one of the additional pointers (as defined in Section 2.2.4.4.2) the parameter to be processed for display is the first information value in the pointing entity. (The information value to be displayed shall be data as opposed to meta-data. For example, if the first parameter of the pointing entity is the number of property values, that should be skipped and the first actual property value should be processed and displayed.) For a more detailed description of the parameters, see the General Note Entity (Type 212). Processing Rules for Text Display The following rules are provided for the sake of uniformity in case postprocessed files are to be tested for identical textual presentation of Integer, Real, and Logical values. Strict application of these rules may lead to overwriting other entities, impaired legibility, and reduced visual association with pertinent nearby structures. Consequently, local site standards and conventions may supersede these rules whenever identical textual presentation is not required. Integer Values. All integers shall be processed such that the resultant text string contains only the valid decimal digits (0-9) and a sign. A leading minus sign shall denote negative values. A leading plus sign shall be provided for positive values. Real Values. All reals shall be processed so that the resulting string represents a valid approxima- tion of the number in scientific notation. The decimal point shall appear immediately to the left of the most significant digit. The decimal point shall be preceded by a zero. A leading minus sign shall denote negative values. A leading plus sign shall be provided for positive values. Logical Values. The logical value .TRUE. (indicated by a 1 in the file) shall be processed as if the string constant "4HTRUE" was to be displayed. The logical value .FALSE. (indicated by a 0 in the file) shall be processed as if the string constant "5HFALSE" was to be displayed. 260 4.71 TEXT DISPLAY TEMPLATE ENTITY (TYPE 312) 4.71.1 Absolute Text Display Template (Form 0). This form of the Text Display Template specifies the parameters for the text block at the specified starting point. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 312 | ) |< n:a: > |< n:a: > | #; ) | 0; ) | 0; ) | 0; ) |??000200 | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 312 |< n:a: > | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 CBW Real Character box width 2 CBH Real Character box height 3 FC Integer Font code (Default = 1) or or Pointer Pointer to the DE of the Text Font Definition Entity if negative 4 SL Real Slant angle (Radians) (Default = ss/2) 5 A Real Rotation angle (Radians) 6 M Integer Mirror Flag 7 VH Integer Rotate internal text flag 8 XS Real Coordinates of lower left corner of first character box 9 YS Real 10 ZS Real Additional pointers as required (see Section 2.2.4.4.2). 261 4.71 TEXT DISPLAY TEMPLATE ENTITY (TYPE 312) 4.71.2 Incremental Text Display Template (Form 1). This form of the Text Display Tem- plate specifies the parameters for the text block at a starting point specified incrementally from one taken from the entity point to the given instance of the Text Display Template. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 312 | ) |< n:a: > |< n:a: > | #; ) | 0; ) | 0; ) | 0; ) |??000200 | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 312 |< n:a: > | #; ) | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 CBW Real Character box width 2 CBH Real Character box height 3 FC Integer Font code (Default = 1) or or Pointer Pointer if negative 4 SL Real Slant angle (Radians) (Default = ss/2) 5 A Real Rotation angle (Radians) 6 M Integer Mirror Flag 7 VH Integer Rotate internal text flag 8 DXS Real Increment in X from X coordinate found in parent entity 9 DYS Real Increment in Y from Y coordinate found in parent entity 10 DZS Real Increment in Z from Z coordinate found in parent entity Additional pointers as required (see Section 2.2.4.4.2). 262 4.72 COLOR DEFINITION ENTITY (TYPE 314) 4.72 Color Definition Entity (Type 314) The Color Definition Entity is used to communicate the relationship of the primary (red, green, and blue) colors to the intensity level of the respective graphics devices as a percent of the full intensity range. These red, green, blue coordinates (RGB) can be readily transformed to cyan, magenta, yellow (CMY) and to hue, lightness, saturation (HLS) using transformations that are given in Appendix D. The preprocessor must select one of the Color Numbers (see Section 2.2.4.3.13) and place the value in Directory Entry Field 13 of the Color Definition Entity. This value should be the closest functional equivalent, or the most visually similar. The value will be used by postprocessors which cannot support the Color Definition Entity. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 314 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0002** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 314 |< n:a: > | # | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: Color Number value must be in the range 1 through 8; 0 is not allowed. Parameter Data Index__ Name____ Type___ Description___ 1 CC1 Real First color coordinate (red) as a percent of full intensity (range 0. to 100.) 2 CC2 Real Second color coordinate (green) as a percent of full intensity (range 0. to 100.) 3 CC3 Real Third color coordinate (blue) as a percent of full intensity (range 0. to 100.) 4 CNAME String Color name; this is an optional character string which may con- tain some verbal description of the color. If the color name is not provided and additional pointers are required, a placekeeper must be supplied between CC3 and the first additional pointer. Additional pointers as required (see Section 2.2.4.4.2). 263 4.73 UNITS DATA ENTITY (TYPE 316) 4.73 Units Data Entity (Type 316) ECO528 The definition of this entity may be found in Appendix G (see Section G.25). 264 4.74 NETWORK SUBFIGURE DEFINITION ENTITY (TYPE 320) 4.74 Network Subfigure Definition Entity (Type 320) The Network Subfigure Definition Entity permits a single definition of a detail to be used in many instances in the file, similar to the Subfigure Definition Entity (Type 308). It differs from the ordinary subfigure definition in that it defines a specialized subfigure, one whose instances may participate in networks. To participate in a network, points of connection (Connect Point Entity (Type 132)) must be defined (see indices NA+7 and following) and instanced along with the subfigure. Often, products which contain networks are designed first as schematics (showing the logical connections or relationships), which are then converted into the designs of the physical products. Whenever both a logical design and a physical design are present in the same file, the processor needs a way to determine which entities belong in which design. The Type Flag field (index 4+NA) implements this distinction. Other fields, such as NAME and DEPTH, function in exactly the same manner as in the Subfigure Definition Entity (Type 308). There is a direct relationship between the points of connection in the Network Subfigure Definition ECO542 Entity (Type 320) and the Network Subfigure Instance Entity (Type 420). The number of associated (child) Connect Point Entities (Type 132) in the instance must match the number in the definition, their order must be identical, and any unused points of connection in the instance must be indicated by a null (zero) pointer. Note: The depth of the subfigure is inclusive of both the Network Subfigure Definition Entity (Type 320) and the ordinary Subfigure Definition Entity (Type 308). Thus, the two may be nested but must indicate that in the depth parameter. 265 4.74 NETWORK SUBFIGURE DEFINITION ENTITY (TYPE 320) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 320 | ) |< n:a: > | #; ) | #; ) |< n:a: > | 0; ) | 0; ) |**??02?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 320 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DEPTH Integer Depth of subfigure (indicating the amount of nesting) 2 NAME String Subfigure name 3 NA Integer Number of associated (child) entities in the subfigure exclusive of primary reference designator and Connect Points 4 APTR1 Pointer Pointer to the DE of the first associated entity .. . . . .. .. 3+NA APTRNA Pointer Pointer to the DE of the last associated entity 4+NA TF Integer Type Flag: 0 = not specified 1 = logical 2 = physical 5+NA PRD String Primary reference designator 6+NA DPTR Pointer Pointer to the DE of the primary reference designator Text Dis- play Template, or null. If null, no Text Display Template spec- ECO546 ified. 7+NA NC Integer Number of associated (child) Connect Point Entities 8+NA CPTR1 Pointer Pointer to the DE of the first associated Connect Point Entity, or zero .. . . . .. .. 7+NC+NA CPTRNC Pointer Pointer to the DE of the last associated Connect Point Entity, or zero Additional pointers as required (see Section 2.2.4.4.2). 266 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) 4.75 Attribute Table Definition Entity (Type 322) ECO561 The Attribute Table Definition Entity is designed to support the concept of a well-defined collection of attributes (Section 3.6.7), whether it is a table or a single row of attributes. The entity provides a template for the instance of attribute tables (see Section 4.86), or for the combination of template and instance (see Section 4.75.2 and Section 4.75.3). The entity includes a table name (NAME), and for each attribute, an attribute type (AT), data type (AVDT), and a count (AVC). Definitions. The following definitions and abbreviations are used in the entity description. Attribute List Type (ALT). The designated attribute list contains the names (or descriptors) of each attribute type appearing in the attribute table. Within each attribute list the integer numbers representing the attributes must be unique. As an aid to implementors and users, the attribute list also may contain useful supporting information such as suggested units, suggested data types, a footnote for reference, or a range of acceptable values. ECO562 __________________________________________________________________________________ |____Value____|_______________________Designated_List_________________________|___ | 0 |See Property Entity Form 15 for the name of the specific | | | engineering standard that defines the attribute list | | 1 |General attribute list | | 2 |Electrical attribute list (see Table 6) | | 3 |AEC attribute list (see Table 7) | | 4 |Process plant attribute list (see Table 8) | | 5 |Electrical and PWA manufacturing attribute list (see Table 9) | | 6-5000 | other application areas | |__5001-9999__|implementor_defined_lists________________________________________|_ Attribute Type (AT). Each integer number designates an attribute type defined in the designated attribute list. The number must exist in the list. Attribute Value Data Type (AVDT). Each attribute has one or more associated value types which may be presented in this entity using one of the following data type indicators (there is no default - a value must be specified): ______________________________ |__Value__|__Data_Type____|___ | 0 |No value | | 1 |Integer | | 2 |Real | | 3 |Character string | | 4 |Pointer | | 5 |Not used | |____6____|Logical___________|_ Note that these are the same types and are in the same order as the constants described in Sec- tion 2.2.2. Attribute Value Count (AVC). The number of values (Form 0 or Form 1) or pairs of values and pointers (Form 2) which follow. The default count is 1. A count of zero implies that values exist and will be recorded at some future time but are currently unknown. In this special case, no values or pairs of values and pointers are required. 267 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Attribute Value (AV). Each attribute contains zero, one or more values as counted by the AVC field. Each AV is specified in the data type field indicated by the current AVDT. Attribute Value Pointer (AVP). A pointer to a Text Display Template Entity (Type 312) can be associated with each AV. If the pointer contains a non-null value, the AV is displayed by the Text Display Template at either the absolute location given (Form 0), or by combining the increment given (Form 1) with the location of the parent entity (to which this entity is attached, if it is dependent). 4.75.1 Attribute Table Definition (Form 0). This form of the entity is for the definition only of a group of attributes (name, type, and count). It is to be used for the one-to-many case where there will be many instances of a single attribute table definition (the file will contain one or more attribute table instance entities referencing the Attribute Table Definition Entity). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 322 | ) |< n:a: > | #; ) | #; ) |< n:a: > | 0; ) | 0; ) |**0002?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 322 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 NAME String Attribute Table name, or comment (default = blank, no name) 2 ALT Integer Attribute list type 3 NA Integer Number of attributes (first attribute definition) 4 AT(1) Integer First attribute type 5 AVDT(1) Integer First attribute value data type 6 AVC(1) Integer First attribute value count .. . . . .. .. Let M = 3*NA (last attribute definition) M+1 AT(NA) Integer Last attribute type M+2 AVDT(NA) Integer Last attribute value data type M+3 AVC(NA) Integer Last attribute value count Additional pointers as required (see Section 2.2.4.4.2). 268 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) 4.75.2 Attribute Table Definition (Form 1). This form of the entity is to be used for the one-to-one case where there will be few, or only one, instance of the group of attributes (the attribute values will follow immediately after the attribute definition). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 322 | ) |< n:a: > | #; ) | #; ) |< n:a: > | 0; ) | 0; ) |**0002?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 322 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 NAME String Attribute Table name, or comment (default=blank, no name) 2 ALT Integer Attribute list type 3 NA Integer Number of attributes (first attribute definition and values) 4 AT(1) Integer First attribute type 5 AVDT(1) Integer First attribute value data type 6 AVC(1) Integer First attribute value count 7 AV(1,1) Variable First attribute value .. . . . .. .. 6+AVC(1) AV(1,AVC(1)) Variable Last attribute value .. . . . .. .. Let M = 3*NA + AVC(1) + . . .+ AVC(NA-1) (last attribute definition and values) M+1 AT(NA) Integer Last attribute type M+2 AVDT(NA) Integer Last attribute value data type M+3 AVC(NA) Integer Last attribute value count M+4 AV(NA,1) Variable First attribute value .. . . .. M+4+AVC(NA) AV(NA,AVC(NA)) Variable Last attribute value Additional pointers as required (see Section 2.2.4.4.2). 269 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) 4.75.3 Attribute Table Definition (Form 2). This form is similar to Form 1 with the addition of a pointer to a Text Display Template Entity following each attribute value. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 322 | ) |< n:a: > | #; ) | #; ) |< n:a: > | 0; ) | 0; ) |**0002?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 322 | # | #; ) | # | 2 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 NAME String Attribute Table name, or comment (default=blank, no name) 2 ALT Integer Attribute list type 3 NA Integer Number of attributes (first attribute definition) 4 AT(1) Integer First attribute type 5 AVDT(1) Integer First attribute value data type 6 AVC(1) Integer First attribute value count 7 AV(1,1) Variable First attribute value 8 AVP(1,1) Pointer Pointer to the DE of the Text Display Template .. . . . .. .. 6+AVC(1) AV(1,AVC(1)) Variable Last attribute value 7+AVC(1) AVP(1,AVC(1)) Pointer Pointer to the DE of the Text Display Template .. . . . .. .. Let M = 3*NA + 2*(AVC(1) + . . .+ AVC(NA-1)) (last attribute definition) M+1 AT(NA) Integer Last attribute type M+2 AVDT(NA) Integer Last attribute value data type M+3 AVC(NA) Integer Last attribute value count M+4 AV(NA,1) Variable First attribute value M+5 AVP(NA,1) Pointer Pointer to the DE of the Text Display Template .. . . . .. .. M+4+AVC(NA) AV(NA,AVC(NA)) Variable Last attribute value M+5+AVC(NA) AVP(NA,AVC(NA)) Pointer Pointer to the DE of the Text Display Template Additional pointers as required (see Section 2.2.4.4.2). 270 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) _____________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit____|_Type__|__Ref.______|_||||||| | 1 |Access time, memory | | second | Real | [IEEE84] | | 2 |Accuracy (percent of full scale) | | |Real | [IEEE84] | || || || || || || || || 3 |Ambient|air temperature |Ta| ||C |Real| ||[MIL195] || || 4 |Amplification| |A| || |Real| ||[IEEE84] || | 5 |Amplification Factor |Af | |Real | [IEEE84] | | 6 |Angle (of a waveform) | | degree |Real | [IEEE84] | || || || || || || || || 7 |Anode|voltage |Va| ||volt ||Real ||[IEEE84] || || 8 |Async.|input pulse width, minimum |AP|W | | second ||Real ||[MIL133] || || 9 |Automatic|gain control |AGC| | | ||Real ||[MIL133] || || 10 |Average|forward-current rating || || ampere ||Real ||[MIL195] || || 11 |Average|gate power dissipation |Wgpd| || watt |Real| ||[MIL195] || | 12 |Average gate-power-dissipation rating | | watt |Real | [MIL195] | | 13 |Backlash | | degree |Real | [IEEE84] | | 14 |Bandwidth |BW | hertz |Real | [MIL133] | | 15 |Base resistance |RB | ohm | Real | [IEEE84] | || 16 |Base|current |IB| ||ampere ||Real ||[MIL195] || || 17 |Base|current, instantaneous total |iB| ||ampere ||Real ||[MIL195] || || 18 |Base|spreading resistance |rb| ||ohm ||Real ||[MIL195] || || 19 |Base|supply voltage |VBB| ||volt |Real| ||[MIL195] || | 20 |Base to emitter voltage |VB | volt |Real | [MIL195] | || 21 |Board|thickness || ||inch |Real| ||[IPCT85] || || 22 |Breakdown|voltage |VBR| ||volt |Real| ||[MIL133] || || 23 |Capacitance| |C| ||farad |Real| ||[IEEE84] || || 24 |Carrier|frequency |Cf| ||hertz |Real| ||[IEEE84] || | 25 |Case temperature |TC | C |Real | [MIL195] | | 26 |Cathode current |Ic | ampere | Real | [IEEE84] | | 27 |Circuit commutated turn-off time | | second | Real | [MIL195] | | 28 |Clearance | | inch |Real | [IEEE84] | || 29 |Clock|level transition time |tT|C ||second ||Real ||[MIL133] || || 30 |Clock|pulse width, minimum |CP|W ||second ||Real ||[MIL133] || | 31 |Clock repetition rate |CRR | hertz |Real | [MIL133] | || 32 |Collector|current |IC| ||ampere ||Real ||[MIL195] || | 33 |Collector current, instantaneous total |iC |ampere | Real | [MIL195] | | 34 |Collector cut-off current |ICEX | ampere | Real | [MIL133] | | 35 |Collector efficiency (percent) | | |Real | [MIL195] | || || || || || || || || 36 |Collector|power dissipation |PC| ||watt |Real| ||[MIL195] || || 37 |Collector|to base voltage |VCB| ||volt |Real| ||[MIL195] || || 38 |Collector|to emitter voltage |VCE| ||volt |Real| ||[MIL195] || || 39 |Common-mode|input voltage |VICR| ||volt |Real| ||[MIL133] || |__40____|Common-mode_output_voltage_____________________|VOC_______|_volt_____|Real___|_[MIL133]__|_ 271 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit______|_Type__|__Ref.______|_||||||| || 41 |Common-mode|rejection ratio |CMRR| || |Real| ||[MIL133] || | 42 |Common-mode voltage amplification |AV C | |Real | [MIL133] | || 43 |Conductance| |G| ||siemens ||Real ||[IEEE84] || | 44 |Conductor spacing | | inch |Real | [IPCT85] | | 45 |Conductor width | | inch |Real | [IPCT85] | | 46 |Conversion efficiency (percent) | | |Real | [MIL195] | || || || || || || || || 47 |Conversion|time, analog-to-digital || ||second ||Real ||[IEEE84] || || 48 |Coupling|coefficient || || |Real| ||[IEEE84] || | 49 |Critical anode voltage | | volt |Real | [IEEE84] | || 50 |Current| |I| ||ampere || Real ||[IEEE84] || | 51 |Current capacity |Ic | ampere | Real | [IEEE84] | || 52 |Current|limit |Il| ||ampere || Real ||[IEEE84] || || 53 |Current|rating |Ir| ||ampere | |Real ||[IEEE84] || | 54 |Cut-off grid voltage |Vgc(off) | volt |Real | [IEEE84] | | 55 |Cutoff current |Ic | ampere | Real | [MIL195] | || 56 |Data|rate || ||hertz ||Real ||[IEEE84] || | 57 |Delay time |td |second | Real | [MIL195] | || 58 |Dielectric|constant |K| || |Real| ||[IEEE84] || || 59 |Dielectric|strength || ||volt/inch |Real| ||[IEEE84] || || 60 |Differential|control voltage || ||volt ||Real ||[IEEE84] || || 61 |Differential|input impedance |Zid| ||ohm ||Real ||[MIL133] || || 62 |Differential|output impedance |Zod| ||ohm ||Real ||[MIL133] || || 63 |Differential|output voltage || ||volt |Real| ||[IEEE84] || | 64 |Differential voltage amplification |Avd | |Real | [MIL133] | | 65 |Distortion (percent) | | |Real | [IEEE84] | | | | | | | | | 66 |Drain currrent |ID | ampere | Real | [MIL195] | || 67 |Drain|cutoff current |ID(off)| ||ampere | |Real ||[MIL195] || || 68 |Drain|supply voltage |VDD| ||volt |Real| ||[MIL195] || || 69 |Drain|to gate voltage |VDG| ||volt |Real| ||[MIL195] || || 70 |Drain|to source voltage |VDS| ||volt |Real| ||[MIL195] || | 71 |Drain to substrate voltage |VDs | volt |Real | [MIL195] | | 72 |Drift (percent of full scale) | | |Real | [IEEE84] | || || || || || || || || 73 |Driving|point impedance |Zdp| ||ohm ||Real ||[IEEE84] || | 74 |Dynamic impedance |ZD | ohm | Real | [MIL195] | | 75 |Efficiency (percent) | | |Real | [IEEE84] | | | | | | | | | 76 |Emission current |Ie | ampere | Real | [IEEE84] | | 77 |Emission efficiency (percent) | | |Real | [IEEE84] | | | | | | | | || 78 |Emitter|current |IE| ||ampere || Real ||[MIL195] || || 79 |Emitter|current, instantaneous total |iE| ||ampere | |Real ||[MIL195] || |__80____|Emitter_supply_voltage_________________________|VEE_______|_volt_______|Real___|_[MIL195]__|_ 272 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ____________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit____|_Type__|__Ref.______|_||||||| || 81 |Emitter|to base voltage |VEB| ||volt |Real| ||[MIL195] || | 82 |Emitter to collector voltage |VEC | volt |Real | [MIL195] | | 83 |External base resistance |RB | ohm | Real | [MIL195] | | 84 |External collector resistance |RC | ohm | Real | [MIL195] | || 85 |External|emitter resistance |RE| ||ohm ||Real ||[MIL195] || | 86 |Extrapolated unity gain frequency |fT | hertz |Real | [MIL195] | | 87 |Failure rate | | |Real | [IEEE84] | | 88 |Fall time |tf |second | Real | [MIL195] | || 89 |Field|emission || || || |[IEEE84]| || || 90 |Figure|of merit || || || ||[IEEE84] || || 91 |Filament|voltage |VF| ||volt |Real| ||[IEEE84] || || 92 |Floating|potential |VF|P ||volt |Real| ||[MIL195] || | 93 |Forward blocking voltage |VF BO | volt |Real | [MIL195] | || 94 |Forward|breakover current |IF|BR ||ampere ||Real ||[MIL195] || | 95 |Forward breakover voltage |VF BR | volt |Real | [MIL195] | || 96 |Forward|current |IF| ||ampere ||Real ||[MIL195] || || 97 |Forward|current, overload |IF|(OV ) ||ampere ||Real ||[MIL195] || || 98 |Forward|current, surge peak |IF|SM ||ampere ||Real ||[MIL195] || || 99 ||Forward gate current |IGF| ||ampere ||Real ||[MIL195] || || 100 |Forward|gate-to-source breakdown voltage |VF|BRGS ||volt |Real| ||[MIL195] || || 101 |Forward|gate-to-source voltage |VF|GS ||volt |Real| ||[MIL195] || || 102 |Forward|power dissipation |PF| ||watt ||Real ||[MIL195] || || 103 |Forward|recovery time |tfr| ||second ||Real ||[MIL195] || || 104 |Forward|voltage |VF| ||volt |Real| ||[MIL195] || | 105 |Frequency |F | hertz |Real | [IEEE84] | | 106 |Gain | | |Real | [IEEE84] | | 107 |Gate controlled turn-off time |tgc(off) |second | Real | [MIL195] | || 108 |Gate|current |IG| ||ampere ||Real ||[MIL195] || || 109 |Gate|supply voltage |VGG| ||volt |Real| ||[MIL195] || || 110 |Gate|to source voltage |VGS| ||volt ||Real ||[MIL195] || || 111 |Gate|trigger current |Igt| ||ampere ||Real ||[MIL195] || | 112 |Gate trigger voltage |Vgt | volt |Real | [MIL195] | || 113 |Gate|turn-off current |Igt(off)| ||ampere ||Real ||[MIL195] || || 114 |Gate|turn-off voltage |Vgt(off)| ||volt |Real| ||[MIL195] || || 115 |Gate|voltage |Vg| ||volt |Real| ||[MIL195] || || 116 |Gate-to-source|cutoff voltage |Vgs(off)| ||volt |Real| ||[MIL195] || || 117 |Gate-to-source|threshold voltage |Vgst| ||volt |Real| ||[MIL195] || | 118 |Gate-to-source voltage |Vgs | volt |Real | [MIL195] | | 119 |Grid control ratio | | |Real | [IEEE84] | |__120__|Grid_current____________________________________|Ig________|_ampere__|_Real___|_[IEEE84]__|_ 273 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) _________________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit________|_Type__|__Ref.______|_||||||| || 121 |Grid|voltage |Vg| ||volt |Real| ||[IEEE84] || || 122 |High|clock level |VCH| ||volt ||Real ||[MIL133] || || 123 |High|level input current |IIH| ||ampere ||Real ||[MIL133] || || 124 |High|level node input current |IINH| ||ampere ||Real ||[MIL133] || || 125 |High|level node input voltage |VINH| ||volt ||Real ||[MIL133] || || 126 |High|level output current |IOH| ||ampere ||Real ||[MIL133] || || 127 |High|level output voltage |VOH| ||volt ||Real ||[MIL133] || || 128 |High|level supply current drain |ICCH| ||ampere ||Real ||[MIL133] || || 129 |Holding|current |IH| ||ampere ||Real ||[MIL195] || | 130 |Impedance |Z | ohm | Real | [IEEE84] | | 131 |Incremental resistance |Rinc | ohm | Real | [IEEE84] | || 132 |Inductance| |L| ||henry ||Real ||[IEEE84] || || 133 |Input|bias current |IIB| ||ampere || Real ||[MIL133] || || 134 |Input|bias current temp. sensitivity |IIB=T| ||amp/deg C || Real ||[MIL133] || || 135 |Input|impedance |Zi| ||ohm ||Real ||[IEEE84] || || 136 |Input|offset current |IIO| ||ampere || Real ||[MIL133] || || 137 |Input|offset current temp. sensitivity |IIO=T| ||amp/deg C | |Real ||[MIL133] || || 138 |Input|offset voltage |VIO| ||volt ||Real ||[MIL133] || || 139 |Input|offset voltage temp. sensitivity |VIO=T| ||volt/deg C ||Real ||[MIL133] || | 140 |Input signals timing relationships |IT R | |Real | [MIL133] | || 141 |Insulation|resistance |Ri| ||ohm ||Real ||[IEEE84] || || 142 |Interelectrode|capacitance |CIE| ||farad ||Real ||[IEEE84] || | 143 |Interrupting current |Ii | ampere | Real | [IEEE84] | || 144 |Ionization|time || ||second ||Real ||[IEEE84] || || 145 |Junction|temperature |TJ| ||deg C ||Real ||[MIL195] || || 146 |Knee|impedance |Zk| ||ohm ||Real ||[MIL195] || || 147 |Knee|voltage |VK| ||volt ||Real ||[MIL195] || || 148 |Latching|current |Il| ||ampere ||Real ||[MIL195] || || 149 |Leakage|current |Ilk| ||ampere ||Real ||[IEEE84] || || 150 |Limiting|current |IL| ||ampere ||Real ||[MIL195] || | 151 |Limiting voltage |VL | volt |Real | [MIL195] | || 152 |Load|immittance || || |Real| ||[MIL195] || || 153 |Logic|level high |H| || |Real| ||[IEEE84] || | 154 |Logic level low |L | |Real | [IEEE84] | || 155 |Low|clock level |VCL| ||volt ||Real ||[MIL133] || || 156 |Low|level input current |IIL| ||ampere ||Real ||[MIL133] || || 157 |Low|level node input current |IINL| ||ampere ||Real ||[MIL133] || || 158 |Low|level node input voltage |VINL| ||volt ||Real ||[MIL133] || || 159 |Low|level output current |IOL| ||ampere ||Real ||[MIL133] || |__160__|Low_level_output_voltage________________________|VOL_______|_volt_________|Real___|_[MIL133]__|_ 274 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit____|__Type___|__Ref.______|_||||||| || 161 |Low|level supply current drain |ICCL| ||ampere || Real ||[MIL133] || | 162 |Luminous energy |cd | | Real | [MIL195] | || 163 |Material| || || ||String ||[IEEE84] || || 164 |Maximum|frequency of oscillation |fmax| ||hertz || Real ||[MIL195] || || 165 |Maximum|surge current, nonrepetitive |Ismax| ||ampere || Real ||[MIL195] || || 166 |Max.|surge-current rating, nonrepetitive || ||ampere | |Real ||[MIL195] || || 167 |Minimum|on-voltage |Vmin| ||volt ||Real ||[MIL195] || | 168 |Mode of operation | | | String |[IEEE84] | || 169 |Moisture-resistant| || || || Logical ||[IEEE84] || | 170 |Mutual impedance |Zm | ohm | Real | [IEEE84] | | 171 |Mutual conductance |Gm | siemens | Real | [IEEE84] | || 172 |N-channel|field-effect transistor |Nfet| || ||Real ||[MIL195] || || 173 |Negative|logic || || ||Logical ||[IEEE84] || || 174 |Noise|figure |NF| ||dB ||Real ||[MIL133] || || 175 |Noise|margin |VN| ||volt ||Real ||[MIL133] || | 176 |Noise temperature |TN | deg C | Real | [MIL195] | | 177 |Nonlinearity (percent of full scale) | | | Real | [IEEE84] | || || || || || || || || 178 |Nonrepetitive|peak off-state voltage |VDSM| ||volt | |Real ||[MIL195] || || 179 |Nonrepetitive|peak reverse current |IRSM| ||ampere | |Real ||[MIL195] || | 180 |Nonrepetitive peak reverse voltage |VRSM | volt |Real | [MIL195] | || 181 |Off-state|current |ID| ||ampere | |Real ||[MIL195] || | 182 |Off-state voltage |VD | volt |Real | [MIL195] | | 183 |Offset error (percent of full range) | | | Real | [IEEE84] | | | | | | | | | 184 |On-state current |IT | ampere | Real | [MIL195] | || 185 |On-state|drain current |ID(on)| ||ampere | |Real ||[MIL195] || || 186 |On-state|drain-to-source voltage |VDS(on)| ||volt |Real| ||[MIL195] || || 187 |On-state|voltage |VT| ||volt ||Real ||[MIL195] || || 188 |Open|loop gain |Av| || ||Real ||[IEEE84] || | 189 |Operating temperature |Top | deg C | Real | [MIL195] | | 190 |Operator (the person's name or initials) | | | String |[IEEE84] | | | | | | | | || 191 |Orientation| || || || String ||[IEEE84] || || 192 |Output|impedance |Zo| ||ohm || Real ||[IEEE84] || || 193 |Output|leakage current high |iozh| ||ampere || Real ||[IEEE84] || || 194 |Output|current || ||ampere || Real ||[IEEE84] || || 195 |Output|frequency |Fo| ||hertz ||Real ||[IEEE84] || || 196 |Output|frequency high |Foh| ||hertz ||Real ||[IEEE84] || || 197 |Output|frequency low |Fol| ||hertz || Real ||[IEEE84] || || 198 |Output|leakage current low |iozl| ||ampere | |Real ||[IEEE84] || || 199 |Output|offset voltage |VOO| ||volt ||Real ||[MIL133] || |__200__|Output_polarity_________________________________|__________|__________|_String___|[IEEE84]__|_ 275 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ________________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit______|__Type___|__Ref.______|_||||||| || 201 |Output|pulse duration |top| |second| ||Real ||[IEEE84] || || 202 |Output|pulse duration high |toph| |second| ||Real ||[IEEE84] || || 203 |Output|pulse duration low |topl| ||second || Real ||[IEEE84] || || 204 |Output|short circuit current |IOS| ||ampere || Real ||[MIL133] || || 205 |Output|swing bandwidth, maximum |BOM| ||hertz ||Real ||[MIL133] || || 206 |Output|type || || ||String ||[IEEE84] || || 207 |Output|voltage |Vo| ||volt |Real| ||[IEEE84] || || 208 |Output|voltage high |Voh| ||volt |Real| ||[IEEE84] || || 209 |Output|voltage low |Vol| ||volt ||Real ||[IEEE84] || | 210 |Output voltage regulation | | | Real | [IEEE84] | | |((high-low)/nominal, percent) | | | | | || || || || -1 || || || || 211 |Output|voltage sensitivity to temperature || ||(degC) | |Real ||[IEEE84] || || 212 |Output|voltage swing, maximum |VOP|P ||volt ||Real ||[MIL133] || || 213 |Outputs| || || ||String |[IEEE84]| || || 214 |Over-voltage|sense || || ||String ||[IEEE84] || || 215 |Overall|average noise figure |Nfoa| || ||Real ||[MIL195] || | 216 |Overload recovery time |tor |second | Real | [MIL133] | || 217 |P-channel|field-effect transistor |Pfet| || ||Real ||[MIL195] || || 218 |Parallel|entry || || ||String |[IEEE84]| || || 219 |Parametric|electrical test required || || || Logical ||[IEEE84] || || 220 |Peak|current rating || ||ampere | |Real ||[IEEE84] || || 221 |Peak|forward-blocking voltage rating || ||volt |Real| ||[MIL195] || || 222 |Peak|forward-current rating, repetitive || ||volt |Real| ||[MIL195] || || 223 |Peak|forward-voltage rating || ||volt | |Real ||[MIL195] || || 224 |Peak|gate current |IGP| || ampere || Real ||[MIL195] || || 225 |Peak|gate power dissipation |WGP| || watt ||Real ||[MIL195] || || 226 |Peak|gate voltage |VGP| ||volt | |Real ||[MIL195] || || 227 |Peak|gate-current rating || ||ampere || Real ||[MIL195] || || 228 |Peak|gate-power-dissipation rating || ||watt ||Real ||[MIL195] || || 229 |Peak|gate-voltage rating || ||volt | |Real ||[MIL195] || || 230 |Peak|repetitive on-state current |Ip| ||ampere || Real ||[MIL195] || | 231 |Phase margin |OEm |degree | Real | [MIL133] | | 232 |Phase shift |OEs |degree | Real | [IEEE84] | | 233 |Photoelectric current |I | ampere | Real | [IEEE84] | | 234 |Pin size | | inch | Real | [IEEE84] | | 235 |Plate efficiency (percent) | | | Real | [IEEE84] | || || || || || || || || 236 |Polarity| || || ||String |[IEEE84]| || || 237 |Polarity|on stud || || ||String |[IEEE84]| || | 238 |Positive logic | | | Logical |[IEEE84] | || 239 |Power| |W| || watt ||Real ||[IEEE84] || |__240__|Power_dissipation_______________________________|PD________|_watt_______|_Real____|_[MIL133]__|_ 276 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit____|_Type___|___Ref.______|_||||||| || 241 |Power|gain |Gp| || dB ||Real || [MIL133] || || 242 |Power|per diode |WD| || watt |Real| || [IEEE84] || || 243 |Power|rating || || watt |Real| || [IEEE84] || || 244 |Power|supply high |Wsh| || volt |Real| || [IEEE84] || || 245 |Power|supply low |Wsl| || volt |Real| || [IEEE84] || | 246 |Power supply rejection ratio |PSRR | |Real | [MIL133] | | 247 |Procurement spec # 1 MIL-M-38510/xxx | | |String | [IEEE84] | || || || || || || || || 248 |Procurement|spec # 2 desc xxxxx || || |String| ||[IEEE84] || || 249 |Programmable| || || |Logical||| [IEEE84] || || 250 |Programmable|gain || || ||Real || [IEEE84] || || 251 |Propagation|delay time || ||second ||Real || [IEEE84] || || 252 |Propagation|delay time, high to low level |tP|HL |second| ||Real || [MIL133] || || 253 |Propagation|delay time, low to high level |tP|LH |second| ||Real || [MIL133] || || 254 |Propagation|delay to output high |tpdh| |second| ||Real || [IEEE84] || | 255 |Propagation delay to output low |tpdl |second | Real | [IEEE84] | || 256 |Protocol| || || ||String || [IEEE84] || | 257 |Pulse storage time |tps |second | Real | [MIL195] | | 258 |Pulse time |tp |second | Real | [MIL195] | || 259 |Pulse|width |tw| ||second ||Real || [IEEE84] || || 260 |Quiescent|input voltage |VI| ||volt |Real| || [MIL133] || || 261 |Quiescent|output voltage |VO| ||volt |Real| || [MIL133] || | 262 |Radiant energy |J! | joule |Real | [MIL195] | || 263 |Radiation|hardened || || |Logical||| [IEEE84] || | 264 |Reach-through voltage | | volt |Real | [MIL195] | || 265 |Reactance| |X| ||ohm ||Real || [IEEE84] || | 266 |Receiver input impedance |Zi | ohm | Real | [IEEE84] | | 267 |Rectification efficiency (percent) | | |Real | [MIL195] | || || || || || || || || 268 |Rectified|voltage |Vrect| ||volt |Real| || [IEEE84] || || 269 |Register|number || || |String| ||[IEEE84] || || 270 |Register|types || || ||String || [IEEE84] || || 271 |Regulator|current |IS| ||ampere ||Real || [MIL195] || || 272 |Regulator|voltage |VS| ||volt ||Real || [MIL195] || || 273 |Regulator|impedance |Zs| ||ohm ||Real || [MIL195] || || 274 |Repetitive|peak reverse voltage |VRRM| ||volt ||Real || [MIL195] || || 275 |Repetitive|peak off-state current |IDRM| ||ampere ||Real || [MIL195] || || 276 |Repetitive|peak off-state voltage |VDRM| ||volt ||Real || [MIL195] || || 277 |Repetitive|peak on-state current |IT|RM ||ampere ||Real || [MIL195] || || 278 |Repetitive|peak reverse voltage |VRRM| ||volt |Real| || [MIL195] || | 279 |Repetitive peak-reverse voltage rating | | volt |Real | [MIL195] | |__280__|Resettable______________________________________|__________|__________|Logical__|_[IEEE84]__|_ 277 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) _______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol___|___Unit____|__Type___|__Ref.______|_ | 281 |Resistance |R | ohm | Real | [IEEE84] | | 282 |Resistance tolerance, high (percent) | | | Real | [IEEE84] | | | | | | | | | 283 |Resistance tolerance, low (percent) | | | Real | [IEEE84] | | | | | | | | | 284 |Resistance value (measured) | |ohm | Real | [IEEE84] | | | | | | | | | 285 |Resistivity (in ohms/square) | | ohm | Real | [IEEE84] | | | | | | | | | 286 |Resistor construction class | | | String |[IEEE84] | || 287 |Resolution|in bits || || || Integer ||[IEEE84] || || 288 |Response|time |tr| |second| || Real ||[IEEE84] || || 289 |Resultant|carry || || || String ||[IEEE84] || | 290 |Reverse blocking current |IRBO |ampere | Real | [MIL195] | || 291 |Reverse|breakdown current |Irb| |ampere| || Real ||[MIL195] || | 292 |Reverse breakdown voltage |Vrb |volt | Real | [MIL195] | || 293 |Reverse|current |IR| |ampere| || Real ||[MIL195] || || 294 |Reverse|current, repetitive peak |IRRM| |ampere| || Real ||[MIL195] || || 295 |Reverse|current, surge peak |IRSM| |ampere| || Real ||[MIL195] || || 296 |Reverse|gate current |IGR| |ampere| || Real ||[MIL195] || || 297 |Reverse|gate-to-source voltage |VSG| |volt| ||Real ||[MIL195] || || 298 |Reverse|power dissipation |PR| |watt| || Real ||[MIL195] || || 299 |Reverse|recovery current |IRM(REC)| |ampere| || Real ||[MIL195] || || 300 |Reverse|recovery time |trr| |second| || Real ||[MIL195] || | 301 |Reverse voltage |VR |volt | Real | [MIL195] | | 302 |Rise time |tr |second | Real | [MIL195] | | 303 |Saturation current |Isat |ampere | Real | [IEEE84] | || 304 |Saturation|resistance |Rsat| ||ohm || Real ||[MIL195] || || 305 |Saturation|voltage |Vsat| |volt| ||Real ||[MIL195] || | 306 |Screening test | | | String |[IEEE84] | || 307 |Sealed| || || || String ||[IEEE84] || || 308 |Settling|time |ts| |second| || Real ||[IEEE84] || || 309 |Settling|time high |tsh| |second| || Real ||[IEEE84] || || 310 |Settling|time low |tsl| |second| || Real ||[IEEE84] || || 311 |Settling|time to p-percent of final max. |tpmax| |second| || Real ||[IEEE84] || | 312 |Settling time to p-percent of final min. |tpmin |second | Real | [IEEE84] | | 313 |Shaft diameter | |inch | Real | [IEEE84] | | 314 |Shift direction (e.g. 4Hleft) | | | String |[IEEE84] | || || || || || || || | 315 |Shift out clock frequency |Fshift |hertz | Real | [IEEE84] | || 316 |Short|circuit || || || String ||[MIL195] || || 317 |Signal|to noise ratio |SN|R ||dB || Real ||[IEEE84] || || 318 |Single-ended|input impedance |Zis| |ohm| || Real ||[MIL133] || || 319 |Single-ended|input voltage |VISR| |volt| || Real ||[MIL133] || |__320__|Single-ended_output_impedance___________________|Zos_________|ohm_____|__Real____|_[MIL133]__|_ 278 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) __________________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit________|__Type___|__Ref.______|_||||||| | 321 |Single-ended voltage amplification |Avs | | Real | [MIL133] | || 322 |Slew|rate |SR| ||volt/second || Real ||[MIL133] || || 323 |Small-signal|breakdown impedance |zBR| ||ohm || Real ||[MIL195] || || 324 |Small-signal|forward impedance |zf| ||ohm || Real ||[MIL195] || | 325 |Small-signal resistance |r | ohm | Real | [MIL195] | || 326 |Soft|start || || ||String |[IEEE84]| || | 327 |Solderability | | | Logical |[IEEE84] | | 328 |Source current |IS | ampere | Real | [MIL195] | || 329 |Source|cutoff current |IS(off)| ||ampere | |Real ||[MIL195] || | 330 |Source supply voltage |VSS | volt |Real | [MIL195] | || 331 |Source|terminal || || ||Real ||[MIL195] || || 332 |Source-to-substrate|voltage |Vss| ||volt ||Real ||[MIL195] || | 333 |Space charge density | | | Real | [IEEE84] | || 334 |Standard|reference || || ||Real ||[MIL195] || | 335 |Standing wave ratio |SW R | | Real | [MIL195] | | 336 |Static drain-to-source on-state resistance |Rsds(on) | ohm | Real | [MIL195] | || 337 |Static|forward current transfer-ratio |Isft| || || Real ||[MIL195] || | 338 |Static input resistance |Rin | ohm | Real | [MIL195] | || 339 |Static|transconductance |GM| ||siemens ||Real ||[MIL195] || || 340 |Storage|temperature |TST|G ||deg C ||Real ||[MIL195] || || 341 |Storage|time |ts| ||second || Real ||[MIL195] || || 342 |Stored|charge |QS| ||coulomb | |Real ||[MIL195] || || 343 |Strip|force || ||lbf | |Real ||[IEEE84] || || 344 |Strobing|input currents |Ist| ||ampere || Real ||[IEEE84] || || 345 |Strobing|pulse width |tst| ||hertz ||Real ||[IEEE84] || | 346 |Stud torque | | inch-lbf |Real | [IEEE84] | || 347 |Subcarrier| || || ||Real ||[IEEE84] || | 348 |Substrate size length | | inch | Real | [IEEE84] | | 349 |Substrate size width | | inch | Real | [IEEE84] | || 350 |Substrate|terminal || || ||Real ||[MIL195] || || 351 |Supply|voltage |VCC| ||volt | |Real ||[MIL133] || || 352 |Surge|current |IS| ||ampere || Real ||[MIL195] || || 353 |Surge,|on-state current |IT|SM ||ampere || Real ||[MIL195] || || 354 |Symbol|function || || ||String ||[IEEE84] || || 355 |Temperature| |T| ||deg C ||Real ||[IEEE84] || || 356 |Temperature|coefficient || || ||Real ||[IEEE84] || || 357 |Terminal|type || || ||String ||[IEEE84] || | 358 |Thermal equilibrium | | | Real | [MIL195] | | 359 |Thermal noise | | | Real | | |__360__|Thermal_resistance______________________________|R_________|_ohm_________|__Real____|_[MIL195]__|_ 279 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) _____________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit____|_Type__|___Ref.______|_||||||| || 361 |Thermal|resistance, case to ambient |RCA| ||ohm ||Real || [MIL195] || || 362 |Thermal|resistance, junction to ambient |RJA| ||ohm ||Real || [MIL195] || || 363 |Thermal|resistance, junction to case |RJC| ||ohm ||Real || [MIL195] || || 364 |Thermal|resistance, junction to lead |Rjl| ||ohm ||Real || [MIL195] || | 365 |Thermal resistance, junction to reference |RJR | ohm | Real | [MIL195] | || 366 |Threshold|current |Ith| ||ampere ||Real || [IEEE84] || | 367 |Threshold current high |Ithh | ampere | Real | [IEEE84] | || 368 |Threshold|current low |Ithl| ||ampere ||Real || [IEEE84] || || 369 |Threshold|voltage |Vth| ||volt |Real| || [IEEE84] || || 370 |Threshold|voltage high |Vthh| ||volt |Real| || [IEEE84] || | 371 |Threshold voltage low |Vthl | volt |Real | [IEEE84] | | 372 |Tolerance | | |Real | [IEEE84] | | 373 |Tolerance at d deg C (percent) | | |Real | [IEEE84] | | | | | | | | | 374 |Total duration |ttd |second | Real | [IEEE84] | | 375 |Total harmonic distortion (percent) |T HD | |Real | [MIL133] | || || || || || || || || 376 |Total|power dissipation, all terminals |PT| ||watt ||Real || [MIL195] || || 377 |Transducer|power gain |GT| ||dB ||Real || [MIL133] || | 378 |Transient response |TR | second | Real | [MIL133] | || 379 |Transition|duration || ||second ||Real || [IEEE84] || || 380 |Transition|time, high to low level |tT|HL |second| ||Real || [MIL133] || | 381 |Transition time, low to high level |tT LH |second | Real | [MIL133] | | 382 |Turn off time |toff |second | Real | [MIL195] | || 383 |Turn|on time |ton| |second| ||Real || [MIL195] || || 384 |Turn-off|delay time |td(off)| |second| ||Real || [MIL195] || || 385 |Turn-on|delay time |td(on)| ||second ||Real || [MIL195] || || 386 |Unbalance|voltage |VOU| ||volt |Real| || [MIL133] || || 387 |Under-voltage|protection || || |String| ||[IEEE84] || | 388 |Under-voltage release | | |String | [IEEE84] | || 389 |Units| || || |String||| [IEEE84] || || 390 |Unity|gain bandwidth |Gb| ||hertz |Real| || [IEEE84] || || 391 |Unity|gain bandwidth, maximum |Gbmax| ||hertz |Real| || [IEEE84] || || 392 |Unity|gain bandwidth, minimum |Gbmin| ||hertz |Real| || [IEEE84] || | 393 |Update time | | |String | [IEEE84] | | 394 |Utilization factor (maximum demand/rated | | |Real | [IEEE84] | | |capacity) | | | | | | | | | | | | || 395 |Value| || || |String||| [IEEE84] || || 396 |Voltage| |V| ||volt |Real| || [IEEE84] || || 397 |Voltage|control |Vc| ||volt |Real| || [IEEE84] || || 398 |Voltage|control oscillator frequency |Fvco| ||hertz |Real| || [IEEE84] || || 399 |Voltage|control oscillator frequency, high |Fvcoh| ||hertz |Real| || [IEEE84] || |__400__|Voltage_control_oscillator_frequency,_low_______|Fvcol_____|_hertz____|Real___|__[IEEE84]__|_ 280 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ECO523 ________________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit_______|__Type__|__Ref.______|_||||||| || 401 |Voltage|control, maximum |Vcmax| ||volt |Real| ||[IEEE84] || || 402 |Voltage|control, minimum |Vcmin| ||volt |Real| ||[IEEE84] || || 403 |Voltage|rating || ||volt |Real| ||[IEEE84] || || 404 |Voltage|reference |Vref| ||volt ||Real ||[IEEE84] || || 405 |Voltage-temperature|coefficient || ||volt/deg C ||Real ||[MIL195] || | 406 |Wavelength | | hertz |Real | [IEEE84] | | 407 |Width | | inch |Real | [IEEE84] | || 408 |Wire|diameter || ||inch |Real| ||[IEEE84] || || 409 |Working|peak off-state voltage |Vwp(off)| ||volt |Real| ||[MIL195] || || 410 |Working|peak reverse voltage |VRW|M ||volt |Real| ||[MIL195] || || 411 |Working|peak off-state voltage |VDW|M ||volt |Real| ||[MIL195] || || 412 |Working|peak-reverse voltage rating || ||volt ||Real ||[MIL195] || || 413 |Write|pulse width |Tw| ||second || Real ||[IEEE84] || || 414 |Write|pulse width, maximum |Twmax| ||ampere || Real ||[IEEE84] || || 415 |Write|pulse width, minimum |Twmin| ||ampere || Real ||[IEEE84] || || 416 |Zero|gate voltage drain current |IDDS| ||ampere || Real ||[MIL195] || || 417 |Zero|gate voltage source current |ISDS| ||ampere || Real ||[MIL195] || |__418__|Zero_power_resistance_at_T_deg_C________________|rT________|_ohm________|__Real___|_[IEEE84]__|_ |_________________________Circuit_Simulation_Parameters_for_Junction_Diodes_________________________|___ | 419 |Saturation Current |IS | A | Real | [SPICE] | | 420 |Ohmic Resistance |RS | ohm | Real | [SPICE] | | 421 |Emission Coefficient |N | | Real | [SPICE] | || 422 |Transit|Time |TT| || s ||Real ||[SPICE] || | 423 |Zero-bias P-N Capacitance |CJO | F | Real | [SPICE] | || 424 |Junction|Potential |VJ| || V ||Real ||[SPICE] || || 425 |Junction|Grading Coefficient |M| || ||Real ||[SPICE] || || 426 |Activation|Energy |EG| || eV ||Real ||[SPICE] || || 427 |Saturation|Current Temperature Coeff. |XTI| || ||Real ||[SPICE] || || 428 |Reverse|Breakdown Voltage |BV| || V ||Real ||[SPICE] || || 429 |Current|at Breakdown Voltage |IBV| || A ||Real ||[SPICE] || | 430 |Forward-bias Depletion Capacitance Coeff. |FC | | Real | [SPICE] | || 431 |Flicker|Noise Coefficient |KF| || ||Real ||[SPICE] || |__432__|Flicker_Noise_Exponent__________________________|AF_______|______________|_Real___|_[SPICE]___|_ 281 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ECO523 _______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol____|___Unit_____|__Type__|__Ref._____|_ |________________________Circuit_Simulation_Parameters_for_JFET_Transistors________________________|___||||||| | 433 |Threshold Voltage |VTO | V 2 | Real | [SPICE] | || 434 |Transconductance| |BETA| | | A/V || Real ||[SPICE] || | 435 |Channel Length Modulation |LAMBDA | 1/V | Real | [SPICE] | | 436 |Drain Ohmic Resistance |RD | ohm | Real | [SPICE] | || 437 |Source|Ohmic Resistance |RS| || ohm || Real ||[SPICE] || || 438 |Zero-bias|Gate-Source Junction Cap. |CGS| || F ||Real ||[SPICE] || | 439 |Zero-bias Gate-Drain Junction Cap. |CGD | F | Real | [SPICE] | | 440 |Gate Junction Potential |PB | V | Real | [SPICE] | || 441 |Gate|Junction Saturation Current |IS| ||A || Real ||[SPICE] || || 442 |Forward-bias|Depletion Capacitance Coeff. |FC| | | | | Real ||[SPICE] || || 443 |Threshold|Voltage Temperature Coeff. |VTOTC| || V/degC || Real ||[SPICE] || | 444 |BETA Exponential Temperature Coeff. |BETATCE | %/degC | Real | [SPICE] | || 445 |Flicker|Noise Coefficient |KF| || ||Real ||[SPICE] || |__446__|Flicker_Noise_Exponent__________________________|AF__________|___________|_Real___|_[SPICE]__|_ |_______________________Circuit_Simulation_Parameters_for_Bipolar_Transistors_______________________|__||||||| | 447 |Transport Saturation Current |IS |A | Real | [SPICE] | | 448 |Ideal Maximum Forward Beta |BF | | Real | [SPICE] | || 449 |Forward|Current Emission Coefficient |NF| || || Real ||[SPICE] || || 450 |Forward|Early Voltage |VAF| || V || Real ||[SPICE] || || 451 |High|Current Beta Rolloff |IKF| ||A || Real ||[SPICE] || || 452 |B-E|Leakage Saturation Current |ISE| ||A || Real ||[SPICE] || | 453 |B-E Leakage Emission Coefficient |NE | | Real | [SPICE] | | 454 |Ideal Maximum Reverse Beta |BR | | Real | [SPICE] | || 455 |Reverse|Current Emission Coefficient |NR| || || Real ||[SPICE] || | 456 |Reverse Early Voltage |VAR | V | Real | [SPICE] | | 457 |High Reverse Current (Irev) Beta Rolloff |IKR | A | Real | [SPICE] | || || || || || || || | 458 |B-C Leakage Saturation Current |ISC | A | Real | [SPICE] | | 459 |B-C Leak Emission Coefficient |NC | | Real | [SPICE] | | 460 |Zero Bias Base Resistance (Rbase) |RB | ohm | Real | [SPICE] | | | | | | | | | 461 |Rbase Cutoff Current |IRB | A | Real | [SPICE] | | 462 |Minimum Base Resistance |RBM | ohm | Real | [SPICE] | | 463 |Emitter Resistance |RE | ohm | Real | [SPICE] | || 464 |Collector|Resistance |RC| ||ohm || Real ||[SPICE] || | 465 |BE Zero Bias Depletion Capacitance |CJE | F | Real | [SPICE] | || 466 |B-E|Built-in Potential |VJE| || V || Real ||[SPICE] || | 467 |B-E Junction Exponential Factor |MJE | | Real | [SPICE] | || 468 |Ideal|Forward Transit Time |TF| || s ||Real ||[SPICE] || || 469 |TF|Bias Depletion Coefficient |XTF| || || Real ||[SPICE] || |__470__|VBC_Dependence_of_TF____________________________|VTF________|__V________|__Real___|_[SPICE]__|_ 282 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ECO523 ___________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol__|___Unit__|__Type___|__Ref._____|_||||||| | 471 |TF High-current Parameter |ITF | A | Real | [SPICE] | || 472 |Excess|Phase |PTF| || deg ||Real ||[SPICE] || | 473 |B-C Zero Bias Depletion Capacitance |CJC | F | Real | [SPICE] | || 474 |B-C|Built-in Potential |VJC| || V ||Real ||[SPICE] || || 475 |B-C|Junction Exponential Factor |MJC| || ||Real ||[SPICE] || | 476 |B-C Capacitance to Base Connection Ratio |XCJC | | Real | [SPICE] | || 477 |Ideal|Reverse Transit Time |TR| || s ||Real ||[SPICE] || | 478 |Zero Bias Collector-Substrate Capacitance |CJS | F | Real | [SPICE] | || 479 |Substrate-Junction|Built-in Potential |VJS| || V ||Real ||[SPICE] || || 480 |Substrate-Junction|Exponential Factor |MJS| || ||Real ||[SPICE] || || 481 |Beta-Temperature|Exponent |XTB| || eV ||Real ||[SPICE] || || 482 |IS-Temperature|Energy Gap |EG| || ||Real ||[SPICE] || | 483 |IS-Temperature Exponent |XT | | Real | [SPICE] | || 484 |Flicker|Noise Coefficient |KF| || ||Real ||[SPICE] || || 485 |Flicker|Noise Exponent |AF| || ||Real ||[SPICE] || | 486 |Forward-Bias Capacitance Coefficient |FC | | Real | [SPICE] | |__487__|Area_Scale-Factor_______________________________|AREA____|__________|_Real____|_[SPICE]__|_ |_______________________Circuit_Simulation_Parameters_for_MOS_Transistors_______________________|__||||||| | 488 |Model Complexity identifier |LEVEL | | Integer |[SPICE] | | 489 |Surface Potential |PHI | V | Real | [SPICE] | | 490 |Drain Ohmic Resistance |RD | ohm | Real | [SPICE] | || 491 |Source|Ohmic Resistance |RS| || ohm || Real ||[SPICE] || || 492 |Zero-bias|Body-Drain Capacitance |CBD| || F ||Real ||[SPICE] || | 493 |Zero-bias Body-Source Capacitance |CVS | F | Real | [SPICE] | | 494 |Bulk Junction Saturation Current |IS | A | Real | [SPICE] | | 495 |Gate-Source Overlap Cap./Channel Width |CGSO | F/m | Real | [SPICE] | | | | | | | | | 496 |Gate-Drain Overlap Cap./Channel Width |CGDO | F/m | Real | [SPICE] | | | | | | | | | 497 |Gate-Bulk Overlap Cap./Channel Width |CGBO | F/m | Real | [SPICE] | || || || | | || || || | 498 |Drain, Source Diffusion Sheet Resistance |RSH | ohm | Real | [SPICE] | | 499 |Zero-bias Bulk Junction Cap./Area |CJ | F/m2 | Real | [SPICE] | || || || || || || || | 500 |Bulk Junction Bottom grading coefficient |MJ | | Real | [SPICE] | | 501 |Zero-bias Bulk Junction perimeter Cap./l |CJSW | F/m | Real | [SPICE] | || || || || || || || | 502 |Bulk Junction Sidewall grading coeff. |MJSW | | Real | [SPICE] | | 503 |Bulk Junction Saturation Current/Area |JS | A/m2 | Real | [SPICE] | | | | | | | | || 504 |Oxide|Thickness |TOX| || m -3 ||Real ||[SPICE] || || 505 |Substrate|Doping Density |NSUB| || cm-2 ||Real ||[SPICE] || || 506 |Surface|State Density |NSS| || cm-2 ||Real ||[SPICE] || || 507 |Fast|Surface State Density |NFS| || cm ||Real ||[SPICE] || |__508__|Type_of_Gate_Matl._+1=opp._0=Al_-1=sub._________|TPG_____|__________|_Real____|_[SPICE]__|_ 283 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 6. Electrical Attribute List (ALT=2) (continued) ECO523 _______________________________________________________________________________________________________ |__No.__|_____________Definition_________________________|Symbol___|____Unit_____|__Type__|__Ref._____|_||||||| || 509 |Metallurgical|Junction Depth |XJ| || m ||Real ||[SPICE] || || 510 |Lateral|Diffusion Length |LD| || m 2 || Real ||[SPICE] || || 511 |Surface|Mobility |UO| | | cm /V*s || Real ||[SPICE] || || 512 |Maximum|Drift Velocity |VMAX| || m/s ||Real ||[SPICE] || || 513 |Width|Effect on Threshold Voltage |DELTA| || ||Real ||[SPICE] || | 514 |Mobility Modulation term |THETA | 1/V | Real | [SPICE] | | 515 |Static Feedback term |ETA | | Real | [SPICE] | || 516 |Saturation|Field factor |KAPPA| | | ||Real ||[SPICE] || | 517 |Channel Length |L | m | Real | [SPICE] | | 518 |Channel Width |W | m | Real | [SPICE] | || 519 |Lateral|Diffusion Width |WD| || m ||Real ||[SPICE] || | 520 |Zero-bias Threshold Voltage |VTO | V 2 | Real | [SPICE] | || 521 |Transconductance| |KP| | | A/V0:5 || Real ||[SPICE] || || 522 |Bulk|Threshold parameter |GAMMA| || V ||Real ||[SPICE] || | 523 |Channel-length Modulation |LAMBDA | 1/V | Real | [SPICE] | | 524 |Gate Ohmic Resistance |RG | ohm | Real | [SPICE] | | 525 |Bulk Ohmic Resistance |RB | ohm | Real | [SPICE] | | 526 |Drain-Source Shunt Resistance |RDS | ohm | Real | [SPICE] | || 527 |Bulk|Junction Potential |PB| || V ||Real ||[SPICE] || || 528 |Bulk|Junction Forward-bias Cap. Coeff. |FC| | | || Real ||[SPICE] || || 529 |Mobility|Degradation critical field |UCRIT| || V/cm || Real ||[SPICE] || || 530 |Mobility|Degradation exponent |UEXP| || ||Real ||[SPICE] || || 531 |Mobility|Degradation Transverse field k |UTRA| || ||Real ||[SPICE] || || 532 |Channel|Charge coefficient |NEFF| || ||Real ||[SPICE] || | 533 |Fraction of Channel Charge due to Drain |XQC | | Real | [SPICE] | || 534 |Flicker|Noise coefficient |KF| || ||Real ||[SPICE] || |__535__|Flicker_Noise_exponent__________________________|AF_________|____________|_Real___|_[SPICE]__|_ 284 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 7. AEC Attribute List (ALT=3) _____________________________________________________________________________ |__No.__|Definition_________________________|_____Unity_____|__Data_Type__|__-1 | 1 |Air changes per hour | hour 2 | Real | | 2 |Area of glazing | foot | Real | | 3 |Bearing wall | | Logical | | 4 |Bearing wall capacity | pound/foot | Real | | 5 |Building name | | String | | 6 |Building occupancy type | | String | | 7 |Capacity per unit of egress width | | Integer | | 8 |Ceiling cavity depth | inch | Real | | 9 |Ceiling type | | String | | 10 |Combustible | | Logical | | 11 |Concentrated dead load | pound | Real | | 12 |Concentrated live load | pound | Real | | 13 |Cooled | | Logical | | 14 |Cost per square foot | dollar(US) | Real | | 15 |Finish color | | String | | 16 |Finish type | | String | | 17 |Finished floor elevation | foot | Real | | 18 |Finished opening height | inch | Real | | 19 |Finished opening width | inch | Real | | 20 |Fire door | | Logical | | 21 |Fire protection | | Logical | | 22 |Fire rating | hour | Real | | 23 |Fire suppression system | | Logical | | 24 |Fire wall | | Logical | | 25 |Floor name | | String | | 26 |Floor to ceiling height | foot | Real | | 27 |Floor to floor height | foot | Real | | 28 |Floor type | | String | | 29 |Frame type | 2 | String | | 30 |Gross area | foot2 | Real | | 31 |Gross floor area per occupant | foot | Real | | 32 |Hardware type | | String | | 33 |Heated | 2 | Logical | | 34 |Hydrostatic pressure | pound/foot | Real | | 35 |Illumination level | foot-candle3 | Real | | 36 |Infiltration f|oot /minute | Real | | 37 |Latent heat gain | BTU/hour | Real | | 38 |Light reflectance (percent) | | Real | | 39 |Lintel height | inch | Real | | 40 |Live load reduction (percent) | | Real | |__41____|Means_of_egress____________________|_______________|____Logical____| y The use of English rather than SI units follows the current practice of the AEC industry. 285 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 7. AEC Attribute list (ALT=3) (continued) ___________________________________________________________________________ |__No.__|Definition____________________|______Unity_______|__Data_Type__|__2 | 42 |Net area | foot2 | Real | | 43 |Net floor area per occupant | foot | Real | | 44 |Number of stories | | Integer | | 45 |Occupant load | | Integer | | 46 |Opening type | | String | | 47 |Operable | | Logical | | 48 |Relative humidity (percent) | | Real | | 49 |Riser height | inch | Real | | 50 |Riser height, maximum | inch | Real | | 51 |Riser height, minimum | inch | Real | | 52 |Room activity | | String | | 53 |Room name | | String | | 54 |Rough opening height | inch | Real | | 55 |Rough opening width | inch | Real | | 56 |Sensible heat gain | BTU/hour | Real | | 57 |Shading coefficient (percent) | | Real | | 58 |Shear wall | | Logical | | 59 |Shear wall capacity | pound/foot | Real | | 60 |Sill height | inch | Real | | 61 |Slope (percent) | | Real | | 62 |Smoke door | | Logical | | 63 |Smoke rating | hour | Real | | 64 |Smoke wall | 2 | Logical | | 65 |Snow load | pound/foot2 | Real | | 66 |Soil bearing capacity | pound/foot3 | Real | | 67 |Soil density | pound/foot | Real | | 68 |Soil type | | String | | 69 |Sound level | dB | Real | | 70 |Sound reflectance (percent) | | Real | | 71 |Sound transmission class | | Integer | | 72 |Temperature | deg F | Real | | 73 |Thermal transmittance | BTU/hour/foot | Real | | 74 |Tread width | inch | Real | | 75 |Tread width, maximum | inch | Real | | 76 |Tread width, minimum | inch 2 | Real | | 77 |Uniform dead load | pound/foot2 | Real | | 78 |Uniform live load | pound/foot | Real | | 79 |Unit of egress width | inch3 | Real | | 80 |Ventilation | foot /minute | Real | | 81 |Wall type | 2 | String | | 82 |Wind pressure | pound/foot | Real | |__83____|Work_plane_height____________|_______inch________|_____Real______| yThe use of English rather than SI units follows the current practice of the AEC industry. 286 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 8. Process Plant Attribute list (ALT=4) ECO600A _________________________________________________________________________________________________ |__No.__|Definition_______________________________________|__Data_Type__|____Default_Units_y__|__ | 1 |Nominal pipe size | Real | model units | | 2 |Material name | String | | | 3 |End preparation | String | | | 4 |Wall thickness | Real | model units | | 5 |User part number | String | | | 6 |Joint identification number | String | | | 7 |Configuration non-deviation code | Integer | | | 8 |Material non-deviation code | Integer | | | 9 |Specification body | String | | | 10 |Material control level | String | | | 11 |Criticality class | String | | | 12 |Joint type | String | | | 13 |Dry weight/mass value | Real | lbs (pounds) | | 14 |Dry weight/mass units | String | | | 15 |Pipe spool/detail name | String | | | 16 |Functional group code | String | | | 17 |Part type | String | | | 18 |Nominal pipe size type | String | | | 19 |Object identifier | String | | | 20 |Object revision | String | | | 21 |Drawing and item concatenation (find number) | String | | | 22 |Applicability | String | | | 23 |Schedule | String | | | 24 |Service | String | | | 25 |Shock rating | String | | | 26 |Sub-safe | String | | | 27 |Noise critical | String | | | 28 |Wall thickness units | String | | | 29 |Equipment name | String | | | 30 |Equipment function | String | | | 31 |Dry center of gravity (x) | Real | model units | | 32 |Dry center of gravity (y) | Real | model units | | 33 |Dry center of gravity (z) | Real | model units | | 34 |Dry center of gravity units | String | | | 35 |Function | String | | | 36 |Class | String | | | 37 |Pipe specification | String | | | 38 |Type | String | | | 39 |Insulation specification | String | | |__40____|Paint_specification________________________________|__String_____|____________________|_ yModel units refer to the units specified in Global Parameters 14 and 15 287 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 8. Process Plant Attribute List (ALT=4) (continued) ECO600A _____________________________________________________________________________________ |__No.__|Definition___________________________|__Data_Type__|____Default_Units_y__|__ | 41 |Tracing specification | String | | | 42 |Status (detailed, stressed, ...) | String | | | 43 |Tag number | String | | | 44 |Maximum design pressure | Real | psia | | 45 |Maximum design pressure units | String | | | 46 |Maximum design temperature | Real | degree, F | | 47 |Maximum design temperature units | String | | | 48 |Vapor pressure | Real | psia | | 49 |Vapor pressure units | String | | | 50 |Material description | String | | | 51 |Gasket thickness | Real | model units | | 52 |Gasket thickness units | String | | | 53 |Integral gasket code | String | | | 54 |Isometric split point indicator | String | | | 55 |Line/sequence number | String | | | 56 |Instrument loop number | String | | | 57 |Nominal pipe size units | String | | | 58 |Design area | String | | | 59 |Project | String | | | 60 |Valve type | String | | | 61 |Valve size | Real | model units | | 62 |Valve size units | String | | | 63 |Valve code | String | | | 64 |Molecular weight | Real | lb/lb mole | | 65 |Molecular weight units | String | | | 66 |Flow rate | Real | lb/hr | | 67 |Flow rate units | String | | | 68 |Flow material | String | | | 69 |Type instrument | String | | | 70 |Tube specification | String | 3 | | 71 |Density | Real | lb/ft | | 72 |Density units | String | | | 73 |Viscosity | Real | centipoise | | 74 |Viscosity units | String | | | 75 |Heat capacity | Real | BTU/lb F | | 76 |Heat capacity units | String | | | 77 |Operating temperature | Real | degree, F | | 78 |Operating temperature units | String | | | 79 |Operating pressure | Real | psia | |__80____|Operating_pressure_units_____________|____String_____|____________________|_ yModel units refer to the units specified in Global Parameters 14 and 15 288 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 8. Process Plant Attribute List (ALT=4) (continued) ________________________________________________________________________________ ECO600A |__No.__|Definition______________________|__Data_Type__|____Default_Units_y__|__ | 81 |Composition | String | | | 82 |Bldg/bent | String | | | 83 |Elevation/floor | Real | model units | | 84 |Elevation/floor units | String | | | 85 |Pressure rating | Real | psi | | 86 |Pressure rating units | String | | | 87 |Flange finish | String | | | 88 |Flow direction | String | | | 89 |Project area | String | | | 90 |Note | String | | | 91 |Note identifier | String | | | 92 |Wet weight/mass value | Real | lbs (pounds) | | 93 |Wet weight/mass units | String | | | 94 |Wet center of gravity (x) | Real | model units | | 95 |Wet center of gravity (y) | Real | model units | | 96 |Wet center of gravity (z) | Real | model units | | 97 |Wet center of gravity units | String | | | 98 |Outside diameter | Real | model units | | 99 |Outside diameter units | String | | | 100 |Dimensional standard | String | | | 101 |Weld i.d. | String | | | 102 |Component name | String | | | 103 |Spec option code | String | | | 104 |Fabrication category | String | | | 105 |Material takeoff indicator | String | | | 106 |Through-bolted indicator | Logical | | | 107 |Valve operator type | String | | | 108 |Reinforcing pad thickness | Real | model units | | 109 |Reinforcing pad thickness units | String | | | 110 |Reinforcing pad width | Real | model units | | 111 |Reinforcing pad width units | String | | | 112 |Chain length | Real | model units | | 113 |Chain length units | String | | | 114 |Pipe support type | String | | | 115 |Support detail reference | String | | | 116 |Bolt type | String | | | 117 |Bolt length | Real | model units | | 118 |Bolt length units | String | | | 119 |Bolt diameter | Real | model units | |__120__|Bolt_diameter_units______________|_____String_____|____________________| yModel units refer to the units specified in Global Parameters 14 and 15 289 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 8. Process Plant Attribute List (ALT=4) (continued) ECO600A __________________________________________________________________________ |__No.__|Definition________________|__Data_Type__|____Default_Units_y__|__ | 121 |Insulation thickness | Real | model units | | 122 |Insulation thickness units | String | 3 | | 123 |Insulation density | Real | lbs/ft | | 124 |Insulation density units | String | | | 125 |Fluid code | String | | | 126 |Unit number | String | | | 127 |Item number | String | | | 128 |Part number | String | | | 129 |Safety zone | String | | | 130 |Design code | String | | | 131 |Nozzle length #1 | Real | model units | | 132 |Nozzle length #2 | Real | model units | | 133 |Nozzle length units | String | | | 134 |Nozzle bend radius | Real | model units | | 135 |Nozzle bend radius units | String | | | 136 |Nozzle type | String | | | 137 |Quantity | Real | piece | | 138 |Quantity units | String | | | 139 |Pipe fit-up | Real | model units | |__140__|Pipe_fit-up_units___________|___String_____|_____________________| yModel units refer to the units specified in Global Parameters 14 and 15 290 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 9. Electrical and PWA Manufacturing Attribute List (ALT=5) ECO578 ______________________________________________________________________________________________________ |__No.__|AVC__|__Definition__________________________|___Symbol__|__Unit____|__Type__|__yRef.________|_ | 1 | 9 |Component Physical Orientation | | | |PWAMA1 | | | | X Rotation, Minimum | |degrees | Real | | | | | Y Rotation, Minimum | |degrees | Real | | | | | Z Rotation, Minimum | |degrees | Real | | | | | X Rotation, Nominal | |degrees | Real | | | | | Y Rotation, Nominal | |degrees | Real | | | | | Z Rotation, Nominal | |degrees | Real | | | | | X Rotation, Maximum | |degrees | Real | | | | | Y Rotation, Maximum | |degrees | Real | | |_______|_______|_____Z_Rotation,_Maximum__________|_______________|degrees__|_Real___|______________|_ | 2 | 9 |PWA Physical Orientation | | | |PWAMA2 | | | | X Rotation, Minimum | |degrees | Real | | | | | Y Rotation, Minimum | |degrees | Real | | | | | Z Rotation, Minimum | |degrees | Real | | | | | X Rotation, Nominal | |degrees | Real | | | | | Y Rotation, Nominal | |degrees | Real | | | | | Z Rotation, Nominal | |degrees | Real | | | | | X Rotation, Maximum | |degrees | Real | | | | | Y Rotation, Maximum | |degrees | Real | | |_______|_______|_____Z_Rotation,_Maximum__________|_______________|degrees__|_Real___|______________|_ | 3 | 3 |Component Physical Thickness | | | |PWAMA3 | | | | Minimum | |inch | Real | | | | | Nominal | |inch | Real | | |_______|_______|_____Maximum_______________________|______________|inch_____|_Real___|______________|_ | 4 | 2 |Component Placement | | | |PWAMA4 | | | | Form Code | | | String | | |_______|_______|_____Form_Code_Description_________|______________|_________|_String__|_____________|_ |___5___|__1____|Component_Placement_Depth_Stop__|_________________|_________|_String__|PWAMA5___|____ | 6 | 3 |Component Placement Force | | | |PWAMA6 | | | | Minimum | |ounces | Real | | | | | Nominal | |ounces | Real | | |_______|_______|_____Maximum_______________________|______________|ounces__|__Real___|______________|_ |___7___|__1____|Component_Placement_Machine_____|_________________|_________|_String__|PWAMA7___|____ |___8___|__1____|Component_Placement_Tool_________|________________|_________|_String__|PWAMA8___|____ | 9 | 2 |Component Placement Feeder | | | |PWAMA9 | | | | ID | | | String | | |_______|_______|_____Description_____________________|____________|_________|_String__|_____________|_ | 10 | 3 |Component Placement Feeder | | | |PWAMA10 | | | | X location | |inch | Real | | | | | Y Location | |inch | Real | | |_______|_______|_____Z_location_______________________|___________|inch_____|_Real___|______________|_ yReferences are to the explanatory notes following this table. 291 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Table 9. Electrical and PWA Manufacturing Attribute List (ALT=5) (continued) ______________________________________________________________________________________________________ |__No.__|AVC__|__Definition_____________________________|__Symbol__|___Unit__|_Type__|__yRef.________|_ |___11___|_1____|Component_Placement_Pick_Point_ID__|________________|________|String__|PWAMA11__|____ |___12___|_1____|Allowable_Test_Point_ID_______________|_____________|________|String__|PWAMA12__|____ |___13___|_1____|Actual_Test_Point_ID__________________|_____________|________|String__|PWAMA13__|____ |___14___|_1____|Physical_Component_Device_ID________|_______________|________|String__|PWAMA14__|____ |___15___|_1____|Printed_Wire_Assembly_ID_____________|______________|________|String__|PWAMA15__|____ |___16___|_1____|PWA_Assembly_ID_____________________|_______________|________|String__|PWAMA16__|____ |___17___|_1____|PWA_Thru_Via_ID_____________________|_______________|________|String__|PWAMA17__|____ |___18___|_1____|PWA_Blind_Via_ID_____________________|______________|________|String__|PWAMA18__|____ |___19___|_1____|PWA_Fiducial_ID______________________|______________|________|String__|PWAMA19__|____ |___20___|_1____|Electrostatic_Discharge_Rating_________|____________|________|String__|PWAMA20__|____ | 21 | 3 |Component Placement Bonding | | | |PWAMA21 | | | | ID | | |String | | | | | Material Spec. | | |String | | |_______|_______|_____Process_Spec.______________________|___________|________|String__|______________| | 22 | 3 |PWA Design Thickness | | | |PWAMA22 | | | | Top | | inch |Real | | | | | Bottom | | inch |Real | | |_______|_______|_____Total______________________________|___________|_inch___|Real___|_______________| yReferences are to the explanatory notes following this table. 292 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Explanatory notes for the Electrical and PWA Manufacturing Attribute List (ALT=5) in Table 9: ECO578 PWAMA1 Component Physical Orientation The Component Physical Orientation attribute values pertain to the actual physical placement orientation of the component, about the X, Y, or Z axis, on the PWA, either by hand, auto- inserter, pick-and-place machine, robot, or other assembly technique. This is not necessarily the same orientation that is applied to the Network Subfigure Instance in the exchange file. These values are with respect to the component's placement in its dispensing mechanism (feeder, DIP tube, part carousel, waffle pack position, etc.). When the rotation is applied to the component, the resulting orientation is the actual component placement orientation on the assembled PWA. This attribute should be assigned to a Network Subfigure Instance which is used to represent a physical electronic component. This attribute can also be assigned to a Subfigure Instance which is used to represent a mechanical component or fastening device. PWAMA2 PWA Physical Orientation The PWA Physical Orientation attribute values pertain to the actual physical orientation of the PWA, about the X, Y, or Z axis, in its work cell. These values are used by the manufacturing postprocessing software to compensate for the PWA's rotation with respect to the original CAD model orientation. When the rotation is applied to the PWA, the resulting orientation is the actual PWA orientation in the work cell's coordinate system. For a particular board, there may be several different work cell environments used during the as- sembly process. Therefore, the PWA Physical Orientation X, Y, and Z Rotation attributes should be assigned to the Group Associativity that defines the components that are associated with each process. If there is only one work cell environment associated with the manufacturing process, the attributes should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file. PWAMA3 Component Physical Thickness The Component Physical Thickness attribute represents the design thickness of the component after it has been assembled on the PWA. It is defined as the distance from the surface of the PWA, where the component is attached or mounted, to the highest point (most protruding) on the component. This value is used for component interference checking, insertion postprocessing, and robotic tool path generation. The Component Physical Thickness Minimum value is the minimum design thickness of the compo- nent after it has been assembled on the PWA. The Component Physical Thickness Nominal value is the nominal design thickness of the component after it has been assembled on the PWA. The Component Physical Thickness Maximum value is the maximum design thickness of the component after it has been assembled on the PWA. This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electrical component. This attribute can also be assigned to a Subfigure Defi- nition/Instance which is used to represent a mechanical component or fastening device. PWAMA4 Component Placement Form The Component Placement Form attribute specifies the way that the leads of certain components should be shaped, whether they are formed automatically, semi-automatically, or by hand. Although there is not a universally accepted document to control form code naming, most organizations have come up with their own standard naming conventions which should be used as the Component 293 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) Placement Form Code Value. This data is typically used for transistors, op-amps, transformers, and vertically mounted components. The Component Placement Form Code Description value is additional information about a specific form code such as a particular die or machine setting. This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. PWAMA5 Component Placement Depth Stop The Component Placement Depth Stop attribute is the actual placement machine depth stop or distance that the insertion machine should use when placing the component. Many insertion machines have a set of graduated depth stops, with fixed increments, that a com- ponent can be placed with. Other insertion machines read a string that represents the height, from the surface of the PWA, that the mounted component should be after assembly. If the value is an insertion machine code such as "C43", "D6", or "1a", then the string should be placed in the attribute. The insertion machine postprocessing software will utilize the code in order to calibrate the machine. If the value is the actual linear distance that the insertion machine should use to place the component, then the value should be placed in the attribute as a string field, such as "0.125". The value should reflect the linear distance measured in inches. This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. This attribute may also be assigned to a Subfigure Definition/Instance which is used to represent a mechanical component or fastening device. PWAMA6 Component Placement Force The Component Placement Force attribute is the pressure that should be exerted on a component during the placement process. The insertion machine uses this data and the feedback from one or more tactile sensors to determine if the component has met the design criteria for placement. This is very important for SMT applications, where the component leads are to be pushed into solder paste on the PWA, with a predetermined force to insure good bonding during the solder process. The force is variable from component to component depending on package type and pin count. The Component Placement Force Minimum value is the minimum pressure that should be exerted on a component during the placement process. The Component Placement Force Nominal value is the nominal pressure that should be exerted on a component during the placement process. The Component Placement Force Maximum value is the maximum pressure that should be exerted on a component during the placement process. This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. This attribute may also be assigned to a Subfigure Definition/Instance which is used to represent a mechanical component or fastening device. PWAMA7 Component Placement Machine The Component Placement Machine attribute is the name, number, or other identification of the machine that is used to install the component on the PWA. This data is used in CAD or CAPP systems to assign components to machines during the design phase of the PWA. For a particular board, there may be several different insertion sequences. Therefore, the Component Placement Machine attribute should be assigned to the Group Associativity that defines the com- ponents that are associated with each insertion sequence. If there is no insertion sequence specified for the board, the attribute should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file. 294 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) PWAMA8 Component Placement Tool The Component Placement Tool attribute is the name of the tool that is used to handle a part during the assembly process. This data element is used by manufacturing postprocessing software to determine which end-effector or tooling head should be used to pick up a component. This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. This attribute may also be assigned to a Subfigure Definition/Instance which is used to represent a mechanical component or fastening device. PWAMA9 Component Placement Feeder The Component Placement Feeder attribute is the feeder machine ID, or organization dependent code for the placement feeder machine, and its description. The ID value is typically a short string of characters that has significance to a particular machine process. The Component Placement Feeder Description value is the name of the part feeder that is used for component placement. This could include names such as waffle_pack_2, TR09, or others that are machine specific identifiers. The name could apply to SMT, through-hole technology, and me- chanical components for specifying where they are physically located in the work cell or placement machine. (Note: most components have standard places that they are located for each placement configuration.) This attribute should be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. This attribute may also be assigned to a Subfigure Definition/Instance which is used to represent a mechanical component or fastening device. PWAMA10 Component Placement Feeder Location The Component Placement Feeder location attribute is the coordinate location for the feeder input. This value is typically a machine absolute coordinate. By analyzing the Component Placement Feeder X, Y, and Z Location and the Component Placement Pick Point X, Y, and Z Location, one is able to determine the exact location of a component in its placement machine. Furthermore, by analyzing the Component Placement Physical Orientation, and PWA Physical Orientation, one is able to determine the exact 3-dimensional movement that is required to place a component. This attribute should always be assigned to a Network Subfigure Definition/Instance which is used to represent a physical electronic component. This attribute may also be assigned to a Subfigure Definition/Instance which is used to represent a mechanical component or fastening device. PWAMA11 Component Placement Pick Point ID The Component Placement Pick Point ID attribute is that feature on a component which is the location that the placement head, tool, or robot end-effector should use for attaching to the part during the placement process. This is generally the center of an SMT component, but may vary for some odd shaped parts or special assembly methods that require holding the part at an offset and/or different angle. This attribute is interpreted as a logical value. This attribute can be assigned to any entity that can be used to locate a feature. If the attribute is assigned to an entity, the parent entity is defined as a component placement pick point, and the string value in the attribute is used to further identify it. PWAMA12 Allowable Test Point ID The Allowable Test Point attribute specifies that a physical feature on the PWA (via, through-hole component pin, SMT lan area, or dedicated test point) is available for test point access or probing. Interference from other components, tool fixtures, and/or physical parameters of an available feature 295 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) (e.g., a SMT lan pad is too fragile for a particular probing technique) could make a candidate test point unacceptable. This attribute is interpreted as a logical value. More than one Allowable Test Point attribute may be associated with the same point to represent its availability for several test schemes (e.g., a particular point may be used for PWB test, In-Circuit, and robotic probing while another might be available only for PWB test). Typical values for this attribute are strings such as: "PWB" (for bare board test), "ICT" (for in-circuit or combinational), "R" (for robotic probing), or "NA" (for not available). This attribute may be assigned to any entity that may be used to locate a feature. If the attribute is assigned to an entity, the parent entity is defined as an allowable test point, and the string value in the attribute is used to further identify it. If there is no attribute assigned to an entity, it is not an allowable test point. PWAMA13 Actual Test Point ID The Actual Test Point attribute specifies that a physical feature on the PWA (via, through-hole component pin, SMT lan area, or dedicated test point) has been assigned as a test point. This attribute is interpreted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a test point, and the string value in the attribute is used to further identify it. If there is no attribute assigned to an entity, it is not a test point. More than one Actual Test Point attribute may be associated with the same point to represent that it is used in several test schemes (e.g., a particular point may be used for PWB test, In-Circuit, and robotic probing while another might be available only for PWB test). Typical values for this attribute are strings that define the name/model number of the tester such as DITMCO_9100, HP3065, GR2750, L293, etc. Another use could be to organize the test points according to the class of test such as PWB, ICT, functional, etc. The primary purpose of this attribute is to convey the design intent of where and how the test point information is to be used. This attribute may be assigned to any entity that may be used to locate a feature. PWAMA14 Physical Component Device ID The Physical Component Device ID attribute specifies that an object is a physical component. This attribute is interpreted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a physical component device, and the string value in the attribute is used to further identify it. This attribute should be assigned to a Network Subfigure Definition or Subfigure Definition which is used to represent a physical component device. PWAMA15 Printed Wire Assembly ID The Printed Wire Assembly ID attribute specifies that an object is a PWA. This attribute is inter- preted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a PWA, and the string value in the attribute is used to further identify it. This attribute should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file. PWAMA16 PWA Assembly ID The PWA Assembly ID attribute specifies that an object is an assembly of PWA's. This attribute is interpreted as a logical value. 296 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) If the attribute is assigned to an entity, the parent entity is defined as an assembly of PWA's, and the string value in the attribute is used to further identify it. This attribute should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file (which represents an assembly of Printed Wire Assemblies). PWAMA17 PWA Thru Via ID The PWA Thru Via ID attribute specifies that an object is a thru via. This attribute is interpreted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a thru via, and the string value in the attribute is used to further identify it. This attribute should be assigned to a Network Subfigure Definition or Subfigure Definition which is used to represent a thru via. PWAMA18 PWA Blind Via ID The PWA Blind Via ID attribute specifies that an object is a blind via. This attribute is interpreted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a blind via, and the string value in the attribute is used to further identify it. This attribute should be assigned to a Network Subfigure Definition or Subfigure Definition which is used to represent a blind via. PWAMA19 PWA Fiducial ID The PWA Fiducial ID attribute is used to specify that an object is a fiducial. A fiducial is an object that is used by PWA insertion equipment to line up the board or a component, such that the pins are properly inserted on or in the board. This attribute is interpreted as a logical value. If the attribute is assigned to an entity, the parent entity is defined as a fiducial, and the string value in the attribute is used to further identify it. This attribute should be assigned to a Subfigure Definition which is used to represent a fiducial. PWAMA20 Electrostatic Discharge Rating The Electrostatic Discharge Rating attribute specifies how sensitive a component or PWA is to electrostatic energy. The value of the attribute is a string which defines the ESD rating. This attribute should be assigned to a Network Subfigure Definition which is used to represent a physical electronic component. This attribute should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file. PWAMA21 Component Placement Bonding The Component Placement Bonding attribute specifies that a feature represents the location for bonding material. The feature can represent a single point, in which it will most likely represent a spot of glue. The feature can also represent a line or polygonal shape, in which it may represent an area to be coated with solder paste. In either case, a Component Placement Bonding Material Specification and Component Placement Bonding Process Specification values shall be specified further defining the intended meaning of the data. The ID value is interpreted as a logical value. The Component Placement Bonding Material Specification value is the type of bonding material that should be used at the specified location. The value of the attribute is a string defining the material specification. The Component Placement Bonding Process Specification value is the type of bonding process for the specified location. The value of the attribute is a string defining the process specification. 297 4.75 ATTRIBUTE TABLE DEFINITION ENTITY (TYPE 322) If the attribute is assigned to an entity, the parent entity is defined as a bonding area, and the ID string value is used to further identify it (e.g., adhesive, glue, solder, paste, etc.). This attribute can be assigned to any entity that can be used to locate a feature. PWAMA22 PWA Design Thickness (Top, Bottom, and Total) The Printed Wire Assembly Design Thickness attribute is the maximum allowable distance from the top surface of the board to the top of the highest component, the maximum allowable distance from the bottom surface of the board to the bottom of the lowest component, and the maximum total thickness of the board. All of the distances are associated with the board after component placement. The top and bottom surface of the board is based on which side is represented by the COMP_PLACEMENT_T functional level and the COMP_PLACEMENT_B functional level, respectively, in the Level to PWB Layer Map Property Entity (Type 406, Form 24). This attribute should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the attribute should stand alone in the file. 298 4.76 ASSOCIATIVITY INSTANCE ENTITY (TYPE 402) 4.76 Associativity Instance Entity (Type 402) Each time an associativity relation is needed in the file an Associativity Instance Entity is used. The form number of the associativity instance will identify the meaning of the entity. If the form number is between 1 and 5000, the definition is specified as described in Section 4.67. If the form number is between 5001 and 9999, an associativity definition will occur in the file, and the structure field of the instance (DE Field 3) will contain a pointer to the directory entry of the Associativity Definition Entity (Type 302). Each entity that is a member of an associativity instance can contain a back pointer to the associa- tivity instance (see Section 2.2.4.4.2). The parameters K and N1, N2, . .,.NK are specified in the associativity definition (see Section 4.67). The general format of the parameter data for an Associativity Instance Entity is: Parameter Data Index__ Name____ Type___ Description___ 1 NE1 Integer Number of class one entries 2 NE2 Integer Number of class two entries .. . . . .. .. K NEK Integer Number of class K entries For K classes with (NE1,. .,.NEK) entries with (N1,. .,.NK) items per entry 1+K I(1,1,1) Variable Class 1, Entry 1, Item 1 . I(1,1,2) Variable Class 1, Entry 1, Item 2 .. . . . .. .. . I(1,1,N1) Variable Class 1, Entry 1, Item N1 . I(1,2,1) Variable Class 1, Entry 2, Item 1 .. . . . .. .. . I(1,2,N1) Variable Class 1, Entry 2, Item N1 .. . . . .. .. . I(1,NE1,1) Variable Class 1, Entry NE1, Item 1 .. . . . .. .. . I(1,NE1,N1) Variable Class 1, Entry NE1, Item N1 . I(2,1,1) Variable Class 2, Entry 1, Item 1 .. . . . .. .. . I(2,1,N2) Variable Class 2, Entry 1, Item N2 . I(2,2,1) Variable Class 2, Entry 2, Item 1 .. . . . .. .. . I(2,2,N2) Variable Class 2, Entry 2, Item N2 .. . . . .. .. . I(2,NE2,N2) Variable Class 2, Entry NE2, Item N2 .. . . . .. .. . I(K,1,1) Variable Class K, Entry 1, Item 1 299 4.76 ASSOCIATIVITY INSTANCE ENTITY (TYPE 402) .. . . . .. .. . I(K,NEK,NK) Variable Class K, Entry NEK, Item NK Additional pointers as required (see Section 2.2.4.4.2). 300 4.76.1.1 (TYPE 402, FORM 1) - GROUP 4.76.1 Predefined Associativities. As defined in Section 4.67, the Associativity Definition Entity (Type 302) will only occur in the file for Form Numbers 5001 through 9999. The following paragraphs contain the definitions of the predefined associativities as they would appear if they were defined by an implementor. Also included in this Section are the descriptions of each associativity's ECO532 parameters in a manner similar to other entities in this specification. 4.76.1.1 FORM NUMBER: 1 Group The Group Associativity allows a collection of a set of entities to be maintained as a single, logical entity. Figure 75 is an example. There are four form numbers which specify group associativities: _______________________________________________________________ |__Form__|__________________Meaning____________________________| | 1 |Unordered group with backpointers required | | 7 |Unordered group with backpointers not required | | 14 |Ordered group with backpointers required | |____15____|Ordered_group_with_backpointers_not_required____|__ The first (Form=1) is defined here; the others are defined in Sections 4.76.1.7 (Form=7), 4.76.1.14 (Form=14), and 4.76.1.15 (Form=15), respectively. DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 1 Back pointers required 3 2 Unordered 4 1 One item per entry 5 1 The item is a pointer 301 4.76.1.1 (TYPE 402, FORM 1) - GROUP DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of entries 2 DE1 Pointer Pointer to the DE of the first entity .. . . . .. .. 1+N DEN Pointer Pointer to the DE of the last entity Additional pointers as required (see Section 2.2.4.4.2). 302 4.76.1.2 (TYPE 402, FORM 2) - EXTERNAL LOGICAL REFERENCE FILE INDEX 4.76.1.2 FORM NUMBER: 2 External Logical Reference File Index The use of this associativity is deprecated (see Appendix F). 303 4.76.1.3 (TYPE 402, FORM 3) - VIEWS VISIBLE 4.76.1.3 FORM NUMBER: 3 Views Visible When an entity is to be displayed in a single view, a pointer to that View Entity is entered in Parameter 6 of the entity's DE. If an entity is to be displayed in more than one view but not all views, Parameter 6 of its DE contains a pointer to an instance of a Form 3 associativity. This form of the associativity contains two classes of information. The first class contains the number of views visible followed by pointers to each of the view entities visible in the specific associativity instance. The second class contains the number of entities whose display is specified by this instance, followed by pointers to each of the entities. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 2 1 Back pointers required 3 2 Unordered 4 1 One item per entry 5 1 Item is a pointer (to view entity) Class 2 6 2 Back pointers not required 7 2 Unordered 8 1 One item per entry 9 1 Item is a pointer (to other entity) 304 4.76.1.3 (TYPE 402, FORM 3) - VIEWS VISIBLE DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0001** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 3 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N1 Integer Number of views visible 2 N2 Integer Number of entities displayed in these views, or zero ECO521 3 DEV1 Pointer Pointer to the DE of the first View Entity .. . . . .. .. 2+N1 DEVN1 Pointer Pointer to the DE of the last View Entity 3+N1 DE1 Pointer Pointer to the DE of the first entity whose display is being specified by this associativity instance .. . . . .. .. 2+N2+N1 DEN2 Pointer Pointer to the DE of the last entity whose display is being spec- ified by this associativity instance Additional pointers as required (see Section 2.2.4.4.2). 305 4.76.1.4 (TYPE 402, FORM 4) - VIEWS VISIBLE, COLOR, LINE WEIGHT 4.76.1.4 FORM NUMBER: 4 Views Visible, Color, Line Weight This associativity is an extension of Form Number 3. For those entities that are visible in multiple views, but must have a different line font, color number, or line weight in each view, there will be an occurrence of the associativity instance Form Number 4. In the parameter data portion of the associativity instance, the Parameter N1 will indicate the number of blocks containing the view visible, line font, color number, and line weight specifications. Each block will contain a pointer to the View Entity (Type 410), a line font value or 0, a pointer to a Line Font Definition Entity (Type 304) if the line font value was 0, a color value or pointer to a Color Definition Entity (Type 314), and a line weight value. Parameter N2 will contain the number of entities which are members of this associativity (i.e., entities which have this particular display ECO521 characteristic). If Parameter N2 is set to zero, then this field is ignored. Note that N2 may often be 1. If more than one entity appears in Class 2 the complete set of display characteristics in Class 1 apply to each entity in Class 2. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (View) 2 1 Back pointers required 3 2 Unordered 4 5 Five items per entry (Entry template) 5 1 Pointer to View Entity 6 2 Line Font value 7 1 Pointer to Line Font Definition Entity 8 3 Color Number (value) or pointer 9 2 Line Weight (value) Class 2 (Entity) 10 2 Back pointers not required 11 2 Unordered 12 1 One item per entry 13 1 Item is a pointer (to entity) 306 4.76.1.4 (TYPE 402, FORM 4) - VIEWS VISIBLE, COLOR, LINE WEIGHT DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0001** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 4 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N1 Integer Number of blocks containing the view visible, line font, color number, and line weight information 2 N2 Integer Number of entities which have this particular set of display characteristics, or zero ECO521 3 DEV1 Pointer Pointer to the DE of the first View Entity 4 LF1 Integer Line font value or zero 5 DEF1 Pointer If parameter 4 = 0, Pointer to the DE of the Line Font Definition Entity. Otherwise = 0 6 CN1 Integer Color number value 1 or pointer to Color Definition Entity or Pointer 7 LW1 Integer Line weight value 1 8 DEV2 Pointer Pointer to the DE of the second View Entity .. . . . .. .. 2+5*N1 LWN1 Integer Last line weight value 3+5*N1 DE1 Pointer Pointer to the DE of the first entity .. . . . .. .. 2+N2+5*N1 DEN2 Pointer Pointer to the DE of the last entity Additional pointers as required (see Section 2.2.4.4.2). 307 4.76.1.5 (TYPE 402, FORM 5) - ENTITY LABEL DISPLAY 4.76.1.5 FORM NUMBER: 5 Entity Label Display Some entities may have one or more possible displays for their entity labels, depending on the view in which they are being displayed. For those entities, the Label Display Field (Field 8) of the DE contains a pointer to an instance of this associativity. In the parameter data portion of the associativity instance, the parameter N will indicate the number of blocks containing label placement information. Each block will contain a pointer to a view entity which specifies the view of visibility. The remaining information (text location, leader, and level number) applies to the label for that view. DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 2 Back pointers not required 3 1 Ordered 4 7 Seven items per entry 5 1 Pointer to View Entity 6 2 XT of text location 7 2 YT of text location 8 2 ZT of text location 9 1 Pointer to Leader Entity 10 2 Entity label level number 11 1 Pointer to entity 308 4.76.1.5 (TYPE 402, FORM 5) - ENTITY LABEL DISPLAY DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 5 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of label placements 2 DEV1 Pointer Pointer to the DE of the first View Entity 3 XT1 Real XT coordinate of text location in first view 4 YT1 Real YT coordinate of text location in first view 5 ZT1 Real ZT coordinate of text location in first view 6 DEARR1 Pointer Pointer to the DE of the Leader Entity in first view 7 LLN1 Integer Entity label level number in first view 8 DE1 Pointer Pointer to the DE of the first entity being displayed .. . . . .. .. -5+7*N DEVN Pointer Pointer to the DE of the last View Entity -4+7*N XTN Real XT coordinate of text location in last view -3+7*N YTN Real YT coordinate of text location in last view -2+7*N ZTN Real ZT coordinate of text location in last view -1+7*N DEARRWN Pointer Pointer to the DE of the Leader Entity in last view 7*N LLNN Integer Entity label level number in last view 1+7*N DEN Pointer Pointer to the DE of the last entity being displayed Additional pointers as required (see Section 2.2.4.4.2). 309 4.76.1.6 TYPE 402, FORM 6) - VIEW LIST 4.76.1.6 FORM NUMBER: 6 View List The use of this associativity is deprecated (see Appendix F). 310 4.76.1.7 (TYPE 402, FORM 7) - GROUP W/O BACK POINTERS 4.76.1.7 FORM NUMBER: 7 Group Without Back Pointers DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 2 Back pointers not required 3 2 Unordered 4 1 One item per entry 5 1 The item is a pointer DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 7 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of entries 2 DE1 Pointer Pointer to the DE of the first entity .. . . . .. .. 1+N DEN Pointer Pointer to the DE of the last entity Additional pointers as required (see Section 2.2.4.4.2). 311 4.76.1.8 (TYPE 402, FORM 8) - SIGNAL STRING 4.76.1.8 FORM NUMBER: 8 Signal String The use of this associativity is deprecated (see Appendix F). 312 4.76.1.9 (TYPE 402, FORM 9) - SINGLE PARENT 4.76.1.9 FORM NUMBER: 9 Single Parent This associativity defines a logical structure of one independent (parent) entity and one or more subordinate (children) entities. Both parent and child entities require back pointers to this instance. Any necessary display param- eters are governed by the parent entity. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (parent) 2 1 Back pointers required 3 2 Unordered 4 1 One item per entry 5 1 Item is pointer to parent entity Class 2 (children) 6 1 Back pointers required 7 1 Ordered 8 1 One item per entry 9 1 Item is pointer to child entity DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 9 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of parent entities (NP=1 is required) 2 NC Integer Number of children 3 DE Pointer Pointer to parent entity 4 DE1 Pointer Pointer to the DE of the first child entity .. . . . .. .. 2+NC DENC Pointer Pointer to the DE of the last child entity Additional pointers as required (see Section 2.2.4.4.2). 313 4.76.1.10 (TYPE 402, FORM 10) - TEXT NODE 4.76.1.10 FORM NUMBER: 10 Text Node The use of this associativity is deprecated (see Appendix F). 314 4.76.1.11 (TYPE 402, FORM 11) - CONNECT NODE 4.76.1.11 FORM NUMBER: 11 Connect Node The use of this associativity is deprecated (see Appendix F). 315 4.76.1.12 (TYPE 402, FORM 12) - EXTERNAL REFERENCE FILE INDEX 4.76.1.12 FORM NUMBER: 12 External Reference File Index The External Reference File Index Entity appears in one file which contains definitions referenced by another file. It contains a list of the symbolic names used by the referencing files and the DE pointers to the corresponding definitions within the referenced file. See Section 3.6.4 and the External Reference Entity (Type 416) for more detail. DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class (externally referenced entities) 2 2 Backpointers not required 3 2 Unordered list of entries in a class 4 2 Number of items in an entry 5 2 First item is a value (External Reference Entity symbolic name) 6 1 Second item is a pointer (internal entity DE pointer) DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 12 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of index entries 2 NAME1 String First External Reference Entity symbolic name 3 PTR1 Pointer Pointer to the DE of the first internal entity .. . . . .. .. 2N NAMEN String Last External Reference Entity symbolic name 1+2*N PTRN Pointer Pointer to the DE of the last internal entity Additional pointers as required (see Section 2.2.4.4.2). 316 4.76.1.13 (TYPE 402, FORM 13) - DIMENSIONED GEOMETRY 4.76.1.13 FORM NUMBER: 13 Dimensioned Geometry This entity has been replaced by the new form of the Dimensioned Geometry Associativity Entity ECO606 (Type 402, Form 21) and should no longer be used by preprocessors. When that entity (Type 402, Form 21) has been tested sufficiently and is moved to the main body of this Specification, this entity (Type 402, Form 13) will be moved to the Obsolete Entities Appendix and its use will be deprecated. This associativity links a dimension entity with the geometry entities it is dimensioning. The pointers to the entities being dimensioned have interpretations related to the type of dimension entity. See Figure 80. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (Dimension Entity) 2 1 Back pointers required 3 2 Unordered 4 1 One item (pointer to dimension) 5 1 Item is pointer Class 2 (Related Geometry) 6 2 Back pointers not required 7 2 Unordered 8 1 One item per entry (pointers to geometry) 9 1 Item is pointer 317 4.76.1.13 (TYPE 402, FORM 13) - DIMENSIONED GEOMETRY DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 13 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 ND Integer Number of dimensions (ND=1 is required) 2 NG Integer Number of associated geometry entities 3 DIMPTR Pointer Pointer to the DE of the dimension entity 4 GEOM1 Pointer Pointer to the DE of the first geometry entity .. . . . .. .. 3+NG GEOMNG Pointer Pointer to the DE of the last geometry entity Additional pointers as required (see Section 2.2.4.4.2). 318 4.76.1.13 (TYPE 402, FORM 13) - DIMENSIONED GEOMETRY Figure 80. Dimensioned Geometry Associativity 319 4.76.1.14 (TYPE 402, FORM 14) - ORDERED GROUP W/ BACK POINTERS 4.76.1.14 FORM NUMBER: 14 Ordered Group with Back Pointers DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 1 Back pointers required 3 1 Ordered 4 1 One item per entry 5 1 The item is a pointer DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 14 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of entries 2 DE1 Pointer Pointer to the DE of the first entity .. . . . .. .. 1+N DEN Pointer Pointer to the DE of the last entity Additional pointers as required (see Section 2.2.4.4.2). 320 4.76.1.15 (TYPE 402, FORM 15) - ORDERED GROUP W/O BACK POINTERS 4.76.1.15 FORM NUMBER: 15 Ordered Group without Back Pointers DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 2 Back pointers not required 3 1 Ordered 4 1 One item per entry 5 1 The item is a pointer DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 15 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of entries 2 DE1 Pointer Pointer to the DE of the first entity .. . . . .. .. 1+N DEN Pointer Pointer to the DE of the last entity Additional pointers as required (see Section 2.2.4.4.2). 321 4.76.1.16 (TYPE 402, FORM 16) - PLANAR 4.76.1.16 FORM NUMBER: 16 Planar This associativity is used to indicate that a collection of entities is coplanar. They may be geometric, annotative, and/or structural. In the case of an entity containing subordinate entities, these must also be coplanar. The first class contains the pointer to the Transformation Matrix indicating the plane the entities have been moved to. The plane in question is the image under this transformation of the XY plane. As noted in the description for DE Field 7, the value 0 may be used to indicate the identity transformation matrix. This matrix is informational only for the associativity; the constituent entities must properly position themselves in model space. The second class contains the pointers to the coplanar entities. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (Transformation Matrix) 2 2 Back pointers not required 3 1 Ordered class 4 1 Number of items per entry 5 1 Pointer Class 2 (Coplanar Entities) 6 2 Back pointers not required 7 2 Unordered class 8 1 Number of items per entry 9 1 Pointer 322 4.76.1.16 (TYPE 402, FORM 16) - PLANAR DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**??05** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 16 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NTR Integer Number of Transformation Matrices (NTR=1 is required) 2 N Integer Number of entities in this plane pointed to by this associativity 3 DETR Pointer Pointer to the DE of the Transformation Matrix moving data from XY plane into space or zero 4 DE1 Pointer Pointer to the DE of the first entity on plane specified .. . . . .. .. 3+N DEN Pointer Pointer to the DE of the last entity on plane specified Additional pointers as required (see Section 2.2.4.4.2). 323 4.76.1.17 (TYPE 402, FORM 18) - FLOW 4.76.1.17 FORM NUMBER: 18 Flow The Flow Associativity represents a single signal or a single fluid flow path. The associativity contains seven classes. Class one contains the type and function flags: __________________________________________ |__Type_Flag__|________Meaning________|___ | 0 |Not specified (Default) | | 1 |Logical | |_______2_______|Physical_________________| The use of the Type Flag is mandatory when both the logical (e.g., schematic) and physical (e.g., printed board) product definitions are in the same file. In such a file, the Type Flag shall not be zero. The Function Flag differentiates between a fluid path and an electrical conductor: _______________________________________________ |__Function_Flag__|_________Meaning________|___ | 0 |Not specified (Default) | | 1 |Electrical signal | |_________2_________|Fluid_flow_path_________|_ A fluid flow path is a single path from a starting Connect Point Entity. The path may include additional intermediate connect points, but separate Flow Entities will be required to describe the branch flow paths. Class four, the Join, lists the elements of the path. For fluid flow paths, the elements are ordered as they occur along the flow path, and the Connect Point Entities (class three) list the connect points in the same sense as the order of the Join. That is, the start of the fluid flow path is the one listed first; the end of the fluid flow path is listed last. Class two contains pointers to other associated Flow Associativities. These other associativities may implement alternative flow representations. The obvious example of this is the file containing both the schematic and physical product definitions. The corresponding Flow Associativities of each type would be paired. Class three is the Link, which contains the list of pointers to the Connect Point Entities involved in the signal/flow. Class four is the Join, which contains the list of pointers to the entities representing the graphical implementation of the signal/flow. Class five contains the flow names which are associated with the signal/flow. Class six contains a list of pointers to the Text Display Template Entities which are to be used to display the first flow name listed in class five. The Text Display Templates provide the locations and attributes for the signal name display. The text string for display is obtained from the first flow name listed in class five. Class seven contains a list of pointers to flow paths which branch from the current flow path. This is an ordered list, and the "main" continuation of the path, if any, is always listed last. A null pointer is used if there is no continuation of the main path. 324 4.76.1.17 (TYPE 402, FORM 18) - FLOW DEFINITION Index__ Set_Value___ Meaning____ 1 7 Seven classes Class 1 (Context Flag) 2 2 Back pointers not required 3 1 Ordered 4 1 One item per entry 5 2 Item is value Class 2 (Associated Flows) 6 2 Back pointers not required 7 2 Unordered 8 1 One item per entry 9 1 Pointer to Flow Associativity Class 3 (Connect Points (Link)) 10 1 Back pointers required 11 1 Ordered 12 1 One item per entry 13 1 Pointer to Connect Point Entity Class 4 (Join) 14 1 Back pointers required 15 1 Ordered 16 1 One item per entry 17 1 Pointer to geometry or Subfigure Instance Entity Class 5 (Flow Name) 18 2 Back pointers not required 19 2 Unordered 20 1 One item per entry 21 2 Item is value Class 6 (Flow Name Display) 22 2 Back pointers not required 23 2 Unordered 24 1 One item per entry 25 1 Pointer to Text Display Template Entity Class 7 (Flow Continuations) 26 1 Back pointers required 27 1 Ordered 28 1 One item per entry 29 1 Item is a pointer 325 4.76.1.17 (TYPE 402, FORM 18) - FLOW DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**??03** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 18 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NCF Integer Count of context flags (NCF=2 is required) 2 NF Integer Count of associated Flow Associativities 3 NC Integer Count of Connect Point Entities 4 NJ Integer Count of Join entities (geometry of subfigure) 5 NN Integer Count of flow names 6 NT Integer Count of Text Display Templates for flow name display 7 NP Integer Count of continuation flow associativities 8 TF Integer Type of flow: 0 = not specified (Default) 1 = logical 2 = physical 9 FF Integer Function flag: 0 = not specified (Default) 1 = electrical signal 2 = fluid flow path 10 SPTR1 Pointer Pointer to the DE of the first Flow Associativity Entity .. . . . .. .. NF+9 SPTRNF Pointer Pointer to the DE of the last Flow Associativity Entity NF+10 CPTR1 Pointer Pointer to the DE of the first Connect Point Entity .. . . . .. .. NF+NC+9 CPTRNC Pointer Pointer to the DE of the last Connect Point Entity NF+NC+10 JPTR1 Pointer Pointer to the DE of the first Join Entity .. . . . .. .. NF+NC+NJ+9 JPTRNJ Pointer Pointer to the DE of the last Join Entity NF+NC+NJ+10 NAME1 String First Flow name .. . . . .. .. 326 4.76.1.17 (TYPE 402, FORM 18) - FLOW NF+NC+NJ+NN+9 NAMENN String Last Flow name NF+NC+NJ+NN+10 GPTR1 Pointer Pointer to the DE of the first Text Display Template Entity .. . . . .. .. NF+NC+NJ+NN+NT+9 GPTRNT Pointer Pointer to the DE of the last Text Display Template Entity NF+NC+NJ+NN+NT+10 CFPTR1 Pointer Pointer to the DE of the first continuation Flow Associativity Entity . . . ECO605 .. .. .. NF+NC+NJ+NN+NT+NP+9 CFPTRNP Pointer Pointer to the DE of the last continuation Flow Associativity Entity (the "main" continuation) Additional pointers as required (see Section 2.2.4.4.2). 327 4.76.1.18 (TYPE 402, FORM 19) - SEGMENTED VIEWS VISIBLE ECO506 4.76.1.18 FORM NUMBER: 19 Segmented Views Visible The definition of this associativity can be found in Appendix G (see Section G.26). 328 4.76.1.19 (TYPE 402, FORM 20) - PIPING FLOW 4.76.1.19 FORM NUMBER: 20 Piping Flow ECO602 The definition of this associativity can be found in Appendix G (see Section G.27). 329 4.76.1.20 (TYPE 402, FORM 21) - DIMENSIONED GEOMETRY ECO606 4.76.1.20 FORM NUMBER: 21 Dimensioned Geometry The definition of this associativity can be found in Appendix G (see Section G.28). 330 4.77 DRAWING ENTITY (TYPE 404) 4.77 Drawing Entity (Type 404) The Drawing Entity specifies a drawing as a collection of annotation entities (i.e., any entity with use flag set to 01) defined in drawing space, and views (i.e., projections of model space data in view space) which, together, constitute a single representation of a part, in the sense that an engineering drawing constitutes a single representation of a part in standard drafting practice. Views are specified by referring to a View Entity (Type 410). If desired, multiple drawings can be included in a single file, referring to the same model space. Drawings are located in drawing space as illustrated in Figure 81, with sides coincident with the drawing coordinate system axes and with the lower left corner at the origin (0,0). The drawing space coordinate system (XD, YD) is a special 2-dimensional coordinate system used for view origin locations in the Drawing Entity and for annotation entities referenced by the Drawing Entity. Any Z coordinates are ignored in the referenced annotation entities, and any transformation matrix from definition space to drawing space must be 2-dimensional (i.e., in Entity 124, T3 = R13 = R31 = R32 = R23 = 0:0 and R33 = 1:0). Annotation entities can be defined in drawing space and be referenced by the Drawing Entity directly, or can be defined in model space and appear in individual views. When defined in drawing space, the subordinate entity switch should be set to physically dependent (01). The subordinate entity switch for a View Entity referenced by the Drawing Entity should be set to logically dependent (02). The transformation of a view from view space to drawing space is controlled by the view scale factor S, specified in the View Entity, and the view origin drawing locations, specified in the Drawing Entity. In the case of orthographic parallel projection the transformation is: 2 XV 3 XD S 0 0 4 5 XORIGIN Y D = 0 S 0 YZVV + Y ORIGIN 2 3 XV where 4 Y V 5 ZV denotes the view space coordinates and XORIGINY ORIGIN denotes the drawing space coordinates of the origin of the transformed view (see Section 4.80). Some CAD systems maintain a rotation, in addition to a translation and scaling, between the ECO538 view and drawing coordinate systems. It is not possible to correctly capture the relationships among all three coordinate systems_model, view and drawing_using Form 0 of the Drawing Entity. A rotation is needed in addition to the translation for transforming view to drawing coordinates provided by Form 0. The definition of a new Form 1 to be used in this case can be found in Appendix G (see Section G.29). 331 4.77 DRAWING ENTITY (TYPE 404) The name of the drawing may be provided by using the Name Property (Type 406, Form 15). If not provided, a receiving system may default the name of the drawing. The size of the drawing may be specified by using the Drawing Size Property (Type 406, Form 16). The units for drawing space may be set differently from the model space units specified in the Global Section. This is accomplished by use of the Drawing Units Property (Type 406, Form 17). When this property is not provided, the drawing units will be the same as the model units. The following values are given in drawing units: o view origin drawing locations o drawing size o coordinates of annotation entities referenced directly Refer to Figures 81 and 82 for examples of the use of the Drawing Entity. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 404 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0001** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 404 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of View pointers 2 VPTR1 Pointer Pointer to the DE of the first View Entity 3 XORIGIN1 Real Drawing space coordinate of the origin of the first transformed View 4 YORIGIN1 Real Drawing space coordinate of the origin of the first transformed View 5 VPTR2 Pointer Pointer to the DE of the second View Entity .. . . . .. .. 2+3*N M Integer Number of Annotation Entities (may be zero) 3+3*N DPTR1 Pointer Pointer to the DE of the first Annotation Entity in this Drawing .. . . . .. .. 2+M+3*N DPTRM Pointer Pointer to the DE of the last Annotation Entity in this Drawing Additional pointers as required (see Section 2.2.4.4.2). 332 4.77 DRAWING ENTITY (TYPE 404) Figure 81. Using Clipping Planes with a View in a Drawing 333 4.77 DRAWING ENTITY (TYPE 404) Figure 82. Parameters of the Drawing Entity 334 4.78 PROPERTY ENTITY (TYPE 406) 4.78 Property Entity (Type 406) The Property Entity contains numerical or textual data. It also has a form number to indicate its meaning. Certain generic property form numbers are described in the following sections and are expected to be augmented by others in future versions of this specification. Form numbers in the range 5001-9999 are left undefined for implementors. ECO532 Note that properties can also point to other properties, participate in associativities, point to related general notes, or display text by pointing to a Text Display Template. Property instances are usually referenced by the presence of a pointer to the instance in the second group of additional pointers as described in Section 2.2.4.4.2; however, as stated in Section 1.7.1, when an instance is independent it applies to all entities on the same level as the instance. The parameter data values have the following common format for all Property Entities: Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 V1 Variable First property value .. . . . .. .. 1+NP VNP Variable Last property value Additional pointers as required (see Section 2.2.4.4.2). 335 4.78.1 (TYPE 406, FORM 1) - DEFINITION LEVELS 4.78.1 FORM NUMBER: 1 Definition Levels For one or more entities in the file that are defined on a set of multiple levels, there will be an occurrence of the Property Instance (Form 1). In the parameter data portion of the property instance, the first parameter, NP, will contain the number of multiple levels followed by a list of those levels. Each entity that is defined on this set of levels will contain a pointer (in the level field of the directory entry) to this property instance. A different set of multiple levels will result in a different property instance. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 L1 Integer First level number .. . . . .. .. 1+NP LNP Integer Last level number Additional pointers as required (see Section 2.2.4.4.2). 336 4.78.2 (TYPE 406, FORM 2) - REGION RESTRICTION 4.78.2 FORM NUMBER: 2 Region Restriction This property allows entities that can define regions to set an application's restriction over that region. The restrictions will indicate whether a given application's item must lie completely within regions with this property or completely outside such regions. The restriction applies to all points of entities used to represent the application's item and to all points within the effect of the item when all properties, such as line widening, are applied. The DE attribute Level Number is used to specify the physical board layers to which the Region ECO577 Restriction is applied. The method used to convey this information is as follows: 1. Create a Definition Levels Property (Type 406, Form 1). 2. Include a level number for each physical board layer to which the Region Restriction is applied. 3. Reference the Definition Levels Property from the DE Level field attribute of the Region Restriction Property through a negated pointer. The values in the Definition Level property are exchange file level numbers. In order to determine the actual physical board layers, the postprocessor must refer to the physical layer number in the Level to PWB Layer Map Property (Type 406, Form 24). Note: The DE level attribute of the boundary curve is used to determine the level(s) upon which the graphic representation of the region is displayed. If the graphic representation is to be displayed on each level to which the Region Restriction is applied, then point to the same Definition Levels Property from the boundary curve and the Region Restriction Property. Each of the property values in this property will have one of three values indicating the region restriction relevant to the application's item. ______________________________________________________ |__Property_Value__|___________Description_________|__ | 0 |No Restriction | | 1 |Item must be inside region | |__________2__________|Item_must_be_outside_region__|_ 337 4.78.2 (TYPE 406, FORM 2) - REGION RESTRICTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 2 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=3) 2 EVR Integer Electrical vias restriction (EVR=0,1 or 2) 3 ECPR Integer Electrical components restriction (ECPR=0,1 or 2) 4 ECRR Integer Electrical circuitry restriction (ECRR=0,1 or 2) Additional pointers as required (see Section 2.2.4.4.2). 338 4.78.3 (TYPE 406, FORM 3) - LEVEL FUNCTION 4.78.3 FORM NUMBER: 3 Level Function This property is used to transfer the meaning or intended use of a level in the sending system. An instance of this property shall apply to all entities in the same file with the same DE level value (Field 5), without the requirement of a pointer to it (see Section 1.7.1). Parameter 2 is used to record an integer code number when the sending system uses a level-use index or table. Parameter 3 is used to record the level-use text, whether such text is obtained from the index which provided Parameter 2, or exists independently. Either Parameter 2 or Parameter 3 may have a default value. This property may be readily added to a file (by edit or data merge) when level-use information is required by the receiving system or archive. The Parameter (2 and 3) values of an instance of this property shall apply to multiple levels if the instance's level value is a pointer to an instance of Property Form 1. Note that Parameter 3 was an integer value for "source level" in Version 2. The source level (for this Version) shall be the level value for the instance of this property. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**00**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 3 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=2) 2 FC Integer Function description code (Default = 0) 3 FD String Function description (Default = null string) Additional pointers as required (see Section 2.2.4.4.2). 339 4.78.4 (TYPE 406, FORM 4) - REGION FILL 4.78.4 FORM NUMBER: 4 Region Fill The use of this property is deprecated (see Appendix F). 340 4.78.5 (TYPE 406, FORM 5) - LINE WIDENING 4.78.5 FORM NUMBER: 5 Line Widening This property defines the characteristics of entities when they are used to define the location of items such as strips of metalization on printed wiring boards. The justification flag terminology is interpreted as follows: right justified means that a defining line segment forms the right edge of the widened line in the direction from first defining point to second. Left justified is the opposite while center justified indicates that the defining line segment splits the widening exactly in half. Figure 83 indicates the measurement of the property values. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 5 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=5) 2 WM Real Width of metalization 3 CC Integer Cornering codes: 0 = rounded 1 = squared 4 EF Integer Extension flag: 0 = No extension 1 = One-half width extension 2 = Extension set by Parameter 6 5 JF Integer Justification flag: 0 = center justified 1 = left justified 2 = right justified 6 E Real Extension value, if Parameter 4=2 (Note: this value may be negative) Additional pointers as required (see Section 2.2.4.4.2). 341 4.78.5 (TYPE 406, FORM 5) - LINE WIDENING Figure 83. Measurement of the Line Widening Property Values 342 4.78.6 (TYPE 406, FORM 6) - DRILLED HOLE 4.78.6 FORM NUMBER: 6 Drilled Hole The Drilled Hole Property identifies an entity representing a drilled hole through a printed circuit board. The parameters of the property define the characteristics of the hole necessary for actual machining. The layer range indicated by Parameters 5 and 6 refers to physical layers of the assembled printed circuit board. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 6 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=5) 2 DDS Real Drill diameter size 3 FDS Real Finish diameter size 4 PF Integer Plating indication flag: 0 = no 1 = yes 5 LNL Integer Lower numbered layer 6 HNL Integer Higher numbered layer Additional pointers as required (see Section 2.2.4.4.2). 343 4.78.7 (TYPE 406, FORM 7) - REFERENCE DESIGNATOR 4.78.7 FORM NUMBER: 7 Reference Designator The Reference Designator Property attaches a text string containing the value of a component reference designator to an entity being used to represent a component. This property is not to be used for the primary reference designator when a component is represented by a Network Subfigure Instance Entity (Type 420) as that value is included in the subfigure parameters. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 7 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 RD String Reference designator text Additional pointers as required (see Section 2.2.4.4.2). 344 4.78.8 (TYPE 406, FORM 8) - PIN NUMBER 4.78.8 FORM NUMBER: 8 Pin Number The Pin Number Property attaches a text string representing a component pin number to an entity being used to represent an electrical component's pin. This property is not to be used when a pin is represented by a Connect Point Entity (Type 132) as the pin number is included in one of the Connect Point parameters. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 8 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 PN String Pin Number Value Additional pointers as required (see Section 2.2.4.4.2). 345 4.78.9 (TYPE 406, FORM 9) - PART NUMBER 4.78.9 FORM NUMBER: 9 Part Number The Part Number Property attaches a set of text strings that define the common part numbers to an entity being used to represent a physical component. Defaulted strings in any parameter will imply that the missing value is not relevant to the transferred data. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 9 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=4) 2 GPN String Generic part number or name 3 MPN String Military Standard (MIL-STD) part number 4 VPN String Vendor part number or name 5 IPN String Internal part number Additional pointers as required (see Section 2.2.4.4.2). 346 4.78.10 (TYPE 406, FORM 10) - HIERARCHY 4.78.10 FORM NUMBER: 10 Hierarchy The Hierarchy Property provides the ability to control the hierarchy of each directory entry attribute. This property is referenced when the directory entry status digits 7 and 8 are 02. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 10 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=6) 2 LF Integer Line font 3 VU Integer View 4 LAB Integer Entity level 5 BL Integer Blank status 6 LW Integer Line weight 7 CO Integer Color number Additional pointers as required (see Section 2.2.4.4.2). Acceptable values for Parameters 2 through 7 are 0 and 1. (See definition in Section 2.2.4.3.9.4). 347 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA 4.78.11 FORM NUMBER: 11 Tabular Data The Tabular Data Property provides a structure to accommodate point form data. The basic structure is a two-dimensional array organized in column row order. In the simplified form this structure can contain a single list of values. The more complex forms contain multiple lists of independent and dependent variables. The Property Type is the key used to define the dependent variable data values. Property Types 1 to 5000 are reserved for defining finite element material properties. ECO528 The default units used for this property shall follow the International System of Units (SI) practice for base units and derived units (IEEE76). Typical SI units are as follows: ___________________________________________________________ |__Base_Units____________________|__Unit______|_Symbol__|__ | Length |meter | m | | Mass |kilogram | kg | | Time | second | s | | Electric Current |ampere | A | | Thermodynamic Temperature | kelvin | K | | Amount | mole | mol | | Luminous Intensity | candela | cd | | Plane Angle | radian | rad | |__Solid_Angle_____________________|steradian__|___sr_____|_ __________________________________________________________ |__Derived_Units__|__Unit____|__Symbol__|____Formula___|__ | Force |Newton | N | (kg*m/s)/s | |__Energy___________|Joule____|_____J_____|_____N*m______|_ 348 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 11 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of Property values 2 PTYPE Integer Property Type: 1 = Young's Modulus ND=3 2 = Poisson's Ratio ND=3 3 = Shear Modulus ND=3 4 = Material Matrix ND=21 5 = Mass Density ND=1 6 = Thermal Expansion Coefficient ND=3 7 = Laminate Material Stiffness Matrix ND=6 8 = Bending Material Stiffness Matrix ND=6 9 = Transverse Shear Material Stiffness Matrix ND=3 10 = Bending Coupling Material Stiffness Matrix ND=6 11 = Material Coordinate System ND=3 12 = Nodal Load/Constraint Data ND=Number of De- grees of Freedom 13 = Sectional Properties for Beam Elements ND=8 if the properties are the same at both ends of the beam otherwise, ND=16 14 = Beam End Releases ND=12 15 = Offsets ND=9 or 18 16 = Stress Recovery Information ND=12 or 24 17 = Element Thickness ND=1 or n 18 = Non-Structural Mass ND=1 19 = Thermal Conductivity ND=3 20 = Heat Capacity ND=1 21 = Convective Film Coefficient ND=1 22 = Radiation Parameters ND=4 3 ND Integer Number of dependent variables 4 NI Integer Number of independent variables 5 TYPI1 Integer Type of first independent variable: 1 = Temperature 2 = Pressure 3 = Relative humidity 4 = Rate of Strain 349 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA 5 = Velocity 6 = Acceleration 7 = Time 8 = Strain .. . . . .. .. 5+NI TYPINI Integer Type of the last independent variable 6+NI NVALI1 Integer Number of different values of the first independent variable .. . . . .. .. 6+2*NI NVALINI Integer Number of different values of the last independent variable 7+2*NI VALI(1,1) Real First value of the first independent variable .. . . . .. .. VALI(1, Real Last value of the first independent variable NVALI1) .. . . . .. .. VALI(NI, Real Last value of the last independent variable NVALINI) VALD(1,1) Real Value of the first dependent variable at the first data point .. . . . .. .. VALD(J,K) Real Value of the j-th dependent variable at the k-th data point .. . . . .. .. N VALD(ND, Real Value of the last dependent variable at the last data point NVALINI) Additional pointers as required (see Section 2.2.4.4.2). 350 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA MATERIAL PROPERTY TYPE DEFINITIONS: PTYPE = 1 Young's Modulus Young's modulus relates stress to strain in materials. In the simple case: oe = E ffl Where oe = Stress vector (row of elements oex; oey; oez) ffl = Strain vector (row of elements fflx; ffly; fflz) E = Young's Modulus matrix of diagonal elements Exx ; Eyy; Ezz The modulus is a vector with three principal values Exx ; Eyy; and Ezz. This implies that ND (Number of Dependent Variables) is equal to three. In matrix form: 2 3 2 3 2 3 oex Exx 0 0 fflx 4 oey5 = 4 0 Eyy 0 5 4 ffly5 oez 0 0 Ezz fflz 351 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 2 Poisson's Ratio Poisson's ratio is the ratio of transverse strain in the j-direction when stressed in the i-direction, i.e., ij = fflj=ffli Where = Poisson's Ratio ffl = Strain i = One orthogonal direction j = Another orthogonal direction The Poisson's Ratio is a vector consisting of matrix elements with the three principal values, xy; yz; zx. The off diagonal matrix values are reciprocals of the principal values, i.e.: xy = 1=yx This implies that ND (Number of Dependent Variables) is equal to three. In matrix form for an orthotropic material: 2 3 2 3 2 3 fflx 1=Exx -yx =Eyy -zx =Ezz oex 64 ffl7 6 7 6 7 y5 = 4 -xy =Exx 1=Eyy -zy=Ezz 5 4 oey 5 fflz -xz =Exx -yz=Eyy 1=Ezz oez 352 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 3 Shear Modulus Shear Modulus - The ratio of shear stress to shear strain. G = os=fl Where G is the Shear Modulus os is the Shear Stress fl is the Shear Strain The Shear Modulus is a vector with three principal values: Gxy ; Gyz; and Gzx . This implies that the ND (Number of Dependent Variables) is equal to three. In matrix form for orthotropic materials: 2 3 2 3 2 3 flxy 1=Gxy 0 0 osxy 64 fl 7 6 7 6 7 yz5 = 4 0 1=Gyz 0 5 4 osyz 5 flzx 0 0 1=Gzx oszx 353 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 4 Material Matrix Material matrix defines the tensor qualities of the material. For example: oe = [C] ffl Where oe is the Stress Vector ffl is the Strain Vector, and [C] is the Material Matrix Because of symmetry, the elements Cji = Cij. Therefore, 21 elements define the material matrix: C11 C44 C46 C12 C15 C56 C22 C25 C66 C13 C35 C23 C45 C33 C55 C14 C16 C24 C26 C34 C36 This implies that ND = 21. In Matrix form: 2 3 2 3 2 3 oex C11 C12 C13 C14 C15 C16 fflx 66 oe 7 6 C C C C C C 7 6 ffl 7 66 y 77 66 21 22 23 24 25 26 7766 y 77 66 oez 77= 66 C31 C32 C33 C34 C35 C36 7766 fflz 77 66 oxy 777 666C41 C42 C43 C44 C45 C46 777666flxy777 4 oyz 5 4 C51 C52 C53 C54 C55 C56 5 4 flyz 5 ozx C61 C62 C63 C64 C65 C66 flzx 354 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 5 Mass Density Mass density is the Mass/Unit Volume. This implies that ND = 1. Mass Density = ae. 355 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 6 Thermal Expansion Coefficient The Thermal Expansion Coefficient is a material property that computes the strain given a temperature differential, i.e., ffl = ff T or ff = ffl=T Where ffl = strain ff = thermal expansion coefficient T = the temperature differential The Thermal Expansion Coefficient may be represented as a vector with three principal values: ffxx ; ffyy and ffzz. This implies that ND (number of Dependent Variables) is equal to three. 356 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPES 7 - 11 Composite Materials Composite materials will be represented with linkages to Tabular Data Property 11 as described in Figure 84. PTYPES required are: ____________________________________________________________ |__PTYPE__|__________________Description_________________|__ | 7 |Laminate material stiffness matrix | | 8 |Bending material stiffness matrix | | 9 |Transverse shear material stiffness matrix | | 10 |Bending coupling material stiffness matrix | |_____11_____|Material_Coordinate_System________________|___ Figure 84. Relationship Between Properties Used to Represent a Composite Material 357 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 7 Laminate Material Stiffness Matrix The membrane material stiffness matrix defines anisotropic material properties for shell membrane action. For example: f = t [M ] ffl Where f = Forces per unit length (row of elements fx; fy; fxy) ffl = Midplane strains (row of elements fflx; ffly; fflxy) t = Shell thickness - see element property [M ] = Membrane material stiffness matrix f and fflare defined in the shell material coordinate system, PTYPE = 11. Because of symmetry, the elements Mji = Mij. Therefore, six elements define the membrane material stiffness matrix (this implies ND = 6): M11 M12 M13 M22 M23 M33 The matrix [M] is a laminate material stiffness matrix which is calculated from lamina stress strain matrices [G]n . One method for calculating [M] for a laminate containing m plies is: 1 Xm [Mij] = __ [Gij]n tn t n = 1 Where tn is thickness of nth ply t is total thickness of laminate Where [G]n is stress strain matrix for nth ply of laminate, defined in the material coordinate system. 358 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 8 Bending Material Stiffness Matrix The bending material stiffness matrix defines the anisotropic material properties for shell bending. For example: ___m= _1_ t3 [B] O 12 Where ___m = Shell bending moments per unit length (row of elements Mx; My; Mxy) O = Shell curvature (row of elements Ox; Oy; Oxy) t = Shell thickness - see element property [B] = Bending_material stiffness matrix M and O are defined in shell material coordinate system, PTYPE=11 Because of symmetry, the elements Bij = Bji. Therefore, six elements define the bending stress strain matrix (this implies ND = 6): B11 B12 B13 B22 B23 B33 The matrix [B] is a laminate matrix for bending which is calculated from lamina matrices [G]n . One method for calculating [B] for a laminate containing m plies is: Xm [Bij] = 12 t-3 Z2n[Gij]n tn n=1 Where [G]n is the stress strain matrix for the nth ply of laminate tn is thickness of nth ply t is total thickness of laminate Zn is the normal distance from midplane of shell to the centroid of the ply 359 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 9 Transverse Shear Material Stiffness Matrix The transverse shear material stiffness matrix defines anisotropic material properties for transverse shear flexibility in shell structure. For example: V = ts [S] fl Where V = Transverse shear force per unit length (row of elements Vx; Vy) fl = Transverse shear strains, dimensionless (row of elements flx; fly) ts = 5/6 of effective transverse shear thickness [S] = Transverse shear material stiffness matrix V and fl are defined in the material coordinate system Because of symmetry, the elements Sij = Sji. Therefore, three elements define the transverse shear material stiffness matrix (this implies ND = 3.): S11 S12 S22 The matrix [S] is a laminate material stiffness matrix for transverse shear flexibility. If the matrix is not defined, deflections normal to the shell do not include contributions from transverse shear strain. 360 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 10 Bending Coupling Material Stiffness Matrix The membrane - bending coupling material stiffness matrix defines the anisotropic material proper- ties for shell structure with the neutral axis for bending offset from the midplane of the shell. For example: f = t2 [C] O and ___m= t2 [C] T ffl Where f = Forces per unit length (row of elements fx; fy; fxy) ___m = Bending moments per unit length (row of elements m x; my; mxy) O = Curvature (measurement of bending strain, (meter )-1 ) (row of elements Ox; Oy; Oxy) ffl = Midplane strain (row of elements fflx; ffly; fflxy) t = shell thickness f ; ___m; O ; and fflare defined in the shell material coordinate system Because of symmetry, the elements Cij = Cji. Therefore, six elements define the membrane bending coupling material matrix (This implies ND = 6): C11 C12 C13 C22 C23 C33 The matrix [C] is a laminate matrix for membrane bending coupling, which is calculated from lamina stress strain matrices [G]n . One method for calculating [C] for a laminate containing m plies is: Xm [Cij] = t-2 (Zn [Gij]n tn ) n=1 Where [G]n = stress strain matrix for nth ply, defined in shell material coordinate system tn = thickness of nth ply Zn = the normal distance from midplane of the shell to centroid of nth ply t = thickness of shell 361 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 11 Material Coordinate System The orientation of_the_element material coordinate_system is specified by a set of direction cosines defining a vector D . The use of the vector D depends upon the element type. For Element Topology Type_1 and 33 of the Finite Element Entity (Type 136), Figure 85 illustrates the use of the_vector D to define the element material coordinate system. For Topology Type 33 the vector D is defined by the Reference Node 3. ___ The cosines for vector D are translated to the location of_the_shear center offset to establish the reference planes for material property definition (vector DT ). For Element Topology Types 2 through 26_of the Finite Element Entity (Type 136), the following paragraphs discuss the use of vector D to define the material coordinate system. ___ Figure 85. Use of the Vector D to Define the Element Material Coordinate System 362 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA ___ ___ The projection of D on the plane of the element face (F1) (outward normal N ) defines a vector in the X direction of the material coordinate system. ___ ___ ___ ___ X = N x D x N ___ N = positive outward normal of the element face (F1) and is defined by nodal connection of the element,_i.e.:___ __ N = S1 x S2 S 1 = vector from first to second corner of element face (F1) __ S 2 = vector from second to third corner of element face (F1) ___ Three direction cosines are required to define the Vector D in the global coordinate system (therefore, ND = 3): D1 D2 D3 ___ ___ The Vectors D and N define the element material X and Z axes, respectively. The internal load and strain sign conventions must be described to ensure consistent definition of Material Types 7-10. See Figure 86. Internal Load Sign Convention: Where x, y, z are material coordinate system axes u, v, w are displacements of a point in the material coordinate system. 8 9 8 9 < fx = __ < fflx= : ffy ; = f forces per unit length : ffly; = ffl midplane strains xy fflxy 8 9 8 9 < Mx = ___ < Ox = : MMy ; = M moments per unit length : Oy ; = O bending curvatures xy Oxy ae oe ae oe Vx __ flx Vy = V transverseunshearitforceslength fly = fl transverse shear strains 363 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA Strain Displacement Relationships: fflx = @u_@x ffly = @__@y fflxy = @u_@y+ @__@x 2u @2 @2w Ox = @___@2x Oy = ____@2w Oxy = 2 _____@x@y flx @w_@x fly @w_@y Figure 86. Internal Load and Strain Sign Convention 364 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 12 Nodal Loads/Constraints Data The nodal load/constraint data will be stored in the Tabular Data Form of the Property Entity in the following manner: PTYPE = 12 ND = Number of degrees of freedom. For example, if the load vector has X, Y, Z, Mx, My, and Mz components, then ND=6. (Note Mx, My, Mz refer to moments). If the load vector has X and Y components, then ND=2. If the load vector has only a Z-component, then ND=3. In other words the X-component is the 1st degree, the Y-component is the 2nd degree, and the Z-component is the 3rd degree. Other components are treated in a similar manner starting with the 4th degree for the rotation X component. The constraint vector has X, Y, Z, Mx, My, and Mz constraints. These constraints are represented by 0 (= No Constraint) and 1 (= Constraint). ND = 6 always for constraints. 365 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 13 Sectional Properties for Beam Elements Sectional properties for beam elements define the structural characteristics of the beam. These properties are: ___________________________________________________________ | Property | | | |____Name____|__Units___|__________Description__________|__2 | AREA | M 4 | Area of section | | IX |M |Area moment of inertia | | | 4 | about the element x-axis | | IY |M |Area moment of inertia | | | 4 | about the element y-axis | | IXY |M 4 | Product of inertia | | J |M |Torsional stiffness parameter | | SRXY | Unitless |Shear stiffness ratio | | SRXZ | Unitless6 |Shear stiffness ratio | |__WC________|_M________|_Warping_coefficient.____________|_ If the properties are the same at both ends of the beam then ND=8, otherwise ND=16. If ND=16, two sets of section properties are specified. They are stated in order of the topology set grid number scheme. 366 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 14 Beam End Releases Beam end releases specify whether the ends of the beam are constrained or free to move. If free to move then both translation and rotational freedoms of the end are considered. Property 8Name___________Description_____________________________ >>>X X direction translation freedom=constraint >>> >>> >>>Y Y direction translation freedom=constraint >> For >>>>>>MX X direction rotational freedom=constraint >>> >>> >>>MY Y direction rotational freedom=constraint >>: MZ Z direction rotational freedom=constraint The value for each property X, Y, Z, Mx, My, and Mz is a 0 (= unconstrained); +1 (= constrained to the global coordinate system); or -1 (= constrained to the element coordinate system). The beam release must be specified at both ends. Therefore, ND=12. The beam ends are defined by the topology set grid number scheme. 367 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 15 Offsets Offsets are global x,y,z values used to define the location of the shear center axis, neutral axis, and non-structural center of mass relative to the element end nodes. Figure 85 shows the Shear Center Offset, SCO, the Neutral Axis Offset, NAO, and the Non-Structural Mass Offset, NSMO. These offsets are vectors in the global coordinate system (model space) relative to the end of the beam. Property 8 Name___________Description________________________________________ >>> SCOX Shear Center Offset in global x direction >>> >>> >>> SCOY Shear Center Offset in global y direction >>> >>> SCOZ Shear Center Offset in global z direction >>> >>> >> NAOX Neutral Axis Offset in global x direction For >>< Each NAOY Neutral Axis Offset in global y direction End >>>>> >>> NAOZ Neutral Axis Offset in global z direction >>> >>> >>> NSMOX Non - Structural Mass Offset in global x direction >>> >>> >>> NSMOY Non - Structural Mass Offset in global y direction >>: NSMOZ Non - Structural Mass Offset in global z direction ND=9 or ND=18 depending on whether or not both ends must be specified. They are stated in order of the topology set grid number scheme. 368 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 16 Stress Recovery Information Stress Recovery Information is used to define up to four offset points at each beam end at which stress levels will be recovered from the finite element analysis program. These offset points are described as global x, y, z offsets from each end node. All offset points are in a plane which is normal to the beam element axis. These points occur in pairs from one end of the beam to the other. Property Name___________Description___________________________________________________ 8 >> SRI1X1 Stress Recovery Information beam end 1 x - direction pair 1 END1 >>< first pair SRI1Y1 Stress Recovery Information beam end 1 y - direction pair 1 offsets >>>>: SRI1Z1 Stress Recovery Information beam end 1 z - direction pair 1 8 >>>SRI2X1 Stress Recovery Information beam end 2 x - direction pair 1 >> END2 >< first pair SRI2Y1 Stress Recovery Information beam end 2 y - direction pair 1 offsets >>>>> >: SRI2Z1 Stress Recovery Information beam end 2 z - direction pair 1 (for the first pair of offsets) .. . . . .. .. 8 >> SRI1X4 Stress Recovery Information beam end 1 x - direction pair 4 END1 >>< fourth pair SRI1Y4 Stress Recovery Information beam end 1 y - direction pair 4 offsets >>>>: SRI1Z4 Stress Recovery Information beam end 1 z - direction pair 4 8 >>>SRI2X4 Stress Recovery Information beam end 2 x - direction pair 4 >> END2 >< fourth pair SRI2Y4 Stress Recovery Information beam end 2 y - direction pair 4 offsets >>>>> >: SRI2Z4 Stress Recovery Information beam end 2 z - direction pair 4 (for the fourth pair of offsets) 369 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 17 Element Thickness Element Thickness defines the net section thickness for a homogeneous element or individual plate thickness for a laminate or sandwich plate. ND=1 or n and is defined as follows: _________________________________________________________________ |__ND__|_____________________Description______________________|__ | 1 |Scalar thickness oftelementh | |___n___|Thickness_of_the_n___plate_of_a_sandwich_or_laminate__|_ The thickness is ordered from 1 to n. The thicknesses are measured in the positive z direction in order of increasing z in local element coordinate system. ____________________________________________________________ | Property | | |____Name____||________________Description________________|_ | T1 |Thickness for homogeneous plate or the | | |thickness for the first lamina of the plate | | .. | .. | | . | . | |______Tn______|Thickness_for_the_nth_lamina_of_the_plate__|_ 370 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 18 Non-Structural Mass Non-Structural Mass is defined as the mass not accounted for in volume and density information for the structural elements. Thus, ND=1. ______________________________________ | Property | | |____Name____|_____Description_____|__ | NSM |Mass/unit length or | | |Mass/unit area or | |______________|Mass/unit_volume____|_ Where the description depends on the type of element. 371 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 19 Thermal Conductivity Thermal Conductivity relates heat flow across a surface as a function of temperature. The heat balance equation shows this relationship: _@_ k @T__ + _@_ k @T__ + _@_ k @T__ = ae C @T__- Q_ @x x @x @y y @y @z z @z p @t I Where kn = Thermal conductivity coefficient where n = x; y; z Cp = Heat capacity at constant pressure ae = Material density T = Temperature t = Time Q_I = Rate that energy is converted to internal heat x; y; z are defined in the local element coordinate system If we consider k (thermal conductivity coefficient) as independent of direction, then k can be repre- sented as constant in the x, y, z directions: i.e., @__ k @T__ = k @2T__ @n n @n n @n2 Where n is x, y, or z. Therefore, the thermal conductivity is a vector with three principal values, kx; ky; and kz. This implies that ND (Number of Dependent Variables) is equal to three. In matrix form the heat balance equation is: 2 @2T 3 ____2 66 @x 77 [kx ky kz]666@2T_@y277= ae Cp @T__- Q_I 4 75 @t @2T_ @z2 Now assume that there are no internal heat sources Q_Iand the heat flow is steady state, (@T =@t = 0). Then, integrating the above equation in one dimension yields Q_x = kx A @T_ @x where Q_x is the heat flux in the x direction across a surface of area A normal to the x direction. Likewise, solutions may be found in the y and z directions. _______________________________________________________________ | Property | | |____Name____||__________________Description__________________|_ | KX |Thermal Conductivity coefficient x direction | | KY |Thermal Conductivity coefficient y direction | |______KZ______|Thermal_Conductivity_coefficient_z_direction__|_ 372 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 20 Heat Capacity Heat Capacity is a material's ability to store heat. The heat balance equation shows the relationship of heat capacity to the spatial variation and time variation of temperature. _@_ k @T__ + _@_ k @T__ + _@_ k @T__ = ae C @T__- Q_ @x x @x @y y @y @z z @z p @t I Where kn = Thermal conductivity coefficient where n = x; y; z Cp = Heat capacity at constant pressure ae = Material density T = Temperature t = Time _QI = Rate that energy is converted to internal heat If we consider constant pressure, the heat capacity can be considered a constant. Consequently, ND=1 to define the constant. _____________________________________________________ | Property | | |____Name____|_____________Description_____________|_ |______CP______|Heat_capacity_at_constant_pressure__|_ 373 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 21 Convective Film Coefficient Convective film coefficient relates to the amount of heat flux that is convected to adjacent materials at the interface boundary of a heat source. Q_ = -hc A T Where Q_ = the heat flux hc = the convective film coefficient A = the surface area through which the heat flows T = the temperature differential between the materials The convective film coefficient may be represented as a constant. This implies that ND=1. ______________________________________________ | Property | | |____Name____|_________Description_________|__ |_____HC______|Convective_Film_Coefficient__|_ 374 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA PTYPE = 22 Electromagnetic Radiation Parameters Properties for Absorptivity, Transmissivity, Reflectivity, and Emissivity are defined for structural elements using four values. Thus, ND=4. __________________________________________ | Property | | |____Name____|_______Description_______|__ | A |Absorptivity Constant | | T |Transmissivity Constant | | R |Reflectivity Constant | |______E______|Emissivity_Constant______|_ 375 4.78.11 (TYPE 406, FORM 11) - TABULAR DATA Examples of the use of the Tabular Data Form of the Property Entity: Consider the representation of the mass density (PTYPE = 5) as a function of pressure. In this case, there is one independent variable. Suppose the density is known for two values of pressure. The Parameter Data Section would contain: ______________________________________________ |__Index__|Name______|___Recorded_Value__|____ | 1 |NP | 9 | | 2 |PTYPE | 5 | | 3 |ND | 1 | | 4 |NI | 1 | | 5 |TYPI | 2 | | 6 |NVALI | 2 | | 7 |VALI1 | 50 | | 8 |VALI2 | 25 | | 9 |VALD(1,1) | 33 | |____10____|VALD(1,2)__|__________46__________| as well as additional pointers as required (see Section 2.2.4.4.2). Consider the representation of Young's modulus (PTYPE = 1) for a linear, static, independent case.In this case, there is no independent variable. The Parameter Data Section would contain: __________________________________________ |__Index__|Name__|___Recorded_Value__|____ | 1 |NP | 6 | | 2 |PTYPE | 1 | | 3 |ND | 3 | | 4 |NI | 0 | | 5 |Exx | 30.0E6 | | 6 |Eyy | 30.0E6 | |____7____|Ezz_____|_______30.0E6_______|_ As well as additional pointers as required (see Section 2.2.4.4.2). 376 4.78.12 (TYPE 406, FORM 12) - EXTERNAL REFERENCE FILE 4.78.12 FORM NUMBER: 12 External Reference File List The External Reference File List appears in a file which references definitions that reside in another file. It contains a list of the names of the files directly referenced by entities within this file. See Section 3.6.4 and the External Reference Entity (Type 416) for more detail. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 12 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of List Entries 2 NAME1 String First External Reference File Name .. . . . .. .. 1+NP NAMENP String Last External Reference File Name Additional pointers as required (see Section 2.2.4.4.2). 377 4.78.13 (TYPE 406, FORM 13) - NOMINAL SIZE 4.78.13 FORM NUMBER: 13 Nominal Size A Nominal Size consists of a value, a name, and optionally a reference to an engineering standard. The nominal size value is a real value in the units appropriate for the specified name. The name is a string constant, but the following names have predefined meanings: ________________________________________________________________________ |__Nominal_Size_Name__|______________Predefined_Meaning__________|______ | 3HAWG | American Wire Gauge | | 3HIPS | Iron Pipe Size | |___________2HOD___________|Outside_Diameter_schedule,_i.e.,_tubing.__|_ Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 13 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=2 or 3) 2 SZ Real Nominal size value 3 NM String Nominal size name 4 SP String Name of relevant engineering standard (optional) Additional pointers as required (see Section 2.2.4.4.2). 378 4.78.14 (TYPE 406, FORM 14) - FLOW LINE SPECIFICATION 4.78.14 FORM NUMBER: 14 Flow Line Specification The Flow Line Specification Property attaches one or more text strings to entities being used to represent a flow line. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 14 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 L1 String Primary flow line specification name 3 L2 String Modifier (optional) .. . . . .. .. 1+NP LNP String Modifier (optional) Additional pointers as required (see Section 2.2.4.4.2). 379 4.78.15 (TYPE 406, FORM 15) - NAME 4.78.15 FORM NUMBER: 15 Name This property contains a string which specifies a user-defined name. It can be used for any entity that does not have a name explicitly specified in the parameter data for the entity. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 15 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 NAME String Entity Name Additional pointers as required (see Section 2.2.4.4.2). 380 4.78.16 (TYPE 406, FORM 16) - DRAWING SIZE 4.78.16 FORM NUMBER: 16 Drawing Size This property specifies the size of the drawing in drawing units. The origin of the drawing is defined to be (0,0) in drawing space. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 16 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=2) 2 XS Real X Size (Extent of Drawing along positive XD axis) 3 YS Real Y Size (Extent of Drawing along positive YD axis) Additional pointers as required (see Section 2.2.4.4.2). 381 4.78.17 (TYPE 406, FORM 17) - DRAWING UNITS 4.78.17 FORM NUMBER: 17 Drawing Units This property specifies the drawing space units as outlined in the Drawing Entity (Type 404). The drawing units are given in the same form as the model space units in the Global Section (see Section 2.2.4.2.15). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 17 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=2) 2 FLAG Integer Units Flag 3 UNIT String Units Name Additional pointers as required (see Section 2.2.4.4.2). 382 4.78.18 (TYPE 406, FORM 18) - INTERCHARACTER SPACING 4.78.18 FORM NUMBER: 18 Intercharacter Spacing The definition of this property can be found in Appendix G (see Section G.30). 383 4.78.19 (TYPE 406, FORM 19) - LINE FONT ECO530 4.78.19 FORM NUMBER: 19 Line Font The definition of this property can be found in Appendix G (see Section G.31). 384 4.78.20 (TYPE 406, FORM 20) - HIGHLIGHT 4.78.20 FORM NUMBER: 20 Highlight ECO534 The definition of this property can be found in Appendix G (see Section G.32). 385 4.78.21 (TYPE 406, FORM 21) - PICK ECO534 4.78.21 FORM NUMBER: 21 Pick The definition of this property can be found in Appendix G (see Section G.33). 386 4.78.22 (TYPE 406, FORM 22) - UNIFORM RECTANGULAR GRID 4.78.22 FORM NUMBER: 22 Uniform Rectangular Grid ECO537 The definition of this property can be found in Appendix G (see Section G.34). 387 4.78.23 (TYPE 406, FORM 23) - ASSOCIATIVITY GROUP TYPE ECO571 4.78.23 FORM NUMBER: 23 Associativity Group Type The definition of this property can be found in Appendix G (see Section G.35). 388 4.78.24 (TYPE 406, FORM 24) - LEVEL TO PWB LAYER MAP 4.78.24 FORM NUMBER: 24 Level to PWB Layer Map ECO573 The definition of this property can be found in Appendix G (see Section G.36). 389 4.78.25 (TYPE 406, FORM 25) - PWB ARTWORK STACKUP ECO574 4.78.25 FORM NUMBER: 25 PWB Artwork Stackup The definition of this property can be found in Appendix G (see Section G.37). 390 4.78.26 (TYPE 406, FORM 26) - PWB DRILLED HOLE 4.78.26 FORM NUMBER: 26 PWB Drilled Hole ECO575 The definition of this property can be found in Appendix G (see Section G.38). 391 4.78.27 (TYPE 406, FORM 27) - GENERIC DATA ECO601 4.78.27 FORM NUMBER: 27 Generic Data The definition of this property can be found in Appendix G (see Section G.39). 392 4.78.28 (TYPE 406, FORM 28) - DIMENSION UNITS 4.78.28 FORM NUMBER: 28 Dimension Units ECO606 The definition of this property can be found in Appendix G (see Section G.40). 393 4.78.29 (TYPE 406, FORM 29) - DIMENSION TOLERANCE ECO606 4.78.29 FORM NUMBER: 29 Dimension Tolerance The definition of this property can be found in Appendix G (see Section G.41). 394 4.78.30 (TYPE 406, FORM 30) - GENERIC DATA 4.78.30 FORM NUMBER: 30 Dimension Display Data ECO606 The definition of this property can be found in Appendix G (see Section G.42). 395 4.78.31 (TYPE 406, FORM 31) - BASIC DIMENSION ECO606 4.78.31 FORM NUMBER: 31 Basic Dimension The definition of this property can be found in Appendix G (see Section G.43). 396 4.79 SINGULAR SUBFIGURE INSTANCE ENTITY (TYPE 408) 4.79 Singular Subfigure Instance Entity (Type 408) This entity defines the occurrence of a single instance of the defined subfigure (Type 308). See Figure 87 and Section 3.6.2. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 408 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 408 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DE Pointer Pointer to the DE of the Subfigure Definition Entity 2 X Real Translation data relative to either model space or to the defini- tion space of a referring entity 3 Y Real 4 Z Real 5 S Real Scale factor (default = 1.0) Additional pointers as required (see Section 2.2.4.4.2). 397 4.79 SINGULAR SUBFIGURE INSTANCE ENTITY (TYPE 408) Figure 87. Relationship Between Subfigure Definition and Subfigure Instance 398 4.80 VIEW ENTITY (TYPE 410) 4.80 View Entity (Type 410) The View Entity defines a framework for specifying a viewing orientation of an object in three dimensional model space (X,Y,Z). The framework is also used to support the projection of all or part of model space onto a view plane. One type of projection, an orthographic parallel projection, can be specified. A second type of projection supporting perspective views is defined in Appendix G ECO507 (see Section G.44). Orthographic Parallel Projection. An orthographic parallel projection onto a view plane of an object in model space is formed by passing rays normal to the view plane through each point of the object and finding the intersection with the view plane as shown in Figure 88. View Coordinate System. The view plane can be described by introducing a right-handed view coordinate system, (XV, YV, ZV) into model space. The view plane is the XV, YV plane, i.e., the plane ZV=0. The view direction is along the positive ZV axis toward the view plane, i.e., in the direction of the vector (0,0,-1). The positive YV axis points in the "up" direction in the resulting view. The point (0,0,0) in the view coordinate system (see Figure 89) is called the view origin. Thus, a complete viewing orientation is specified by a view coordinate system. View Coordinates Obtained from Model Coordinates. View coordinates are obtained from model coordinates through translation and rotation. There are several ways that systems specify the data required to transfer from model to view coordinates. However, in each case, the data can be recorded using Form 0 of the Transformation Matrix Entity such that the model coordinates are taken as input and the view coordinates are produced as output, as follows, where R denotes the rotation matrix and T the translation vector (see Section 4.19): 2 3 2 3 2 3 2 3 XV R11 R12 R13 X T1 4 Y V 5 = 4 R21 R22 R23 5 4 Y 5 + 4 T2 5 ZV R31 R32 R33 Z T3 In this situation, R is called the view matrix. The View Entity specifies the view matrix and the translation vector by use of a pointer to a Trans- formation Matrix Entity in DE Field 7. In the special case when the view matrix is the identity matrix and there is zero translation, a zero value in DE Field 7 may be used. Example 1: (View coordinates obtained from model coordinates by a translation and then a rotation.) The system defines a viewing orientation by specifying a view origin (XO, YO, ZO) in model space and a rotation matrix so that: 2 3 2 3 0 2 3 2 31 XV 3 x 3 X XO 4 Y V 5 = 4 Rotation 5 @ 4 Y 5 - 4 Y O 5A ZV Matrix Z ZO or: 2 3 2 3 2 3 2 3 2 3 XV 3 x 3 X 3 x 3 XO 4 Y V 5 = 4 Rotation 5 4 Y 5 - 4 Rotation 5 4 Y O 5 : ZV Matrix Z Matrix ZO 399 4.80 VIEW ENTITY (TYPE 410) Therefore, the rotation matrix is the view matrix, and in the Transformation Matrix Entity: 2 3 2 3 2 3 3 x 3 3 x 3 XO R = 4 Rotation 5 ; T = - 4 Rotation 5 4 Y O 5 Matrix Matrix ZO Example 2: (View coordinates obtained from model coordinates by a rotation and then a transla- tion.) The system defines a viewing orientation by specifying a rotation matrix and a translate or pan vector (XL, YL, ZL) expressed in the rotated coordinate system, so that: 2 3 2 3 2 3 2 3 XV 3 x 3 X XL 4 Y V 5 = 4 Rotation 5 4 Y 5 - 4 Y L 5 ZV Matrix Z ZL Therefore, the rotation matrix is the view matrix, and in the Transformation Matrix Entity: 2 3 2 3 3 x 3 XL R = 4 Rotation 5 ; T = - 4 Y L 5 : Matrix ZL Simple Form of the View Entity. The View Entity provides a view number for the purpose of identifying differing view orientations. However, no standard indexing scheme is presumed to exist. In its simplest form, the View Entity consists of a pointer to the Transformation Matrix Entity (in DE Field 7), and a view number. The Transformation Matrix Entity specifies a view matrix R and a translation vector T as given in the preceding section. Projection of a View Volume. In some cases, a view volume and a scale factor may be required to control the projection of the view into a two-dimensional drawing space specified by a Drawing Entity (see Section 4.77). The view volume bounds that portion of the data which will be projected after clipping is performed. ECO603 The view volume is a rectangular parallelepiped with limits specified by Plane Entities (Type 108) ECO610 defined in the model coordinate system. The absence of clipping in a particular direction may be indicated by setting the pointer for the appropriate Plane Entity equal to zero. The Plane Entities used to define the view volume shall not be arbitrary planar definitions (see Figure 90). After the transformation from model coordinates to view coordinates, each plane must be perpendicular to the appropriate view coordinate system axis (e.g., the left side of the view ECO533 volume must transform into a plane XV=constant). Only the unbounded form of the Plane Entity (Type 108, Form 0) is required for use as a clipping plane; if another form is encountered, the bounding curve and display symbol should be ignored. Projection Operations. The order of operations for the View Entity is as follows: 1. Transform from model to view space. 2. Perform clipping (if included). 400 4.80 VIEW ENTITY (TYPE 410) 3. Perform projection onto the view plane. 4. Transform from view space to drawing space. For Form 0 of the Drawing Entity (Type 404), the projection onto the view plane and the transform ECO538 from view space to drawing space can be controlled by the following equation in the case of ortho- graphic parallel projection, where S is the scale factor and XORIGIN and YORIGIN are defined in the Drawing Entity (see Section 4.77): 2 XV 3 XD S 0 0 4 5 XORIGIN Y D = 0 S 0 YZVV + Y ORIGIN As with Form 0, the transformation for Form 1 of the Drawing Entity (Type 404) is controlled by the ECO538 view scale factor S and the view origin drawing location. In addition, a rotation angle is applied as follows: 2 XV 3 XD cos - sin 0 4 5 XORIGIN Y D = S sin cos 0 YZVV + Y ORIGIN Entity Display. The display of an entity in a particular view is controlled by the use of the view value in Field 6 of the Directory Entry for the entity. If this value is zero or undefined, the entity is displayed with its own characteristics in all views unless display is controlled by other pa- rameters (e.g., pointed to by another entity such as Subfigure Definition or Drawing). If this value is a pointer to a View Entity, the entity is displayed with its own characteristics in only the one view. The selection of multiple views, display characteristics, or both, for an entity may be made by using one of the Views Visible Associativity Entities (Type 402, Form 3, 4, or 19). The view value for the ECO558 entity then is a pointer to this associativity instead of to a View Entity. 401 4.80 VIEW ENTITY (TYPE 410) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 410 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |< n:a: > |**??01** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 410 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 VNO Integer View number 2 SCALE Real Scale factor (Default = 1.0) 3 XVMINP Pointer Pointer to left side of view volume (XVMIN plane), or zero 4 YVMAXP Pointer Pointer to top of view volume (YVMAX plane) or zero 5 XVMAXP Pointer Pointer to right side of view volume (XVMAX plane), or zero 6 YVMINP Pointer Pointer to bottom of view volume (YVMIN plane), or zero 7 ZVMINP Pointer Pointer to back of view volume (ZVMIN plane), or zero 8 ZVMAXP Pointer Pointer to front of view volume (ZVMAX plane), or zero Additional pointers as required (see Section 2.2.4.4.2). 402 4.80 VIEW ENTITY (TYPE 410) Figure 88. Orthographic Parallel Projection of AB on a View Plane Figure 89. View Coordinate System (View Origin at XV=YV=ZV=0) 403 4.80 VIEW ENTITY (TYPE 410) Figure 90. Planes Defining the View Volume 404 4.81 RECTANGULAR ARRAY SUBFIGURE INSTANCE ENTITY (TYPE 412) 4.81 Rectangular Array Subfigure Instance Entity (Type 412) The Rectangular Array Subfigure Instance Entity produces copies of an object called the base entity, arranging them in equally spaced rows and columns. The following types of entities are valid for use as a base entity: Group Associativity, Point, Line, Circular Arc, Conic Arc, Parametric Spline Curve, Rational B-spline Curve, any annotation entity, Rectangular Array Instance, Circular Array Instance, or Subfigure Definition. The number of columns and rows of the rectangular array together with their respective horizontal and vertical displacements are given. Also, the coordinates of the lower left hand corner for the entire array are given. This is where the first entity in the reproduction process is placed and is called position Number 1. The successive positions are counted vertically up the first column, then vertically up the second column to the right, and so on. The array of instance locations for the base entity is rotated about the line through the point (X,Y), parallel to the ZT-axis. The angle of rotation is specified in radians counterclockwise from the positive XT-axis. The instances of the base entity are not rotated from their original orientation. A DO-DON'T flag controls which portion of the array is displayed. If the DO value is chosen, half or fewer of the elements of the rectangular array are to be defined. If the DON'T value is chosen, half or more of the elements of the rectangular array are to be defined. 405 4.81 RECTANGULAR ARRAY SUBFIGURE INSTANCE ENTITY (TYPE 412) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 412 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 412 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DE Pointer Pointer to the DE of the base entity 2 S Real Scale factor (default = 1.0) 3 X Real Coordinates of point to be used as lower left corner of array 4 Y Real 5 Z Real 6 NC Integer Number of columns 7 NR Integer Number of rows 8 DX Real Horizontal distance between columns 9 DY Real Vertical distance between rows 10 AX Real Rotation angle in radians 11 LC Integer DO-DON'T list count (LC=0 indicates all to be displayed.) 12 DDF Integer DO-DON'T flag: 0 = DO 1 = DON'T 13 N1 Integer Number of first position to be processed (DO), or not to be processed (DON'T) .. . . . .. .. 12+LC NLC Integer Number of last position Additional pointers as required (see Section 2.2.4.4.2). 406 4.82 CIRCULAR ARRAY SUBFIGURE INSTANCE ENTITY (TYPE 414) 4.82 Circular Array Subfigure Instance Entity (Type 414) The Circular Array Subfigure Instance Entity produces copies of an object called the base entity, arranging them around the edge of an imaginary circle whose center and radius are specified. The following types of entities are valid for use as a base entity: Group Associativity, Point, Line, Circular Arc, Conic Arc, Parametric Spline Curve, Rational B-spline Curve, any annotation entity, Rectangular Array Subfigure Instance, Circular Array Instance, or Subfigure Definition. The number of possible instance locations for the base entity is specified, and the location of the first instance position is specified in terms of a radius and a start angle measured positive, counterclockwise in radians from the line through the point (X,Y), parallel to the ZT-axis. The successive positions follow a counterclockwise direction around the imaginary circle and are distributed according to a given delta angle. A DO-DON'T flag controls which portion of the array is displayed. If the DO value is chosen, half or fewer of the elements of the circular array are to be defined. If the DON'T value is chosen, half or more of the elements of the circular array are to be defined. 407 4.82 CIRCULAR ARRAY SUBFIGURE INSTANCE ENTITY (TYPE 414) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 414 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 414 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DE Pointer Pointer to the DE of the base entity 2 NE Integer Total number of possible instance locations 3 X Real Coordinates of center of imaginary circle 4 Y Real 5 Z Real 6 R Real Radius of imaginary circle 7 AS Real Start angle in radians 8 AD Real Delta angle in radians 9 LC Integer DO-DON'T list count (LC=0 indicates all replicated entities to be displayed) 10 DDF Integer DO-DON'T Flag: 0 = DO 1 = DON'T 11 N1 Number of first position to be processed (DO), or to be not processed (DON'T) .. . . . .. .. 10+LC NLC Integer Number of last position Additional pointers as required (see Section 2.2.4.4.2). 408 4.83 EXTERNAL REFERENCE ENTITY (TYPE 416) 4.83 External Reference Entity (Type 416) The External Reference Entity provides a link between an entity in a referencing file and the definition of a logically related entity in a referenced file. Further, in keeping with the concept of treating this entity as the definition which it replaces, the subordinate entity switch should be set as it would be on the definition replaced. See Section 3.6.4 for the entities used in the linkage. Five forms of the External Reference Entity are defined. Two of these forms are used to reference ECO572 a definition and one form is a logical reference. Form 0 is used when a single definition from the ECO604 referenced file is desired. This would be the case where the referenced file contained a collection of definitions. Form 1 is used when the entire file is to be instanced. This would be the case where the referenced file contained a complete subassembly. Form 2 is used for external logical references where an entity in one file relates to an entity in a separate file (e.g., when each sheet of a drawing is a separate file, and a flange on one sheet is also depicted on, or mates with, a flange on another sheet). Forms 3 and 4 are used when it is assumed that a copy of the subfigure exists in native form ECO604 on the receiving system; these forms can only be used to replace the Subfigure Definition (Type 308) and Network Subfigure Definition (Type 320). Forms 0, 2, 3, and 4 require an entity-unique symbolic name. The following entities and the parameter which supplies the symbolic name are identified for use. Form 3 is defined in Appendix G (see Section G.45). Form 4 is defined in Appendix G (see ECO572 Section G.46). ECO604 _________________________________________________________________________________________ | Entity | | | | | Type | Entity | Parameter | | |__Number__|___________Name__________|_______Index_____|_________Description__________|__ | 132 |Connect Point | 9 | CP Function Name (unique) | | 302 |Associativity Definition | ( ) |Implementor assigned | | 304 |Line Font Definition | ( ) |Implementor assigned | | 306 |MACRO Definition | 2 | Entity Type Identification | | 308 |Subfigure Definition | 2 | Subfigure name (unique) | | 310 |Text Font Definition | 2 | Font name | | 312 |Text Display Template | ( ) |Implementor assigned | | 314 |Color Definition | ( ) |Implementor assigned | |_____320_____|Network_Subfigure_Def.__|_______2_______|_Subfigure_name_(unique)______|__ Possible alternatives for the entity-unique symbolic name for those entities marked "Implementor assigned" could be: (1) the property Reference Designator (Type 406, Form 7), or (2) the Entity Label, Entity Subscript (Directory Entry Fields 18 and 19). 409 4.83 EXTERNAL REFERENCE ENTITY (TYPE 416) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 416 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 416 |< n:a: > |< n:a: > | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0, 2. Parameter Data Index__ Name____ Type___ Description___ 1 EXTFID String External Reference File Identifier (contained as Global Param- eter Number 4 in the referenced file) 2 EXTNAM String External Reference Entity Symbolic Name Additional Pointers as required (see Section 2.2.4.4.2). 410 4.83 EXTERNAL REFERENCE ENTITY (TYPE 416) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 416 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 416 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 EXTFID String External Reference File Identifier (contained as Global Param- eter Number 4 in the referenced file) Additional Pointers as required (see Section 2.2.4.4.2). 411 4.84 NODAL LOAD/CONSTRAINT ENTITY (TYPE 418) 4.84 Nodal Load/Constraint Entity (Type 418) This entity relates loads and/or constraints to specific nodes in the Finite Element Model. This is accomplished by creating a relation between Node Entities and the Tabular Data Property that con- tains the load or constraint data. Each load and constraint case will require a Nodal Load/Constraint Entity and a Tabular Data Property Form 11 with PTYPE=12. Figure 91 shows the relationship or linkage between the Nodal Load/Constraint Entity and the Tab- ular Data Property which carries the load or constraint vector. The relationship or linkage is also shown on the General Note Entity which describes the load/constraint test case being performed. There is a one-to-one correspondence between the load case description and the General Note En- tity and the pointer to the Tabular Data Property containing the load case magnitudes (see also Section 3.6.6). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 418 | ) |< n:a: > |< n:a: > |< n:a: > | 0; ) | 0; ) | 0; ) |??????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 418 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NC Integer Total number of cases 2 TYPE Integer 1 = Loads 2 = Constraints 3 DE Pointer Pointer to Node 4 PTR1 Pointer Pointer to the DE of the first Tabular Data Property .. . . . .. .. 3+NC PTRNC Pointer Pointer to the DE of the last Tabular Data Property Additional Pointers as required (see Section 2.2.4.4.2). 412 4.84 NODAL LOAD/CONSTRAINT ENTITY (TYPE 418) Figure 91. Relationship Between the Nodal Load/Constraint Entity and Tabular Data Properties 413 4.85 NETWORK SUBFIGURE INSTANCE ENTITY (TYPE 420) 4.85 Network Subfigure Instance Entity (Type 420) Each instance of a Network Subfigure Definition Entity (Type 320) is specified by a Network Sub- figure Instance Entity. Its use is described in Section 3.6.2. In addition though, the points of connection (Connect Point Entity, Type 132) specified by the Network Subfigure Definition Entity must be instanced and associated with each Network Subfigure Instance (see indices 11 and 12). ECO542 There is a direct relationship between the points of connection in the Network Subfigure Definition Entity (Type 320) and the Network Subfigure Instance Entity (Type 420). The number of associated (child) Connect Point Entities (Type 132) in the instance must match the number in the definition, their order must be identical, and any unused points of connection in the instance must be indicated by a null (zero) pointer. The Type Flag Field (Index 8) implements the distinction between logical design and physical design data, and is required if both are present in the file. The Network Subfigure Instance Entity allows different scale factors in the x, y, and z directions. This scaling is performed before the translation from X, Y, and Z and before the Transformation Matrix Entity pointed to in the directory entry (if any) is applied. The scaling does not apply to the model space placement coordinates (X, Y, Z). 414 4.85 NETWORK SUBFIGURE INSTANCE ENTITY (TYPE 420) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 420 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 420 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 DE Pointer Pointer to the DE of the Network Subfigure Definition Entity 2 X Real Translation data relative to either model space or to the defini- tion space of a referring entity 3 Y Real 4 Z Real 5 XS Real Scale factor in definition space x axis (default 1.0) 6 YS Real Scale factor in definition space y axis (default XS) 7 ZS Real Scale factor in definition space z axis (default XS) 8 TF Integer Type flag: 0 = not specified (default) 1 = logical 2 = physical 9 PRD String Primary reference designator 10 DPTR Pointer Pointer to the DE of the primary reference designator Text Dis- play Template Entity, or null. If null, no Text Display Template Entity specified. ECO546 11 NC Integer Number of associated (child) Connect Point Entities 12 CPTR1 Pointer Pointer to the DE of the first associated Connect Point Entity, or zero .. . . . .. .. 11+NC CPTRNC Pointer Pointer to the DE of the last associated Connect Point Entity, or zero Additional pointers as required (see Section 2.2.4.4.2). 415 4.86 ATTRIBUTE TABLE INSTANCE ENTITY (TYPE 422) 4.86 Attribute Table Instance Entity (Type 422) ECO561 Each occurrence of an Attribute Table (Type 322, Form 0) is represented by an Attribute Table Instance Entity (Type 422). Directory Entry Field 3 (Structure) of each instance contains a negated pointer to the Directory Entry of its corresponding Attribute Table Definition Entity. All forms of this entity may be independent (not necessarily attached to another entity), or dependent ("pointed at" by other entities as a property would be). See Section 2.2.4.4.2 for more details. 4.86.1 Attribute Table Instance (Form 0). This form of the entity is for an instance of a single row or tuple. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 422 | ) | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 422 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ (first attribute instance) 1 AV(1,1) Variable First attribute value 2 AV(1,2) Variable Second attribute value .. . . . .. .. AVC(1) AV(1,AVC(1)) Variable Last attribute value .. . . . .. .. Let M = AVC(1) + . . .+ AVC(NA-1) (last attribute instance) M+1 AV(NA,1) Variable First attribute value M+2 AV(NA,2) Variable Second attribute value .. . . . .. .. M+AVC(NA) AV(NA,AVC(NA)) Variable Last attribute value Additional pointers as required (see Section 2.2.4.4.2). 416 4.86 ATTRIBUTE TABLE INSTANCE ENTITY (TYPE 422) 4.86.2 Attribute Table Instance (Form 1). This form of the entity is for a table of attributes in row-major order; that is, the values for the first attribute through the last attribute for the first row are followed by the values for the first attribute through the last attribute for the second row, etc. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 422 | ) | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 422 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ (attributes, first row, first column) 1 NR Integer Number of rows 2 AV(1,1,1) Variable First attribute value 3 AV(1,1,2) Variable Second attribute value .. . . . .. .. 1+AVC(1) AV(1,1,AVC(1)) Variable Last attribute value .. . . . .. .. Let M = 1+ AVC(1) + . . .+ AVC(NA-1)) (attributes, first row, last column) M+1 AV(1,NA,1) Variable First attribute value M+2 AV(1,NA,2) Variable Second attribute value .. . . . .. .. M+AVC(NA) AV(1,NA,AVC(NA)) Variable Last attribute value .. . . . .. .. Let M = 1 + NR*(AVC(1) + . . .+ AVC(NA)) - AVC(NA) (attributes, last row, last column) M+1 AV(NR,NA,1) Variable First attribute value M+2 AV(NR,NA,2) Variable Second attribute value .. . . . .. .. M+AVC(NA) AV(NR,NA,AVC(NA)) Variable Last attribute value Additional pointers as required (see Section 2.2.4.4.2). 417 4.87 SOLID INSTANCE ENTITY (TYPE 430) 4.87 Solid Instance Entity (Type 430) The Solid Instance Entity provides a mechanism for replicating a solid representation. The solid pointed to in this entity is allowed to be: o Primitive Entity o Boolean Tree Entity o Solid Assembly Entity o Solid Instance Entity Note that a transformation matrix may be pointed to by Field 7 of the DE to position this instance in any desired manner. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 430 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |???????? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 430 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: When the Hierarchy is set to Global Defer (01), all of the following are ignored and may be defaulted: Line Font Pattern, Line Weight, Color Number, Level, View, and Blank Status. Parameter Data Index__ Name____ Type___ Description___ 1 PTR Pointer Pointer to the DE of the solid Additional pointers as required (see Section 2.2.4.4.2). 418 4.88 VERTEX ENTITY (TYPE 502) 4.88 Vertex Entity (Type 502) ECO603 The definition of this entity can be found in Appendix G (see Section G.47). 419 4.89 EDGE ENTITY (TYPE 504) 4.89 Edge Entity (Type 504) ECO603 The definition of this entity can be found in Appendix G (see Section G.48). 420 4.90 LOOP ENTITY (TYPE 508) 4.90 Loop Entity (Type 508) ECO603 The definition of this entity can be found in Appendix G (see Section G.49). 421 4.91 FACE ENTITY (TYPE 510) 4.91 Face Entity (Type 510) ECO603 The definition of this entity can be found in Appendix G (see Section G.50). 422 4.92 SHELL ENTITY (TYPE 514) 4.92 Shell Entity (Type 514) ECO603 The definition of this entity can be found in Appendix G (see Section G.51). 423 4.92 SHELL ENTITY (TYPE 514) 424 Appendix A. Part File Examples This appendix contains three sample parts encoded in the ASCII Form. These files are included to provide guidance in the usage of this Specification and, as such, they do not represent all design ap- plication uses. The files are a two-dimensional application using structure entities, a two-dimensional drawing of a mechanical part with dimensioning, and a three-dimensional part with two-dimensional drawing views defined. Example file 1 is an integrated circuit (IC) cell. The IC application was selected because of the predominance of two-dimensional geometry used in electrical designs. The geometry used in the cell in Figure A1 consists of simple closed planar curve, linear path entities and line widening property. ECO526 The structure entities are nested subfigures using a Network Subfigure Definition Entity and Array Subfigure Instance Entities. A Connect Point Entity is included to identify the signal port. The geometry is on five different levels, each representing a process mask. The entity label field of each Directory Entry record contains (optional) text included to describe the entity's use. The entities in this file would be typical of those used in an IC application to transfer either cell libraries or a complete design between design systems. The file of a design prepared for pattern generation, with subfigures resolved and the geometry fractured, would use the Flash Entity exclusively. The cell file was adapted from a cell library in [HON80] with kind permission from the author. Example file 2 is a two-dimensional drawing of a mechanical part containing geometry entities and annotation entities typically found on engineering drawings. Included as geometry are points, lines, circular arcs and conics. For annotation, the file includes linear dimensions, angular dimensions, radius dimensions, ordinate dimensions, a general label and general notes. Figure A2 shows the mechanical part, which was used during one of the early public demonstrations of intersystem data exchange. Example file 3 is included to show the use of View Entities and Drawing Entities in conjunction with a three-dimensional part model to convey a drawing to the receiving system. Figure A3 shows the example drawing. In this way, model geometry and viewing parameters are logically separate. A three-dimensional model, as well as the drawing, is received enabling additional views to be created if necessary, and changes to the part model are reflected in all views. 425 A. ELECTRICAL PART EXAMPLE Figure A1. Electrical Part Example 426 A. ELECTRICAL PART EXAMPLE Example 1 Electrical Part INTEGRATED CIRCUIT SEMICUSTOM CELL (ONE PART OF A LIBRARY FILE) S 1 USED IN APPENDIX A OF IGES VERSION 3.0 AND MODIFIED FOR VERSION 4.0 S 2 1H,,1H;,10H5MICRONLIB,5HPADIN,9HEXAMPLE 1,4HHAND,16,38,06,38,13, G 1 10HIC.LIBRARY,1.0,9,2HUM,1,,13H900729.231212,0.01,265.0, G 2 25HIGES RFC Review Committee,8HIPO/NIST,6,0; G 3 308 01 1 0 0 00020201D 01 308 0 1 SUBFIG1 D 02 106 02 1 1 0 00020200D 03 106 0 4 1 63 VDDPORT D 04 106 03 1 1 0 00020200D 05 106 0 4 1 63 GNDPORT D 06 106 04 1 1 0 00020200D 07 106 0 4 1 63 BONDPAD D 08 106 05 1 7 0 00020200D 09 106 0 5 1 63 GLASSBOX D 10 320 06 1 0 0 00010201D 11 320 0 1 CELLFIG D 12 408 07 1 0 0 00030200D 13 408 0 1 INST1 D 14 106 08 1 3 0 00020200D 15 106 0 3 2 63 ACTBOX D 16 106 10 1 3 0 00020200D 17 106 0 3 1 63 ACTBOX D 18 106 11 1 3 0 00020200D 19 106 0 3 1 11 ACTSTG D 20 106 12 1 3 0 00020200D 21 106 0 3 2 63 ACTBOX D 22 132 14 1 3 0 00020400D 23 132 0 1 SIGPORT D 24 106 15 1 6 0 00020200D 25 106 0 8 2 63 CUT D 26 106 17 1 6 0 00020200D 27 106 0 8 2 63 CUT D 28 308 19 1 0 0 00020201D 29 308 0 1 SUBFIG2 D 30 106 20 1 6 0 00030200D 31 106 0 8 1 63 CUTDEF D 32 412 21 1 0 0 00030201D 33 412 0 1 CUTARR D 34 106 22 1 2 0 00020200D 35 106 0 2 2 11 GATESTG D 36 106 24 1 2 0 00020200D 37 106 0 2 2 63 GATEBOX D 38 106 26 1 1 0 00020200D 39 106 0 4 1 63 GATEBOX D 40 406 27 1 0 0 00010200D 41 406 0 1 5 LINWIDTH D 42 427 A. ELECTRICAL PART EXAMPLE 308,0,6HPADBLK,4,03,05,07,09; 01P 01 106,1,5,0.,0.,0.,265.,0.,265.,-20.,0.,-20.,0.,0.; 03P 02 106,1,5,0.,30.,-245.,245.,-245.,245.,-265.,30.,-265.,30.,-245.; 05P 03 106,1,5,0.,65.,-65.,200.,-65.,200.,-200.,65.,-200.,65.,-65.; 07P 04 106,1,5,0.,75.,-75.,190.,-75.,190.,-190.,75.,-190.,75.,-75.; 09P 05 320,1,5HPADIN,11,13,15,17,19,21,25,27,33,35,37,39,2,,,1,23; 11P 06 408,01,0.,0.,0.; 13P 07 106,1,5,0.,30.,-210.,222.5,-210.,222.5,-255.,30.,-255.,30., 15P 08 -210.; 15P 09 106,1,5,0.,65.,-25.,75.,-25.,75.,-45.,65.,-45.,65.,-25.; 17P 10 106,1,3,0.,77.5,-27.5,240.,-27.5,240.,-262.5,0,1,41; 19P 11 106,1,5,0.,222.5,-215.,237.5,-215.,237.5,-247.5,222.5,-247.5, 21P 12 222.5,-215.; 21P 13 132,240.,-265.,0.,,2,1,,,,,01,1,1,11; 23P 14 106,1,5,0.,67.5,-32.5,72.5,-32.5,72.5,-42.5,67.5,-42.5,67.5, 25P 15 -32.5; 25P 16 106,1,5,0.,227.5,-252.5,232.5,-252.5,232.5,-257.5,227.5,-257.5, 27P 17 227.5,-252.5; 27P 18 308,0,7HCONTACT,1,31; 29P 19 106,1,5,0.,-5.,2.5,5.,2.5,5.,-2.5,-5.,-2.5,-5.,2.5; 31P 20 412,29,1.0,37.5,-250.,0.,8,1,25.,0.,0.,0; 33P 21 106,1,6,0.,232.5,-212.5,232.5,-222.5,50.,-222.5,50.,-240., 35P 22 232.5,-240.,232.5,-247.5,0,1,41; 35P 23 106,1,5,0.,225.,-250.,235.,-250.,235.,-260.,225.,-260.,225., 37P 24 -250.; 37P 25 106,1,5,0.,65.,-30.,75.,-30.,75.,-65.,65.,-65.,65.,-30.; 39P 26 406,5,5.0,1,1,0,0; 41P 27 S 2G 3D 42P 27 T 1 428 A. MECHANICAL PART EXAMPLE Figure A2. Mechanical Part Example 429 A. MECHANICAL PART EXAMPLE Example 2 Mechanical Part Example PLATE.001 SAMPLE MECHANICAL PART WITH ANNOTATION S 1 USED AT AUTOFACT - OCTOBER 1982 AND IN VERSION 3.0 APPENDIX A S 2 S 3 ENTITY CONTENT: POINT, LINE, ARC and CONIC S 4 LINEAR, ANGULAR, RADIUS, POINT and ORDINATE DIMENSION S 5 GENERAL NOTE, GENERAL LABEL S 6 S 7 ,,8HPANEL123,10HPANEL.IGES,4HEX 2,4HHAND,16,38,7,38,14,8HPANEL123,1.0, G 1 1,4HINCH,1,0.028,13H900729.231652,0.0005,100.0, G 2 25HIGES RFC Review Committee,8HIPO/NIST,6,0; G 3 124 1 1 1 0 0 0 0 0D 1 124 0 0 2 0 0D 2 212 3 1 1 5 0 0 0 10100D 3 212 0 0 2 0 0D 4 214 5 1 1 5 0 0 0 10100D 5 214 0 0 1 2 0D 6 210 6 1 1 5 0 0 0 101D 7 210 0 0 1 0 0D 8 110 7 1 1 1 0 0 0 0D 9 110 0 0 1 0 0D 10 110 8 1 1 1 0 0 0 0D 11 110 0 0 1 0 0D 12 110 9 1 1 1 0 0 0 0D 13 110 0 0 1 0 0D 14 110 10 1 1 1 0 0 0 0D 15 110 0 0 1 0 0D 16 100 11 1 1 1 0 0 0 0D 17 100 0 0 1 0 0D 18 100 12 1 1 1 0 0 0 0D 19 100 0 0 1 0 0D 20 100 13 1 1 1 0 0 0 0D 21 100 0 0 1 0 0D 22 100 14 1 1 1 0 0 0 0D 23 100 0 0 1 0 0D 24 116 15 1 1 2 0 0 0 0D 25 116 0 0 1 0 0D 26 116 16 1 1 2 0 0 0 0D 27 116 0 0 1 0 0D 28 116 17 1 1 2 0 0 0 0D 29 116 0 0 1 0 0D 30 116 18 1 1 2 0 0 0 0D 31 116 0 0 1 0 0D 32 104 19 1 1 3 0 1 0 0D 33 104 0 0 2 1 0D 34 116 21 1 1 2 0 0 0 0D 35 116 0 0 1 0 0D 36 116 22 1 1 2 0 0 0 0D 37 116 0 0 1 0 0D 38 430 A. MECHANICAL PART EXAMPLE 212 23 1 1 4 0 0 0 10100D 39 212 0 0 1 0 0D 40 214 24 1 1 4 0 0 0 10100D 41 214 0 0 1 2 0D 42 214 25 1 1 4 0 0 0 10100D 43 214 0 0 1 2 0D 44 106 26 1 1 4 0 0 0 10100D 45 106 0 0 1 40 0D 46 106 27 1 1 4 0 0 0 10100D 47 106 0 0 1 40 0D 48 216 28 1 1 4 0 0 0 101D 49 216 0 0 1 0 0D 50 212 29 1 1 4 0 0 0 10100D 51 212 0 0 1 0 0D 52 214 30 1 1 4 0 0 0 10100D 53 214 0 0 1 2 0D 54 214 31 1 1 4 0 0 0 10100D 55 214 0 0 1 2 0D 56 106 32 1 1 4 0 0 0 10100D 57 106 0 0 1 40 0D 58 106 33 1 1 4 0 0 0 10100D 59 106 0 0 1 40 0D 60 216 34 1 1 4 0 0 0 101D 61 216 0 0 1 0 0D 62 212 35 1 1 5 0 0 0 10100D 63 212 0 0 1 0 0D 64 106 36 1 1 5 0 0 0 10100D 65 106 0 0 1 40 0D 66 218 37 1 1 5 0 0 0 101D 67 218 0 0 1 0 0D 68 212 38 1 1 5 0 0 0 10100D 69 212 0 0 1 0 0D 70 106 39 1 1 5 0 0 0 10100D 71 106 0 0 1 40 0D 72 218 40 1 1 5 0 0 0 101D 73 218 0 0 1 0 0D 74 212 41 1 1 5 0 0 0 10100D 75 212 0 0 1 0 0D 76 106 42 1 1 5 0 0 0 10100D 77 106 0 0 1 40 0D 78 218 43 1 1 5 0 0 0 101D 79 218 0 0 1 0 0D 80 212 44 1 1 5 0 0 0 10100D 81 212 0 0 1 0 0D 82 106 45 1 1 5 0 0 0 10100D 83 106 0 0 1 40 0D 84 218 46 1 1 5 0 0 0 101D 85 431 A. MECHANICAL PART EXAMPLE 218 0 0 1 0 0D 86 212 47 1 1 5 0 0 0 10100D 87 212 0 0 1 0 0D 88 106 48 1 1 5 0 0 0 10100D 89 106 0 0 1 40 0D 90 218 49 1 1 5 0 0 0 101D 91 218 0 0 1 0 0D 92 212 50 1 1 5 0 0 0 10100D 93 212 0 0 1 0 0D 94 106 51 1 1 5 0 0 0 10100D 95 106 0 0 1 40 0D 96 218 52 1 1 5 0 0 0 101D 97 218 0 0 1 0 0D 98 212 53 1 1 5 0 0 0 10100D 99 212 0 0 2 0 0D 100 106 55 1 1 5 0 0 0 10100D 101 106 0 0 1 40 0D 102 218 56 1 1 5 0 0 0 101D 103 218 0 0 1 0 0D 104 212 57 1 1 5 0 0 0 10100D 105 212 0 0 2 0 0D 106 106 59 1 1 5 0 0 0 10100D 107 106 0 0 1 40 0D 108 218 60 1 1 5 0 0 0 101D 109 218 0 0 1 0 0D 110 212 61 1 1 5 0 0 0 10100D 111 212 0 0 2 0 0D 112 214 63 1 1 5 0 0 0 10100D 113 214 0 0 1 2 0D 114 222 64 1 1 5 0 0 0 101D 115 222 0 0 1 0 0D 116 212 65 1 1 6 0 0 0 10100D 117 212 0 0 1 0 0D 118 214 66 1 1 6 0 0 0 10100D 119 214 0 0 1 2 0D 120 214 67 1 1 6 0 0 0 10100D 121 214 0 0 1 2 0D 122 106 68 1 1 6 0 0 0 1010100D 123 106 0 0 1 40 0D 124 106 69 1 1 6 0 0 0 10100D 125 106 0 0 1 40 0D 126 216 70 1 1 6 0 0 0 101D 127 216 0 0 1 0 0D 128 212 71 1 1 6 0 0 0 10100D 129 212 0 0 1 0 0D 130 214 72 1 1 6 0 0 0 10100D 131 214 0 0 1 2 0D 132 432 A. MECHANICAL PART EXAMPLE 214 73 1 1 6 0 0 0 10100D 133 214 0 0 1 2 0D 134 106 74 1 1 6 0 0 0 10100D 135 106 0 0 1 40 0D 136 106 75 1 1 6 0 0 0 1010100D 137 106 0 0 1 40 0D 138 216 76 1 1 6 0 0 0 101D 139 216 0 0 1 0 0D 140 212 77 1 1 6 0 0 0 10100D 141 212 0 0 1 0 0D 142 214 78 1 1 6 0 0 0 10100D 143 214 0 0 1 2 0D 144 214 79 1 1 6 0 0 0 10100D 145 214 0 0 1 2 0D 146 106 80 1 1 6 0 0 0 10100D 147 106 0 0 1 40 0D 148 106 81 1 1 6 0 0 0 10100D 149 106 0 0 1 40 0D 150 216 82 1 1 6 0 0 0 101D 151 216 0 0 1 0 0D 152 212 83 1 1 6 0 0 0 10100D 153 212 0 0 1 0 0D 154 214 84 1 1 6 0 0 0 10100D 155 214 0 0 1 2 0D 156 214 85 1 1 6 0 0 0 10100D 157 214 0 0 1 2 0D 158 106 86 1 1 6 0 0 0 10100D 159 106 0 0 1 40 0D 160 106 87 1 1 6 0 0 0 10100D 161 106 0 0 1 40 0D 162 216 88 1 1 6 0 0 0 101D 163 216 0 0 1 0 0D 164 110 89 1 4 6 0 0 0 100D 165 110 0 0 1 0 0D 166 110 90 1 4 6 0 0 0 100D 167 110 0 0 1 0 0D 168 212 91 1 1 6 0 0 0 10100D 169 212 0 0 1 0 0D 170 214 92 1 1 6 0 0 0 10100D 171 214 0 0 1 2 0D 172 214 93 1 1 6 0 0 0 10100D 173 214 0 0 1 2 0D 174 106 94 1 1 6 0 0 0 1010100D 175 106 0 0 1 40 0D 176 106 95 1 1 6 0 0 0 1010100D 177 106 0 0 1 40 0D 178 202 96 1 1 6 0 0 0 101D 179 433 A. MECHANICAL PART EXAMPLE 202 0 0 1 0 0D 180 124,0.70710678,-0.70710678,0.0,1.0,0.70710678,0.70710678,0.0, 1P 1 1.0,0.0,0.0,1.0,0.0,0,0; 1P 2 212,2,10,0.98,0.1,1,1.571,0.0,0,0,3.21,1.656,0.0,10HDRILL .010, 3P 3 10,1.02,0.1,1,1.571,0.0,0,0,3.210,1.506,0.0,10H(6 PLACES),0,0; 3P 4 214,2,0.150,0.050,0.0,4.800,2.000,4.562,1.546,4.262,1.546,0,0; 5P 5 210,3,1,5,0,0; 7P 6 110,0.0,0.200,0.0,0.0,3.000,0.0,0,0; 9P 7 110,0.200,0.0,0.0,4.800,0.0,0.0,0,0; 11P 8 110,5.000,0.200,0.0,5.000,3.000,0.0,0,0; 13P 9 110,0.200,3.200,0.0,4.800,3.200,0.0,0,0; 15P 10 100,0.0,4.800,3.000,5.000,3.000,4.800,3.200,0,0; 17P 11 100,0.0,0.200,3.000,0.200,3.200,0.0,3.000,0,0; 19P 12 100,0.0,0.200,0.200,0.0,0.200,0.200,0.00,0,0; 21P 13 100,0.0,4.800,0.200,4.800,0.0,5.000,0.200,0,0; 23P 14 116,4.000,3.000,0.0,0,0,0; 25P 15 116,3.000,3.000,0.0,0,0,0; 27P 16 116,2.000,3.000,0.0,0,0,0; 29P 17 116,1.000,3.000,0.0,0,0,0; 31P 18 104,4.000,0.0,16.000,0.0,0.0,-1.000,0.0,0.500,0.0,0.500,0.0, 33P 19 0,0; 33P 20 116,4.800,1.000,0.0,0,0,0; 35P 21 116,4.800,2.000,0.0,0,0,0; 37P 22 212,1,3,0.421,0.156,1,1.571,0.0,0,0,-0.639,1.614,0.0,3H3.2,0,0; 39P 23 214,1,0.150,0.050,0.0,-0.454,3.200,-0.454,1.870,0,0; 41P 24 214,1,0.150,0.050,0.0,-0.454,0.0,-0.454,1.514,0,0; 43P 25 106,1,3,0.0,0.0,3.200,-0.094,3.200,-0.579,3.200,0,0; 45P 26 106,1,3,0.0,0.0,0.0,-0.094,0.0,-0.579,0.0,0,0; 47P 27 216,39,41,43,45,47,0,0; 49P 28 212,1,3,0.437,0.156,1,1.571,0.0,0,0,2.032,-0.447,0.0,3H5.0,0,0; 51P 29 214,1,0.150,0.050,0.0,0.0,-0.369,1.932,-0.369,0,0; 53P 30 214,1,0.150,0.050,0.0,5.000,-0.369,2.519,-0.369,0,0; 55P 31 106,1,3,0.0,0.0,0.0,0.0,-0.094,0.0,-0.494,0,0; 57P 32 106,1,3,0.0,5.000,0.0,5.000,-0.094,5.000,-0.494,0,0; 59P 33 216,51,53,55,57,59,0,0; 61P 34 212,1,3,0.374,0.156,1,1.571,1.571,0,0,4.078,4.181,0.0,3H1.0,0,0; 63P 35 106,1,3,0.0,4.000,3.094,4.000,3.188,4.000,3.993,0,0; 65P 36 218,63,65,0,0; 67P 37 212,1,3,0.421,0.156,1,1.571,1.571,0,0,3.078,4.183,0.0,3H2.0,0,0; 69P 38 106,1,3,0.0,3.000,3.094,3.000,3.188,3.000,3.996,0,0; 71P 39 218,69,71,0,0; 73P 40 212,1,3,0.437,0.156,1,1.571,1.571,0,0,2.078,4.177,0.0,3H3.0,0,0; 75P 41 106,1,3,0.0,2.000,3.094,2.000,3.188,2.000,3.989,0,0; 77P 42 218,75,77,0,0; 79P 43 212,1,3,0.437,0.156,1,1.571,1.571,0,0,1.078,4.177,0.0,3H4.0,0,0; 81P 44 106,1,3,0.0,1.000,3.094,1.000,3.188,1.000,3.989,0,0; 83P 45 218,81,83,0,0; 85P 46 434 A. MECHANICAL PART EXAMPLE 212,1,3,0.374,0.156,1,1.571,0.0,0,0,6.211,0.922,0.0,3H1.0,0,0; 87P 47 106,1,3,0.0,4.894,1.000,4.988,1.000,6.024,1.000,0,0; 89P 48 218,87,89,0,0; 91P 49 212,1,3,0.421,0.156,1,1.571,0.0,0,0,6.211,1.922,0.0,3H2.0,0,0; 93P 50 106,1,3,0.0,4.894,2.000,4.988,2.000,6.024,2.000,0,0; 95P 51 218,93,95,0,0; 97P 52 212,1,7,1.248,0.156,1,1.571,0.,0,0,6.23,-0.078,0.0,7HDATUM B,0, 99P 53 0; 99P 54 106,1,3,0.0,5.094,0.0,5.188,0.0,6.042,0.0,0,0; 101P 55 218,99,101,0,0; 103P 56 212,1,7,1.232,0.156,1,1.571,1.571,0,0,5.078,4.193,0.,7HDATUM A, 105P 57 0,0; 105P 58 106,1,3,0.0,5.000,3.094,5.000,3.187,5.000,4.006,0,0; 107P 59 218,105,107,0,0; 109P 60 212,2,4,0.35,0.100,1,1.571,0.,0,0,4.029,2.611,0.,4H.2 R,5,0.500, 111P 61 0.100,1,1.571,0.0,0,0,4.029,2.461,0.0,5H(TYP),0,0; 111P 62 214,2,0.150,0.050,0.0,4.877,3.185,4.862,2.511,4.562,2.511,0,0; 113P 63 222,111,113,4.800,3.000,0,0; 115P 64 212,1,3,0.240,0.100,1,1.571,0.0,0,0,1.559,0.602,0.0,3H1.0,0,0; 117P 65 214,1,0.150,0.050,0.0,1.663,0.0,1.663,0.538,0,0; 119P 66 214,1,0.150,0.050,0.0,1.663,1.000,1.663,0.766,0,0; 121P 67 106,1,3,0.0,0.200,0.0,0.294,0.0,1.788,0.0,0,0; 123P 68 106,1,3,0.0,1.000,1.000,1.094,1.000,1.788,1.000,0,0; 125P 69 216,117,119,121,123,125,0,0; 127P 70 212,1,3,0.240,0.100,1,1.571,0.0,0,0,0.537,0.275,0.0,3H1.0,0,0; 129P 71 214,1,0.150,0.050,0.0,1.000,0.325,0.809,0.325,0,0; 131P 72 214,1,0.150,0.050,0.0,0.0,0.325,0.473,0.325,0,0; 133P 73 106,1,3,0.0,1.000,1.000,1.000,0.906,1.000,0.200,0,0; 135P 74 106,1,3,0.0,0.0,0.012,0.0,0.106,0.0,0.200,0,0; 137P 75 216,129,131,133,135,137,0,0; 139P 76 212,1,3,0.240,0.100,1,1.571,0.0,0,0,0.470,1.289,0.0,3H1.0,0,0; 141P 77 214,1,0.150,0.050,0.0,0.971,1.736,0.688,1.453,0,0; 143P 78 214,1,0.150,0.050,0.0,0.264,1.029,0.459,1.225,0,0; 145P 79 106,1,3,0.0,1.354,1.354,1.287,1.420,0.882,1.825,0,0; 147P 80 106,1,3,0.0,0.646,0.646,0.580,0.713,0.175,1.118,0,0; 149P 81 216,141,143,145,147,149,0,0; 151P 82 212,1,2,0.170,0.100,1,1.571,0.0,0,0,1.631,1.622,0.0,2H.5,0,0; 153P 83 214,1,0.150,0.050,0.0,1.863,1.509,2.146,1.226,0,0; 155P 84 214,1,0.150,0.050,0.0,1.509,1.863,1.226,2.146,0,0; 157P 85 106,1,3,0.0,1.177,0.823,1.243,0.890,1.951,1.598,0,0; 159P 86 106,1,3,0.0,0.823,1.177,0.890,1.243,1.598,1.951,0,0; 161P 87 216,153,155,157,159,161,0,0; 163P 88 110,0.500,0.500,0.0,1.500,1.500,0.0,0,0; 165P 89 110,1.225,0.775,0.0,0.775,1.225,0.0,0,0; 167P 90 212,1,2,0.220,0.100,1,1.571,0.0,0,0,2.566,0.786,0.0,2H45,0,0; 169P 91 214,1,0.150,0.050,0.0,2.847,0.0,2.754,0.722,0,0; 171P 92 214,1,0.150,0.050,0.0,2.013,2.013,2.683,0.951,0,0; 173P 93 435 A. MECHANICAL PART EXAMPLE 106,1,3,0.0,4.988,0.0,4.894,0.0,2.972,0.0,0,0; 175P 94 106,1,3,0.0,2.000,2.000,2.066,2.066,2.101,2.101,0,0; 177P 95 202,169,175,177,0.0,0.0,2.847,171,173,0,0; 179P 96 S 7G 3D 180P 96 T 1 436 A. DRAWING AND VIEW EXAMPLE Figure A3. Drawing and View Example 437 A. DRAWING AND VIEW EXAMPLE Example 3 Drawing and View Example Test file of model with DRAWING (404) and VIEW (410) entities S 1 S 2 This file demonstrates annotation attached to the VIEWS, S 3 i.e., the dimensions entities are flagged as INDEPENDENT, S 4 and their DE field 6 points to a VIEW entity. The coordinates S 5 of the dimensions are in MODEL space, and they have a S 6 transformation matrix which is the inverse of the VIEW matrix. S 7 S 8 A companion file demonstrates annotation attached to the DRAWING, S 9 i.e., the dimension entities are flagged as DEPENDENT, S 10 and they are pointed to by the PD of the DRAWING entity. The S 11 coordinates of the dimensions are in DRAWING space. S 12 S 13 1H,,1H;,8HVIEWDWG2,12HVIEWDWG2.IGS,13H,13H, G 1 32,38,6,38,15,8HVIEWDWG2,1.,1,2HIN,8,0.016,13H900729.231904,0.0001,71., G 2 25HIGES RFC Review Committee,8HIPO/NIST,6,0; G 3 406 1 0 0 0 0 0 0 10300D 1 406 0 0 1 15 0D 2 124 2 0 0 0 0 0 0 10300D 3 124 0 0 2 0 0D 4 108 4 0 0 0 0 0 0 10201D 5 108 0 0 2 0 0D 6 108 6 0 0 0 0 0 0 10201D 7 108 0 0 2 0 0D 8 108 8 0 0 0 0 0 0 10201D 9 108 0 0 2 0 0D 10 108 10 0 0 0 0 0 0 10201D 11 108 0 0 2 0 0D 12 410 12 0 0 0 0 3 0 20201D 13 410 0 0 1 0 0D 14 406 13 0 0 0 0 0 0 10300D 15 406 0 0 1 15 0D 16 124 14 0 0 0 0 0 0 10300D 17 124 0 0 1 0 0D 18 108 15 0 0 0 0 0 0 10201D 19 108 0 0 1 0 0D 20 108 16 0 0 0 0 0 0 10201D 21 108 0 0 1 0 0D 22 108 17 0 0 0 0 0 0 10201D 23 108 0 0 1 0 0D 24 108 18 0 0 0 0 0 0 10201D 25 108 0 0 1 0 0D 26 410 19 0 0 0 0 17 0 20201D 27 410 0 0 1 0 0D 28 406 20 0 0 0 0 0 0 10300D 29 406 0 0 1 15 0D 30 124 21 0 0 0 0 0 0 10300D 31 438 A. DRAWING AND VIEW EXAMPLE 124 0 0 1 0 0D 32 108 22 0 0 0 0 0 0 10201D 33 108 0 0 1 0 0D 34 108 23 0 0 0 0 0 0 10201D 35 108 0 0 1 0 0D 36 108 24 0 0 0 0 0 0 10201D 37 108 0 0 1 0 0D 38 108 25 0 0 0 0 0 0 10201D 39 108 0 0 1 0 0D 40 410 26 0 0 0 0 31 0 20201D 41 410 0 0 1 0 0D 42 406 27 0 0 0 0 0 0 10300D 43 406 0 0 1 15 0D 44 108 28 0 0 0 0 0 0 10201D 45 108 0 0 1 0 0D 46 108 29 0 0 0 0 0 0 10201D 47 108 0 0 1 0 0D 48 108 30 0 0 0 0 0 0 10201D 49 108 0 0 1 0 0D 50 108 31 0 0 0 0 0 0 10201D 51 108 0 0 1 0 0D 52 410 32 0 0 0 0 0 0 20201D 53 410 0 0 1 0 0D 54 110 33 0 1 2 0 0 0 10100D 55 110 1 4 1 0 0D 56 110 34 0 1 2 0 0 0 10100D 57 110 1 4 1 0 0D 58 110 35 0 1 2 0 0 0 10100D 59 110 1 4 1 0 0D 60 110 36 0 1 2 0 0 0 10100D 61 110 1 4 1 0 0D 62 110 37 0 1 2 0 0 0 10100D 63 110 1 4 1 0 0D 64 110 38 0 1 4 0 0 0 10100D 65 110 1 4 1 0 0D 66 110 39 0 1 4 0 0 0 10100D 67 110 1 4 1 0 0D 68 110 40 0 1 4 0 0 0 10100D 69 110 1 4 1 0 0D 70 110 41 0 1 4 0 0 0 10100D 71 110 1 4 1 0 0D 72 406 42 0 1 0 0 0 0 10300D 73 406 0 0 1 15 0D 74 404 43 0 1 0 0 0 0 201D 75 404 0 0 2 0 0D 76 110 45 0 1 2 0 0 0 0D 77 110 1 2 1 0 0D 78 439 A. DRAWING AND VIEW EXAMPLE 110 46 0 1 2 0 0 0 0D 79 110 1 2 1 0 0D 80 110 47 0 1 2 0 0 0 0D 81 110 1 2 1 0 0D 82 110 48 0 1 2 0 0 0 0D 83 110 1 2 1 0 0D 84 110 49 0 1 2 0 0 0 0D 85 110 1 2 1 0 0D 86 110 50 0 1 2 0 0 0 0D 87 110 1 2 1 0 0D 88 110 51 0 1 2 0 0 0 0D 89 110 1 2 1 0 0D 90 110 52 0 1 2 0 0 0 0D 91 110 1 2 1 0 0D 92 110 53 0 1 2 0 0 0 0D 93 110 1 2 1 0 0D 94 110 54 0 1 2 0 0 0 0D 95 110 1 2 1 0 0D 96 110 55 0 1 2 0 0 0 0D 97 110 1 2 1 0 0D 98 110 56 0 1 2 0 0 0 0D 99 110 1 2 1 0 0D 100 110 57 0 1 2 0 0 0 0D 101 110 1 2 1 0 0D 102 110 58 0 1 2 0 0 0 0D 103 110 1 2 1 0 0D 104 110 59 0 1 2 0 0 0 0D 105 110 1 2 1 0 0D 106 110 60 0 1 2 0 0 0 0D 107 110 1 2 1 0 0D 108 110 61 0 1 2 0 0 0 0D 109 110 1 2 1 0 0D 110 110 62 0 1 2 0 0 0 0D 111 110 1 2 1 0 0D 112 106 63 0 1 2 53 0 0 10101D 113 106 1 3 1 40 0D 114 214 64 0 1 2 53 0 0 10101D 115 214 1 3 1 2 0D 116 212 65 0 1 2 53 0 0 10101D 117 212 1 3 1 0 0D 118 214 66 0 1 2 53 0 0 10101D 119 214 1 3 1 2 0D 120 106 67 0 1 2 53 0 0 10101D 121 106 1 3 1 40 0D 122 216 68 0 1 2 53 0 0 100D 123 216 1 3 1 0 0D 124 106 69 0 1 2 27 0 0 10101D 125 440 A. DRAWING AND VIEW EXAMPLE 106 1 3 1 40 0D 126 214 70 0 1 2 27 0 0 10101D 127 214 1 3 1 2 0D 128 212 71 0 1 2 27 0 0 10101D 129 212 1 3 1 0 0D 130 214 72 0 1 2 27 0 0 10101D 131 214 1 3 1 2 0D 132 106 73 0 1 2 27 0 0 10101D 133 106 1 3 1 40 0D 134 216 74 0 1 2 27 211 0 100D 135 216 1 3 1 0 0D 136 106 75 0 1 2 41 0 0 10101D 137 106 1 3 1 40 0D 138 214 76 0 1 2 41 0 0 10101D 139 214 1 3 1 2 0D 140 212 77 0 1 2 41 0 0 10101D 141 212 1 3 1 0 0D 142 214 78 0 1 2 41 0 0 10101D 143 214 1 3 1 2 0D 144 106 79 0 1 2 41 0 0 10101D 145 106 1 3 1 40 0D 146 216 80 0 1 2 41 213 0 100D 147 216 1 3 1 0 0D 148 106 81 0 1 2 41 0 0 10101D 149 106 1 3 1 40 0D 150 214 82 0 1 2 41 0 0 10101D 151 214 1 3 1 2 0D 152 212 83 0 1 2 41 0 0 10101D 153 212 1 3 1 0 0D 154 214 84 0 1 2 41 0 0 10101D 155 214 1 3 1 2 0D 156 106 85 0 1 2 41 0 0 10101D 157 106 1 3 1 40 0D 158 216 86 0 1 2 41 213 0 100D 159 216 1 3 1 0 0D 160 106 87 0 1 2 53 0 0 10101D 161 106 1 3 1 40 0D 162 214 88 0 1 2 53 0 0 10101D 163 214 1 3 1 2 0D 164 212 89 0 1 2 53 0 0 10101D 165 212 1 3 1 0 0D 166 214 90 0 1 2 53 0 0 10101D 167 214 1 3 1 2 0D 168 106 91 0 1 2 53 0 0 10101D 169 106 1 3 1 40 0D 170 216 92 0 1 2 53 0 0 100D 171 216 1 3 1 0 0D 172 441 A. DRAWING AND VIEW EXAMPLE 106 93 0 1 2 41 0 0 10101D 173 106 1 3 1 40 0D 174 214 94 0 1 2 41 0 0 10101D 175 214 1 3 1 2 0D 176 212 95 0 1 2 41 0 0 10101D 177 212 1 3 1 0 0D 178 214 96 0 1 2 41 0 0 10101D 179 214 1 3 1 2 0D 180 106 97 0 1 2 41 0 0 10101D 181 106 1 3 1 40 0D 182 216 98 0 1 2 41 213 0 100D 183 216 1 3 1 0 0D 184 106 99 0 1 2 27 0 0 10101D 185 106 1 3 1 40 0D 186 214 100 0 1 2 27 0 0 10101D 187 214 1 3 1 2 0D 188 212 101 0 1 2 27 0 0 10101D 189 212 1 3 1 0 0D 190 214 102 0 1 2 27 0 0 10101D 191 214 1 3 1 2 0D 192 106 103 0 1 2 27 0 0 10101D 193 106 1 3 1 40 0D 194 216 104 0 1 2 27 211 0 100D 195 216 1 3 1 0 0D 196 106 105 0 1 2 27 0 0 10101D 197 106 1 3 1 40 0D 198 214 106 0 1 2 27 0 0 10101D 199 214 1 3 1 2 0D 200 212 107 0 1 2 27 0 0 10101D 201 212 1 3 1 0 0D 202 214 108 0 1 2 27 0 0 10101D 203 214 1 3 1 2 0D 204 106 109 0 1 2 27 0 0 10101D 205 106 1 3 1 40 0D 206 216 110 0 1 2 27 211 0 100D 207 216 1 3 1 0 0D 208 212 111 0 1 2 0 0 0 10101D 209 212 1 3 1 0 0D 210 124 112 0 0 0 0 0 0 10300D 211 124 0 0 1 0 0D 212 124 113 0 0 0 0 0 0 10300D 213 124 0 0 1 0 0D 214 406 114 0 1 0 0 0 0 10300D 215 406 0 0 1 16 0D 216 406 115 0 1 0 0 0 0 10300D 217 406 0 0 1 17 0D 218 406,1,7HCLIPPED; 1P 1 442 A. DRAWING AND VIEW EXAMPLE 124,-0.67499,-0.171,0.71774,0.,-0.24401,0.96977,0.00157,0., 3P 2 -0.69631,-0.17408,-0.69631,0.; 3P 3 108,0.67499,0.171,-0.71774,5.0055,0,6.390347,2.455541,-0.379235, 5P 4 0.; 5P 5 108,-0.24401,0.96977,0.00157,3.55308,0,3.025032,4.420965, 7P 6 2.494731,0.; 7P 7 108,-0.67499,-0.171,0.71774,2.99094,0,0.992841,1.088152, 9P 8 5.360119,0.; 9P 9 108,0.24401,-0.96977,-0.00157,1.9103,0,4.358156,-0.877273, 11P 10 2.486153,0.; 11P 11 410,4,1.,5,7,9,11,0,0,0,1,1; 13P 12 406,1,5HRIGHT; 15P 13 124,0.,0.,-1.,0.,0.,1.,0.,0.,1.,0.,0.,0.; 17P 14 108,0.,0.,1.,36.,0,0.,0.,36.,0.; 19P 15 108,0.,1.,0.,24.59627,0,0.,24.59627,0.,0.; 21P 16 108,0.,0.,-1.,36.,0,0.,0.,-36.,0.; 23P 17 108,0.,-1.,0.,24.59627,0,0.,-24.59627,0.,0.; 25P 18 410,3,1.,19,21,23,25,0,0,0,1,15; 27P 19 406,1,3HTOP; 29P 20 124,1.,0.,0.,0.,0.,0.,-1.,0.,0.,1.,0.,0.; 31P 21 108,-1.,0.,0.,36.,0,-36.,0.,0.,0.; 33P 22 108,0.,0.,-1.,24.59627,0,0.,0.,-24.59627,0.; 35P 23 108,1.,0.,0.,36.,0,36.,0.,0.,0.; 37P 24 108,0.,0.,1.,24.59627,0,0.,0.,24.59627,0.; 39P 25 410,2,1.,33,35,37,39,0,0,0,1,29; 41P 26 406,1,5HFRONT; 43P 27 108,-1.,0.,0.,36.,0,-36.,0.,0.,0.; 45P 28 108,0.,1.,0.,24.59627,0,0.,24.59627,0.,0.; 47P 29 108,1.,0.,0.,36.,0,36.,0.,0.,0.; 49P 30 108,0.,-1.,0.,24.59627,0,0.,-24.59627,0.,0.; 51P 31 410,1,1.,45,47,49,51,0,0,0,1,43; 53P 32 110,67.,0.,0.,67.,2.,0.; 55P 33 110,60.,4.,0.,60.,2.,0.; 57P 34 110,57.,4.,0.,57.,0.,0.; 59P 35 110,70.,4.,0.,57.,4.,0.; 61P 36 110,70.,2.,0.,57.,2.,0.; 63P 37 110,0.,40.,0.,0.,0.,0.; 65P 38 110,70.,40.,0.,0.,40.,0.; 67P 39 110,70.,0.,0.,70.,40.,0.; 69P 40 110,0.,0.,0.,70.,0.,0.; 71P 41 406,1,7HDRAWING; 73P 42 404,4,13,51.,29.,27,46.,8.,41,7.,24.,53,7.,8.,10,55,57,59,61,63, 75P 43 65,67,69,71,209,0,3,73,215,217; 75P 44 110,0.,9.,0.,0.,9.,-9.; 77P 45 110,2.5,9.,0.,2.5,9.,-9.; 79P 46 110,2.5,2.5,0.,2.5,2.5,-9.; 81P 47 110,20.,2.5,0.,20.,2.5,-9.; 83P 48 443 A. DRAWING AND VIEW EXAMPLE 110,20.,0.,0.,20.,0.,-9.; 85P 49 110,0.,0.,0.,0.,0.,-9.; 87P 50 110,0.,9.,-9.,0.,0.,-9.; 89P 51 110,2.5,9.,-9.,0.,9.,-9.; 91P 52 110,2.5,2.5,-9.,2.5,9.,-9.; 93P 53 110,20.,2.5,-9.,2.5,2.5,-9.; 95P 54 110,20.,0.,-9.,20.,2.5,-9.; 97P 55 110,0.,0.,-9.,20.,0.,-9.; 99P 56 110,0.,9.,0.,0.,0.,0.; 101P 57 110,2.5,9.,0.,0.,9.,0.; 103P 58 110,2.5,2.5,0.,2.5,9.,0.; 105P 59 110,20.,2.5,0.,2.5,2.5,0.; 107P 60 110,20.,0.,0.,20.,2.5,0.; 109P 61 110,0.,0.,0.,20.,0.,0.; 111P 62 106,1,3,0.,0.,0.,0.,-0.5,0.,-4.; 113P 63 214,1,1.,0.5,0.,0.,-3.5,7.625,-3.5; 115P 64 212,1,5,3.75,1.,1,1.5707963267949,0.,0,0,8.,-4.,0.,5H20.00; 117P 65 214,1,1.,0.5,0.,20.,-3.5,12.125,-3.5; 119P 66 106,1,3,0.,20.,0.,20.,-0.5,20.,-4.; 121P 67 216,117,115,119,113,121; 123P 68 106,1,3,0.,0.,0.,0.,-0.5,0.,-3.5; 125P 69 214,1,1.,0.5,0.,0.,-3.,2.125,-3.; 127P 70 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,2.5,-3.5,0.,4H9.00; 129P 71 214,1,1.,0.5,0.,9.,-3.,5.875,-3.; 131P 72 106,1,3,0.,9.,0.,9.,-0.5,9.,-3.5; 133P 73 216,129,127,131,125,133; 135P 74 106,1,3,0.,2.5,0.,2.5,-0.5,2.5,-4.; 137P 75 214,1,1.,0.5,0.,2.5,-3.5,8.625,-3.5; 139P 76 212,1,5,3.75,1.,1,1.5707963267949,0.,0,0,9.,-4.,0.,5H17.50; 141P 77 214,1,1.,0.5,0.,20.,-3.5,13.125,-3.5; 143P 78 106,1,3,0.,20.,0.,20.,-0.5,20.,-4.; 145P 79 216,141,139,143,137,145; 147P 80 106,1,3,0.,0.,9.,0.,9.5,0.,12.5; 149P 81 214,1,1.,0.5,0.,0.,12.,-3.,12.; 151P 82 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,6.,11.5,0.,4H2.50; 153P 83 214,1,1.,0.5,0.,2.5,12.,5.5,12.; 155P 84 106,1,3,0.,2.5,9.,2.5,9.5,2.5,12.5; 157P 85 216,153,151,155,149,157; 159P 86 106,1,3,0.,0.,0.,-0.5,0.,-3.5,0.; 161P 87 214,1,1.,0.5,0.,-3.,0.,-3.,3.5; 163P 88 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,-4.5,4.,0.,4H9.00; 165P 89 214,1,1.,0.5,0.,-3.,9.,-3.,5.5; 167P 90 106,1,3,0.,0.,9.,-0.5,9.,-3.5,9.; 169P 91 216,165,163,167,161,169; 171P 92 106,1,3,0.,0.,0.,-0.5,0.,-3.5,0.; 173P 93 214,1,1.,0.5,0.,-3.,0.,-3.,3.5; 175P 94 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,-4.5,4.,0.,4H9.00; 177P 95 444 A. DRAWING AND VIEW EXAMPLE 214,1,1.,0.5,0.,-3.,9.,-3.,5.5; 179P 96 106,1,3,0.,0.,9.,-0.5,9.,-3.5,9.; 181P 97 216,177,175,179,173,181; 183P 98 106,1,3,0.,0.,0.,-0.5,0.,-3.,0.; 185P 99 214,1,1.,0.5,0.,-2.5,0.,-2.5,-2.; 187P 100 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,-4.,5.,0.,4H2.50; 189P 101 214,1,1.,0.5,0.,-2.5,2.5,-2.5,4.5; 191P 102 106,1,3,0.,0.,2.5,-0.5,2.5,-3.,2.5; 193P 103 216,189,187,191,185,193; 195P 104 106,1,3,0.,9.,2.5,9.5,2.5,13.,2.5; 197P 105 214,1,1.,0.5,0.,12.5,2.5,12.5,4.5; 199P 106 212,1,4,3.,1.,1,1.5707963267949,0.,0,0,11.,5.,0.,4H6.50; 201P 107 214,1,1.,0.5,0.,12.5,9.,12.5,6.5; 203P 108 106,1,3,0.,9.,9.,9.5,9.,13.,9.; 205P 109 216,201,199,203,197,205; 207P 110 212,1,7,8.25,1.,1,1.5707963267949,0.,0,0,58.,0.5,0.,7HIN VIEW; 209P 111 124,0.,0.,1.,0.,0.,1.,0.,0.,-1.,0.,0.,0.; 211P 112 124,1.,0.,0.,0.,0.,0.,1.,0.,0.,-1.,0.,0.; 213P 113 406,2,70.,40.; 215P 114 406,2,1,2HIN; 217P 115 S 13G 3D 218P 115 T 1 445 A. DRAWING AND VIEW EXAMPLE 446 Appendix B. Spline Curves and Surfaces B.1 Introduction Chapter 4 of this Specification includes four different types of spline representations: 1. A parametric piecewise cubic polynomial curve, 2. A rational B-spline curve, 3. A grid of bicubic patches (for surfaces), and 4. A rational B-spline surface. Most of the spline types used in CAD/CAM systems can be mapped into these representations without change in shape. Spline types supported in Chapter 4 include parametric cubics, piecewise linear, Wilson-Fowler, modified Wilson-Fowler, rational and nonrational B-splines, and rational and nonrational Cartesian product B-spline surfaces. Spline types not supported include splines under tension and extended Coons patches. Software to convert between parametric spline curves or surfaces and the corresponding rational B-spline curves or surfaces is available from the IGES/PDES Administration office at the National Institute of Standards and Technology. Materials provided include Pascal source code and accom- panying documentation. B.2 Spline Functions In Section 4.12, spline curves are represented by a number of cubic spline functions, one for each of the X; Y; Z coordinates. Each cubic spline function S(u) is defined by: 1. N : The number of segments, 2. T (1); . .;.T (N + 1): The endpoints and the breakpoints separating the cubic polynomial seg- ments, 3. A(i); B(i); C(i); D(i); i = 1; . .;.N : The coefficients of the polynomials representing the spline in each of the N segments, 4. CTYPE: The spline type (1=linear, 2=quadratic, 3=cubic, 4=Wilson-Fowler, 5=Modified Wilson-Fowler, 6=B-spline) of the originating system. See Section 4.12. 5. H: Degree of continuity. See Section 4.12. 447 B.3 SPLINE CURVES To evaluate the spline at a point "u", first determine the segment containing "u", i.e., the segment "i" such that T (i) u T (i+1); then evaluate the cubic polynomial in that segment, i.e., compute, S(u) = A(i) + B(i) * (uu) + C(i) * (uu)2 + D(i) * (uu)3 where uu = u - T (i). The polynomial is written in terms of the relative displacement uu (rather than u) so that the values of the spline at the breakpoints can be read directly out of the representation (i.e., S(T (i)) = A(i); i = 1; . .;.N , and S(T (N + 1)) = T P 0). Computations using the relative displacement also have less floating-point round-off error. This particular "piecewise polynomial" form is only one of many used to represent the spline segments in CAD/CAM systems. Other representations employed include: 1. End points E1; E2 and end slopes S1; S2: The spline can be evaluated using the "Hermite" basis (see [DEBO78], p. 59). 2. Values at four points: The spline value can be computed from the Lagrange or Newton inter- polation formulas (see [DEBO78]). 3. End points and "control" points: There are a number of schemes for computing splines from control points which will not be described here. DeBoor [DEBO78] gives techniques for conversion between these representations. Splines can also be represented as a linear combination of the B-spline basis functions. In CAD/CAM systems, B-splines have been used directly in curve fitting (e.g., the B-spline Bezier polygon (see [GORD74])) and indirectly in various spline calculations (e.g., computing a cubic spline interpo- late). For every set of breakpoints T (1); . .;.T (N + 1) and degree of continuity H, a set of B-spline functions B(1; u), B(2; u); . .;.B(n*; u) can be constructed (see [DEBO78]). Then, for any piece- wise polynomial S(u) with these breakpoints and continuity there is a set of B-spline coefficients a(1); . .;.a(n*) such that S(u) can be represented as a linear combination of these B-splines, S(u) = a(1) * B(1; u) + a(2) * B(2; u) + . . .+ a(n*) * B(n*; u) where n* = (N - 1) * (3 - H) + 4. B-splines can be computed from piecewise polynomials and vice versa (see [DEBO78], p. 116). B.3 Spline Curves The comments in this section pertain primarily to Section 4.12. The most common approach to curve fitting is to parameterize the curves, i.e., to represent each curve as either two or three spline functions (one for each coordinate), X(u) = Sx(u); Y (u) = Sy(u); and Z(u) = Sz(u) which sketch out the curve as the parameter u varies from T (1) to T (N + 1). 448 B.4 RATIONAL B-SPLINE CURVES All of the spline function representations of the previous section can be generalized to parametric curves, and the algorithms for converting spline curves from one representation to the other follow easily from multiple applications of the corresponding function conversion algorithms. Wilson-Fowler Curves: In the early sixties, the Wilson-Fowler spline (a special case of parametric cubics) was developed for curve fitting (see [IITR68]). It is still used in many turnkey drafting systems. In the Wilson-Fowler representation, each spline segment is defined in a separate coordinate system whose X-axis begins at one endpoint of the segment and passes through the other. Each spline segment is then defined by a cubic spline function Swf(x) and the coordinates of the two endpoints. These Wilson-Fowler splines can be converted to splines defined in Section 4.12 by rotating the parametric spline (u,Swf(u)) back into the current coordinate system; however, most types of splines defined in Section 4.12 cannot be converted to Wilson-Fowler splines. B.4 Rational B-spline Curves The comments in this section pertain primarily to Section 4.21. A rational B-spline curve is expressed parametrically in the form, P K W (i)P (i)bi(t) G(t) = ___i=0________________PK i=0 W (i)bi(t) where the notation is interpreted as follows: The W (i) are the weights (positive real numbers). The P (i) are the control points (points in R3). The bi are the B-spline basis functions. These are defined as soon as their degree, M , and underlying knot sequence, T , are specified. This is done as follows: Let N = K - M + 1. Then, the knot sequence consists of the nondecreasing set of real numbers; T (-M ); . .;.T (0); . .;.T (N ); . .;.T (N + M ). The curve itself is parameterized for V (0) t V (1) where T (0) V (0) < V (1) T (N ). The B-spline basis functions bi are each non-negative piecewise polynomials of degree M . The function bi is supported by the interval [T (i - M ); T (i + 1)]. Between any two adjacent knot values T (j), T (j + 1) the function can be expressed as a single polynomial of degree M . For any parameter value t between T (0) and T (N ), the basis functions satisfy the identity XK bi(t) = 1: i=0 As the weights are all positive, the curve G(t) is contained within the convex hull of its control points. 449 B.5 SPLINE SURFACES There are a number of ways to precisely define the B-spline basis functions. A recursive approach proceeds as follows. Let N (t|ti-M ; . .;.ti+1) denote the B-spline basis function of degree M supported by the interval [ti-M ; ti+1]. With this notation, the degree 0 functions are simply characteristic functions of a half-open interval. 1 if a t < b N (t| a; b) = 0 otherwise The degree k functions are defined in terms of those of degree k - 1. N (t|s0; . .;.sk) = (t_-_s0)_N_(t|s0;_._.;.sk-1_)s+ (sk_-_t)N_(t|s1;_._.;.sk)_ k-1 - s0 sk - s1 Since some of the denominators will be 0 in the case of multiple knots, the convention 0/0 = 0 is adopted in the above definition. Rational Bezier curves can be expressed exactly as rational B-spline curves. An unpublished paper by Fuhr on this subject is available from the IGES/PDES Administration Office at the National Institute of Standards and Technology. ECO522 For further information, see [FARI88]. Note that the indexing of the knot vectors is done differently. B.5 Spline Surfaces The spline surface defined in Section 4.13 is the analog of the spline curve defined in Section 4.12, i.e., it is also pieced together out of other primitive functions. The surface is a grid of parametric bicubic patches defined by: 1. M : The number of grid lines in u, 2. T U (1); . .;.T U (M + 1): The breakpoints in u (u values of grid lines), 3. N : The number of grid lines in v, 4. T V (1); . .;.T V (N + 1): The breakpoints in v (v values of grid lines), 5. Ax(i; j); Bx(i; j); . .;.Ay(i; j); . .;.Az(i; j); . .;.fori = 1; . .;.M ; j = 1; . .;.N : The M * N sets of 3 * 16 coefficients defining the bicubic polynomial for each of the three coordinates of the patch, 6. CTYPE: The spline type. (1=linear, 2=quadratic, 3=cubic, 4=Wilson- Fowler, 5=Modified Wilson-Fowler, 6 = B-spline), and 7. PTYPE: The patch type. (1=Cartesian product, 0=unspecified). 450 B.6 RATIONAL B-SPLINE SURFACES To evaluate the spline at a point "u; v", first determine the patch containing the point "u; v" in the parameter grid, i.e., the patch "i; j" such that T U (i) u T U (i + 1) and T V (j) v T V (j + 1), then evaluate the bicubic polynomial in that patch, i.e., compute: X(u; v) = Ax(i; j) * vv0 * uu0 + Bx(i; j) * vv0 * uu1 + Cx(i; j) * vv0 * uu2 + Dx(i; j) * vv0 * uu3 +Ex(i; j) * vv1 * uu0 + F x(i; j) * vv1 * uu1 + Gx(i; j) * vv1 * uu2 + Hx(i; j) * vv1 * uu3 +Kx(i; j) * vv2 * uu0 + Lx(i; j) * vv2 * uu1 + M x(i; j) * vv2 * uu2 + N x(i; j) * vv2 * uu3 +P x(i; j) * vv3 * uu0 + Qx(i; j) * vv3 * uu1 + Rx(i; j) * vv3 * uu2 + Sx(i; j) * vv3 * uu3 Y (u; v) = Ay(i; j) . . . Z(u; v) = Az(i; j) . . . where uu = u - T U (i) and vv = v - T V (j). The patches in the spline surface are equivalent to the bicubic surface patch (see [ROGE76], p. 170) for the conversion details). The parameters of the bicubic surface patch are given as the corner points, corner slopes, and twist vectors (similar in spirit to the point/slope representation for curves). However, because the Specification spline is more general than splines found in many CAD/CAM systems (i.e., the APT Wilson-Fowler spline), shape-preserving transformations out of the Spec- ification spline format may not be possible. Difficulties encountered include restrictions such as uniform breakpoint spacing and smooth second derivatives. In these cases, the conversion must be accomplished by an interpolation or smoothing process. For further information, see [FARI88]. Note that the indexing of the knot vectors is done differently. ECO522 B.6 Rational B-spline Surfaces The comments in this section pertain primarily to Section 4.22. A rational B-spline surface is expressed parametrically in the form, P K1 P K2 W (i; j)P (i; j)bi(s)bj(t) G(s; t) = ___i=0____j=0_________________________PK1PK2 i=0 j=0 W (i; j)bi(s)bj(t) where the notation is analogous to that used for rational B-spline curves. The W (i; j) are the weights (positive real numbers). The P (i; j) are the control points (points in R3). The bi are the B-spline basis functions of degree M 1 determined by the knot sequence S(-M 1), ..., S(N 1 + M 1). The bj are the B-spline basis functions of degree M 2 determined by the knot sequence T (-M 2), ..., T (N 2 + M 2). Here, N 1 = K1 - M 1 + 1 and N 2 = K2 - M 2 + 1. The surface itself is parameterized for U (0) s U (1) and for V (0) t V (1) where S(0) U (0) < U (1) S(N 1) and T (0) V (0) < V (1) T (N 2). Rational Bezier surfaces can be expressed exactly as rational B-spline surfaces. An unpublished paper by Fuhr on this subject is available from the IGES/PDES Administration Office at the National Institute of Standards and Technology. 451 B.6 RATIONAL B-SPLINE SURFACES If the surface is periodic with respect to the first parametric variable, set PROP4 to 1; otherwise set PROP4 to 0. If the surface is periodic with respect to the second parametric variable, set PROP5 to 1; otherwise set PROP5 to 0. The periodic flags are to be interpreted as purely informational. The surfaces which are flagged to be periodic are to be evaluated exactly the same as in the nonperiodic case. Software to convert between parametric spline curves or surfaces and the corresponding rational B-spline curves or surfaces is available from the IGES/PDES Administration Office at the National Institute of Standards and Technology. Materials provided include Pascal source code and accom- panying documentation. 452 Appendix C. Conic Arcs Conic arcs as specified are extremely sensitive to the data in two distinct ways: Accuracy. It is numerically sensitive; small changes in the coefficients can cause large changes in the locations of the points satisfying the conic equation. Stability. The determination of the conic type depends upon whether certain invariants are positive, zero or negative. Working in floating point arithmetic, a machine value of 0.0 is unlikely to be encountered. Furthermore, small changes in coefficient values can easily result in positive values when negative ones are intended and conversely. It is assumed that data are represented by a Conic Arc Entity with the intent of preserving geometric properties (major and minor semi-axes, asymptotes, directrices, etc.) in addition to describing the points on the curve. If the geometric properties are desired, the Conic Arc Entity (Type 104) should be used as described below. This method primarily addresses the stability problem, though the accuracy of the conic should improve because the range of coefficient values will decrease. While the geometric properties are not explicitly defined in this representation, they can be obtained from it in a direct and arithmetically stable manner. If both the sending and intended receiving system are known to use the A-F form of the Conic Arc Entity in their own databases, the preprocessor may put the data into the unchanged form. This minimizes the loss of information caused by truncation and roundoff errors as no changes are made to the data. The stability problem is presumably not of concern in this case. The following are suggested sets of values for the cases of an ellipse, a hyperbola, and a parabola: _____________________________________________________ |______________________Ellipse______________________|_ | 2 | | A = AXISY2 B = 0 | | C = AXISX D = 0 | | E = 0 F = -A * C | |___________________________________________________|_ | where AXISY and AXISX are the lengths | | | | of the major and minor semi-axes (not nec- | | essarily in order). | |____________________________________________________| 453 C. CONIC ARCS ______________________________________________________________________________ |_________________________________Hyperbola_________________________________|_ | | | A = -AXISY 2 (or +AXISY 2) B = 0 | | | | C = +AXISX2 (or -AXISX2 , if A > 0) D = 0 | | | | E = 0 F = -A * C. | |_____________________________________________________________________________| | where AXISY and AXISX are the lengths of the major and minor | | semi-axes (not necessarily in order). | |_____________________________________________________________________________ | ______________________________________________________________________________ |__________________________________Parabola__________________________________|_ | | | A = 0 (or 1 ) B = 0 | | | | C = 1 (or 0, if A = 1) D = 4 * DIST (or | | 0, if A=1) | | | | E = 0 (or 4 * DIST, if A=1) F = 0 | | | |_____________________________________________________________________________| |__where_DIST_is_the_distance_of_the_vertex_from_the_focus.___________________ | Preprocessor Conic Handling The conic arc must be put into standard form, parallel to the X or Y axis and centered about the origin. A Transformation Matrix Entity (Type 124) must be used to move the conic arc into its desired position in space. In this form, the coefficients in the format that should be 0.0 will be exactly so. In particular, for the ellipse and hyperbola B, D, and E must be 0.0, and for the parabola B and F and either A and E or C and D must be 0.0. Determination of the conic type from the equations becomes straight forward for the postprocessor. For further mathematical details, see [THOM60]. 454 Appendix D. Color-Space Mappings It is often more convenient to operate in some color space other than RGB. The relationship between RGB (Red, Green, Blue) and CMY (Cyan, Magenta, Yellow) is given by: R = 100.0 - C R = red C = cyan G = 100.0 - M where: G = green M = magenta B = 100.0 - Y B = blue Y = yellow The HSL (Hue, Saturation, Lightness) color space can be defined in terms of RGB in several ways with subtle variations. A typical approach is given by the following transformation: i j H = _1_2sstan-1 2R-G-B____p_3(G-B) p _____________________________________________ S = R2 + G2 + B2 - RG - RB - BG L = 1_3(R + G + B) where: H = Hue S = Saturation L = Lightness Variations on this transformation are given in [JOBL78] and [SMIT78]. 455 D. COLOR-SPACE MAPPINGS 456 Appendix E. ASCII Form Conversion Utility This appendix gives details of a utility program to convert a file in the ASCII Form from the regular (fixed line length) ASCII Format to the Compressed ASCII Format and back again. The program is written in FORTRAN 77 code. The program is known to fail to convert a file from Compressed ASCII Format to regular ASCII Format if the file contains any string constant compressed such that an ASCII character "D" falls into column one. The source code is available from the IGES/PDES Administration Office at the National Institute of Standards and Technology. C************************************************************************** C THIS PROGRAM IS WRITTEN IN VAX 4.2 FORTRAN 77 SOURCE. ITS PURPOSE IS C TO CONVERT BETWEEN REGULAR ASCII FORMAT AND COMPRESSED ASCII FORMAT. C PROGRAM IGES C C PROGRAM ORIGINALLY WRITTEN BY J. M. SPAETH 7-24-84 C GENERAL ELECTRIC CORP. RE. & DEV. C RE-WRITTEN BY LEE KLEIN 9-20-84 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY LEE KLEIN 7-28-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY LEE KLEIN 8-1-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY LEE KLEIN 8-7-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO CONVERT NEW FORM OF IGES OUTPUT TO OLD FORM AND C OLD FORM TO NEW. C C INPUT: C YOU MUST GIVE THE NAME (INCLUDING DIRECTORY IF DIFFERENT) OF C THE FILE CONTAINING THE NEW FORM OF OUTPUT. YOU MUST ALSO C GIVE THE NAME OF THE FILE TO CONTAIN THE CONVERTED OUTPUT. C C************************************************************************** C SPECIAL NOTES: C C 1. THE DOLLAR SIGN IN I/O FORMAT STATEMENTS IS THERE TO SUPPRESS C THE CARRIAGE RETURN AT THE END OF THE PROMPT LINE. 457 E. ASCII FORM CONVERSION UTILITY C 2. IN COMPILERS THAT DO NOT ACCEPT A VARIABLE LENGTH OUTPUT FORMAT, C SOME MEANS OF COMPRESSING BLANK PADDED LINES MUST BE USED. C 3. SEE CHANGE NOTES THROUGHOUT THE CODE C C************************************************************************** CHARACTER * 80 LINE1 CHARACTER * 60 INFILE,OUTFIL C C PROMPT AND GET FILE NAMES... C GOTO 1010 1000 WRITE(*,1900) 1010 WRITE(*,1910) WRITE(*,1920) READ(*,1930)INFILE WRITE(*,1940) READ(*,1930)OUTFIL C C READ THE FIRST LINE... C OPEN(UNIT=10,FILE=INFILE,STATUS='OLD',ERR=1000) READ(10,1950)LINE1 CLOSE(10) C C CHECK TO SEE WHICH FORM THE INPUT IS IN... C C ONLY A 'C'OMPRESS RECORD CAN OCCUR AT BEGINNING OF 'NEW' FILE C ONLY A 'S'TART RECORD CAN OCCUR AT BEGINNING OF 'OLD' FILE C IF (LINE1(73:73).EQ.'C') THEN CALL OLDFRM(INFILE,OUTFIL) ELSE IF (LINE1(73:73).EQ.'S') THEN CALL NEWFRM(INFILE,OUTFIL) ELSE WRITE(*,1960)' File contains ILLEGAL record format' CLOSE(10) STOP ENDIF WRITE(*,1960)' ' WRITE(*,1960)' IGES conversion complete' WRITE(*,1960)' ' C C FORMATS C 1900 FORMAT(/1X,'Error in filename. Try again.') 1910 FORMAT(/1X,'*** IGES FILE CONVERSION PROGRAM ***'/) 1920 FORMAT($,' Enter input file name: ') 1930 FORMAT(A60) 1940 FORMAT($,' Enter output file name: ') 1950 FORMAT(A80) 458 E. ASCII FORM CONVERSION UTILITY 1960 FORMAT(A) C END C************************************************************************** C SUBROUTINE OLDFRM(INFILE,OUTFIL) C C OLD FORM CONVERSION C C PROGRAM ORIGANALLY WRITTEN BY J. M. SPAETH 7-24-84 C GENERAL ELECTRIC CORP. RE. & DEV. C RE-WRITTEN BY LEE KLEIN 9-20-84 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO CONVERT NEW FORM OF IGES OUTPUT TO OLD FORM... C C VARIABLE DECLARATIONS... C CHARACTER * (*) INFILE,OUTFIL CHARACTER * 8 BLNK,INARR(20),NEWARR(20) CHARACTER * 80 INLINE CHARACTER * 160 OUTARR INTEGER ICNT1,ICNT2,ICNT3,IA,IB,IC INTEGER IJ,IK,IL,IT C C INITIALIZE OUTARR TO BLANKS... C OUTARR(1:160)=' ' C C OPEN INPUT AND TEMP FILES... C OPEN(UNIT=1,FILE='FILE1.TMP',STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=2,FILE='FILE2.TMP',STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=3,FILE='FILE3.TMP',STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=4,FILE='FILE4.TMP',STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=9,FILE=OUTFIL,STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=10,FILE=INFILE,STATUS='OLD') C C INITIALIZE COUNTERS... C ICNT1 = -1 ICNT2 = 1 ICNT3 = 0 C C READ THE FILE AND SEPARATE INTO PARTS... C 459 E. ASCII FORM CONVERSION UTILITY 2000 READ(10,2900,END=2090)INLINE IF ((INLINE(73:73).EQ.'S').OR.(INLINE(73:73).EQ.'G')) GOTO 2010 IF (INLINE(73:73).EQ.'T') GOTO 2020 IF ((INLINE(1:1).EQ.'@').OR.(INLINE(1:1).EQ.'D')) GOTO 2040 C C IF IT IS AN C THAN DELETE IT OFF BY READING THE NEXT LINE C IF (INLINE(73:73).EQ.'C') GOTO 2000 C C PUT THE PARAMETER DATA INTO FILE4.TMP... C WRITE(4,2910) (INLINE(1:64),ICNT1,'P',ICNT2) ICNT2 = ICNT2 + 1 GOTO 2000 C C WRITE HEADER LINES INTO FILE1.TMP... C 2010 WRITE(1,2900)INLINE GOTO 2000 C C WRITE TERMINATION LINE INTO FILE2.TMP... C 2020 WRITE(2,2900)INLINE GOTO 2000 C C WRITE DIRECTORY ENTRY LINES INTO FILE3.TMP... C 2030 WRITE(3,2920) (OUTARR(1:8),ICNT2,OUTARR(17:80)) WRITE(3,2900) OUTARR(81:160) ICNT1 = ICNT1 + 2 GOTO 2000 C C REWRITE TO DE LINES IN THE NEW FORM... C C GO THRU INLINE ONE CHAR. AT A TIME LOOKING FOR THE C DELIMETER (@, ,_)... C 2040 IL = 1 2050 IF (IL.GT.80) GOTO 2000 IF (INLINE(IL:IL).EQ.';') GOTO 2030 IF (INLINE(IL:IL).NE.'@') GOTO 2080 C C DETERMINE IF THE FIELD IS ONE OR TWO CHARACTERS... C IF (INLINE(IL+2:IL+2).EQ.'_') THEN IC=ICHAR(INLINE(IL+1:IL+1))-48 IL=IL+2 ELSE IA=ICHAR(INLINE(IL+1:IL+1))-48 IB=ICHAR(INLINE(IL+2:IL+2))-48 460 E. ASCII FORM CONVERSION UTILITY IC=10*IA+IB IL=IL+3 ENDIF C C AT THIS POINT IC IS THE NUMBER OF THE RECORD FIELD BEING C PROCESSED, AND INLINE(IL)=USCORE C IT=0 IK=0 IJ=(IC-1)*8+1 C C RESET THE FIELD TO BE CHANGED TO ALL BLANKS IN ORDER TO CREATE C A COMPLETELY NEW FILED... C OUTARR(IJ:IJ+7)=' ' C C WE WILL NOW CONTINUE THRU THE LINE PICKING OFF THE CHAR. C OF THE RECORD FIELD ONE AT A TIME UNTIL A DELIMETER IS HIT... C 2060 IK=IK+1 IF (INLINE(IL+IK:IL+IK).EQ.'@') GOTO 2070 IF (INLINE(IL+IK:IL+IK).EQ.' ') THEN IF (INLINE(IL+IK+1:IL+IK+1).EQ.' ') GOTO 2070 ENDIF IF (INLINE(IL+IK:IL+IK).EQ.';') GOTO 2070 IT=IT+1 IJ=(IC-1)*8+IT OUTARR(IJ:IJ)=INLINE(IL+IK:IL+IK) IF (IC.EQ.1) THEN OUTARR(IJ+80:IJ+80)=INLINE(IL+IK:IL+IK) ENDIF GOTO 2060 2070 IL=IL+IT 2080 IL = IL + 1 GOTO 2050 C C REWIND ALL FILES BEFORE WE WRITE THEM TO OUTPUT... C 2090 REWIND 1 REWIND 2 REWIND 3 REWIND 4 C C WRITE START AND GLOBAL RECORDS TO OUTPUT FILE... C 2100 READ(1,2900,END=2110) INLINE WRITE(9,2900) INLINE GOTO 2100 C 461 E. ASCII FORM CONVERSION UTILITY C WRITE THE DE RECORDS TO OUTPUT FILE. THEY NOW BECOME RE-FORMATTED... C 2110 READ(3,2930,END=2140) (INARR(I),I=1,10) READ(3,2930) (INARR(I),I=11,20) DO 2130 IP=1,20 IF ((IP.NE.9).AND.(IP.NE.18)) GOTO 2120 NEWARR(IP)=INARR(IP) GOTO 2130 C C CHANGE THOSE FIELDS THAT MUST BE RIGHT JUSTIFIED C 2120 NEWARR(IP)=BLNK(INARR(IP)) 2130 CONTINUE ICNT3=ICNT3+1 WRITE(9,2940) ((NEWARR(J),J=1,9),'D',ICNT3) ICNT3=ICNT3+1 WRITE(9,2940) ((NEWARR(J),J=11,19),'D',ICNT3) GOTO 2110 C C WRITE THE PD LINES TO THE OUTPUT FILE... C 2140 READ(4,2900,END=2150) INLINE WRITE(9,2900) INLINE GOTO 2140 C C WRITE THE TERMINATE LINES TO THE OUTPUT FILE... C 2150 READ(2,2900,END=2160) INLINE WRITE(9,2900) INLINE GOTO 2150 C C NOW CLOSE THE FILES AND DELETE THE TEMP ONES... C 2160 CONTINUE CLOSE(UNIT=1,STATUS='DELETE') CLOSE(UNIT=2,STATUS='DELETE') CLOSE(UNIT=3,STATUS='DELETE') CLOSE(UNIT=4,STATUS='DELETE') CLOSE(9) CLOSE(10) RETURN C C FORMATS C 2900 FORMAT(A80) 2910 FORMAT(A64,1I8,1A1,1I7) 2920 FORMAT(A8,I8,A64) 2930 FORMAT(10A8) 2940 FORMAT(9A8,A,I7) 462 E. ASCII FORM CONVERSION UTILITY C END C************************************************************************** C CHARACTER*(*) FUNCTION BLNK(BUF) C C START FUNCTION BLNK HERE C C WRITTEN BY P. R. KENNICOTT 9-29-83. C GENERAL ELECTRIC CORP. RE. & DEV. C RE-WRITTEN BY LEE KLEIN 9-2-84. C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY LEE KLEIN 8-7-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO REMOVE BLANKS FROM END OF A CHARACTER STRING (RIGHT JUSTIFY) C C INPUT: C BUF STRING WITH TRAILING BLANKS C C OUTPUT: C BLNK STRING WITH TRAILING BLANKS REMOVED C C METHOD: C FIND FIRST BLANK, THEN TRANSLATE OUTPUT STRING C C RESTRICTIONS: C 1. BUF <= 512 CHARACTERS. C 2. LENGTHS OF BUF & BLNK MUST BE =. C 3. FIRST CHARACTER MUST NOT BE BLANK OR NO CONVERSION. C C C VARIABLE DECLARATIONS... C CHARACTER*(*) BUF INTEGER I CHARACTER*512 IBUF C C SET UP COUNTERS... C N=INDEX(BUF(1:),' ')-1 M=LEN(BUF) C C CHECK FOR SIZE TOO BIG... C IF (M.GT.512) STOP 'Buffer too big at function BLNK' C 463 E. ASCII FORM CONVERSION UTILITY C CHECK FOR FIRST CHAR A BLANK... C IF (BUF(1:1).EQ.' '.OR.BUF(M:M).NE.' ') THEN BLNK=BUF RETURN ENDIF C C OK PROCESS STRING... C DO 3000 I=1,N 3000 IBUF(M-I+1:M-I+1)=BUF(N-I+1:N-I+1) IBUF(1:M-N)=' ' BLNK=IBUF RETURN END C************************************************************************** C SUBROUTINE NEWFRM(INFILE,OUTFIL) C C START NEW SUBROUTINE HERE C C PROGRAM ORIGANALLY WRITTEN BY J. M. SPAETH 7-24-84 C GENERAL ELECTRIC CORP. RE. & DEV. C RE-WRITTEN BY LEE KLEIN 9-20-84 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY LEE KLEIN 8-7-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO CONVERT OLD FORM OF IGES OUTPUT TO NEW FORM... C C VARIABLE DECLARATIONS... C INTEGER PDRCD CHARACTER * 80 INLINE CHARACTER * (*) INFILE,OUTFIL C C OPEN THE INPUT AND TEMP FILES... C OPEN(UNIT=10,FILE=INFILE,STATUS='OLD') OPEN(UNIT=1,FILE='TEST.TMP',STATUS='NEW',CARRIAGECONTROL='LIST') OPEN(UNIT=2,FILE='FILE2.TMP',STATUS='NEW',RECL=80, + ACCESS='DIRECT',FORM='FORMATTED') OPEN(UNIT=3,FILE='FILE3.TMP',STATUS='NEW') OPEN(UNIT=7,FILE='FILE5.TMP',STATUS='NEW') C C WRITE THE HEADER WITH A "C" TO SHOW COMPRESSED ASCII FORM... 464 E. ASCII FORM CONVERSION UTILITY C WRITE(1,4900)'C',1 C C SEPERATE THE PD AND DE RECORDS, WHILE WRITING G,S, &T LINES C TO THE OUTPUT FILE... C 4000 READ(10,4910,END=4040) INLINE IF (INLINE(73:73).EQ.'D') GOTO 4010 IF (INLINE(73:73).EQ.'P') GOTO 4020 IF (INLINE(73:73).EQ.'T') GOTO 4030 C C WRITE HEADER LINES INTO A TEST.TMP... C WRITE (1,4910) INLINE GOTO 4000 C C WRITE DIRECTORY LINES INTO FILE3.TMP... C 4010 WRITE (3,4910) INLINE GOTO 4000 C C WRITE PARAMETER DATA INTO FILE2.TMP... C 4020 READ (INLINE(74:80),4920) PDRCD WRITE (2,REC=PDRCD,FMT=4910) INLINE GOTO 4000 C C WRITE TERMINATE RECORD INTO FILE5.TMP... C 4030 WRITE (7,4910) INLINE 4040 CALL XPD REWIND 7 4050 READ(7,4910,END=4060) INLINE WRITE (1,4910) INLINE GOTO 4050 4060 CALL CMPRES(OUTFIL) C C CLOSE FILES AND DELETE TEMP ONES... C CLOSE(UNIT=1,STATUS='DELETE') CLOSE(UNIT=2,STATUS='DELETE') CLOSE(UNIT=3,STATUS='DELETE') CLOSE(UNIT=4) CLOSE(UNIT=7,STATUS='DELETE') CLOSE(UNIT=10) RETURN C C FORMATS C 465 E. ASCII FORM CONVERSION UTILITY 4900 FORMAT(72X,A,I7) 4910 FORMAT(A80) 4920 FORMAT(I7) C END C************************************************************************** C SUBROUTINE XPD C C PROGRAM ORIGINALLY WRITTEN BY J. M. SPAETH 7-24-84 C GENERAL ELECTRIC CORP. RE. & DEV. C REVISED BY LEE KLEIN 8-7-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO TRANSFER ALL PD & DE RECORDS FORM TEMPORY FILES TO C OUTPUT FILE IN MERGED FORM... C C VARIABLE DECLARATIONS... C CHARACTER * 1 SCOLN/';'/ CHARACTER * 8 BLNK,LSTDAT(20),NEWDAT(20),NUDAT CHARACTER * 80 PDLINE,DELIN1,DELIN2 CHARACTER * 160 NEWDE INTEGER LFLD(20),FLDNUM,FLDBEG,FLDEND INTEGER CHRPTR,NEWPTR,PDPTR,PDCNT C C REWIND THE FILES... C REWIND 3 C C INITIALIZE LAST DATA SO AS NOT TO EQUAL NEXT DATA... C DO 5000 FLDNUM=1,20 LSTDAT(FLDNUM) = 'XXXXXXXX' 5000 CONTINUE C C GET NEW DE RECORD C 5010 READ(3,5900,END=5100) DELIN1 READ(3,5900) DELIN2 READ(DELIN1(9:16),5910) PDPTR READ(DELIN2(25:32),5910) PDCNT DELIN1(73:73)=' ' DELIN2(73:73)=' ' C C CLEAR OUT THE DE RECORD BUFFER... C NEWDE(1:160) = ' ' 466 E. ASCII FORM CONVERSION UTILITY C C GET THE DATA FROM EACH FIELD OF THE DE RECORD SET... C FLDBEG = -7 FLDEND = 0 DO 5020 FLDNUM=1,10 FLDBEG=FLDBEG + 8 FLDEND=FLDEND + 8 READ(DELIN1(FLDBEG:FLDEND),5920) NEWDAT(FLDNUM) READ(DELIN2(FLDBEG:FLDEND),5920) NEWDAT(FLDNUM+10) 5020 CONTINUE C C FIELD 9 MUST BE ZERO FILLED C DO 5030 I = 1,8 IF (NEWDAT(9)(I:I).EQ.' ')NEWDAT(9)(I:I) = '0' 5030 CONTINUE C C FIELD 18 MUST BE RIGHT JUSTIFIED... C NEWDAT(18)=BLNK(NEWDAT(18)) C C DETERMINE THE LENGTH OF THE DATA WITHIN EACH FIELD C DO 5050 FLDNUM=1,20 DO 5040 I=1,8 IF (NEWDAT(FLDNUM)(I:I).NE.' ') THEN LFLD(FLDNUM)= 9 - I GOTO 5050 ENDIF 5040 CONTINUE 5050 CONTINUE C C WRITE THE DE SEQUENCE NUMBER AT THE BEGINNING OF THE OUTPUT DE RECORD C NUDAT=NEWDAT(10) ENCODE(LFLD(10)+1,5930,NEWDE(1:LFLD(10)+1)) NUDAT(9-LFLD(10):8) CHRPTR = LFLD(10) + 2 C C SEARCH NEW DE RECORD SET FOR CHANGED DATA; WHEN FOUND WRITE CHANGED C DATA TO OUTPUT DE RECORD... C DO 5060 FLDNUM=1,20 C C SKIP FIELDS THAT NO LONGER NEED PROCESSING... C IF ((FLDNUM.EQ. 2).OR. + (FLDNUM.EQ.10).OR. + (FLDNUM.EQ.11).OR. + (FLDNUM.EQ.20)) GOTO 5060 467 E. ASCII FORM CONVERSION UTILITY IF (NEWDAT(FLDNUM).NE.LSTDAT(FLDNUM)) THEN IF (FLDNUM.GT.9) THEN ENCODE(4,5940,NEWDE(CHRPTR:CHRPTR+3)) FLDNUM CHRPTR=CHRPTR+4 ELSE ENCODE(3,5950,NEWDE(CHRPTR:CHRPTR+2)) FLDNUM CHRPTR=CHRPTR+3 ENDIF IF (LFLD(FLDNUM).NE.0) THEN IF (FLDNUM.NE.9) THEN READ(NEWDAT(FLDNUM)(9-LFLD(FLDNUM):8),5960) + NEWDE(CHRPTR:CHRPTR-1+LFLD(FLDNUM)) CHRPTR=CHRPTR+LFLD(FLDNUM) ELSE C C FIELD 9 IS A SPECIAL CASE... C READ(NEWDAT(9)(1:8),5960) NEWDE(CHRPTR:CHRPTR+7) CHRPTR=CHRPTR+8 ENDIF ENDIF ENDIF C C STORE DATA FROM CURRENT DE RECORD SET TO COMPARE WITH NEXT SET C LSTDAT(FLDNUM)=NEWDAT(FLDNUM) 5060 CONTINUE NEWDE(CHRPTR:CHRPTR) = SCOLN C C IF OUTPUT DE RECORD > 80 CHAR'S, WRITE 2 LINES... C IF (CHRPTR.GT.80) THEN DO 5070 I=1,11 IF (NEWDE(82-I:82-I).EQ.'@') GOTO 5080 5070 CONTINUE 5080 WRITE(1,5970)NEWDE(1:81-I) NEWDE(1:80)=NEWDE(82-I:161-I) ENDIF WRITE(1,5900) NEWDE(1:80) C C ERASE UNNECESSARY DATA FROM PD RECORD AND WRITE TO OUTPUT FILE; C DO 5090 IL=1,PDCNT READ (2,5900,REC=PDPTR) PDLINE PDPTR = PDPTR+1 PDLINE(65:80) = ' ' WRITE(1,5900) PDLINE 5090 PDLINE(1:80) = ' ' C C END OF LOOP GET NEXT DE RECORD... 468 E. ASCII FORM CONVERSION UTILITY C GOTO 5010 5100 CONTINUE RETURN C C FORMATS C 5900 FORMAT(A80) 5910 FORMAT(I8) 5920 FORMAT(A8) 5930 FORMAT ('D',A) 5940 FORMAT('@',I2,'_') 5950 FORMAT('@',I1,'_') 5960 FORMAT(A) 5970 FORMAT(A<81-I>) C END C************************************************************************** C SUBROUTINE CMPRES(OUTFIL) C C START OF SUBROUTINE C C PROGRAM ORIGINALLY WRITTEN BY J. M. SPAETH 7-24-84 C GENERAL ELECTRIC CORP. RE. & DEV. C REVISED BY LEE KLEIN 8-7-86 C GENERAL DYNAMICS CAD/CAM POMONA DIV. C REVISED BY ROBERT COLSHER 22 AUG 1986 C IGES DATA ANALYSIS COMPANY C C PURPOSE: C TO CLEAR AWAY ALL TRAILING BLANKS FROM THE OUTPUT FILE C C VARIABLE DECLARATIONS... C CHARACTER * 80 TEXT CHARACTER * (*) OUTFIL INTEGER LENGTH C C REWIND THE INPUT FILE AND OPEN THE OUTPUT FILE C REWIND 1 OPEN (UNIT=4,NAME=OUTFIL,STATUS='NEW',CARRIAGECONTROL='LIST', + ERR=6000) GOTO 6010 C C GETS HERE IF THERE IS AN ERROR IN THE OUTPUT FILE NAME... C 469 E. ASCII FORM CONVERSION UTILITY 6000 WRITE(*,6900)'Error in OUTPUT file name. Output written to file', + ' IGES.OUT' OPEN (UNIT=4,NAME='IGES.OUT',STATUS='NEW',CARRIAGECONTROL='LIST') C C READ RECORD LINES INTO BUFFER ONE AT A TIME... C 6010 READ(1,6910,END=6999) TEXT LENGTH = 80 C C GO THRU EACH LINE DELETING TRAILING BLANKS C 6020 IF (TEXT(LENGTH:LENGTH).NE.' ') GOTO 6030 LENGTH=LENGTH-1 IF (LENGTH.GT.1) GOTO 6020 C C WRITE PROCESSED LINES TO THE OUTPUT FILE C 6030 WRITE(4,6920) TEXT(1:LENGTH) C GOTO 6010 C 6999 CONTINUE RETURN C C FORMATS C 6900 FORMAT(1X,A,A) 6910 FORMAT(A80) 6920 FORMAT(A) C END 470 Appendix F. Obsolete Entities F.1 General The addition of new entities and forms which greatly increase the capability for transfer of specific data constructs has given cause to deprecate other entities and forms published in previous versions of this Specification. The parameter lists for these entities and forms are included herein to provide for interpretation of files created under an earlier version. The new entities or forms which are valid for the previous forms are as follows: ____________________________________________________________________ |____Obsolete_Entity/Form____|__________Valid_Entity/Form_____|_____ | 402/2 |External Logical | 402/12 | External Reference | | |Reference File Index | |File Index | | 402/6 |View List | 402/3 | Views Visible | | 402/8 |Signal String |402/18 | Flow | | 402/10 |Text Node | 312 | Text Template | | 402/11 |Connect Node | 132 | Connect Point | |__406/4___|Region_Fill_Property__|_230_____|_Sectioned_Area______|_ In addition, FC Zero for the General Note Entity (Type 212) is obsolete, and the use of the Single Parent Associativity (Type 402, Form 9) to create holes in bounded planar regions is deprecated. The parameter lists for these following entities may have additional parameters as specified in Sec- tion 2.2.4.4.2. 471 F.2.1 (TYPE 402, FORM 2) - EXTERNAL LOGICAL REFERENCE FILE INDEX F.2 Obsolete Associativity Instance Entities (Type 402) The following forms of the Associativity Instance Entity are obsolete. F.2.1 (Type 402, Form 2) - External Logical Reference File Index The External Logical Reference File Index Entity appears in one file which contains references from another file. It contains a list of the symbolic names used by the referencing files and the DE pointers to the corresponding definitions within the referenced file. See Section 3.6.4 and the External Reference Entity (Type 416) for more detail. DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class (externally referenced entities) 2 2 Backpointers not required 3 2 Unordered list of entries in a class 4 2 Number of items in an entry 5 2 First item is a value (External Reference Entity Symbolic Name) 6 1 Second item is a pointer (Internal Entity DE Pointer) DESCRIPTION Directory Entry Entity Type Number: 402 Form Number: 2 Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of Index Entries 2 NAME1 String First External Reference Entity Symbolic Name 3 PTR1 Pointer Pointer to the DE of the First Internal Entity .. . . . .. .. 2*N NAMEN String Last External Reference Entity Symbolic Name 1+2*N PTRN Pointer Pointer to the DE of the Last Internal Entity ECO605 Additional pointers as required (see Section 2.2.4.4.2). 472 F.2.2 (TYPE 402, FORM 6) - VIEW LIST F.2.2 (Type 402, Form 6) - View List This associativity has two classes. The first class has only one entry which is a pointer to the directory entry of a specific view. The second class is a list of entities (pointers to their respective directory entries) which are visible in the view referenced in Class 1. Back pointers are required in both classes; the view as well as all entities visible in the view must have pointers to this associativity instance. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (View) 2 1 Back pointers required 3 2 Unordered 4 1 One item per entry 5 1 Pointer to view Directory Entry Class 2 (Entities) 6 1 Back pointers required 7 2 Unordered 8 1 One item per entry 9 1 Pointer to Directory Entry of entity visible in view DESCRIPTION Directory Entry Entity Type Number: 402 Form Number: 6 Parameter Data Index__ Name____ Type___ Description___ 1 1 Integer Single entry in first class 2 N1 Integer Number of entities in second class 3 DEV Pointer Pointer to the DE of the View Entity 4 DE1 Pointer Pointer to the DE of the first entity visible in view specified in Parameter 3 .. . . . .. .. 3+N1 DEN1 Pointer Pointer to the DE of the last entity visible Additional pointers as required (see Section 2.2.4.4.2). ECO605 473 F.2.3 (TYPE 402, FORM 8) - SIGNAL STRING F.2.3 (Type 402, Form 8) - Signal String This associativity has four classes and is intended to represent a single signal string. Class one provides all names of the signal in an order that should be preserved. Class two collects together a set of connection nodes in the string and thus can be considered as specifying the connections for the signal. Class three relates the signal string to a set of geometric entities on a schematic drawing, while class four accomplishes the same thing with respect to the implemented board or chip. The geometric entities which may be members of classes 2 and 3 include composite, copious (Forms 11 or 12), or any of the entities which may be members of composite. DEFINITION Index__ Set_Value___ Meaning____ 1 4 Four classes Class 1 (Signal Names) 2 2 Back pointers not required 3 1 Ordered 4 1 One item per entry 5 2 Item is value Class 2 (Connections) 6 1 Back pointers required 7 2 Unordered 8 1 One item per entry 9 1 Pointer to Connect Node Class 3 (Schematic) 10 1 Back pointers required 11 1 Ordered 12 1 One item per entry 13 1 Pointer to geometry Class 4 (Physical Layout) 14 1 Back pointers required 15 1 Ordered 16 1 One item per entry 17 1 Pointer to geometry 474 F.2.3 (TYPE 402, FORM 8) - SIGNAL STRING DESCRIPTION Directory Entry Entity Type Number: 402 Form Number: 8 Parameter Data Index__ Name____ Type___ Description___ 1 NS Integer Number of signal names 2 N1 Integer Number of Connection Nodes 3 N2 Integer Number of entities in schematic signal string 4 N3 Integer Number of entities in physical signal string 5 SIG1 String Signal name .. . . . .. .. 4+NS SIGNS String Signal name 5+NS PC1 Pointer Pointer to the DE of the first Connect Node Entity .. . . . .. .. 4+NS+N1 PCN1 Pointer Pointer to the DE of the last Connect Node Entity 5+NS+N1 PS1 Pointer Pointer to the DE of the first entity in schematic logical signal string .. . . . .. .. 4+NS+N1 PSN2 Pointer Pointer to the DE of the last entity in schematic logical signal +N2 string 5+NS+N1 PP1 Pointer Pointer to the DE of the first entity in physical signal string +N2 .. . . . .. .. 4+NS+N1 PPN3 Pointer Pointer to the DE of the last entity in physical signal string +N2+N3 Additional pointers as required (see Section 2.2.4.4.2). ECO605 475 F.2.4 (TYPE 402, FORM 10) - TEXT NODE F.2.4 (Type 402, Form 10) - Text Node The purpose of the text node is to act as a template for future addition of text. It is defined as an associativity to allow it to refer to multiple instances of itself in those cases in which it is instanced as part of a subfigure definition. In accordance with the general rule of multiply instanced entities, digits 5-6 of Directory Entry Field 9 have the value 04, and Class 1 consists of a pointer to a point representing its original location followed by pointers to multiple instances, if these exist. Class 2 consists of those parameters of the General Note which are pertinent to the definition of a text template, as opposed to text itself. In general, these consist of all parameters but the text string. The location is omitted because it is included in Class 1 as a pointer to a point representing the geometric location of the text node. An instance of a text node consists of this Associativity, a point indicating the position of the instance, and one or more General Notes attached to the node through the text pointers of the geometric entities. If parameters in the General Notes are null, the value of the same parameter in Class 2 of the associativity is taken as the default; non-null parameters over-ride the defaults. In the cases of multiple instances from a subfigure, the General Notes representing text will be attached to the instance point (pointers 2, 3,. . .in Class 1). As a text-type entity, the Text Node can be pointed to by the back pointer/text pointer field in each entity. Note that the associativity definition has an unusual value for Parameter 11 (Font Characteristic). The value 3 implies either a pointer or a data item. A positive value implies a data item; a negative value implies the absolute value is to be taken as a pointer. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (Geometry Pointers) 2 1 Back pointers required 3 1 Ordered class 4 1 One item per entry 5 1 Item is pointer (to Point Entity) Class 2 (Text Description) 6 2 Back pointers not required 7 1 Ordered class 8 7 Seven items/entry 9 2 Box length 10 2 Box height 11 3 Font characteristic 12 2 Slant angle 13 2 Rotation angle 14 2 Mirror flag 15 2 Rotate internal flag 476 F.2.4 (TYPE 402, FORM 10) - TEXT NODE DESCRIPTION Directory Entry Entity Type Number: 402 Form Number: 10 Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of geometry pointers 2 NTD Integer Number of Text Descriptions (NTD=1) 3 GP1 Pointer Pointer to the DE of the point entity (original location) 4 GP2 Pointer Pointer to the DE of the instance point entity (first instance) .. . . . .. .. NP+2 GPNP Pointer Pointer to the DE of the instance point entity (NP-1 instance) NP+3 WT Real Box length NP+4 HT Real Box height NP+5 FC Integer Font characteristic (default = 1) or pointer NP+6 SL Real Slant angle of text in radians. ss=2 is the value for no slant angle and is the default value. NP+7 A Real Rotation angle in radians for text. NP+8 M Integer Mirror flag (0=no mirror, 1=YT mirror axis, 2=XT mirror axis.) NP+9 VH Integer Rotate internal text flag (0=text horizontal, 1=text vertical) Additional pointers as required (see Section 2.2.4.4.2). ECO605 477 F.2.5 (TYPE 402, FORM 11) - CONNECT NODE F.2.5 (Type 402, Form 11) - Connect Node The purpose of the Connect Node is to imply a logical connection between one or more entities. In the case of an electrical application, this logical connectivity would mean an electrical connection, but the Connect Node has applicability in other applications such as piping. The Connect Node is defined as a two-class associativity with the second class undefined. In accordance with the general rule of multiple-instanced entities, digits 5-6 of directory entry field 9 have the value 04, and class 1 consists of a pointer to the geometry representing the original location of the Connect Node, followed by pointers to multiple instances, if these exist. Each of the geometry entities is the Point Entity. In the case of a singly-instanced Connect Node, the point represents the position of the Connect Node. In the case of a multiply-instanced Connect Node (i.e., a Connect Node in a Subfigure Definition), the first point in the class represents the defining location (in the Subfigure Definition), while the remaining points represent instance locations of the Connect Node. The second class is intended to describe the properties of the Connect Node such as physical con- nection constraints. Its definition will be developed in the future when these requirements become more clear. The name of a Connect Node is found in its entity label. If the name is longer than 8 characters, the entity label is blank, and the name is found in a Name Property attached to the entity. In the case of multiply-instanced Connect Nodes, separate names can be attached to the instance points by the same means. DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (Geometry Pointers) 2 1 Back pointers required 4 1 One item per entry 5 1 Pointer (to Point Entity) Class 2 (Connection entities) 6 2 Back pointers not required 7 2 Unordered class 8 1 One item per entry 9 2 Item is value 478 F.2.5 (TYPE 402, FORM 11) - CONNECT NODE DESCRIPTION Directory Entry Entity Type Number: 402 Form Number: 11 Parameter Data Index__ Name____ Type___ Description___ 1 NC Integer Number of pointers (to points) 2 NP Integer Number of entries in second class 3 PT1 Pointer Pointer to the DE of the defining point entity (original location) 4 PT2 Pointer Pointer to the DE of the instance point entity (first instance) .. . . . .. .. NC+2 PTNC Pointer Pointer to the DE of the last instance point entity (NC-1 in- stance) NC+3 DT1 Data First data entry .. . . . .. .. NC+NP+2 DTNP Data Last data entry Additional pointers as required (see Section 2.2.4.4.2). ECO605 479 F.3.1 (TYPE 406, FORM 4) - REGION FILL F.3 Obsolete Property Entity (Type 406) The following form of the property Entity (Type 406) is obsolete. F.3.1 (Type 406, Form 4) - Region Fill DESCRIPTION This property helps define the functional value of any closed region. It classifies the region as to its "filled" status. It will be used most often to identify which region-defining entities are defining a functional region (or a gap in that region) and which have other purposes. The actual function of the region will likely be determined in conjunction with level or subfigure membership. Directory Entry Entity Type Number: 406 Form Number: 4 Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=2) 2 FC Integer Fill code: 0=solid fill 1=unfill (i.e., a gap in solid fill) 2=meshed fill Use of Fill Code = 2 indicates that an associativity is used to link the fill area with its fill mesh description. Using the asso- ciativity will allow the implementation of this obsolete method. The recommended method of mesh fill is to use the Type 230 Sectioned Area Entity. 3 O Pointer Obsolete. Note: a previous erroneous implementation of this parameter was as a pointer to the DE of a Section Entity defin- ing linear segments of meshed fill. This previous implementa- tion would be indicated by a nonzero value. ECO605 Additional pointers as required (see Section 2.2.4.4.2). 480 F.4 OBSOLETE GENERAL NOTE FC ZERO F.4 Obsolete General Note FC Zero FC 0 specifies an obsolete symbol font for the General Note Entity (Type 212) and should not be used. It is included here (see Figure F1) for reference in processing files written in accordance with Version 1.0 of the Specification. 481 F.4 OBSOLETE GENERAL NOTE FC ZERO I'm a fake F0 table Figure F1. Obsolete General Note Font specified by FC 0 482 F.5 OBSOLETE USE OF SINGLE PARENT ASSOCIATIVITY F.5 Obsolete Use of Single Parent Associativity The use of the Single Parent Associativity to create holes in bounded planar regions is deprecated. The following is the obsolete description that was present in previous versions of the Specification. The case of a bounded portion of a fixed plane minus some portion(s) of that plane is expressed through the use of the Single Parent Associativity (Type 402, Form 9), where the outer closed curve defines the parent bounded plane and each internal closed curve defines some child bounded plane to be subtracted from the parent. Each of these planes (parent and child) is a separate plane entity in the file and has a backpointer to the associativity structure. The child plane entity will have a subordinate entity switch class of 01 (Physically Dependent). 483 F.5 OBSOLETE USE OF SINGLE PARENT ASSOCIATIVITY 484 Appendix G. Untested Entities G.1 Introduction This appendix contains extensions to this Specification which have been approved by the IGES/PDES Organization but have not been sufficiently tested to be included in the main body of the Specifi- cation. Implementors should be cautioned that the entities may not work and may be significantly changed based on implementation experience. When the IGES/PDES Organization deems that sufficient implementation experience has been obtained on a specific extension, it will be moved to its appropriate place in the main body of the Specification. This appendix serves the same function as "gray pages" in other specifications. The following entities or entity forms are included in this appendix: ECO610 ________________________________________________________________________ | Entity | | | |__Type_Number__|____Form__|_______________Entity_Type______________|___ | 123 | | Direction | | 136 | | Finite Element (additional topologies) | | 141 | | Boundary | | 143 | | Bounded Surface | | 146 | 0-34 | Nodal Results | | 148 | 0-34 | Element Results | | 182 | | Selected Component | | 186 | | Manifold Solid B-Rep Object | | 190 | | Plane Surface | | 192 | | Right Circular Cylindrical Surface | | 194 | | Right Circular Conical Surface | | 196 | | Spherical Surface | | 198 | | Toroidal Surface | | 204 | | Curve Dimension | | 212 | All | Additional General Note Fonts: | | | | OCR-B Text Font | | | | Kanji Text Font | | 213 | | New General Note | | 216 | 0-2 | Linear Dimension (Form Numbers) | | 218 | 1 | Ordinate Dimension (Form Number) | | 222 | 1 | Radius Dimension (Multiple Leader) | | 228 | 1-3 | General Symbol (Form Numbers) | |____(continued)____|________|__________________________________________| 485 G. UNTESTED ENTITIES ECO610 ________________________________________________________________________ | Entity | | | |__Type_Number__|____Form__|_______________Entity_Type______________|___ | (continued) | | | | 230 | 0 | Sectioned Area (Pattern Hatches) | | 230 | 1 | Sectioned Area (Form Number) | | 306 | | MACRO | | 316 | | Units Data | | 402 | 19 | Segmented Views Visible Associativity | | 402 | 20 | Piping Flow Associativity | | 402 | 21 | Dimensioned Geometry Associativity | | 404 | 1 | Drawing with Rotated Views | | 406 | 18 | Intercharacter Spacing Property | | 406 | 19 | Line Font Property | | 406 | 20 | Highlight Property | | 406 | 21 | Pick Property | | 406 | 22 | Uniform Rectangular Grid Property | | 406 | 23 | Associativity Group Type Property | | 406 | 24 | Level to PWB Layer Map Property | | 406 | 25 | PWB Artwork Stackup Property | | 406 | 26 | PWB Drilled Hole Property | | 406 | 27 | Generic Data Property | | 406 | 28 | Dimensioned Units Property | | 406 | 29 | Dimension Tolerance Property | | 406 | 30 | Dimension Display Data Property | | 406 | 31 | Basic Dimension Property | | 410 | 1 | View (Perspective) | | 416 | 3 | External Reference (Form Number) | | 416 | 4 | External Reference (Form Number) | | 502 | | Vertex | | 504 | | Edge | | 508 | | Loop | | 510 | | Face | |________514________|________|_Shell____________________________________ | 486 G.2 DIRECTION ENTITY (TYPE 123) G.2 Direction Entity (Type 123) ECO603 A direction entity is a non-zero vector in Euclidean 3-space that is defined by its three components (direction ratios) with respect to the coordinate axes. If x; y; z are the direction ratios then x2 + y2 + z2 > 0. The Subordinate Entity Switch must always be set to Physically Dependent. The Transformation Matrix Entity (Type 124) may not be used in conjunction with this entity. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 123 | ) |< n:a: > | #; ) | #; ) | 0; ) |< n:a: > | 0; ) |**0102** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 123 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 X Real Direction ratio with respect to X axis 2 Y Real Direction ratio with respect to Y axis 3 Z Real Direction ratio with respect to Z axis (default value is zero) Additional pointers as required (see Section 2.2.4.4.2). 487 G.3 FINITE ELEMENT ENTITY (TYPE 136) G.3 Finite Element Entity (Type 136) ECO515 Additional element topologies for the Finite Element Entity are defined below. See Section 4.26 for more detail. Table G1 lists the data to define the element topology. Figure G1 illustrates the node connectivity for each element topology. Table G1. Finite Element Topology Set _____________________________________________________________________________ | Element | Element | Order | Number | Number | Number | | Name | Topology | | of Nodes | of Edges | of Faces | |______________|__Type____|__________|_____________|____________|____________| | OMASS | 34 | 0 | 2 | 0 | 0 | | OFBEAM | 35 | 1 | 4 | 1 | 0 | | PBEAM | 36 | 2 | 3 | 1 | 0 | | CBEAM | 37 | 2 | 3 | 1 | 0 | |__CPSOW___|_______38______|____3_____|____21______|_____9______|_____5______| 488 G.3 FINITE ELEMENT ENTITY (TYPE 136) 34. OFMASS - Offset Mass Node 2 specifies the center of mass. 35. OFBEAM - Offset Beam E1 = 3,4 36. PBEAM - Three Node Beam E1 = 1,2,3 37. CBEAM - Curved Beam Part of a circle. E1 = 1,2 A < 45 degrees 38. CPSOW - Cubic/Parabolic Solid Wedge E1 = 1,2,3,4 E2 = 4,5,6,7 E3 = 7,8,9,1 E4 = 13,14,15,16 E5 = 16,17,18,19 E6 = 19,20,21,13 E7 = 1,10,13 E8 = 4,11,16 E9 = 7,12,19 F1 = 1,2,3,4,5,6,7,8,9 F2 = 1,2,3,4,11,16,15,14,13,10 F3 = 4,5,6,7,12,19,18,17,16,11 F4 = 7,8,9,1,10,13,21,20,19,12 F5 = 13,14,15,16,17,18,19,20,21 5001. Implementor-Defined ITOP values greater than or equal 5001 are considered to be implementor-defined. Figure G1. Finite Element Topology Set 489 G.3 FINITE ELEMENT ENTITY (TYPE 136) Figure G1. Finite Element Topology Set (continued) 490 G.3 BOUNDARY ENTITY (TYPE 141) G.4 Boundary Entity (Type 141) ECO511 Each Boundary Entity (Type 141) identifies a surface boundary consisting of a set of curves lying on the surface. The properties of the surface, the boundary and the curves comprising the boundary are defined below: D1. S(U; V ) may be used as a parameterized surface representation with the Boundary Entity (Type 141) if it meets the following criteria: (a) The untrimmed domain of S(U; V ) is a rectangle, D, consisting of those points (U; V ) such that a <= U <= b and c <= V <= d for given constants a,b,c and d with a < b and c < d. (b) The mapping S = S(U; V ) = (x(U; V ); y(U; V ); z(U; V )) is defined for each ordered pair (U; V ) in D. (c) It is one-to-one in the interior (but not necessarily on the boundary) of D. (d) It has continuous normal vectors at every point of D except those which map to poles (see definition D3). D2. The isoparametric curves U = a, U = b, V = c and V = d will be referred to as boundary curves of the parameter space or simply boundary curves. D3. Let P be a 3-D Euclidean (model space) point. Then P is a pole of the surface defined by the mapping S(U; V ) if any of the following are true: (a) P = S(a; V ) for all V such that c <= V <= d (b) P = S(b; V ) for all V such that c <= V <= d (c) P = S(U; c) for all U such that a <= U <= b (d) P = S(U; d) for all U such that a <= U <= b D4. Let C be a 3-D Euclidean (model space) curve. Then C is a seam of the surface defined by the mapping S(U; V ) if it is the image in model space of (a) C(V ) = S(a; V ) for all V such that c <= V <= d and C(V ) = S(b; V ) for all V such that c <= V <= d or (b) C(U ) = S(U; c) for all U such that a <= U <= b and C(U ) = S(U; d) for all U such that a <= U <= b. D5. A model space curve is represented parametrically, has a unique nonzero tangent vector at each point, lies on the surface, and is not self-intersecting except, possibly, at its endpoints. D6. A boundary is an ordered list of model space curves (Ci, i = 1; n) which has the following properties: (a) It is closed. This implies that the endpoint of Cn is the startpoint of C1. (b) Each curve in the list is oriented such that the endpoint of the curve Ci-1 is the startpoint of the curve Ci, i = 2; n. (c) It is not self-intersecting except at its endpoints. The endpoints of the boundary are the startpoint of C1 and the endpoint of Cn . It does not intersect other boundaries except at its endpoints. 491 G.4 BOUNDARY ENTITY (TYPE 141) D7. A model space trimming curve is one of the model space curves in the ordered list forming a boundary and thus its usage is oriented. D8. The positive surface normal is given by the cross product (in the order specified) of the partial derivative of S(U; V ) with respect to U and the partial derivative of S(U; V ) with respect to V . D9. Left of a model space trimming curve at a point, p, is the direction of the vector formed as the cross product (in the order specified) of the surface normal and the tangent vector to the model space trimming curve at p. D10. The region of the surface being communicated is called the active region, it must satisfy the following: (a) The active region has finite area. (b) Any two points on the active region must be path connected. (c) The interior of the active region lies on the left of all of its boundaries. (d) The active region consists of all of its boundaries and its interior. (e) The closure of the interior of the active region (in the relative topology of the surface induced by R3) is the active region. D11. C*ais an associated parameter space curve of an arc, Ca, of a model space trimming curve, C, on the surface, S, with domain D, if C*ais contained in D and the composition S O C*a= Ca. An associated parameter space curve is assumed to be represented parametrically, to have a unique nonzero tangent vector at each point, and to be not self-intersecting except, possibly, at endpoints. D12. An associated parameter space curve collection (or simply "collection") is defined to be the associated parameter space curves (C*i, i = 1; p) such that the Ci given by the composition (S O C*i, i = 1; p) form a composite curve. The Ci of the composite curve are ordered and oriented such that as the parameter goes from its initial to final value the complete model space trimming curve is produced. The Ci given by the composition (S O C*i, i = 1; p) have the same orientation as the model space trimming curve developed from the model space curve Cj. Thus the SENSE orientation flag of the model space curve is not applicable. The C*iforming the associated parameter space collections of a boundary are not required to satisfy the `closed' property for a boundary (see definition D6). The C*ican be formed into a boundary by adding the appropriate sections of the boundary curves of the parameter space (see definition D2). 492 G.4 BOUNDARY ENTITY (TYPE 141) Directory Entry ECO605 |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 141 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |??????** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 141 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 TYPE Integer The type of bounded surface representation: 0 = The boundary entities may only reference model space trim- ming curves. The associated surface representation (located by SPTR) may be parametric. 1 = The boundary entities must reference model space curves and associated parameter space curve collections. The associ- ated surface (located by SPTR) must be a parametric represen- tation. 2 PREF Integer Indicates the preferred representation of the trimming curves in the sending system: 0 = Unspecified 1 = Model space 2 = Parameter space 3 = Representations are of equal preference 3 SPTR Pointer Pointer to the DE of the untrimmed surface entity to be bounded. If associated parameter space curves are being trans- ferred (TYPE = 1) the surface representations must be paramet- ric. 4 N Integer Number of curves included in this boundary entity 5 CRVPT1 Pointer Pointer to the DE of the first model space curve entity of this Boundary Entity 6 SENSE1 Integer An orientation flag indicating whether the direction of the first model space curve should be reversed before use in the bound- ary. The possible values for the sense flag are: 1 = The direction of the model space curve does not require reversal 2 = The direction of the model space curve needs to be reversed 7 K1 Integer A count of the associated parameter space curves in the collec- tion for the first model space trimming curve. In the case of a TYPE = 0 transfer, this count must be zero. 8 PSCPT1 Pointer Pointer to the DE of the first associated parameter space entity curve of the collection for the first model space trimming curve .. . . . .. .. 7+K1 PSCPTK1 Pointer Pointer to the DE of the last associated parameter space curve entity of the collection for the first model space trimming curve .. . . . .. .. Let M=5 + 3*(N-1) + (K1 + K2 + ... + KN-1) 493 G.4 BOUNDARY ENTITY (TYPE 141) M CRVPTN Pointer Pointer to the DE of the last model space curve entity in this Boundary Entity 1+M SENSEN Integer An orientation flag indicating whether the direction of the last model space curve should be reversed before use in the bound- ary. The possible values for the sense flag are: 1 = The direction of the model space curve does not require reversal 2 = The direction of the model space curve needs to be reversed 2+M KN Integer A count of the associated parameter space curves in the collec- tion for the last model space trimming curve. In the case of a TYPE = 0 transfer, this count must be zero. 3+M PSCPTN Pointer Pointer to the DE of the first associated parameter space curve entity of the collection for the last model space trimming curve .. . . . .. .. KN+M PSCPTKN Pointer Pointer to the DE of the last associated parameter space curve entity of the collection for the last model space trimming curve Additional pointers as required (see section 2.2.4.4.2). 494 G.5 BOUNDED SURFACE ENTITY (TYPE 143) G.5 Bounded Surface Entity (Type 143) ECO511 The Bounded Surface Entity (Type 143) is used to communicate trimmed surfaces. The surface and trimming curves are assumed to be represented parametrically and to comply with the definitions listed below: D1. S(U; V ) may be used as a parameterized surface representation with the Bounded Surface Entity (Type 143) if it meets the following criteria: (a) The untrimmed domain of S(U; V ) is a rectangle, D, consisting of those points (U; V ) such that a <= U <= b and c <= V <= d for given constants a,b,c and d with a < b and c < d. (b) The mapping S = S(U; V ) = (x(U; V ); y(U; V ); z(U; V )) is defined for each ordered pair (U; V ) in D. (c) It is one-to-one in the interior (but not necessarily on the boundary) of D. (d) It has continuous normal vectors at every point of D except those which map to poles (see definition D3). D2. The isoparametric curves U = a, U = b, V = c and V = d will be referred to as boundary curves of the parameter space or simply boundary curves. D3. Let P be a 3-D Euclidean (model space) point. Then P is a pole of the surface defined by the mapping S(U; V ) if any of the following are true: (a) P = S(a; V ) for all V such that c <= V <= d (b) P = S(b; V ) for all V such that c <= V <= d (c) P = S(U; c) for all U such that a <= U <= b (d) P = S(U; d) for all U such that a <= U <= b D4. Let C be a 3-D Euclidean (model space) curve. Then C is a seam of the surface defined by the mapping S(U; V ) if it is the image in model space of (a) C(V ) = S(a; V ) for all V such that c <= V <= d and C(V ) = S(b; V ) for all V such that c <= V <= d or (b) C(U ) = S(U; c) for all U such that a <= U <= b and C(U ) = S(U; d) for all U such that a <= U <= b. D5. A model space curve is represented parametrically, has a unique nonzero tangent vector at each point, lies on the surface, and is not self-intersecting except, possibly, at its endpoints. D6. A boundary is an ordered list of model space curves (Ci, i = 1; n) which has the following properties: (a) It is closed. This implies that the endpoint of Cn is the startpoint of C1. (b) Each curve in the list is oriented such that the endpoint of the curve Ci-1 is the startpoint of the curve Ci, i = 2; n. (c) It is not self-intersecting except at its endpoints. The endpoints of the boundary are the startpoint of C1 and the endpoint of Cn . It does not intersect other boundaries except at its endpoints. 495 G.5 BOUNDED SURFACE ENTITY (TYPE 143) D7. A model space trimming curve is one of the model space curves in the ordered list forming a boundary and thus its usage is oriented. D8. The positive surface normal is given by the cross product (in the order specified) of the partial derivative of S(U; V ) with respect to U and the partial derivative of S(U; V ) with respect to V . D9. Left of a model space trimming curve at a point, p, is the direction of the vector formed as the cross product (in the order specified) of the surface normal and the tangent vector to the model space trimming curve at p. D10. The region of the surface being communicated is called the active region, it must satisfy the following: (a) The active region has finite area. (b) Any two points on the active region must be path connected. (c) The interior of the active region lies on the left of all of its boundaries. (d) The active region consists of all of its boundaries and its interior. (e) The closure of the interior of the active region (in the relative topology of the surface induced by R3) is the active region. D11. C*ais an associated parameter space curve of an arc, Ca, of a model space trimming curve, C, on the surface, S, with domain D, if C*ais contained in D and the composition S O C*a= Ca. An associated parameter space curve is assumed to be represented parametrically, to have a unique nonzero tangent vector at each point, and to be not self-intersecting except, possibly, at endpoints. D12. An associated parameter space curve collection (or simply "collection") is defined to be the associated parameter space curves (C*i, i = 1; p) such that the Ci given by the composition (S O C*i, i = 1; p) form a composite curve. The Ci of the composite curve are ordered and oriented such that as the parameter goes from its initial to final value the complete model space trimming curve is produced. Two types of transfer are supported by the bounded surface. A TYPE = 0 transfer communicates a surface and its model space boundaries. A TYPE = 1 transfer communicates a surface, its model space boundaries and the associated parameter space curve collection for each model space trimming curve of each boundary. Because of seams and poles, the associated parameter space curve collections of a boundary do not necessarily enclose a region in parameter space. The bounded surface information is communicated using several entities. These are the Bounded Sur- face Entity (Type 143), the Boundary Entity (Type 141), the parametrically represented untrimmed surface entities and the parametrically represented curve entities. 496 G.5 BOUNDED SURFACE ENTITY (TYPE 143) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 143 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????00** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 143 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 TYPE Integer The type of bounded surface representation: 0 = The boundary entities may only reference model space curves. The associated surface representation (located by SPTR) may be parametric. 1 = The boundary entities must reference both model space curves and the associated parameter space curve collections. The associated surface (located by SPTR) must be a parametric representation. 2 SPTR Pointer Pointer to the DE of the untrimmed surface entity to be bounded. If parameter space trimming curves are being trans- ferred (TYPE = 1) the surface representations must be paramet- ric. 3 N Integer The number of boundary entities 4 BDPT1 Pointer Pointer to the DE of the first Boundary Entity (Type 141) .. . . . .. .. 3+N BDPTN Pointer Pointer to the DE of the last Boundary Entity (Type 141) Additional pointers as required (see section 2.2.4.4.2). 497 G.6 NODAL RESULTS ENTITY (TYPE 146) G.6 Nodal Results Entity (Type 146) The number of analysis results data values per FEM node and their physical interpretation depends upon specified values of the form number (TYPE) and NV (see Table G2). Also, the node number identifier is equivalent to the node number in the directory entry subscript field of the node entity. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 146 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |**??03** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 146 |< n:a: > | #; ) | # | TYPE | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Entity Subscript field shall contain the Analysis Case Number. The Entity Label field optionally may contain the Analysis Label. The value of TYPE (see Table G2) indicates the physical interpretation of the finite element analysis result data. For a specific TYPE of data, multiple values are positioned within the Parameter Data record in the order in which they appear in the parenthetical expression in the description column of the table. Parameter Data Index__ Name____ Type___ Description___ 1 GNOTE Pointer Pointer to the DE of the General Note Entity that describes the analysis case. 2 SCN Integer Analysis Subcase number. If there is no subcase, then the value of this parameter should be zero. 3 TIME Real Analysis time value used for this subcase. (This time value is not the time that the analysis was executed, nor does it have anything to do with the amount of time that a computer took to execute the job. It is the time at which transient analysis results occur in the mathematical FEM model.) 4 NV Integer Number of real values in array V for a FEM node. (The value of NV must agree with the form number specified in the Directory Data, see Table G2.) 5 NN Integer Number of FEM nodes for which data is to be read. 6 NODE(1) Integer FEM node number identifier for first node. 7 NP(1) Pointer Pointer to the DE of the first FEM Node Entity 8 V(i) Real Values of the finite element analysis result data array for the first FEM node. There are NV data values in array V. .. . . . .. .. loop over number of nodes, NN In subsequent index equations, let NNV = (NV+2)*(NN-1) 6+NNV NODE(NN) Integer FEM node number identifier for last node. 498 G.6 NODAL RESULTS ENTITY (TYPE 146) 7+NNV NP(NN) Pointer Pointer to the DE of the last FEM Node Entity 8+NNV V(i) Real Values of the finite element analysis result data array for the last FEM node. There are NV data values in array V. Additional pointers as required (see Section 2.2.4.4.2). 499 G.6 NODAL RESULTS ENTITY (TYPE 146) Table G2. Description of TYPE Numbers for the Nodal and Element Results Entities _______________________________________________________________________________________________ |__Type__|_NV__|_________________________________Description_________________________________|_ | 0 | nv | Unknown/Miscellaneous (The number of values, nv, is not predefined for | | | | form type 0. The value of nv must always be positive.) | | 1 | 1 | Temperature | | 2 | 1 | Pressure | | 3 | 3 | Total Displacement (xx, yy, zz - consistent with the Nodal Displacement | | | | Coordinate System) | | 4 | 6 | Total Displacement and Rotation (Dxx, Dyy, Dzz, Rxx, Ryy, Rzz - | | | | consistent with the Nodal Displacement Coordinate System) | | 5 | 3 | Velocity | | 6 | 3 | Velocity Gradient | | 7 | 3 | Acceleration | | 8 | 3 | Flux | | 9 | 3 | Elemental Force | | 10 |1 | Strain Energy | | 11 |1 | Strain Energy Density | | 12 |3 | Reaction Force | | 13 |1 | Kinetic Energy | | 14 |1 | Kinetic Energy Density | | 15 |3 | Hydrostatic Pressure | | 16 |1 | Coefficient of Pressure | | 17 |3 | Symmetric 2-Dimensional Elastic Stress Tensor (xx, yy, xy) | | 18 |3 | Symmetric 2-Dimensional Total Stress Tensor (xx, yy, xy) | | 19 |3 | Symmetric 2-Dimensional Elastic Strain Tensor (xx, yy, xy) | | 20 |3 | Symmetric 2-Dimensional Plastic Strain Tensor (xx, yy, xy) | | 21 |3 | Symmetric 2-Dimensional Total Strain Tensor (xx, yy, xy) | | 22 |3 | Symmetric 2-Dimensional Thermal Strain (xx, yy, xy) | | 23 |6 | Symmetric 3-Dimensional Elastic Stress Tensor (xx, yy, zz, xy, yz, zx) | | 24 |6 | Symmetric 3-Dimensional Total Stress Tensor (xx, yy, zz, xy, yz, zx) | | 25 |6 | Symmetric 3-Dimensional Elastic Strain Tensor (xx, yy, zz, xy, yz, zx) | | 26 |6 | Symmetric 3-Dimensional Plastic Strain Tensor (xx, yy, zz, xy, yz, zx) | | 27 |6 | Symmetric 3-Dimensional Total Strain Tensor (xx, yy, zz, xy, yz, zx) | | 28 |6 | Symmetric 3-Dimensional Thermal Strain (xx, yy, zz, xy, yz, zx) | | 29 |9 | General Elastic Stress Tensor (xx, yx, zx, xy, yy, zy, xz, yz, zz) | | 30 |9 | General Total Stress Tensor (xx, yx, zx, xy, yy, zy, xz, yz, zz) | | 31 |9 | General Elastic Strain Tensor (xx, yx, zx, xy, yy, zy, xz, yz, zz) | | 32 |9 | General Plastic Strain Tensor (xx, yx, zx, xy, yy, zy, xz, yz, zz) | | 33 |9 | General Total Strain Tensor (xx, yx, zx, xy, yy, zy, xz, yz, zz) | |____34____|9___|_General_Thermal_Strain_(xx,_yx,_zx,_xy,_yy,_zy,_xz,_yz,_zz)__________________| 500 G.7 ELEMENT RESULTS ENTITY (TYPE 148) G.7 Element Results Entity (Type 148) The number of result data values depends upon: (1) NV, the number of results data values per reporting location; (2) NRL, the number of result data reporting locations in a FEM element per layer; and (3) NL, the number of layers in the FEM element. The physical interpretation and location of the results data depends upon: (1) TYPE, the type of results data which is specified by using the form number in the Directory Data section (see Table G2); (2) RRF, the results reporting flag which associates results data with FEM element location; and (3) DLF, the data layer flag which specifies the FEM element layer location of the results data. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 148 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |**??03** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 148 |< n:a: > | #; ) | # | TYPE | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Entity Subscript field shall contain the Analysis Case Number. The Entity Label field optionally may contain the Analysis Label. The value of TYPE (see Table G2) indicates the physical interpretation of the finite element analysis result data. For a specific TYPE of data, multiple values are positioned within the Parameter Data record in the order in which they appear in the parenthetical expression in the description column of the table. Parameter Data Index__ Name____ Type___ Description___ 1 GNOTE Pointer Pointer to the DE of the General Note Entity that describes the analysis case. 2 SCN Integer Analysis Subcase number. If there is no subcase, then the value of this parameter should be zero. 3 TIME Real Analysis time value used for this subcase. (This time value is not the time that the analysis was executed, nor does it have anything to do with the amount of time that a computer took to execute the job. It is the time at which transient analysis results occur in the mathematical model.) 4 NV Integer Number of result values per FEM element reporting location. (The value of NV must agree with the form number specified in the Directory Data, see Table G2.) 5 RRF Integer Results Reporting Flag. This flag is used to associate the data with a FEM location. The following values are possible: 0 - Indicates that the results data pertains to the FEM ele- ment's nodes. 1 - Indicates that the results data pertains to the FEM ele- ment's centroid. 501 G.7 ELEMENT RESULTS ENTITY (TYPE 148) 2 - Indicates that the results data is constant on all faces and throughout the entire volume of the FEM element. 3 - Indicates that the results data pertains to the FEM ele- ment's Gauss points (reserved for future definition). 6 NE Integer Number of FEM elements defined in this entity. 7 EN(1) Integer FEM element number identifier for first element. 8 EP(1) Pointer Pointer to the DE of the first FEM Element Entity. 9 ITOP(1) Integer Element Topology type of first FEM element. 10 NL(1) Integer Number of layers per result data report location. This param- eter along with the form number indicates the total number of result values to be read for a particular FEM element. 11 DLF(1) Integer Data Layer Flag. This flag indicates other information neces- sary to interpret the actual layer position of the data. Five values are possible. They are: 0 - Indicates that a layer is not special. (NL must be 1 for this case.) 1 - Indicates the layer is the top surface of a FEM plate element. (NL must be 1 for this case.) 2 - Indicates the layer is the middle surface of a FEM plate element. (NL must be 1 for this case.) 3 - Indicates the layer is the bottom surface of a FEM plate element. (NL must be 1 for this case.) 4 - Indicates the layers are an ordered set of values from the top to the bottom surface of a FEM element. There are NL individual layers. 12 NRL(1) Integer Number of result data report locations for first FEM element. 13 RDRL(I) Integers The result data report locations for the FEM element. The values of RDRL depends on the results reporting flag, RRF. If RRF is: 0 - These are the node numbers for this FEM element at which result values are reported. There are NRL of them. 1 - This is FEM element centroidal results data. NRL should be 1 and this value should be zero. 2 - This is FEM element constant results data. NRL should be 1 and this value should be zero. 3 - These are a topologically ordered list of gauss points (re- served for future definition). There are NRL values for RDRL. .. . . . .. .. 13+NRL NUMV(1) Integer This value represents the total number of results contained in the following V array. It is the product of NV, NL, and NRL for this FEM element; e.g., for FEM element number one, NUMV(1) = NV*NL(1)*NRL(1). 14+NRL V(J,K,L) Reals The result data values of the FEM analysis for the first FEM element. The result data values are arranged in column major order; i.e., the leftmost subscript changes most rapidly. The subscripts are: (1) J is the value number that is incremented from 1 to NV (see Table G2); (2) K is the layer number that is incremented from 1 to NL(I); and (3) L is the results data report location index that is incremented from 1 to NRL(I). (The subscript I indicates that these values are dependent upon a particular FEM element.) 502 G.7 ELEMENT RESULTS ENTITY (TYPE 148) The loop through the V array is done by using the following FORTRAN code fragment: DO 10 L = 1, NRL(I) DO 20 K = 1, NL(I) DO 30 J = 1, NV READ(unit,*) V(J,K,L) 30 CONTINUE 20 CONTINUE 10 CONTINUE There are NUMV values for array V. . . (loop over number of elements) . P In subsequent index equations, let NLS = (7+(NL*NV+1)*NRL(I)); where I = 1 to NE-1 and NE represents the number of elements. Also, let NLSE = NLS + NRL(NE). 7+NLS EN(NE) Integer FEM element number identifier for last element. 8+NLS EP(NE) Pointer Pointer to the DE of the last FEM Element Entity. 9+NLS ITOP(NE) Integer Element Topology type of last FEM element. 10+NLS NL(NE) Integer Number of layers per result data report location for last FEM element. 11+NLS DLF(NE) Integer Data Layer Flag of last FEM element. 12+NLS NRL(NE) Integer Number of result data report locations for the last FEM ele- ment. 13+NLS RDRL(I) Integers The result data location list for the last FEM element. 13+NLSE NUMV(NE) Integer This value represents the total number of results contained in the V array for the last FEM element. 14+NLSE V(J,K,L) Reals The result data values of the FEM element analysis for the last FEM element. Additional pointers as required (see Section 2.2.4.4.2). 503 G.8 SELECTED COMPONENT ENTITY (TYPE 182) G.8 Selected Component Entity (Type 182) ECO505 The Selected Component Entity provides a means of selecting one component of a disjoint CSG solid. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 182 | ) |< n:a: > |< n:a: > | #; ) | 0; ) | 0; ) | 0; ) |**??03** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 182 |< n:a: > | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 BTREE Pointer Pointer to the DE of the Boolean Tree Entity 2 SELX Real X component of a point in or on the desired component 3 SELY Real Y component of a point in or on the desired component 4 SELZ Real Z component of a point in or on the desired component Additional pointers as required (see Section 2.2.4.4.2). 504 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY (TYPE 186) G.9 Manifold Solid B-Rep Object Entity (Type 186) ECO603 A manifold solid is a bounded, closed, and finite volume V in three dimensional Euclidean space, R3. V is restricted to be the closure of the interior of V which must be arcwise connected. There is no restriction on the number of voids within V or on the genus of the boundary surfaces. Discussion of the manifold solid from a graph theoretic view is contained in Appendix ??. The Manifold Solid B-Rep Object (MSBO) defines a manifold solid by enumerating its boundary. This boundary may be decomposed into its maximal connected components called shells. Each shell is composed of faces which have underlying surface geometry. The faces are bounded by loops of edges having underlying curve geometry. The edges are bounded by vertices whose underlying geometry is the point. Implicit in the representation is a concept of oriented uses of topological entities by containing entities. This allows the referencing entity to reverse the natural orientation of the referenced entity. The natural orientation is derived from the underlying geometry. Figure G2 illustrates the hierarchical nature of this representation. The vertex represents a location. The geometry underlying a vertex is a point in R3. An edge connects two vertices. It is bounded by two vertices (V1 and V2). It does not contain its bounds. The start and terminate vertices do not have to be distinct. Edges do not intersect except at their boundaries (i.e., vertices). The geometry underlying an edge is some portion of a curve in R3. The edge has a natural orientation in the same direction as its underlying curve in R3. Thus the edge is traced from start vertex to terminate vertex as the underlying curve is traced in the direction of increasing parameter value. Each edge is used once in each orientation and therefore should be referenced exactly twice in an MSBO. The loop is a path of oriented edges and vertices having the same start and terminate vertex. Typically, a loop represents a connected collection of face boundaries, seams, and poles of a single face (refer to Figures in Appendix ??). Its underlying geometry is a connected curve or a single point in R3. The loop is represented as an ordered list of oriented edges, edge-uses (EUi; i = 1; n), which has the following properties: o The terminal vertex of EUi is the initial vertex of EUi+1; i = 1; n - 1. o The loop is closed. This implies that the terminal vertex of EUn is the same as the initial vertex of EU1. o The orientation of the loop is defined to be the same as its constituent edge-uses which reference edges. Therefore the direction of the loop at an edge-use which references a vertex, A, can be taken from any edge-use having an underlying edge which has A as either its start or terminate vertex. The edge-use is an instancing of an edge or vertex into a loop. It consists of either an edge, an orientation, and optional parameter space curves (see the definitions of associated parameter space and collections in the Boundary Entity (Type 141)), or (in the case of a pole) a vertex and an optional parameter space curve. If the edge-use references an edge, then the orientation describes whether the direction of this use of the edge is in agreement with the natural orientation of the edge. If the orientation of the edge-use is in agreement with the edge, then the use is directed from the start vertex to the terminate vertex of the edge. If the orientation is not in agreement, then the use of the edge is directed from the terminate vertex to the start vertex. At any point the direction of an edge-use is called its topological tangent vector, T . See the face discussion to determine how to set the orientation. If the edge-use references a vertex, then no orientation is defined. 505 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY(TYPE 186) The face is a bound (partial) of an arcwise connected open subset of R3 and has finite area. It has an underlying surface, S, and is bounded by at least one loop. If more than one loop bounds a face, then the loops must be disjoint. The cross product, N x T , where N is in the same direction as the normal to S and T is the topological tangent vector of an edge-use in a loop bounding the face, points toward the material of the face. Note that this determines the edge-use orientation. The shell is represented as a set of edge connected oriented uses of faces (face-use). The shell divides R3 into two arcwise connected open subsets (parts). The normal of the shell is in the same direction as the normal of its face-uses. The normal of each face-use of the shell points toward the same part of R3. The normal of the face-use is assumed to be in the direction of the normal of the underlying surface of the face unless the face-use orientation indicates it needs to be reversed. The faces used by the shell are connected to each other only via edges. Each edge must be used exactly twice, once in each orientation, in the shell. The MSBO describes the boundaries of the solid via oriented uses of shells (shell-use). It is the orientation of the use of the shells which define the volume of R3 the MSBO is describing. The orientation of the shell-use is determined by the shell-use normal which is either in the same or opposite direction as the shell normal. By convention the direction of the shell-use normal points away from the part of R3 being described. One shell, the outer, must completely enclose all the other shells and only the outer shell may enclose a shell. The geometric entities that may be used in an MSBO consist of the point, curve, and surface. The point data is embedded in the Vertex Entity for reasons of data compaction. The entities that may be used for a curve are restricted to the subset identified for Form 1 of the Edge Entity. The subset of surface entities that can be used is identified in Form 1 of the Face Entity. To avoid processing difficulties the use of nested constructs is discouraged. For example allowing the Edge to point at a Composite Curve which uses an Offset Curve as one of its components is not recommended. The geometric surface definition used to specify the geometry of a face must be a 2-manifold which is arcwise connected, oriented, bounded, non-self-intersecting, and has no handles within the region underlying the face. The surfaces can be represented implicitly, F (x; y; z) = 0, or parametrically, S(u; v). In the implicit representation the direction of the surface normal (orientation) is defined by the gradient of F (x; y; z). If the surface is represented parametrically, the surface normal (orienta- tion) is given by the cross product of the partial derivatives (in the order stated) with respect to u and v. The model space (R3) curves underlying the edges are assumed to be parametrically represented, have a unique non-zero tangent vector at each point, lie on the two (2) intersecting surfaces, and be non-self intersecting on the open segment underlying the edge. Note that, due to seams and poles, the representation of the pre-image of the curve, C, in the parameter space of the surfaces, S1 and S2, can consist of ordered lists of curves, C1 *i; i = 1; n for surface S1 and C2 *j; j = 1; m for surface S2. The C1i given by the composition (S1 O C1 *i; i = 1; n) and the C2j given by the composition (S2 O C2 *j; j = 1; n) form composite curves in R3 which are coincident with the curve C. The optional parameter space curves, C*i; i = 1; n, referenced by an edge-use are in the parameter space defined by the surface underlying the face bounded by the loop containing the referencing edge- use. These curves are assumed to be ordered in the list and oriented such that as the parameter goes from its initial to its final value for each parameter space curve the composition (S O C*i; i = 1; n) produces a composite curve, Ci; i = 1; n, which is coincident with the curve underlying the edge. The orientation of Ci; i = 1; n is in agreement with the orientation of the edge-use. See Appendix ?? for examples that illustrate the general model for any entity modeling of a Cylinder, Sphere, and Torus. 506 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY(TYPE 186) The following is a summary of the major constraints on the topological and geometrical entities that may be used in representing the MSBO: o The MSBO must contain exactly one outer shell o The volume described by the MSBO must be arcwise connected. This implies that voids inside the outer shell may not be contained in another void. o The shells of an object must be disjoint. o The direction of the normals of the face-uses of a shell, reversed if the shell orientation flag is false, must point away from the portion of R3 that is in the volume being communicated by the MSBO. o The face interiors, edge interiors, and vertices must not intersect. o Only the MSBO and the R3 curve and surface entities may have a transform. The following topological entities may be used in representing the MSBO: o Manifold Solid B-Rep Object (MSBO) Entity (Type 186, Form 0) - Identifies the shell-uses (shell + orientation) which make up the MSBO. o Shell Entity (Type 514, Form 1) - defines a boundary for a region of R3 by identifying and orienting the use of faces. o Face Entity (Type 510, Form 1) - implements the topological concept of a portion of a boundary of R3. The underlying surface is required. o Loop Entity (Type 508, Form 1) - identifies and orients the use of edges as bounds (partial) of faces. It also establishes the optional association of parameter space geometry. o Edge List Entity (Type 504, Form 1) - models an edge or a list of edges. Each edge referenced in an MSBO must be modeled in only one Edge List Entity. Thus all references to a specific edge must use the same Edge List Entity and list index. The underlying curve geometry in R3 is required. o Vertex List Entity (Type 502, Form 1) - models a vertex or a list of vertices. Each vertex referenced in an MSBO must be modeled in only one Vertex List Entity. Thus all references to a specific vertex must use the same Vertex List Entity and list index. Figure G3 illustrates the construction of an MSBO. 507 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY(TYPE 186) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 186 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > | 0; ) | 0; ) |???????? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 186 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 SHELL Pointer Pointer to the DE of the shell 2 SOF Logical Orientation flag of shell with respect to its underlying faces (True = agrees) 3 N Integer Number of void shells, or zero 4 VOID1 Pointer Pointer to the DE of the first void shell 5 VOF1 Logical Orientation flag of first void shell .. . . . .. .. 2+2*N VOIDN Pointer Pointer to the DE of the last void shell 3+2*N VOFN Logical Orientation flag of last void shell Additional pointers as required (see Section 2.2.4.4.2). 508 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY(TYPE 186) Figure G2. Hierarchical nature of the MSBO 509 G.9 MANIFOLD SOLID B-REP OBJECT ENTITY(TYPE 186) Figure G3. Construction of the MSBO 510 G.10 PLANE SURFACE ENTITY (TYPE 190) G.10 Plane Surface Entity (Type 190) ECO603 The plane surface is defined by a point on the plane and the normal direction to the surface (Fig- ure G4). If C is the point and z is the unitized normal direction then the plane surface is defined as the collection of all points r in Euclidean 3-space satisfying the equation r . z - C . z = 0 The data (Figure G5) for the parameterized surface form is to be interpreted as follows: C = LOCATION z = d = x = y = and the surface is parameterized as oe(u; v) = C + ux + vy where the parameterization range is -1 < u; v < 1. Note that d must be distinct from z and should be (approximately) perpendicular to z. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________ |__Form__|_________Meaning_________|__ | 0 |Unparameterized surface | |____1____|Parameterized_surface_____|_ The plane surface type is unbounded unless it is subordinate to another entity, such as the Bounded Surface Entity (Type 143) or the Trimmed Parametric Surface Entity (Type 144), that points to its bounding geometry. If the Subordinate Entity Switch for this entity is set to Independent, then the plane is infinite in extent. This entity may not be used as a clipping plane for a View Entity (Type 410). 511 G.10 PLANE SURFACE ENTITY (TYPE 190) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 190 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 190 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on the surface (LOCATION) 2 DENRML Pointer Pointer to the DE of the surface normal direction (NORMAL) Additional pointers as required (see Section 2.2.4.4.2). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 190 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**????** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 190 | # | #; ) | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on the surface (LOCATION) 2 DENRML Pointer Pointer to the DE of the surface normal direction (NORMAL) 3 DEREFD Pointer Pointer to the DE of the reference direction (REFDIR) Additional pointers as required (see Section 2.2.4.4.2). 512 G.10 PLANE SURFACE ENTITY (TYPE 190) Figure G4. Defining data for unparameterized plane surface (Form Number = 0). Figure G5. Defining data for parameterized plane surface (Form Number = 1). 513 G.11 RIGHT CIRCULAR CYLINDRICAL SURFACE ENTITY (TYPE 192) G.11 Right Circular Cylindrical Surface Entity (Type 192) ECO603 The right circular cylindrical surface is defined by a point on the axis of the cylinder, the direction of the axis of the cylinder and a radius (Figure G6). The positive direction of the surface normal is outwards from the axis. If a local coordinate system is defined with the origin at the axis point and the Z axis in the axis direction, then the equation of the surface in this system is S = 0, where S(x; y; z) = x2 + y2 - r2 and the positive direction of the surface normal is in the direction of increasing S. That is, the normal, N, to the surface at any point on the surface is given by N = (Sx; Sy; Sz) The data for the parameterized form of the surface (Figure G7) is to be interpreted as follows: C = LOCATION z = d = x = y = r = RADIUS and the surface is parameterized as oe(u; v) = C + r(cos(u)x + sin(u)y) + vz where the parameterization range is 0 u 360 degrees and -1 < v < 1. Note that d must be distinct from z and should be (approximately) perpendicular to z. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________ |__Form__|_________Meaning_________|__ | 0 |Unparameterized surface | |____1____|Parameterized_surface_____|_ This surface type is intended to represent the geometry underlying topology, and may only be pointed to by a Face Entity (Type 510, Form 1). The Subordinate Entity Switch must always be set to Physically Dependent, i.e., independent instances of this entity are not permitted. 514 G.11 RIGHT CIRCULAR CYLINDRICAL SURFACE ENTITY (TYPE 192) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 192 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 192 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on axis (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 RADIUS Real Value of radius (> 0) Additional pointers as required (see Section 2.2.4.4.2). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 192 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 192 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on axis (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 RADIUS Real Value of radius (> 0) 4 DEREFD Pointer Pointer to the DE of the reference direction (REFDIR) Additional pointers as required (see Section 2.2.4.4.2). 515 G.11 RIGHT CIRCULAR CYLINDRICAL SURFACE ENTITY (TYPE 192) Figure G6. Defining data for unparameterized right circular cylindrical surface (Form Number = 0). 516 G.11 RIGHT CIRCULAR CYLINDRICAL SURFACE ENTITY (TYPE 192) Figure G7. Defining data for parameterized right circular cylindrical surface (Form Number = 1). 517 G.12 RIGHT CIRCULAR CONICAL SURFACE ENTITY (TYPE 194) G.12 Right Circular Conical Surface Entity (Type 194) ECO603 The right circular conical surface is defined by a point on the axis of the cone, the direction of the axis of the cone, the radius of the cone at the axis point and the cone semi-angle (Figure G8). The positive direction of the surface normal is outwards from the axis. If a local coordinate system is defined with the origin at the axis point and the Z axis in the axis direction, then the equation of the surface in this system is S = 0, where S(x; y; z) = x2 + y2 - (r + z tan s)2 where s is the cone semi-angle and r is the given cone radius. The positive direction of the surface normal is in the direction of increasing S. At any point on the surface the surface normal N is N = (Sx; Sy; Sz) The data for the parameterized form of the surface (Figure G9) is to be interpreted as follows: C = LOCATION z = d = x = y = r = RADIUS s = ANGLE and the surface is parameterized as oe(u; v) = C + (r + v tan(s))(cos(u)x + sin(u)y) + vz where the parameterization range is 0 u 360 degrees and -1 < v < 1. Note that d must be distinct from z and should be (approximately) perpendicular to z. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________ |__Form__|_________Meaning_________|__ | 0 |Unparameterized surface | |____1____|Parameterized_surface_____|_ This surface type is intended to represent the geometry underlying topology, and may only be pointed to by a Face Entity (Type 510, Form 1). The Subordinate Entity Switch must always be set to Physically Dependent, i.e., independent instances of this entity are not permitted. 518 G.12 RIGHT CIRCULAR CONICAL SURFACE ENTITY (TYPE 194) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 194 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 194 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on axis (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 RADIUS Real Value of radius at axis point ( 0) 4 SANGLE Real Value of semi-angle in degrees (> 0 and < 90) Additional pointers as required (see Section 2.2.4.4.2). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 194 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 194 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the point on axis (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 RADIUS Real Value of radius at axis point ( 0) 4 SANGLE Real Value of semi-angle in degrees (> 0 and < 90) 5 DEREFD Pointer Pointer to the DE of the reference direction (REFDIR) Additional pointers as required (see Section 2.2.4.4.2). 519 G.12 RIGHT CIRCULAR CONICAL SURFACE ENTITY (TYPE 194) Figure G8. Defining data for unparameterized right circular conical surface (Form Number = 0). Figure G9. Defining data for parameterized right circular conical surface (Form Number = 1). 520 G.13 SPHERICAL SURFACE ENTITY (TYPE 196) G.13 Spherical Surface Entity (Type 196) ECO603 The spherical surface is defined by the center point and the radius (Figure G10). The positive direction of the surface normal is outwards from the center. If a local coordinate system is defined with the origin at the center point then the equation of the surface in this system is S = 0, where S(x; y; z) = x2 + y2 + z2 - r2 and the positive direction of the surface normal is in the direction of increasing S. The normal, N, to the surface at any point on the surface is given by N = (Sx; Sy; Sz) The data for the parameterized form of the surface (Figure G11) is to be interpreted as follows: C = LOCATION z = d = x = y = r = RADIUS and the surface is parameterized as oe(u; v) = C + r cos(v)(cos(u)x + sin(u)y) + r sin(v)z where the parameterization range is 0 u 360 degrees and -90 v 90 degrees. Note that d must be distinct from z and should be (approximately) perpendicular to z. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________ |__Form__|_________Meaning_________|__ | 0 |Unparameterized surface | |____1____|Parameterized_surface_____|_ This surface type is intended to represent the geometry underlying topology, and may only be pointed to by a Face Entity (Type 510, Form 1). The Subordinate Entity Switch must always be set to Physically Dependent, i.e., independent instances of this entity are not permitted. 521 G.13 SPHERICAL SURFACE ENTITY (TYPE 196) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 196 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 196 | # | #; ) | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the center point (LOCATION) 2 RADIUS Real Value of radius (> 0) Additional pointers as required (see Section 2.2.4.4.2). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 196 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 196 | # | #; ) | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the center point (LOCATION) 2 RADIUS Real Value of radius (> 0) 3 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 4 DEREFD Pointer Pointer to the DE of the reference direction (REFDIR) Additional pointers as required (see Section 2.2.4.4.2). 522 G.13 SPHERICAL SURFACE ENTITY (TYPE 196) Figure G10. Defining data for unparameterized spherical surface (Form Number = 0). Figure G11. Defining data for parameterized spherical surface (Form Number = 1). 523 G.14 TOROIDAL SURFACE ENTITY (TYPE 198) G.14 Toroidal Surface Entity (Type 198) ECO603 The toroidal surface is defined by the center point, the axis direction and the major and minor radii (Figure G12). The positive direction of the surface normal is outwards from the center of the generating circle. If a local coordinate system is defined with the origin at the axis point and the Z axis in the axis direction, then the equation of the surface in this system is S = 0, where p ________ S(x; y; z) = x2 + y2 + z2 - 2R x2 + y2 - r2 + R2 and the positive direction of the surface normal is in the direction of increasing S. The surface normal, N, at any point on the surface is given by N = (Sx; Sy; Sz) The data for the parameterized form of the surface (Figure G13) is to be interpreted as follows: C = LOCATION z = d = x = y = R = MAJRAD r = MINRAD and the surface is parameterized as oe(u; v) = C + (R + r cos(u))(cos(v)x - sin(v)y) + r sin(u)z where the parameterization range is 0 u; v 360 degrees. Note that d must be distinct from z and should be (approximately) perpendicular to z. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: ______________________________________ |__Form__|_________Meaning_________|__ | 0 |Unparameterized surface | |____1____|Parameterized_surface_____|_ This surface type is intended to represent the geometry underlying topology, and may only be pointed to by a Face Entity (Type 510, Form 1). The Subordinate Entity Switch must always be set to Physically Dependent, i.e., independent instances of this entity are not permitted. 524 G.14 TOROIDAL SURFACE ENTITY (TYPE 198) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 198 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 198 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the center point (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 MAJRAD Real Value of major radius (> 0) 4 MINRAD Real Value of minor radius (> 0 and < MAJRAD) Additional pointers as required (see Section 2.2.4.4.2). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 198 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |**01??** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 198 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DELOC Pointer Pointer to the DE of the center point (LOCATION) 2 DEAXIS Pointer Pointer to the DE of the axis direction (AXIS) 3 MAJRAD Real Value of major radius (> 0) 4 MINRAD Real Value of minor radius (> 0 and < MAJRAD) 5 DEREFD Pointer Pointer to the DE of the reference direction (REFDIR) Additional pointers as required (see Section 2.2.4.4.2). 525 G.14 TOROIDAL SURFACE ENTITY (TYPE 198) Figure G12. Defining data for unparameterized toroidal surface (Form Number = 0). Figure G13. Defining data for parameterized toroidal surface (Form Number = 1). 526 G.15 CURVE DIMENSION ENTITY (TYPE 204) G.15 Curve Dimension Entity (Type 204) ECO566 A Curve Dimension Entity consists of a general note, one or two curves which can be any of the parameterized curves (with the exception of the case where both curves are Line Entities (Type 110), in which case a Linear Dimension (Type 216) is appropriate), two leaders, and zero, one, or two witness lines. Refer to Figure G14 for examples. Each leader entity consists of one tail segment of nonzero length which begins with an arrowhead, and which serves only to define the orientation of the arrowhead. The start and terminate point of a curve are determined by its parameterization. The start point of the curve has the lowest parameterization value; the terminate point of the curve has the highest parameterization value. In the case where one curve is defined, the coordinates of the curve start point coincide with the coordinates of the arrowhead of the first leader. The coordinates of the curve terminate point coincide with the coordinates of the arrowhead of the second leader. In the case where two curves are defined, the coordinates of the start point of the first curve coincide with the coordinates of the arrowhead of the first leader. The coordinates of the terminate point of the second curve coincide with the coordinates of arrowhead of the second leader. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 204 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 204 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DECURV1 Pointer Pointer to the DE of the first curve entity 3 DECURV2 Pointer Pointer to the DE of the second curve entity, or zero 4 DEARR1 Pointer Pointer to the DE of the first Leader Entity 5 DEARR2 Pointer Pointer to the DE of the second Leader Entity 6 DEWIT1 Pointer Pointer to the DE of the first Witness Line Entity, or zero 7 DEWIT2 Pointer Pointer to the DE of the second Witness Line Entity, or zero Additional pointers as required (see Section 2.2.4.4.2). 527 G.15 CURVE DIMENSION ENTITY (TYPE 204) Figure G14. Examples Defined Using the Curve Dimension Entity 528 G.16 ADDITIONAL GENERAL NOTE FCS G.16 Additional General Note FCs Two additional FCs_FC 19 (OCR-B) and FC 2001 (Kanji)_are defined for use by the General ECO547 Note Entity (Type 212). See Section 4.58 for more detail. ECO562 FC 19 specifies OCR-B [ISO1073] and is defined in Figure G15. FC 2001 specifies Japanese characters defined by the JIS Kanji (Kuten) Code Table [JIS6226]. ECO547 Values in that table are implemented here as a two hexadecimal digit row number followed by a two hexadecimal digit column number. (Leading or embedded zeroes, or both, shall be used to avoid confusion.) The fact that four consecutive ASCII characters are being used to represent one character in the alphabet is implicit in the FC, and a postprocessor which supports this FC shall behave accordingly. The hexadecimal row/column codes must be biased by 20 (decimal 32). As an example, the char- acters represented by the decimal Kuten codes 20, 33 ("KAN") and 27, 90 ("JI") must be coded as "8H34413B7A" (20 + 32 = 5210 = 3416, etc.). The same value must appear in the NC field of the PD record as appears in the Hollerith constant, e.g., even though 2 Kanji characters are represented as 8 Hollerith characters, NC must have a value of 8 rather than 2. Preprocessors must define the text box height and box width so as to accurately reflect the display box size for the text string. Postprocessors which cannot display Japanese characters must process this FC as if it were FC 1 (default style for ASCII character set). The Rotate Internal Text Flag (VH) field in the PD record must be used to convey vertical text orientation. The Imbedded Font Change form (Form 2) must be used when the text note combines mixed English and Japanese. The use of imbedded "escape" characters or metacharacters is forbidden; all of the characters are assumed to be for display. 529 G.16 ADDITIONAL GENERAL NOTE FCS ________________________________________________________________________________________________ | | BL | | |0 | 0 | | @ | @ | | P | P | | | | |p | p | | |_|_________|____|_|_____|______|_|______|______|_|_____|_______|_|_____|_______|_|_____|______|_| | | ! |! | |1 | 1 | | A | A | | Q | Q | | a | a | | q | q | | |_|________|_____|_|____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | " |" | | 2 | 2 | | B | B | | R | R | | b | b | | r | r | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|________| | | | # |# | | 3 | 3 | | C | C | | S | S | | c | c | | s | s | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | $ |$ | | 4 | 4 | | D | D | | T | T | | d | d | | t | t | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|________| | | | % |% | | 5 | 5 | | E | E | | U | U | | e | e | | u | u | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|______|_|_____|_______|_| | | & |& | | 6 | 6 | | F | F | | V | V | | f | f | |v | v | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | | | | 7 | 7 | | G | G | | W | W | | g | g | | w | w | | |_|_______|____|_|______|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | ( |( | | 8 | 8 | | H | H | | X | X | | h | h | | x | x | | |_|________|____|_|_____|_______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | ) |) | | 9 | 9 | | I | I | | Y | Y | | i | i | |y | y | | |_|________|____|_|_____|_______|_|_____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | * |* | | : | : | |J | J | | Z | Z | | j | j | |z | z | | |_|________|____|_|_____|________|_|____|_______|_|_____|______|_|______|_______|_|____|_______|_| | | + |+ | | ; | ; | |K | K | | [ | [ | |k | k | | { | { | | |_|________|____|_|_____|________|_|____|______|_|______|________|_|____|______|_|_____|_______|_| | | , | , | |< | < | | L | L | | " | " | | l | l | |_ | I | | |_|________|______|_|____|______|_|_____|_______|_|_____|______|_|______|_______|_|____|________| | | | - |- | |= | = | | M | M | | ] | ] | |m | m | | } | } | | |_|________|_____|_|____|_______|_|_____|______|_|______|________|_|____|______|_|_____|_______|_| | | . | . | |> | > | | N | N | | ^ | ^ | | n | n | | " | " | | |_|________|______|_|____|______|_|_____|______|_|______|______|_|______|______|_|_____|_______|_| | | / |/ | | ? | ? | | O | O | | _ | _ | | o | o | | |_|________|____|_|_____|_______|_|_____|______|_|______|_______|_|_____|______|_| Figure G15. General Note Font (OCR-B) Specified by FC 19 530 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) G.17 New General Note Entity (Type 213) ECO567 The sequence of strings within the note must be from left to right and top to bottom within the defined "imaginary" text containment area. This entity assumes all text strings are related and coplanar. G.17.1 Field Descriptions 1 TXTCW - width of an imaginary text containment area drawn around all text strings within the note. There is no space between the characters and the imaginary box lines. The text containment width is established after the slant angle (SLn), rotation angle (An), character angle (CHRANGn), and mirror (Mn) are applied. See Figure G16. All text must be within the defined text containment area, including descenders. 2 TXTCH - height of an imaginary text containment area drawn around all text strings within the note. There is no space between the characters and the imaginary box lines. The text containment height is established after the slant angle (SLn), rotation angle (An), character angle (CHRANGn), and mirror (Mn) are applied. See Figure G16. All text must be within the defined text containment area, including descenders. 3 JUSTCD - justification of all text strings relative to the text containment area. 4 TXTCX, TXTCY, TXTCZ - location of the upper left corner of the imaginary containment area drawn around all text string. See Figure G16. 7 TXTAG - rotation angle of the text box in radians. See Figure G16. 8 BASELX, BASELY, BASELZ - starting position of the first base line of the text strings. The base line is the imaginary line upon which the normal characters are placed. Control codes are used to place characters in a position away from the baseline. The superscript is an example of a control code which moves the character away from the baseline. The baseline is horizontal and can be rotated with TXTAG. See Figure G16. 11 NILS - normal interline spacing between baselines. The distance is between two lines of text which only have the new line control code associated with both. The LSPACE would not be normal if fractions, superscript, subscript, etc., text is on the same base line. In Figure G16, the distance between the base line for the string "TOLERANCE AND" and the base line for the string "CENTERED" is the normal interline space. The distance between the baseline for the string "5.00" and the baseline for the string "TOLERANCE AND" is not the normal interline spacing. A negative NILS is allowed. See Figure G16. 13 FIXVAR - integer switch indicating whether the character and font set specified is displayed with fixed spacing (i.e., an "I" uses the same amount of space as a "M") or is variable spaced. Box width WTn establishes the outer boundary into which the text TEXTn must fit. 14 CHRWID - the width of a character excluding its preceding and succeeding spacing. The char- acter width is not changed by the slant angle, rotation angle, or character angle. Variable width character display fonts: The width of the widest character in the font, typically the character capital "M". Fixed width character display fonts: The width of any character. The character width must be a positive nonzero value. See Figures G18, G22, and G23. 531 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) 15 CHRHGT - the height of a capital character, typically the character "M". The character height is not changed by applying the slant angle, rotation angle, or character angle. The character height must be a positive nonzero value. See Figures G18, G22, and G23. 16 CSPACE - inter-character spacing Fixed width character display fonts: The distance between the right side of one character and the left side of the next character in the same text string. A negative CSPACE is allowed which permits characters within a string to overlap. The lower limit of a negative CSPACEn is the width of a character (CHRWIDn) within the string. See Figures G18, G19, G22, and G23. Variable width character display fonts: Intercharacter spacing is multiplied by the standard spacing in the kerning table for the font. A value of one is the default. Zero is the minimum value and indicates that the characters touch. Overlapping of variable width fonts is not permitted. The character interspace is measured before the slant angle, rotation angle, or character angle are applied. The Intercharacter Spacing Property Entity (Type 406, Form 18) may not be attached to this entity. 17 LSPACE - indicates the distance between the base line of the nth text string and the base line of the previous line of text. It is only valid for a new line after the first line. It is not valid and must be set to zero for the first substring or for substrings which are a continuation of an existing line. This value is helpful when consecutive strings are not displayed horizontally or when the first substring of the new line is not placed on the baseline. For example, a dimension with upper and lower tolerances and appended text followed by a second line of appended text: The LSPACE value for the second through fourth strings is meaningless since they are displayed on the same "line". But the LSPACE value for the fifth string will give the proper distance between the first and fifth string. A negative LSPACE is allowed. See Figure G17. 18 FONT - display font style of the character set. The existing FC is renamed CHRSET which is the character set. It is the functional interpretation of the set of symbols. For example, the 1003 is a character set defining different symbols (CHRSET), whereas font 18 Helvetica is a font display style (FONT). Some special symbols within a character set may not be affected by the font style. ___________________________________ |__FONT__|________Meaning_______|__ | 1 |Standard Block | | 2 |LeRoy | | 3 |Futura | | 6 |Comp 80 | | 12 |News Gothic | | 13 |Lightline Gothic | | 14 |Simplex Roman | | 17 |Century Schoolbook | | 18 |Helvetica | |____19____|OCR_(ISO1073)______|___ 19 CHRANG - angle of the character relative to the base line (0:0 CHRANG 2ss). This value is different than the rotation angle or slant angle. The default value is 0.0. The character angle is applied after the slant angle has been applied. See Figures G21 and G23. 532 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) 20 CCTEXT - string of control code sequences that are applied to the string of displayed characters. The codes are expressed as pairs of characters which identify what action must be taken prior to the display of the text string. The order that the control codes are presented in CCTEXT must be preserved when conditions call for imbedding unlike control codes (e.g., boxing, underscore, and overscore). Some control codes can be nested to any level. The corresponding ending control codes must be defined in all cases. 22 WT - box width is established after the rotation angle, slant angle, and character angle have been applied. See Figures G18, G22, and G23. 23 HT - box height is established after the rotation angle, slant angle, and character angle have been applied. See Figure G23. 25 SL - slant angle is in addition to that already predefined in the font. See Figures G20, G21, G22, and G23. 26 A - Rotation angle is relative to the positive x axis in construction space, and is independent of the text containment angle (TXTAG) and may be different from the text containment angle. See Figures G20 and G21. G.17.2 Control Codes Below is a list of currently defined control sequences. NOTE: The character "Z" is used to indicate the end of a control code type. For example, SU...SZ represent Superscript start and Superscript end. All conditions are implicitly terminated at the end of the final text substring. G.17.2.1 Control Codes Which Cannot Be Nested CC - Change character/font set. This is to indicate to a postprocessor that the only reason that this string is separate is to change character sets. This might be used if a special character is to be used within the context of a fraction or tolerance string. BL - Base Line. The base line is defined as the first string in the note until a "new line" is encountered which redefines the "base line". If the initial strings are such that they do not define a base line, the string which contains the base line control code can derive its origin from the X and Y start positions. The strings which do not define a base line are all tolerance, fraction, and super- and subscript control coded strings. NL - New Line. This condition is used to indicate a new base line is being defined. BD - Bold text display start. BZ - Bold text display end. IT - Italics text display start. IZ - Italics text display end. TB - Tolerance text, bilateral start. TT - Tolerance, text being toleranced. TU - Tolerance text, upper portion start. 533 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) TL - Tolerance text, lower portion start. TZ - Tolerance text end (all types). US - Underscore start. UZ - Underscore end. OS - Overscore start. OZ - Overscore end. ES - Enclosing Separator. This causes the display of a vertical line relative to the rotation angle to the text, that extends from the top of the enclosing symbol to the bottom of the enclosing symbol at the point of the text. The ES code is not nested, therefore there is not an ending code for it. See Figure G17. G.17.2.2 Control Codes Which Can Be Nested En -_Enclosing_Symbol_start._The_value_n_will_determine_the_type_of_symbol_to_be_used:________ |__Value__|__________________________________Meaning___________________________________|__ | 1 |Standard Size Box - half character height above and below, half character | | | | | |width on each side | | 2 |Oversized Box - full character height above and below, full character width | | | | || |on|each side || || 3 |Undersized|Box - no space between characters and lines of the box || | 4 |Bullet Right - box with semi-circle arc for right side | || 5 |Bullet|Left - box with semi-circle arc for left side || || 6 |Capsule|- box with both ends replaced by arcs || || 7 |Flag|Note Start - per Entity Type 208 definition || |____8____|Lozenge_-_box_where_sides_are_replaced_by_<_and_>______________________________| EZ - Enclosing Symbol End. Stop the display of the lowest nested enclosing symbol that is currently ON. HU - Horizontally aligned fraction, upper portion start. HL - Horizontally aligned fraction, lower portion start. HZ - Horizontally aligned fraction, upper or lower end. VU - Vertically aligned fraction, upper portion start. VL - Vertically aligned fraction, lower portion start. VZ - Vertically aligned fraction, upper or lower end DU - Diagonally aligned fraction, upper portion start. DL - Diagonally aligned fraction, lower portion start. DZ - Diagonally aligned fraction, upper or lower end. SU - Superscript text start. SL - Subscript text start. SZ - Superscript or Subscript text end. 534 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 213 | ) |< n:a: > | 1 | #; ) | 0; ) | 0; ) | 0; ) |????01** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 213 | # | #; ) | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 TXTCW Real Width of text containment area of all strings in the note 2 TXTCH Real Height of text containment area of all strings in the note 3 JUSTCD Integer Justification code of all strings within the note: 0 = no justification 1 = right justified 2 = center justified 3 = left justified 4 TXTCX Real Text containment area location point X 5 TXTCY Real Text containment area location point Y 6 TXTCZ Real Z depth from TXTCX,TXTCY plane 7 TXTAG Real Rotation Angle of text containment area in radians 8 BASELX Real Position of first base Line 9 BASELY Real Position of first base Line 10 BASELZ Real Z depth from BASELX,BASELY plane 11 NILS Real Normal Interline spacing 12 NS Integer Number of Text Strings 13 FIXVAR1 Integer Fixed/Variable width character display: 0 = Fixed 1 = Variable 14 CHRWID1 Real Character Width 15 CHRHGT1 Real Character Height 16 CSPACE1 Real Inter-character spacing 17 LSPACE1 Real Interline spacing 18 FONT1 Integer Font style 19 CHRANG1 Real Character Angle 20 CCTEXT1 String Control Code String 21 NC1 Integer Number of characters in the first string (TEXT1) or zero. The number of characters (NCn) must always be equal to the char- acter count of its corresponding text string (TEXTn) 22 WT1 Real Box Width 23 HT1 Real Box Height 24 CHRSET1 Integer Character Set Interpretation (default=1): or 1 = Standard ASCII Pointer 1001 = Symbol Font1 1002 = Symbol Font2 1003 = Symbol Font3 535 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) 25 SL1 Real Slant angle of TEXT1 in radians (ss=2 is the value for no slant angle and is the default) 26 A1 Real Rotation angle in radians for TEXT1 27 M1 Integer Mirror Flag: 0 = no mirroring 1 = mirror axis is perpendicular to text base line 2 = mirror axis is text base line 28 VH1 Integer Rotate internal text flag: 0 = text horizontal 1 = text vertical 29 XS1 Real Text start point 30 YS1 Real Text start point 31 ZS1 Real Z depth from XT,YT plane 32 TEXT1 String First text string .. . . . .. .. 20*NS-7 FIXVARN Integer Fixed/Variable width character display . .. . .. ... 20*NS+12 TEXTN String Last text string Additional pointers as required (see Section 2.2.4.4.2). The following control code string and text string values apply to Figure G16 (NS = 6 in this example): _________________________________________________________________ |__Parameter__|__Value__|_||__Parameter__|________Value________|_ | CCTEXT1 |2HTU | | TEXT1 | 5H+1.00 | | CCTEXT2 |4HTLTZ | | TEXT2 | 5H-1.00 | | CCTEXT3 |4HTTTZ | | TEXT3 | 4H5.00 | | CCTEXT4 |4HTZNL | | TEXT4 | 13HTOLERANCE AND | | CCTEXT5 |2HNL | | TEXT5 | 8HCENTERED | |____CCTEXT6____|2HNL____|_|___TEXT6_____|_4HTEXT______________|_ The following control code string and text string values apply to Figure G17 (NS = 6 in this example): ______________________________________________________ |__Parameter__|___Value___|_||__Parameter__|_Value__|_ | CCTEXT1 |2HTT | | TEXT1 | 3HAAA | | CCTEXT2 |2HTU | | TEXT2 | 3H567 | | CCTEXT3 |4HTLTZ | | TEXT3 | 4H1234 | | CCTEXT4 |4HNL6TT | | TEXT4 | 3HCCC | | CCTEXT5 |2HTU | | TEXT5 | 2H56 | |____CCTEXT6____|4HTLTZ___|_|___TEXT6_____|__2H78____|_ 536 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Figure G16. Text Containment Area (see text for CCTEXTn and TEXTn values) Figure G17. Character Height, Inter-line Spacing (see text for CCTEXTn and TEXTn values) 537 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Figure G18. Character Width, Interspace, Box Width Figure G19. Examples of Fixed Width Character Interspace 538 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Figure G20. Rotation, Slant and Character Angle Figure G21. Text Containment Area 539 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Figure G22. Character Height, Width, Interspace, Box Width 540 G.17 NEW GENERAL NOTE ENTITY (TYPE 213) Figure G23. Character Height, Width, Interspace, Box Width 541 G.18 LINEAR DIMENSION ENTITY (TYPE 216, FORMS 0,1,2) G.18 Linear Dimension Entity (Type 216, Forms 0,1,2) ECO512 Three forms_Form Numbers 0,1, and 2_of the Linear Dimension Entity are defined below. See Section 4.61 for more detail. ______________________________________________________ |__Form__|________________Meaning_________________|___ | 0 |Linear dimension of undetermined form | | 1 |Linear dimension of diameter form | |____2____|Linear_dimension_of_radius_form__________|_ 542 G.19 ORDINATE DIMENSION ENTITY (TYPE 218, FORM 1) G.19 Ordinate Dimension Entity (Type 218, Form 1) ECO541 This additional form of the Ordinate Dimension Entity (Type 218) is defined below. See Section 4.62 for more detail. This second form of the Ordinate Dimension Entity (Type 218) allows for both a witness/leader line and a supplemental leader as shown in the example in Figure G24. The entity pointed to by DEORD defines the ordinate position being dimensioned. The entity pointed to by DESUPP is supplemental to those systems that may support it. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 218 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 218 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEORD Pointer Pointer to the DE of the Witness Line Entity 3 DESUPP Pointer Pointer to the DE of the Leader (Arrow) Entity Additional pointers as required (see Section 2.2.4.4.2). 543 G.19 ORDINATE DIMENSION ENTITY (TYPE 218, FORM 1) Figure G24. Example Defined Using the Ordinate Dimension Entity 544 G.20 RADIUS DIMENSION ENTITY (TYPE 222, FORM 1) G.20 Radius Dimension Entity (Type 222, Form 1) This additional form of the Radius Dimension Entity (Type 222) is defined below. See Section 4.64 for more detail. This second form of the existing Radius Dimension Entity (Type 222) accounts for the occasional need to have two Leader (Arrow) Entities referenced. An example is shown in Figure G25. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 222 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 222 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the General Note Entity 2 DEARRW1 Pointer Pointer to the DE of the first Leader (Arrow) Entity; the arrow head should touch the arc 3 XT Real Arc center coordinates 4 YT Real 5 DEARRW2 Pointer Pointer to the DE of the second Leader (Arrow) Entity, or zero Additional pointers as required (see Section 2.2.4.4.2). 545 G.20 RADIUS DIMENSION ENTITY (TYPE 222, FORM 1) Figure G25. Example Defined Using the Radius Dimension Entity 546 G.21 GENERAL SYMBOL ENTITY (TYPE 228, FORMS 1,2,3) G.21 General Symbol Entity (Type 228, Forms 1,2,3) Three additional forms_Form Numbers 1,2, and 3_of the General Symbol Entity are defined below. Examples of symbols defined using these form numbers are shown in Figure G26. See Section 4.65 ECO556 for more detail. __________________________________________________________________________________________________ |__Form__|_____________________________Meaning_(see_[ANSI82])______________________________|______ | 0 |General Symbol - Originated as a symbol which was not necessarily a standard | | |symbol. | || || || | 1 |Datum Feature Symbol - the included data originated as a datum feature symbol | | |consisting of a frame containing the datum identifying letter preceded and followed | | | | | |by a dash. The identifying letter is a letter of the alphabet (except I, O, and Q). | | | | | |Where datum features are so numerous as to exhaust the single alpha series, the | | |double alpha series is used - AA through AZ, BA through BZ, etc. | || || || | 2 |Datum Target Symbol - The included data originated as a datum target symbol | | |consisting of a circle divided horizontally into two halves. The lower half contains | | | | | |a letter identifying the associated datum, followed by the target number assigned | | |sequentially starting with one for each datum. Where the target is an area, the area | | | | | |size may be entered into the upper half of the symbol; otherwise, the upper half is | | | | | |blank. A radial line attached to the symbol is directed to the target point, line, or | | |area, as applicable. | || || || | 3 |Feature Control Frame - The included data originated as a feature control frame | | |consisting of a frame divided into compartments containing the geometric charac- | | | | | |teristic symbol followed by the tolerance. The tolerance may be preceded by a | | |diameter symbol or followed by a material condition symbol. | |_________|_______________________________________________________________________________________| Forms 1 (Datum Feature Symbol) and 3 (Feature Control Frame) may be related to the considered ECO513 feature(s) by a plane surface extension line (witness line) or by leader/arrow(s) as specified in Section 3.5(b) or (c) of [ANSI82]. Form numbers in the range 5001-9999 are left undefined to allow for implementor defined meaning. ECO514 Implementor defined forms must conform to the parameter requirements of the General Symbol Entity (Type 228), and are to be interpreted like those defined as Form 0 when the implementor defined meaning is not understood. 547 G.21 GENERAL SYMBOL ENTITY (TYPE 228, FORMS 1,2,3) ECO607A Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 228 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 228 | # | #; ) | # | # | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: Valid values of the Form Number are 0, 1, 2, 3, and 5001-9999. Parameter Data Index__ Name____ Type___ Description___ 1 DENOTE Pointer Pointer to the DE of the associated General Note Entity 2 N Integer Number of pointers to geometry 3 DEGEOM1 Pointer Pointer to the DE of the first defining geometry entity .. . . . .. .. 2+N DEGEOMN Pointer Pointer to the DE of the last defining geometry entity 3+N L Integer Number of Leaders or zero 4+N DEARRW1 Pointer Pointer to the DE of the first associated Leader Entity .. . . . .. .. 3+L+N DEARRWL Pointer Pointer to the DE of the last associated Leader Entity Additional pointers as required (see Section 2.2.4.4.2). 548 G.21 GENERAL SYMBOL ENTITY (TYPE 228, FORMS 1,2,3) Figure G26. Examples of Symbols Defined Using New Form Numbers of the General Symbol Entity 549 G.22 SECTIONED AREA ENTITY (TYPE 230) G.22 Sectioned Area Entity (Type 230) ECO509 Additional fill patterns are defined in the following for the Sectioned Area Entity (Type 230). See Section 4.66 for more detail. For the fill pattern codes 20 through 268, which use a composite of geometric entities, preprocessors must set the indices 3 through 7 to 0.0, and postprocessors should ignore them. It is not intended that exact visual equivalence be preserved. The receiving system is to use similar but not necessarily identical patterns based on the pattern codes; the intention is to preserve the functionality implicit in the code. If the receiving system does not have a similar pattern, the default will be no pattern fill. _______________________________________________________________________ |__PATRN__|_________________Meaning________________|____Authorityy__|__ | 20 |Earth | [ANSI79] | | 22 |Rock | [ANSI79] | | 26 |Cliffs | [ANSI72] | | 28 |Sand | [ANSI79] | | 29 |Sand and Sand Dunes | [ANSI72] | | 32 |Stone Fill | AIA | | 34 |Tailings or Mining Debris | [ANSI72] | | 36 |Hill Shading | [ANSI72] | | 38 |Water and Other Liquids | [ANSI79] | | 40 |Wood (Across Grain) | [ANSI79] | | 41 |Wood (With Grain) | [ANSI79] | | 42 |Finish Wood | AIA | | 46 |Large Scale Plywood | AIA | | 50 |Shingles Siding | AIA | | 60 |Glass | AIA | | 70 |Cork, Felt, Fabric, Leather and Fiber | [ANSI79] | | 72 |Sound Insulation | [ANSI79] | | 80 |Thermal Insulation | [ANSI79] | | 82 |Insulation (Loose Fill or Batts) | AIA | |_____84_____|Insulation_(Boards_or_Quilt)___________|______AIA______|_ yAIA refers to the publications of the American Institute of Architects 550 G.22 SECTIONED AREA ENTITY (TYPE 230) Figure G27. Predefined Fill Patterns for the Sectioned Area Entity 551 G.22 SECTIONED AREA ENTITY (TYPE 230) ____________________________________________________________ |__PATRN__|____________Meaning___________|____Authorityy__|_ | 86 |Insulation (Solid Core) | AIA | | 90 |Concrete | [ANSI79] | | 92 |Structural Concrete | AIA | | 94 |Light Weight Concrete | AIA | | 110 |Concrete Block | AIA | | 124 |Fire Brick on Common | AIA | | 134 |Running Bond Masonry | AIA | | 136 |Stack Bond Masonry | AIA | | 140 |Marble | AIA | | 142 |Slate, Bluestone, Soapstone | AIA | | 152 |Cut Stone | AIA | | 154 |Ashlar Stone | AIA | | 156 |Cast Stone (Concrete) | AIA | | 157 |Rubble | AIA | | 158 |Rubble Stone | AIA | | 159 |Squared Stone | AIA | | 172 |Plaster, Sand and Cement | AIA | | 174 |Concrete Plaster | AIA | | 178 |Terrazzo | AIA | |_____210_____|Glaciers______________________|_[ANSI72]___|_ yAIA refers to the publications of the American Institute of Architects 552 G.22 SECTIONED AREA ENTITY (TYPE 230) Figure G27. Predefined Fill Patterns for the Sectioned Area Entity (continued) 553 G.22 SECTIONED AREA ENTITY (TYPE 230) _________________________________________________ |__PATRN__|_______Meaning______|____Authority__|_ | 220 |Fresh Marsh | [ANSI72] | | 224 |Salt Marsh | [ANSI72] | | 226 |Submerged Marsh | [ANSI72] | | 234 |Tidal Flat | [ANSI72] | | 236 |Water Line | [ANSI72] | | 240 |Cleared Land | [ANSI72] | | 244 |Cultivated Land | [ANSI72] | | 246 |Meadow | [ANSI72] | | 252 |Deciduous Trees | [ANSI72] | | 254 |Evergreen Trees | [ANSI72] | | 256 |Oak Trees | [ANSI72] | | 262 |Orchard | [ANSI72] | | 264 |Vineyard | [ANSI72] | | 265 |Willows | [ANSI72] | | 266 |Corn | [ANSI72] | |_____268_____|Tobacco____________|__[ANSI72]___|_ 554 G.22 SECTIONED AREA ENTITY (TYPE 230) Figure G27. Predefined Fill Patterns for the Sectioned Area Entity (continued) 555 G.23 SECTIONED AREA ENTITY (TYPE 230, FORM 1) G.23 Sectioned Area Entity (Type 230, Form 1) ECO570 This additional form of the Sectioned Area Entity (Type 230) is defined below. See Section 4.66 for more detail. Field 15 of the Directory Entry accomodates a form number. For this entity, the options are as follows: _____________________________________ |__Form__|________Meaning_________|__ | 0 |Standard Crosshatching | |____1____|Inverted_Croshatching___|_ Form 0 (Standard crosshatching) is used when the main boundary contains section lines; if there are nested island curves (i.e., N > 0), then section lines change state for each nested interior boundary. Form 1 (Inverted crosshatching) is used when the main boundary does not contain section lines, or when there is no main boundary defined. At least one island curve must be defined, i.e., N > 0 is required. Unnested island curves contain section lines; if any island curves are nested, then section lines change state for each nested interior boundary. Refer to Figure G28 for examples of both standard and inverted crosshatching. 556 G.23 SECTIONED AREA ENTITY (TYPE 230, FORM 1) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 230 | ) |< n:a: > | #; ) | #; ) | 0; ) | 0; ) | 0; ) |????01?? | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 230 | # | #; ) | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 BNDP Pointer Pointer to the DE of the exterior definition curve entity, or zero 2 PATRN Integer Fill pattern code 3 XT Real X coordinate through which a line should pass 4 YT Real Y coordinate through which a line should pass 5 ZT Real Z depth of lines 6 DIST Real Normal distance between adjacent lines 7 ANGLE Real Angle measured in radians from the XT axis to the lines of the sectioning. Default = ss=4 8 N Integer Number of island curves (N > 0) 9 ISLPT1 Pointer Pointer to the DE of the first interior definition curve entity for an island .. . . . .. .. 8+N ISLPTN Pointer Pointer to the DE of the last interior definition curve entity for an island Additional pointers as required (see Section 2.2.4.4.2). 557 G.23 SECTIONED AREA ENTITY (TYPE 230, FORM 1) Figure G28. Examples of Standard and Inverted Crosshatching. 558 G.24 MACRO CAPABILITY G.24 MACRO Capability ECO548 G.24.1 General This Specification provides a means for communicating 3-dimensional and 2-dimensional geometric models and drawings. The Specification, however, does not provide a format for every geometric or drafting entity available on all currently used CAD/CAM systems, and is thus a common subset of such entities. To allow exchange of a larger subset of entities - a subset containing some of the entities not defined in this Specification but which can be defined in terms of the basic entities, the MACRO capability is provided. This capability allows the use of the Specification to be extended beyond the common entity subset, utilizing a formal mechanism which is a part of the Specification. The MACRO capability provides for the definition of a "new" entity in terms of other entities. The "new" entity schema is provided in a MACRO definition which occurs once for every "new" entity in the file. Instances of these "new" entities are replaced during the MACRO processing by the constituent entities specified in the corresponding MACRO definition. A MACRO definition is written using the MACRO Definition Entity (Type 306). The Parameter Data section of the entity contains the MACRO body. In the MACRO body, eleven types of language statements are usable. The statements are LET, SET, REPEAT, CONTINUE, BREAK, IF, LABEL, GOTO, MACRO, ENDM, MREF. The details of the MACRO syntax are given in Section G.24.2. Each of the statements in a MACRO Definition Entity is terminated by a record delimiter. In order to use a "new" entity defined by the MACRO definition, a MACRO instance is placed in the file. The Directory Entry portion of an instance specifies the new entity type number in Field 1 and 11 of the Directory Entry record and refers to the definition by a pointer in the Structure Field (DE Field 3). The parameters for the instance are placed in the Parameter Data record of the instance. The Directory Entry record of a MACRO definition has a standard form. The attributes 4 through 9, 12, 13, 15, 18, and 19 have no significance. The default values for these attributes are taken from the Directory Entry record of the MACRO instance (described in Section G.24.4). The Parameter Data records of a MACRO definition consist of MACRO language statements. The statements are not in Hollerith form, i.e., they have no preceding "H" specification. The statements are free format and may branch over record boundaries (see Section 2.2.3). Every statement is terminated by a record delimiter. G.24.2 MACRO Syntax Constants. Constants may be integer, real, double precision real, pointer or string (See Sec- tion 2.2.2). Variables. The significant part of a variable name is from one to six characters in length. The first character must be one of the characters listed below. This character determines the variable type. It is not possible to override the conventions. The six character limitation includes the first character. Upper and lower case letters are recognized as distinct, i.e., X is different from x. Variable names longer than six characters may be used; however, only the first six characters will be significant. Variable names may contain imbedded blanks. These blanks are NOT taken as part of the name; therefore "A B" is equivalent to "AB." Except for the first character, as outlined below, all characters must be alphabetic (A--Z or a--z), or numeric (0--9). 559 G.24 MACRO CAPABILITY Variable Naming Convention _________________________________________________ |____Variable_Type____|_____First_Character___|__ | Integer | I-N, i-n | | Real |A-H, O-Z a-h, o-z | | Double precision real | ! | | String | $ | | Pointer | # | |__Label__________________|_________&____________| Examples of valid variable names. ______________________________________________________________________________ |______Variable_Type______|___________________Valid_Names_________________|___ | Integer |IJK ICOUNT K101 NTIMES max | | Real |XYZ X1 y2 QrsTu1 | | Double precision real | !h !xi !Y2 !12341 | | String |$str $TITLE $label | |__Pointer__________________|_#line____#note_______#REF______#XYZ1____________| Some examples of invalid variable names are: $$$$ $ not permitted after first character 1X43B 1 may not be first character A.BC . is illegal Note that there are no "reserved" words. Thus a variable name such as MACRO, which is identical to a statement keyword (described below), will not confuse the interpreter, although it may confuse the user of such a MACRO. It is suggested that these words be avoided. Functions. Functions similar to FORTRAN library functions are provided. The rules for mixed mode have been relaxed so that it is not necessary to use SQRT(2.) instead of SQRT(2). While this assists the preprocessor writer in preparing MACROs, it places a responsibility on the writer of a processor for the MACRO language in handling the mixed mode. While the arguments can be mixed mode, the functions do have a specific type of value that they return, i.e., integer, real, double precision real, or string. The functions are listed here by the type of value returned. The type of argument usually used is also noted for clarity. For example, either IDINT(!d) or INT(!d) will work equally well, although the meaning might be a little clearer with IDINT(!d). Functions are only recognized in upper case. Functions Returning Integer Values: ______________________________________ |__Function__|__Value_Returned__|_____ | IABS(i) | Absolute value of i | | IDINT(!d) | Integer part of !d | | IFIX(x) | Integer part of x | | INT(x) | Integer part of x | | ISIGN(i) | 1 if i is positive, or | | |0 if it is zero, or | |______________|-1_if_it_is_negative__ | 560 G.24 MACRO CAPABILITY Functions Returning Real Values: __________________________________________________________________________________________ |__Function__|____________________________Value_Returned____________________________|_____ | ABS(x) | Absolute value of x | | AINT(x) | Integer part of x, in real form | | ALOG(x) | Natural logarithm of x | | ALOG10(x) | Common (base 10) logarithm of x | | ATAN(x) | Arctangent of x; angle returned in radians | | COS(x) | Cosine of angle x; angle in radians | | EXP(x) | Natural anti-logarithm of x (i.e., e to the x) | | FLOAT(i) | Real (floated) value for i, e.g., FLOAT(2) returns 2. | | SIGN(x) | 1. if x is positive, or 0. if x is zero, or -1. if x is negative | | SIN(x) | Sine of angle x; angle in radians | | SNGL(!d) | Single precision (real) value of double precision variable !d. As many | | |significant digits of !d as possible are used in the returned value | | SQRT(x) | Square root of x | |__TAN(x)_____|_Tangent_of_angle_x;_angle_in_radians____________________________________|_ Functions Returning Double Precision Real Values: _______________________________________________________________________________ |___Function___|______________________Value_Returned______________________|____ | DABS(!d) | Absolute value of !d | | DATAN(!d) | Arctangent of !d; value returned in radians | | DBLE(x) | Returns double precision real value of x. Note that this is | | |merely conversion, not an extension. Thus, | | |DBL(.333333333) will return .333333333D0, but not | | |.333333333333333333333333D0. Thus, DBLE(1./3.) | | |is not necessarily equal to 1D0/3D0 | | DCOS(!d) | Cosine of angle !d; angle in radians | | DEXP(!d) | Natural anti-logarithm of !d (i.e., e to the !d) | | DLOG(!d) | Natural logarithm of !d | | DLOG10(!d) | Common (base 10) logarithm of !d | | DSIGN(!d) | 1D0 if !d is positive, or 0D0 if zero, or -1D0 if negative | | DSIN(!d) | Sine of angle !d; angle in radians | | DSQRT(!d) | Square root of !d | |__DTAN(!d)____|_Tangent_of_angle_!d;_angle_in_radians_______________________|_ Functions Returning String Values: __________________________________________________________________________________ |_____________Function_____________|_____________Value_Returned______________|____ | STRING(expression, format) | Character representation of the argument | | |"expression". See Section G.24.3.1 for a | |___________________________________|description_of_the_argument_"format"._____|__ 561 G.24 MACRO CAPABILITY Expressions. Expressions may be formed using the above functions, variables and constants, and the following operators: _______________________________ |____Function____|__Symbol__|__ | addition | + | | subtraction | - | | multiplication | * | | division | / | |__exponentiation__|___**_____|_ The operators are evaluated in normal algebraic order, i.e., first exponentiation, then unary negation, then multiplication or division, then addition or subtraction. Within any one hierarchy, operators evaluate left to right. Parentheses may be used to override the normal evaluation order, as in the ex- pression "A*(B+C)," which is different from "A*B+C." Extra parentheses do not alter the value of the expression; it is a good idea to use them, even if not truly necessary. Examples of expressions include: X+1.0 -B+SQRT(B**2 - 4*A*C) I + 1 3.14159/2. -X !DEL*(!ALPHA-!BETA) Except for the ** operator, it is never permissable to have two operators next to each other, i.e., not 2*-2, but -2*2 or 2*(-2). Multiplication may not be implied by parentheses, e.g., (A+B)(C+D) is invalid, and AB does not imply A*B, but rather the separate variable AB. Mode of expression evaluation. Mixed mode (integer mixed with real, etc.) is permitted. When- ever two different types are to be operated upon, the calculation is performed in the "higher" type. Integer is the lowest type, real is next, and double precision real is the highest. Note, however, that this decision is made for each operation, not once for the entire expression. Thus 1/3 + 1.0 evalu- ates to 1.0, because the "1/3" is done first, and it is done in integer mode. Integer mode truncates fractions, and does not round. Therefore, the expression "2/3+2/3+2/3" has a value of zero. Conditional expressions. Conditional expressions may be formed using functions, variables, and constants, and the following six standard relational operators: _____________________________________ |_______Function_______|___Symbol__|_ | less than or equal | .LE. | | less than | .LT. | | equal | .EQ. | | greater than or equal | .GE. | | greater than | .GT. | |__not_equal______________|__.NE.____| 562 G.24 MACRO CAPABILITY Examples of conditional expressions include: X.GT.3 SQRT(A+B).NE.I+1 (!A-!B).GE.3.14159 G.24.3 MACRO Definition Entity (Type 306) The MACRO Definition Entity specifies the action of a specific MACRO. After having been specified in a definition entity, the MACRO can be used as often as necessary by means of the MACRO Instance Entity. The MACRO Definition Entity differs from other entity structures in this specification by consisting of only language statements in the parameter data. The character strings constituting the language statements in the MACRO definition are not set off by means of the nH structure of string con- stants but rather consist of only the actual character string terminated by a record delimiter (see Section 2.2.2.5). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 306 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0002** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 306 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 ID Literal MACRO 2 NE Integer Entity Type ID 3 TEXT Language First statement statement .. . . . .. .. 2+N TEXT Language Last statement statement 3+N T Literal ENDM Additional parameters as required (see Section 2.2.4.4.2). 563 G.24 MACRO CAPABILITY G.24.3.1 Language Statements. There are eleven language statements that can be used. They are: BREAK IF MREF CONTINUE LABEL REPEAT ENDM LET SET GOTO MACRO These "keywords" are recognized only in upper case, and every statement must begin with one of these keywords. Statements are free format; blanks and tabs are ignored except within strings. Statements may extend over several lines, or more than one statement may be present on a line. All statements are terminated by a record delimiter which must be present. LET Statement (Arithmetic) This is the assignment statement and is equivalent to the LET statement of BASIC. The format of a LET statement is: LET variable = expression; The expression and the variable may be integer, real, or double precision; they need not be of the same type. Note that this is an assignment statement and not an algebraic equality. All of the variables on the right hand side of the expression must have been previously defined; it cannot be assumed that variables will default to zero if they are undefined. Some examples of valid LET state- ments: LET HYPOT = SQRT(A**2+B**2); LET X = X + 1; LET ROOT1 = -B + SQRT(B*B - 4*A*C); LET I = i; LET !XYZ = I * 2; LET START = 0; LET Statement (String) String variables allow characters to be manipulated. String variables may be used in statements almost anywhere that any other variable type may be used; exceptions are noted below. String variables may be used in LET statements. Note that they shall not be mixed with any other type of variable in a LET statement. Also note that arithmetic operations (i.e., +, -, *, /, **) are not possible with string variables. Two forms of LET statements for string variables are possible: 564 G.24 MACRO CAPABILITY LET $str = 23Hstring of 23 characters; or LET $str1 = $str2; In the first case, the 23 characters following the H are assigned to the string variable $str. In the second case, the string "$str2" is copied into "$str1." Examples of these statements include: LET $title = 3HBox; LET $subti = 6HBottom; LET $x = $subti; Note that if a string variable appears on the right hand side of the statement, it must have been previously defined. Spaces are not ignored within a string constant; they become part of the string. Any printable ASCII character may be part of a string. There is one other form for setting up a string. It involves the STRING function. The STRING function may only appear in this form. Specifically, it shall not appear in SET statement argument lists, MACRO statements, or MREF statements. However, string constants, such as "6Hstring," and variables, such as "$x," may appear in SET statements and MACRO statements. The form of a LET statement including string function is: LET $str = STRING(expression, format); where "expression" is any normal integer, real or double precision real expression, "$str" is a string variable name, and "format" is a format specification as used in a FORTRAN FORMAT statement. The allowable format specifications are: Iw Fw.d Ew.d Dw.d The effect of this statement is to convert the numeric value of the expression into characters, i.e., the statement: LET $PI = STRING(3.14159,F7.5); will result in the same thing as 565 G.24 MACRO CAPABILITY LET $PI = 7H3.14159; Of course, the usefulness of the STRING function is that expressions can be converted, rather than constants. Thus: LET x = 1; LET y = 2; LET $xyz = STRING(x+y+1,F5.0); will result in the same thing as LET $xyz = 5H 4.; The rules for the format specifications follow the standard FORTRAN convention. "Iw" causes integer conversion, resulting in "w" characters. "Fw.d" causes real conversion, resulting in "w" char- acters, with "d" characters after the decimal point. "Ew.d" results in real conversion, but using an exponent form. "Dw.d" is the same as "E" but for double precision real values. Note that this is one place where mixed mode is not allowed. The type of format specification and the type of the expression's result must be identical. LET Statements (Attributes) Attributes (those appearing in the directory entry record for the MACRO instance) may be set using the LET statement. The format is: LET /attribute name = expression; or LET /attribute name = /HDR; The first form allows an attribute to be set to any constant value, including numeric expressions. Attributes may also be set to string constants or string variables but not to the result of a STRING function. Examples include: LET /LEV = 1; LET /VIEW = 3; LET /LABEL = 6HBottom; LET /LABEL = $X; The second form allows restoring an attribute to its default value. Examples include: 566 G.24 MACRO CAPABILITY LET /LEV = /HDR; LET /LABEL = /HDR; The word "/HDR" is the only nonconstant that is allowed on the right side of an attribute assignment statement. The effect is to restore the value of the attribute to what it was in the directory entry for the instance or, in some cases, to a specified default value. The defaults are described below. Attributes may not be mixed with any other variable type nor may they appear anywhere but in the above two forms of LET statements. The allowable attribute names and their defaults are given here. A default of /HDR indicates that the attribute defaults to the value in the directory entry of the instance. _____________________________________________________ |__________Attribute__________|_Name__|___Default__|_ | Line font pattern |/LFP | /HDR | | Level |/LEV |/HDR | | View |/VIEW | /HDR | | Transformation matrix | /MTX | /HDR | | Label display associativity |/CE |0 | | Blank status |/BS | /HDR | | Subordinate entity |/SE | /HDR | | Entity use |/ET | /HDR | | Hierarchy |/HF | /HDR | | Line weight |/LW | /HDR | | Color Number | /PN | /HDR | | Form Number | /FORM | 0 | | Entity label |/LABEL |blanks | |__Entity_subscript____________|/SUB____|_0_________|_ SET Statement The SET statement establishes directory and parameter data entries for the specified entity. The form is: SET #ptr = entity type number, argument list; "#ptr" is a pointer variable, such as "#XYZ"; "entity type number" is an entity type number, such as "110"; and "argument list" is a group of variables which is the parameter data of the entity. Examples of this type of SET statement include: SET #LINE = 110,X1,Y1,Z,X2,Y2,Z,0,0; SET #ABC = 828,Z,A+B/C,Y1,X2,Y2+1,0,0; SET #qwe = 864,15Hstrings allowed, X,Y,$this2; The argument list may contain expressions and may spread over more than one line. At least one argument must be present, i.e., the argument list may not be null. The entity type number may not 567 G.24 MACRO CAPABILITY be an expression; i.e., it must be an integer constant. The pointer variable will be assigned a value corresponding to the sequence number of the directory entry of the entity created. "Forward referencing" of pointers is valid in the argument list of a SET statement. A pointer may appear in the argument list of a SET statement that comes before the SET statement defining the pointer. The only restriction is that any pointer so referenced must appear on the left hand side of one SET statement. Pointers which appear on the left hand side of more than one SET statement or those which are located inside of REPEAT loops should not be forward referenced. Note that the STRING function is not allowable in a SET statement - use a separate LET statement with a string variable instead. REPEAT Statement The REPEAT statement causes a group of statements terminated by a CONTINUE statement to be repeated a specified number of times. The form of a REPEAT statement is: REPEAT expression; The expression is evaluated, and the resulting value is the number of times the statements will be repeated. The expression may be of integer, real or double precision real type; in the case of real or double precision real expressions, the result is truncated to determine the repeat count. If the repeat count is zero or negative, the group of statements is still executed one time. Examples of REPEAT statements are: REPEAT 3; REPEAT N+1; REPEAT 0; REPEAT X+Y; REPEAT statements may be nested only to a depth of ten. After a REPEAT statement, such as REPEAT N, it is valid to alter the value of N. This does not affect the repeat count. Also note that REPEAT is unlike a FORTRAN DO statement because there is no variable being incremented on every pass. CONTINUE Statement The CONTINUE statement marks the end of a REPEAT group. The form of a CONTINUE statement is: CONTINUE; 568 G.24 MACRO CAPABILITY When a CONTINUE statement is encountered, the repeat count is decremented by one and checked to see if it is greater than zero. If it is, the interpreter goes back to the first statement after the most recent REPEAT. If not, then the next statement is processed. The number of REPEAT statements and CONTINUE statements in a MACRO shall be the same. A CONTINUE statement(s) is not implied by ENDM. BREAK Statement A BREAK statement may be used within a REPEAT construct to terminate the processing of state- ments of the REPEAT construct before the completion of the specified number of loops, such as upon detection of a condition during the processing. The form of a BREAK statement is: BREAK; or IF conditional expression, BREAK; When a BREAK statement is encountered, processing of MACRO statements resumes with the state- ment immediately following the CONTINUE statement marking the end of the affected REPEAT con- struct. IF Statement The IF statement causes a single language statement to be executed if a certain condition is true. The form of an IF statement is: IF conditional expression, language statement; where "conditional expression" is a conditional expression as described in Section G.24.2, "language statement" can be any statement allowed in a MACRO except: MACRO ENDM IF LABEL Examples of IF statements: 569 G.24 MACRO CAPABILITY IF A.LT.3,LET A=3; IF B.EQ.0,SET #LIN1=110,...; IF SWITCH.EQ.1, GOTO &A; LABEL Statement The LABEL statement is used to mark a position in a MACRO where the execution control is trans- ferred to using a GOTO statement. The form of a LABEL statement is: LABEL label name; where "label name" is any character string beginning with an ampersand (&). It should be from one to six characters long (including the &). Within a single MACRO definition, all label names must be unique. Examples are: LABEL &loop; LABEL &end; GOTO Statement This statement is used to transfer the execution control to a particular point which is marked by a LABEL statement. The form of a GOTO statement is: GOTO label name; where "label name" is any label name specified in a LABEL statement. The GOTO statement can be used to jump both forward and backward, but both the GOTO statement and the target LABEL must be at the same nesting level and within the same REPEAT construct. Examples are: GOTO &start; GOTO &end; MACRO Statement The MACRO statement is used to signify the start of a MACRO definition. The first statement in every MACRO definition must be a MACRO statement. The form of a MACRO statement is: 570 G.24 MACRO CAPABILITY 306,MACRO, entity type number, argument list; where "entity type number" is the assigned entity number of the MACRO, and "argument list" is a list of parameters that are to be assigned values at execution time. Entity type numbers in the range of 600 to 699 and 10000 to 99999 will be used. The argument list may not be null. The parameters in the argument list take the form of the variables described in Section G.24.2. Note that the argument list may not contain expressions, only symbolic variable names. One additional type of variable, the "class variable" can be used in an argument list. The class variable takes the form: size_variable (class_var_1, class_var_2, ..., class_var_n) where size_variable precedes the occurrence of the class variable in the argument list and class_var_i members are referenced in the MACRO body by means of a subscript: class_var_i (J) In the MACRO statement, the size_variable is used to identify the class variable collection being defined. In the MACRO body, the size_variable indicates the number of sets of class variable members that are included (i.e., the number of times the class variable collection is to be repeated). A simple class variable example is: N(ITEM1, ITEM2, ITEM3, ITEM4) which specifies a class variable collection with four members. For an instance of the MACRO, using the example class variable with N equal to 3, three sets of class variable data for the collection are available to the macro body statements. The parameter list for the associated MACRO instance is: ITEM1(1), ITEM2(1), ITEM3(1), ITEM4(1),...,ITEM3(3), ITEM4(3) Each value for each member of the class variable may be referenced individually: ITEM1(1), ITEM1(2), ITEM1(3), ITEM1(4), etc. in any order, or implicitly, by using an index variable, i.e., J: 571 G.24 MACRO CAPABILITY ITEM3 (J) with J ranging from 1 to 3 Use of the class variable to represent a MACRO with a parameter list identical to the Views Visible Associativity, Form 4, would be specified as: 306,MACRO,681,N1,N2,N1(#DEV,LF,#DEF,IPN,LW), N2(#DE),N,N(#DEA),M,M(#DEP); where: N1(#DEV,LF,#DEF,ICN,LW) indicates the blocks of views visible, line font, color number, and line weight information N2(#DE) contains the pointers to the entities included in the view N(#DEA) contains the back pointers/text pointers M(#DEP) contains the pointers to properties Note that zero is a valid value for a size_variable in a MACRO instance. ENDM Statement ENDM signifies the end of a MACRO. The form of an ENDM statement is: ENDM; All MACROs must have an ENDM statement as their last statement. ENDM is not implied by the end of the parameter data section. MREF Statement The MREF statement is used to reference another MACRO from inside a MACRO definition. The form of an MREF statement is: MREF, ptr, entity type number, argument list; where "ptr" may be either a pointer variable or an integer expression. The value is the sequence number of the Directory Entry record of the MACRO definition being referenced. "Entity type number" is the assigned entity number of the MACRO being referenced. "Argument list" is exactly like that of a SET statement. The effect of the argument list is to replace the symbolic names found in the MACRO definition with the values of the expressions contained in the MREF statement, so 572 G.24 MACRO CAPABILITY that execution of the referenced MACRO will start with the appropriate values. Note that MREF does not start expansion of the referenced MACRO. Rather it creates an entity entry which may later be expanded. It is thus not possible for a MACRO being referenced to have access to any of those values except for those in the argument list. (All variables not in the argument list are treated as local variables.) Even then, it is not possible for the occurrence of a MREF statement to alter any of those values. Examples of MREF statements: MREF,#mac1,600,X1,Y1,Z1,X2,Y2,3.1; MREF,33,621,A,B,3+X/W+1,6*W,3.,0,6Hstring,$x; It is not strictly necessary for the values in a MREF statement to be of the same type as the values in the definition MACRO, within certain limitations. Integer, real, and double precision real values may be freely mixed, although it might be considered a good idea not to do so. String values may only appear where string variables appear in the definition. 573 G.24 MACRO CAPABILITY G.24.4 MACRO Instance Entity A MACRO Instance Entity is used to invoke a MACRO. The Parameter Data records of the instance contain values for the arguments to the MACRO. This is similar to a standard entity entry. The Directory Entry for a MACRO Instance Entity contains the attribute values that are to be used as the default values during the expansion of the MACRO. The only special field is the structure field (Directory Entry Field 3), which contains a pointer to the Directory Entry of the MACRO definition. The pointer is preceded by a minus sign. Directory Data Entity Type Number: As defined for each MACRO in the range 600 to 699 or 10000 to 99999. Structure Field: Pointer to the DE of the MACRO definition, preceded by a minus sign. Other attributes: Default values to be used during expansion of the MACRO. Attributes listed as defaulting to /HDR obtain their values from here. (See discussion of LET statement attributes)). Parameter Data The parameter data section for an instance has the following form: With all parameter data entities, the first record begins with the entity type number as defined in the MACRO. Index__ Name____ Type___ Description___ 1,...,K As appropriate Values for the arguments to the MACRO must agree in format and number with the arguments in the MACRO statement of the definition. Additional pointers as required (See Section 2.2.4.4.2). 574 G.24 MACRO CAPABILITY G.24.4.1 Examples of MACRO Usage Five examples are given to illustrate some of the capabilities of a MACRO. 1. Isosceles Triangle 2. Repeated Parallelograms 3. Concentric Circles 4. Ground Symbol 5. Useful Features Example 1: Isosceles Triangle The following MACRO definition creates an isosceles triangle, given a vertex point, a height, a base width and a scale. Directory Entry Entity Type Number: 306 Parameter Data 306, MACRO, 621, X1, Y1, A1, A2, K; LET Z = 0; SET #Line1 = 110,X1,Y1,Z,X1+(K*A1),Y1+(K*A2/2.),Z,0,0; SET #Line2 = 110,X1+(K*A1),Y1+(K*A2/2.),Z, X1+(K*A1),Y1-(K*A2/2.),Z,0,0; SET #Line3 = 110,X1+(K*A1),Y1-(K*A2/2.),Z, X1,Y1,Z,0,0; ENDM; The MACRO can be used to create a triangle by using a MACRO instance which supplies the needed values for X1, Y1, A1, A2, and K. The parameter data section for the MACRO instance would have the following format: Index__ Name____ Type___ Description___ 1 X1 Real X coordinate of vertex 2 Y1 Real Y coordinate of vertex 3 A1 Real Height of triangle 4 A2 Real Base of triangle 5 K Integer Scaling factor In particular, to create a triangle shown in Figure G29 with a base of 5. and a height of 17., a vertex at (0,0), and a scale factor 1, the following instance could be placed into the file: 575 G.24 MACRO CAPABILITY Directory Entry Entity Type Number: 621 Structure: -nnn, where "nnn" is the sequence number of the directory entry of the definition. Other attributes: As desired for default values during MACRO expansion. Parameter Data 621, 0., 0., 17., 5., 1; Figure G29. Parameters of the Isoceles Triangle Macro in Example 1 in Text 576 G.24 MACRO CAPABILITY Example 2: Repeated parallelograms The following MACRO takes the coordinates of three points and a repetition number as arguments and creates a pattern of repeated parallelograms as shown in Figure G30. The three points represent the vertices of the initial parallelogram. The repetition number argument (NTANG) controls how many additional parallelograms will be drawn offset in the positive X and Y direction from the ini- tial one. For simplicity, the points have been constrained to all lie in a plane parallel to the X-Y plane. Directory Entry Entity Type Number: 306 Parameter Data 306,MACRO, 600, X1, Y1, X2, Y2, X3, Y3, Z, NTANG; IF NTANG.EQ.0, GOTO &END; LET XDEL = (X2-X1)/NTANG; LET YDEL = (Y3-Y1)/NTANG; LET K = 0; REPEAT NTANG +1; SET #VLINE = 110,X1+K*XDEL,Y1+K*YDEL,Z, X2+K*XDEL,Y2+K*YDEL,Z,0,0; SET #HLINE = 110,X1+K*XDEL,Y1+K*YDEL,Z, X3+K*XDEL,Y3+K*YDEL,Z,0,0; SET #VLINE = 110,X3+K*XDEL,Y3+K*YDEL,Z, X3+(X2-X1)+K*XDEL,Y2+(Y3-Y1)+K*YDEL, Z,0,0; SET #HLINE = 110,X2+K*XDEL,Y2+K*YDEL, Z, X3+(X2-X1)+K*XDEL,Y2+(Y3-Y1)+K*YDEL, Z,0,0; LET K = K+1; CONTINUE; LABEL &END; ENDM; Parameter Data for an instance of this MACRO looks like this: Directory Entry Entity Type Number: 600 Parameter Data 600, 1., 1., 2., 5., 5., 2., 1., 3; 577 G.24 MACRO CAPABILITY Figure G30. Repeated Parallelograms Created by Macro Example 2 in Text 578 G.24 MACRO CAPABILITY Example 3: Concentric circles The following MACRO, given a coordinate, a radius, and a number, creates concentric circles out to the radius. A point is put into the center. Figure G31 shows the result. Directory Entry Entity Type Number: 306 Parameter Data 306,MACRO,601,XC,YC,ZC,R,NCIRC; IF NCIRC .EQ. 0, GOTO &END; LET DELTR = R/NCIRC; REPEAT NCIRC; SET #CIR = 100,ZC,XC,YC,XC,YC+R,XC,YC+R,0,0; LET R = R - DELTR; CONTINUE; SET #PT = 116, XC, YC, ZC, 0, 0, 0; LABEL &END; ENDM; Parameter Data for an instance of the MACRO which would create four concentric circles around the origin out to a radius of 20 looks like this: Directory Entry Entity Type Number: 600 Parameter Data 601, 0., 0., 0., 20., 4; 579 G.24 MACRO CAPABILITY Figure G31. Concentric Circles Created by Macro Example 3 in Text 580 G.24 MACRO CAPABILITY Example 4: Electrical ground symbol This MACRO takes a point and a base length and constructs a ground symbol (horizontally) at that point. Figure G32 shows the result. Directory Entry Entity Type Number: 306 Parameter Data 306, MACRO, 602, X, Y, Z, B; IF B.EQ.0, GOTO &A; LET DELY = B/6; LET DELX = DELY; SET #LINE1 = 110, X, Y, Z, X+B, Y, Z, 0, 0; SET #LINE2 = 110, X+DELX, Y-DELY, Z, X+B-DELX, Y-DELY, Z, 0, 0; SET #LINE3 = 110, X+2*DELX, Y-2*DELY, Z, X+B-2*DELX, Y-2*DELY, Z, 0, 0; LABEL &A; ENDM; Parameter Data for an instance of this MACRO looks like this: Directory Entry Entity Type Number: 602 Parameter Data 602, 1., 6., 2., 1.3; 581 G.24 MACRO CAPABILITY Figure G32. Ground Symbol Created by Macro Example 4 in Text 582 G.24 MACRO CAPABILITY Example 5: Useful features This last example demonstrates the use of various MACRO features. It is not meant as an example of a "useful" MACRO. Parameter Data 306,MACRO,613,NROW,NCOL,VDIST,HDIST,!ANGLE; LET/LABEL = 6HPOINTS; LET !SIN=DSIN(!ANGLE); LET !COS=DCOS(!ANGLE); LET YHD=HDIST*!SIN; LET XHD=HDIST*!COS; LET YVD=VDIST*!COS; LET XVD=VDIST*(-!SIN); LET IRC=0; LET ICC=0; REPEAT NROW; LET XCOL=IRC*XVD; LET YCOL=IRC*YVD; REPEAT NCOL; LET X = XCOL + ICC*XHD; LET Y = YCOL + ICC*YHD; SET #PT = 116, X, Y, 0., 0,0,0; LET ICC = ICC + 1; CONTINUE; LET IRC = ICC +1; CONTINUE; LET $NPTS = STRING(NROW*NCOL,I7); LET/LABEL = $NPTS; SET #LINE = 110, 0., 0., 0., 10., 0., 0.; SET #CIRC = 100, 0., 0., 0., 10., 0., 10., 0.; MREF, 22, 601, 0., 0., 0., 10., 5; ENDM; Parameter Data for an instance of this MACRO looks like this: Directory Entry Entity Type Number: 613 Parameter Data 613, 4, 5, 0.2, 0.1, 7.85398D-01; 583 G.25 UNITS DATA ENTITY (TYPE 316) G.25 Units Data Entity (Type 316) ECO528 This entity stores data about a model's fundamental units. The first entry (NP) is the number of data strings in the PD. The entity then contains records, each of which contains a pair of string variables and a real scale factor. The first variable contains the unit to be set, the second variable contains one of the legal entries, and the third variable contains a scale factor to be applied to the unit. If the real data associated with any entity is not expressed in the units of length defined in the global section or the SI (MKSA) defaults for the Tabular Data Entity (Type 406, Form 11), then a Units Data Entity (Type 316) may be attached to the data entity via a property pointer. There are seven base units and two supplementary units from which all other units can be derived. Therefore, the value of TYP in the above parameter data must be chosen from from the following complete list of legal TYP strings: ___________________________________________________ |______TYP______|_______Indicates_unit_of_______|__ | LENGTH |Length | | MASS |Mass | | TIME |Time | | CURRENT |Electric Current | | TEMPERATURE | Thermodynamic Temperature | | AMOUNT |Amount of Substance | | INTENSITY | Luminous Intensity | | PLANE |Plane Angle | |__SOLID_________|Solid_Angle_____________________|_ A given TYP determines which of the following lists can be used to specify the particular units. Legal VAL strings for TYP = LENGTH : _______________________________ |__VAL__|____Description____|__ | A |Angstrom | | AU |Astronomical Unit | | FT |Foot | | IN |Inch | | LY |Light Year | | M |Meter | | UM |Micron | | MIL |Mil (.001 Inch) | | MI |Mile | | KN |Nautical Mile | |__Y______|Yard________________| Legal VAL strings for TYP = MASS : 584 G.25 UNITS DATA ENTITY (TYPE 316) __________________________ |__VAL__|_Description__|__ | C |Carat | | DR |Dram | | GA |Grain | | KG |Kilogram | | MT |Metric Tonne | | OU |Ounce | | LB |Pound | |__S______|Slug___________| Legal VAL strings for TYP = TIME : _________________________ |__VAL__|_Description__|_ | D |Day | | HR |Hour | | M |Minute | | S |Second | | W |Week | |__Y______|Year__________ | Legal VAL strings for TYP = CURRENT : _________________________ |__VAL__|_Description__|_ |__A______|Ampere_______|_ Legal VAL strings for TYP = TEMPERATURE : _________________________ |__VAL__|_Description__|_ | C |Centigrade | | F |Fahrenheit | | K |Kelvin | |__R______|Rankine_______| Legal VAL strings for TYP = AMOUNT : _________________________ |__VAL__|_Description__|_ |__M______|Mole__________| Legal VAL strings for TYP = INTENSITY : _________________________ |__VAL__|_Description__|_ |__C______|Candela_______| Legal VAL strings for TYP = PLANE : _________________________ |__VAL__|_Description__|_ | D |Degree | | G |Grad | | M |Minute | | R |Radian | | REV |Revolution | |__S______|Second________| 585 G.25 UNITS DATA ENTITY (TYPE 316) Legal VAL strings for TYP = SOLID : _________________________ |__VAL__|_Description__|_ |__C______|Steradian_____| Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 316 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0002** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 316 |< n:a: > |< n:a: > | # | 0 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of units defined by this entity 2 TYP(1) String Type of first unit being defined (see note below) 3 VAL(1) String Units of first unit being defined (see note below) 4 SF(1) Real A multiplicative scale factor to be applied to the first unit .. . . . .. .. -1+3*NP TYP(NP) String Type of last unit being defined 3*NP VAL(NP) String Units of last unit being defined 1+3*NP SF(NP) Real A multiplicative scale factor to be applied to the last unit Additional pointers are required (see Section 2.2.4.4.2). 586 G.25 (TYPE 402, FORM 19) - SEGMENTED VIEWS VISIBLE G.26 Segmented Views Visible Associativity ECO506 This additional form of the Associativity Instance Entity (Type 402) is defined below. See Sec- ECO605 tion 4.76 for more detail. FORM NUMBER: 19 Segmented Views Visible This entity permits the association of display parameters with the segments of curves in a given view. This entity works in the same way as the Views Visible Associativity Entity. It is pointed to by an entity's DE Field 6 (View). The curve to be displayed is broken into segments. The display parameters are associated with these segments. A segment is defined by the breakpoints between segments. The first segment starts at the minimum parameterization value and ends at the first parameter breakpoint. The second segment starts at the first parameter breakpoint and runs to the second preakpoint and so on. The data in the instances of this entity shall be ordered in ascending parameter breakpoint order within a given view. That is, the parameter breakpoints for a given view shall be adjacent in increasing parametric order. There is no particular order for the sequence of views. The last parameter breakpoint shall be equal to the maximum parameterization value for the entity for the final view defined. Negative values for parameters 5 and 6 indicate pointers to Color Definition and Line Font Definition Entities. Where the data for the display parameters of a segment of the curve is defaulted, i.e., consecutive delimiters, the display parameters for that segment shall be taken from the curve's DE values for color, line font, or line weight as required. Receiving systems which do not have the ability to segment its display of a curve should apply the curve's DE values for color, line font, and line weight across the entire curve. DEFINITION Index__ Set_Value___ Meaning____ 1 1 One class 2 2 No Back pointers required 3 1 Ordered class 4 6 Six items per entry 5 1 Pointer to View Entity 6 2 Parameter of Breakpoint 7 2 Display Flag (DE Field 9a) 8 3 Color 9 3 Line Font 10 2 Line Weight 587 G.26 (TYPE 402, FORM 19) - SEGMENTED VIEWS VISIBLE DESCRIPTION Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0001** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 19 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of view/segment blocks 2 PT1 Pointer Pointer to the DE of the first View Entity 3 P1 Real Parameter of first breakpoint 4 DF1 Integer First display flag 5 C1 Integer First color value or Pointer Pointer to the DE of the first Color Definition Entity if negative 6 L1 Integer First line font or Pointer Pointer to the DE of the first Line Font Definition Entity if negative 7 W1 Integer First line weight 8 PT2 Pointer Pointer to the DE of the second View Entity (may be the same as PT1 or different) 9 P2 Real Parameter of second breakpoint .. . . . .. .. 2+6*(N-1) PTn Pointer Pointer to the DE of the last View Entity for last segment 3+6*(N-1) Pn Real Parameter of last segment .. . . . .. .. 7+6*(N-1) Wn Integer Last line weight Additional pointers as required (see Section 2.2.4.4.2). 588 G.26 (TYPE 402, FORM 20) - PIPING FLOW G.27 Piping Flow Associativity ECO602A This additional form of the Associativity Instance Entity (Type 402) is defined below. See Sec- tion 4.76.1 for more detail. FORM NUMBER: 20 Piping Flow The Piping Flow Associativity represents a single fluid flow path. The associativity contains seven classes. Class one contains the type flag: __________________________________________ |__Type_Flag__|________Meaning________|___ | 0 |Not specified (Default) | | 1 |Logical | |_______2_______|Physical_________________| The use of the Type Flag is mandatory when both the logical (e.g., P&ID) and physical (e.g., piping product model) product definitions are in the same file. In such a file, the Type Flag shall not be zero. Class two contains pointers to other associated Piping Flow Associativities. These other associa- tivities may implement alternative flow representations. The obvious example of this is the file containing both the logical and physical product definitions. The corresponding Piping Flow Asso- ciativities of each type would be paired. Class three is the Link, which contains the list of pointers to the Connect Point Entities involved in the flow. Class four is the Join, which contains the list of pointers to the entities representing the graphical implementation of the flow. Class five contains the flow names which are associated with the flow. Class six contains a list of pointers to the Text Display Template Entities which are to be used to display the first flow name listed in class five. Class seven contains a list of pointers to flow paths which branch from the current flow path. This is an ordered list, and the "main" continuation of the path, if any, is always listed last. A null pointer is used if there is no continuation of the main path. 589 G.27 (TYPE 402, FORM 20) - PIPING FLOW DEFINITION Index__ Set_Value___ Meaning____ 1 7 Seven classes Class 1 (Context Flag) 2 2 Back pointers not required 3 1 Ordered 4 1 One item per entry 5 2 Item is value Class 2 (Associated Flows) 6 2 Back pointers not required 7 2 Unordered 8 1 One item per entry 9 1 Pointer to Piping Flow Associativity Class 3 (Connect Points (Link)) 10 2 Back pointers not required 11 1 Ordered 12 1 One item per entry 13 1 Pointer to Connect Point Entity Class 4 (Join) 14 2 Back pointers not required 15 1 Ordered 16 1 One item per entry 17 1 Pointer to geometry or Subfigure Instance Entity Class 5 (Flow Name) 18 2 Back pointers not required 19 2 Unordered 20 1 One item per entry 21 2 Item is value Class 6 (Flow Name Display) 22 2 Back pointers not required 23 2 Unordered 24 1 One item per entry 25 1 Pointer to Text Display Template Entity Class 7 (Flow Continuations) 26 2 Back pointers not required 27 1 Ordered 28 1 One item per entry 29 1 Item is a pointer 590 G.27 (TYPE 402, FORM 20) - PIPING FLOW DESCRIPTION Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**??03** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 20 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NCF Integer Count of context flags (NCF=1 is required) 2 NF Integer Count of associated Piping Flow Associativities 3 NC Integer Count of Connect Point Entities 4 NJ Integer Count of Join entities (geometry of subfigure) 5 NN Integer Count of flow names 6 NT Integer Count of Text Display Templates for flow name display 7 NP Integer Count of continuation piping flow associativities 8 TF Integer Type of flow: 0 = not specified (Default) 1 = logical 2 = physical 9 SPTR1 Pointer Pointer to the DE of the first Piping Flow Associativity Entity .. . . . .. .. NF+8 SPTRNF Pointer Pointer to the DE of the last Piping Flow Associativity Entity NF+9 CPTR1 Pointer Pointer to the DE of the first Connect Point Entity .. . . . .. .. NF+NC+8 CPTRNC Pointer Pointer to the DE of the last Connect Point Entity NF+NC+9 JPTR1 Pointer Pointer to the DE of the first Join Entity .. . . . .. .. NF+NC+NJ+8 JPTRNJ Pointer Pointer to the DE of the last Join Entity NF+NC+NJ+9 NAME1 String First Flow name .. . . . .. .. NF+NC+NJ+NN+8 NAMENN String Last Flow name NF+NC+NJ+NN+9 GPTR1 Pointer Pointer to the DE of the first Text Display Template Entity .. . . . .. .. 591 G.27 (TYPE 402, FORM 20) - PIPING FLOW NF+NC+NJ+NN+NT+8 GPTRNT Pointer Pointer to the DE of the last Text Display Template Entity NF+NC+NJ+NN+NT+9 CFPTR1 Pointer Pointer to the DE of the first continuation Flow Associativity Entity .. . . . .. .. NF+NC+NJ+NN+NT+NP+8 CFPTRNP Pointer Pointer to the DE of the last continuation Flow Associativity Entity (the "main" continuation) Additional pointers as required (see Section 2.2.4.4.2). 592 G.27 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY G.28 Dimensioned Geometry Associativity ECO606 This additional form of the Associativity Instance Entity (Type 402) is defined below. See Sec- tion 4.76 for more detail. This entity is intended to replace the existing Dimensioned Geometry Associativity Entity (Type 402, Form 13). When this entity has been tested sufficiently and is moved to the main body of this Specification, that entity (Type 402, Form 13) will be moved to the Obsolete Entities Appendix and its use will be deprecated. FORM NUMBER: 21 Dimensioned Geometry This associativity links a dimension entity with the geometry entities it is dimensioning, so that later, in the receiving database, the dimension can be automatically recalculated and redrawn should the geometry be changed. Due to the generality of the allowed geometry, the GEOMn_PNTs have been introduced to help postprocessors resolve ambiguous situations. GEOMn_PNT refers to the coordinates (GPXn, GPYn, GPZn) which are associated with the pointer GEOMn. A GEOMn_PNT is a point in model space at the point of interest on the geometry. Examples of "points of interest" are a corner of a solid, or an endpoint of a line. If there are two arrowheads in the dimension, it is required that there be two geometry pointers (GEOM1 and GEOM2, NG=2) even if that means repeating a single pointer twice, as in the case of dimensioning a line. This allows space for GEOM1_PNT and GEOM2_PNT. In a straightfor- ward case like dimensioning a line, some postprocessors may ignore the two points as redundant information, but others may depend on them. The dimension orientation flag (DOF) is used for angular, ordinate, and linear dimensions. The values 0-3 are used by the Angular Dimension (Type 202). The values 4-7 are used by the Linear Dimension (Type 216, all forms), and the Ordinate Dimension (Type 218). In the case of angular dimensioning, the angle to be measured is between the first piece of geometry (GEOM1) and the second (GEOM2). Both pieces of geometry are then projected onto the plane of the dimension, and the measurement of the angle is taken in a counterclockwise direction. There are four such angles. The one intended is indicated by the DOF and GEOM1_PNT and GEOM2_PNT, where neither of these two points can be the vertex. In the case of ordinate dimensioning, GEOM1 shall point to the particular geometry whose distance from a baseline is to be measured. GEOM2 shall be set to 0 and the related GEOM2_PNT shall be set to the origin of the baseline. The DOF value shall be determined on the basis of whether the distance to be dimensioned is horizontal or vertical in the dimension's definition space. The values of DOF are as follows (see Figure G33 and Figure G34): 0 The angle starts on the same side of the vertex as GEOM1_PNT and ends on the same side as GEOM2_PNT. This is the default. 1 The angle starts on the opposite side of the vertex from GEOM1_PNT, but ends on the same side as GEOM2_PNT. 2 The angle starts on the same side of the vertex as GEOM1_PNT, and ends on the opposite side as GEOM2_PNT. 3 The angle starts on the opposite side of the vertex from GEOM1_PNT and ends on the opposite side from GEOM2_PNT. 4 The dimension is a true dimension measuring the euclidean distance between GEOM1_PNT and GEOM2_PNT in model space. 593 G.28 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY 5 The dimension is a parallel dimension measuring the distance between GEOM1_PNT and GEOM2_PNT in the XT-YT plane of the definition space of the dimension. 6 The dimension is a vertical dimension measuring the YT distance in definition space of the dimension between GEOM1_PNT and GEOM2_PNT. 7 The dimension is a horizontal dimension measuring the XT distance in definition space of the dimension between GEOM1_PNT and GEOM2_PNT. 8 The dimension is an AT-ANGLE dimension measuring the distance between GEOM1_PNT and GEOM2_PNT in definition space parallel to a line at angle AV with respect to the XT axis. The dimension location flag (DLF) indicates the relationship between the associated geometry and the position being dimensioned. The values of DLF are as follows: 0 End Point (default). The position being dimensioned is the endpoint of the associated geometry nearest the corresponding GEOMn_PNT. 1 Center. The position being dimensioned is the center of the associated geometry. The corre- sponding GEOMn_PNT is ignored. 2 Tangent Point. The position being dimensioned is the point on the associated geometry where the tangent to the geometry is perpendicular to the direction in which the dimension is being measured. If multiple points qualify, the one nearest the corresponding GEOMn_PNT is used. 3 Perpendicular Point. The position being dimensioned is the point on the associated geometry where the normal to the geometry is perpendicular to the direction in which the dimension is being measured. If multiple points qualify, the one nearest the corresponding GEOMn_PNT is used. 4 Relative Parameter Value. The position being dimensioned is the point on the associated geometry nearest the corresponding GEOMn_PNT. If the geometry is modified, the new di- mension position is at the same relative parameter value on the resulting geometry as the original position was on the original geometry. 5 Relative Arc Length. The position being dimensioned is the point on the associated geometry nearest the corresponding GEOMn_PNT. If the geometry is modified, the new dimension position is at the same relative arc length on the resulting geometry as the original position was on the original geometry. Figure G35 illustrates the effects of each value of DLF. An instance of this property must have its Subordinate Entity Switch set to Physically Dependent; it is physically dependent on the dimension entity that backpoints to it. That backpointer must be the only pointer to this associativity entity in the data file. 594 G.28 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY DEFINITION Index__ Set_Value___ Meaning____ 1 2 Two classes Class 1 (Dimension Entity) 2 1 Back pointers required 3 2 Unordered 4 3 Three items per entry 5 1 Pointer to a Dimension Entity 6 2 Dimension Orientation Flag 7 2 Angle value Class 2 (Related Geometry) 8 2 Back pointers not required 9 2 Ordered 10 5 Five items per entry 11 1 Pointer to geometry 12 2 Dimension location flag 13 2 X coordinate of a point on the geometry 14 2 Y coordinate of a point on the geometry 15 2 Z coordinate of a point on the geometry 595 G.28 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 402 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0102** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 402 |< n:a: > |< n:a: > | # | 21 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 ND Integer Number of dimensions (ND=1) 2 NG Integer Number of associated geometry entities 3 DIMPTR Pointer Pointer to the DE of the dimension entity 4 DOF Integer Dimension Orientation Flag 5 AV Real Angle Value 6 GEOM1 Pointer Pointer to the DE of the first geometry entity 7 DLF1 Integer Dimension location flag for GEOM1 8 GPX1 Real Coordinate of point on GEOM1 9 GPY1 Real 10 GPZ1 Real .. . . . .. .. NG*5+1 GEOMNG Pointer Pointer to the DE of the last geometry entity or zero NG*5+2 DLFNG Integer Dimension location flag for GEOMng NG*5+3 GPXNG Real Coordinate of point on GEOMng or origin of base line NG*5+4 GPYNG Real NG*5+5 GPZNG Real Additional pointers as required (see Section 2.2.4.4.2). 596 G.28 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY Figure G33. Use of DOF with Angular Dimensions. Figure G34. Use of DOF with Linear and Ordinate Dimensions. 597 G.28 (TYPE 402 FORM 21) - DIMENSIONED GEOMETRY Figure G35. Use of DLF. 598 G.29 DRAWING ENTITY (TYPE 404, FORM 1) G.29 Drawing Entity (Type 404, Form 1) ECO538 This additional form of the Drawing Entity (Type 404) is defined below. See Section 4.77 for more detail. Some CAD systems maintain a rotation, in addition to a translation and scaling, between the view and drawing coordinate systems. It is not possible to correctly capture the relationships among all three coordinate systems_model, view and drawing_using Form 0 of the Drawing Entity. A rotation is needed in addition to the translation for transforming view to drawing coordinates provided by Form 0. As with Form 0, the transformation for Form 1 is controlled by the view scale factor S and the view origin drawing location. In addition, a rotation angle is applied as follows: 2 XV 3 XD cos - sin 0 4 5 XORIGIN Y D = S sin cos 0 YZVV + Y ORIGIN Systems not having the ability to apply a rotation between their view and drawing coordinate systems will have to choose which of the two to keep correctly. It is recommended that drawing coordinates be maintained in preference to view coordinates in all cases where both coordinate systems cannot be maintained in the receiving system. To do this, the rotation must be incorporated into the transformation from Model to View coordinates. If there is plane clipping, the situation is more complex, as clipping is done in View coordinates. In this case, conceptually (there are other ways of obtaining the same result), the following must be done: o Transform from model to view space. o Perform clipping. o Perform projection onto the view plane. o Transform from view space to drawing space. 599 G.29 DRAWING ENTITY (TYPE 404, FORM 1) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 404 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0001** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 404 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of View pointers 2 VPTR1 Pointer Pointer to the DE of the first View Entity 3 XORIGIN1 Real Drawing space coordinate of the origin of the first transformed View 4 YORIGIN1 Real Drawing space coordinate of the origin of the first transformed View 5 ANGLE1 Real Orientation angle for first transformed View (default = 0.0) .. . . . .. .. -2+4*N VPTRN Pointer Pointer to the DE of the last View Entity -1+4*N XORIGINN Real Drawing space coordinate of the origin of the last transformed View 4*N YORIGINN Real Drawing space coordinate of the origin of the last transformed View 1+4*N ANGLEN Real Orientation angle for last transformed View (default = 0.0) 2+4*N M Integer Number of Annotation Entities (may be zero) 3+4*N DPRT1 Pointer Pointer to the DE of the first Annotation Entity in this Drawing .. . . . .. .. 2+M+4*N DPRTM Pointer Pointer to the DE of the last Annotation Entity in this Drawing Additional pointers as required (see Section 2.2.4.4.2). 600 G.29 (TYPE 406, FORM 18) - INTERCHARACTER SPACING G.30 Intercharacter Spacing Property ECO605 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 18 Intercharacter Spacing The intercharacter spacing is used to specify the gap between letters when fixed-pitch spacing is used. It is applicable to text generated by the General Note and Text Template Entities. The gap is specified as a percentage of the text height. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 18 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP = 1) 2 ISPACE Real Intercharacter Space in percent of text height (Range 0. to 100.) Additional pointers as required (see Section 2.2.4.4.2). ECO605 601 G.31 (TYPE 406, FORM 19) - LINE FONT G.31 Line Font Property ECO530 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more detail. FORM NUMBER: 19 Line Font This property provides the ability to specify a line font pattern from a predefined list rather than from Directory Entry Field 4 (either the default line font patterns, or those available by defining a repeating pattern using the Line Font Definition Entity (Type 304)). Illustrations of line font patterns are found in Figure G36. It is not intended that exact visual equivalence be preserved. The receiving system is to use similar but not necessarily identical patterns based on the pattern codes; the intention is to preserve the functionality implicit in the code. If the receiving system does not have a similar pattern, the default is to use the pattern specified by DE Field 4 of the entity pointing to this property. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 19 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 LFPC Integer Line Font Pattern Code (see Figure G36) Additional pointers as required (see Section 2.2.4.4.2). 602 G.31 LINE FONT PROPERTY ______________________________________________________________________ |__LFPC__|__________________Meaning______________________Authority__|_ | 12 |Compressed Air Line | [ANSI72] | | 14 |Duct & Air | [ANSI72] | | 16 |Mech Pipe & Air | [ANSI72] | | 18 |Mech Pipe Duct & Air | [ANSI72] | | 22 |Gas Pipe Line | [ANSI72] | | 42 |High-Pressure Steam | [ANSI79a] | | 44 |High-Pressure Return | [ANSI79a] | | 46 |Medium-Pressure Steam | [ANSI79a] | | 48 |Medium-Pressure Return | [ANSI79a] | | 52 |Feedwater Pump Discharge | [ANSI79a] | | 54 |Condensate or Vacuum Pump Discharge | [ANSI79a] | | 152 | Fence (on Street Line) | [ANSI72] | | 154 | Fence (on Railway Property Line) | [ANSI72] | | 156 | Rail Fence | [ANSI72] | | 162 | Woven Wire Fence | [ANSI72] | | 164 | Barbwire Fence | [ANSI72] | | 166 | Picket Fence | [ANSI72] | | 172 | Hedge Fence | [ANSI72] | | 174 | Stone Fence | [ANSI72] | | 176 | Snow Fence | [ANSI72] | | 178 | Worm Fence | [ANSI72] | | 192 | City | [ANSI72] | | 194 | City Limit | [ANSI72] | | 198 | Fire Limit | [ANSI72] | | 200 | Coke Ovens | [ANSI72] | | 203 | Soil, Waste or Leader (Below Grade) | [ANSI79a] | | 206 | Vent | [ANSI79a] | | 223 | Cold Water | [ANSI79a] | | 227 | Hot Water | [ANSI79a] | | 230 | Hot Water Return | [ANSI79a] | | 232 | Make-up Water | [ANSI79a] | |___237___|_Acid_Waste________________________________|__[ANSI79a]__|_ 603 G.31 (TYPE 406, FORM 19) - LINE FONT Figure G36. Illustrations of Line Font Patterns for Different Values of LFPC 604 G.31 LINE FONT PROPERTY ___________________________________________________________ |__LFPC__|____________Meaning________________Authority__|__ | 239 | Acid Vent | [ANSI79a] | | 240 | Indirect Drain | [ANSI79a] | | 253 | Fire Line | [ANSI79a] | | 270 | Vacuum Cleaning | [ANSI79a] | | 330 | Pneumatic Tubes/Tube Runs | [ANSI79a] | | 355 | Low Pressure Steam Return | [ANSI79a] | | 360 | Boiler Blow Off | [ANSI79a] | | 380 | Air Relief Line | [ANSI79a] | | 385 | Fuel Oil Return | [ANSI79a] | | 390 | Fuel Oil Tank Vent | [ANSI79a] | | 395 | Hot Water Heating Supply | [ANSI79a] | | 400 | Hot Water Heating Return | [ANSI79a] | | 405 | Refrigerant Liquid | [ANSI79a] | | 410 | Refrigerant Discharge | [ANSI79a] | | 415 | Humidification Line | [ANSI79a] | | 420 | Drain | [ANSI79a] | | 425 | Brine Supply | [ANSI79a] | | 430 | Brine Return | [ANSI79a] | | 445 | Branched Head Sprinkler | [ANSI79a] | |___485___|_Fence_Intertrack_______________|__[ANSI79a]__|_ 605 G.31 (TYPE 406, FORM 19) - LINE FONT Figure G36. Illustrations of Line Font Patterns for Different Values of LFPC (Continued) 606 G.31 (TYPE 406, FORM 20) - HIGHLIGHT G.32 Highlight Property ECO534 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more ECO605 details. FORM NUMBER: 20 Highlight The Highlight Property attaches information that an entity is to be displayed in some system de- pendent manner, as it is in GKS (see [ANSI85, ISO7942]), to draw attention to the display of an entity. Blinking or increasing intensity are two possible methods of accomplishing this. Hierarchical application of the Highlight Property is to be the same as is done for Blank Status. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 20 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 HIGHLIGHT Integer Highlight Flag: 0 = entity is not highlighted (default) 1 = entity is highlighted Additional pointers as required (see Section 2.2.4.4.2). 607 G.33 (TYPE 406, FORM 21) - PICK G.33 Pick Property ECO534 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 21 Pick The Pick Property attaches information that an entity may be picked by whatever pick device is used in the receiving system. See [ANSI85, ISO7942] for a discussion of this in the context of the Graphical Kernel System (GKS). Hierarchical application of the Pick Property is to be the same as is done for Blank Status. Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 21 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=1) 2 PICK Integer Pick flag: 0 = entity is pickable (default) 1 = entity is not pickable Additional pointers as required (see Section 2.2.4.4.2). 608 G.33 (TYPE 406, FORM 22) - UNIFORM RECTANGULAR GRID G.34 Uniform Rectangular Grid Property ECO534 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more ECO605 details. FORM NUMBER: 22 Uniform Rectangular Grid This property stores sufficient information for the creation of a uniform rectangular grid within a drawing. It must be attached to the Drawing Entity (Type 404). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 22 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP = 9) 2 FFLAG Integer Finite/infinite grid flag: 0 = infinite, 1 = finite 3 LFLAG Integer Line/point grid flag: 0 = points, 1 = lines 4 WFLAG Integer Weighted/unweighted grid flag (Weighting means the nearest grid point will be selected by screen position indication by cur- sor, light pen or other such means.): 0 = weighted, 1 = un- weighted 5 PX Real X coordinate of a point on the grid in drawing coordinates. If the grid is finite, this point is the lower left corner of the grid. If the grid is infinite, this point is an arbitrary point on the grid. 6 PY Real Y coordinate of a point on the grid in drawing coordinates. If the grid is finite, this point is the lower left corner of the grid. If the grid is infinite, this point is an arbitrary point on the grid. 7 DX Real Grid spacing in X direction in drawing coordinates 8 DY Real Grid spacing in Y direction in drawing coordinates 9 NX Integer Number of points/lines in X direction (only applicable if FFLAG = 1) 10 NY Integer Number of points/lines in Y direction (only applicable if FFLAG = 1) Additional pointers as required (see Section 2.2.4.4.2). 609 G.35 (TYPE 406, FORM 23) - ASSOCIATIVITY GROUP TYPE G.35 Associativity Group Type Property ECO571 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more detail. FORM NUMBER: 23 Associativity Group Type The Associativity Group Type Property is used to assign an unambiguous identification to a Group Associativity. This allows for the automated processing of the Unordered Group with Backpointers Entity (Type 402, Form 1), the Unordered Group without Backpointers Entity (Type 402, Form 7), the Ordered Group with Backpointers Entity (Type 402, Form 14), and the Ordered Group without Backpointers Entity (Type 402, Form 15). This property may be attached to only these four associativity types. It includes a Type and a Name. The following definitions and abbreviations are used in the entity description. TYPE. The Type field is an enumerated list, specifying a particular associativity type. The list of Type field values may be extended by modification of the specification. __________________________________________________ |___Value___|________Designated_Type________|_____ | 1 |Insertion Sequence | | 2 |Functional Group | | 3 |Work Cell | | 4 |Fiducial | | 5 |Drill Path | | 6 |Profile Routing Sequence | | 7 |Component Trimming Sequence | | 8-5000 | other associativity types | |__5001-9999__|implementor_defined_types_______|__ NAME. The Name field can be used to further identify the associativity. The Name field is specified by native CAD/CAM system properties, the user, or other means. One example of the usage of the Associativity Group Type Property is to group electronic compo- nents for proper insertion sequence. In this example the entities to be inserted would be grouped with the Ordered Group without Backpointers Associativity Entity (Type 402, Form 15) and the Associativity Group Type Property would be attached to the associativity. The Type field would contain the value 1, indicating the associativity is an insertion sequence. The Name field would contain the string "DIPS" (or other meaningful user-specified name), distinguishing it from other insertion sequences (e.g., "RESISTORS"). In some case (e.g., Drill Path), it may be necessary to specify an overall group of smaller groups (e.g., if each Drill Path is for a unique drill size, then the sequence of individual Drill Paths may be specified). In these cases, one of the group associativities (as appropriate to the application) should be used as a parent (Subordinate Entity Switch = 00) to the individual (child) group associativities (Subordinate Entity Switch = 02). The parent associativity should have an Associativity Group Type Property attached which specifies the same type of associativity as the child associativities. 610 G.35 ASSOCIATIVITY GROUP TYPE PROPERTY Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 23 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Specifies the number parameter data fields (NP=2) 2 TYPE Integer Specifies the type of the attached associativity 3 NAME String Uniquely identifies a particular instance of an associativity of type TYPE Additional pointers as required (see Section 2.2.4.4.2). 611 G.36 (TYPE 406, FORM 24) - LEVEL TO PWB LAYER MAP G.36 Level to PWB Layer Map Property ECO573 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more detail. FORM NUMBER: 24 Level to PWB Layer Map The Level to PWB Layer Map property is used to correlate an exchange file level number with its corresponding native level identifier, physical PWB layer number, and predefined functional level identification. Therefore, the postprocessor of the exchange file can interpret the individual entity level number in terms of what physical PWB layer it maps to. Furthermore, the postprocessor can determine what the functional use of the level was in the native system by analyzing the predefined functional level identification. This property should be attached to the entity defining the Printed Wire Assembly (PWA) or, if no such entity exists, then the property should stand alone in the file. In order to unambiguously represent what the intended functionality of the level was in the native system, the functional level identification must be selected from a predefined list. There is no specific way to determine which side of a board is the top or bottom; it is an arbitrary decision. However, it is necessary to set a baseline orientation from which many other functions will be associated. Through the assignment of the functional level identifiers, the top and bottom side of the board becomes established. All consequent functions that require identifying the top and/or bottom of the board will utilize this method of identification. The following list represents the current set of key-words. If the level identification key-word is followed by the string (T/#/B), then it specifies that the actual level identification can be either level, level_T, level_# or level_B. level Represents data on a generic level. (A generic level attribute specifies that the base entity is associated with one or more levels based on a set of corresponding specific levels.) level_T Represents data on a specific level that maps into the top board layer. level_# Represents data on a specific level that maps into an internal board layer (where # is equal to the internal physical layer number 2,3,4,5,. .,.etc.) level_B Represents data on a specific level that maps into the bottom board layer. Level Identification Description ANNOTATION General comment text and graphics. ANNOTATION (T/#/B) General comment text and graphics that are associated with data on a specific physical layer. BOARD_OUTLINE Board outline. BREAKOUT (T/#/B) Component breakout leads. COMP_OUTLINE (T/#/B) Component placement outlines. COMP_PLACEMENT (T/#/B) Component placement instances. ERRORS Error data. GLUE_MASK (T/#/B) Glue outlines. GROUND (T/#/B) Conductive ground planes. PAD (T/#/B) Component pad geometry. PIN_ID (T/#/B) Pin identification text. PIN_PLACE (T/#/B) Pin instances. PLACE_KEEPIN (T/#/B) Component placement keepin outlines. PLACE_KEEPOUT (T/#/B) Component placement keepout outlines. POWER (T/#/B) Conductive power planes. 612 G.36 (TYPE 406, FORM 24) - LEVEL TO PWB LAYER MAP PRD_ID (T/#/B) Primary Reference Designator text. ROUTING_KEEPIN (T/#/B) Routing keepin outlines. ROUTING_KEEPOUT (T/#/B) Routing keepout outlines. SIGNAL (T/#/B) Signal traces. SIGNAL_GUIDE Signal guide wires. SIGNAL_ID (T/#/B) Signal identification text. SILKSCREEN (T/#/B) Silkscreen data. SOLDER_MASK (T/#/B) Solder outlines. SOLDER_PASTE_MASK (T/#/B) Solder paste outlines. UNDEFINED Undefined with no suffix, specifies that the native level number's functionality is not currently defined within the set of exchange file level identifications and the level does not map into a specific physical layer. UNDEFINED (T/#/B) Undefined with the (T/#/B) suffix, specifies that the native level number's functionality is not currently defined within the set of exchange file level identifications and the level maps into a specific physical layer. VIA_KEEPIN (T/#/B) Via keepin outlines. VIA_KEEPOUT (T/#/B) Via keepout outlines. VIA_PLACE (T/#/B) Via instances. Note: If a level number is found in an entity subordinate to the Network Subfigure Definition that is used to define the PWA, and the level number is not listed in the Level to PWB Layer Map property, then it is assumed that the level does not correspond to a physical layer of the board, and is intended to be a general annotation of the model. However, for levels that do not correspond with a physical layer, they should be entered in this property, specified with a physical layer equal to zero and a functional identification equal to UNDEFINED. 613 G.36 (TYPE 406, FORM 24) - LEVEL TO PWB LAYER MAP Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 24 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 NLD Integer Number of level to layer definitions 3 IL1 Integer Exchange file level number for the first level definition 4 NLID1 String Identification that the sending system used to identify the na- tive level that was mapped to the first exchange file level number 5 PLN1 Integer Physical layer number that the first level number applies to. If the level does not apply to data that maps to a physical layer of the PWB, set this field to zero 6 FLN1 String Exchange file level identification for the first level number 7 IL2 Integer Exchange file level number for the second level definition .. . . . .. .. 2+4*NLD FLNn String Exchange file level identification for the last level number Additional pointers as required (see Section 2.2.4.4.2). 614 G.36 (TYPE 406, FORM 25) - PWB ARTWORK STACKUP G.37 PWB Artwork Stackup Property ECO574 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more ECO605 detail. FORM NUMBER: 25 PWB Artwork Stackup Property The Printed Wire Board Artwork Stackup Property is used to communicate which exchange file levels are to be combined in order to create the artwork for a printed wire board (PWB). This property should be attached to the entity defining the printed wire assembly (PWA) or, if no such entity exists, then the property should stand alone in the file. Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 25 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 ID String Artwork stackup identification 3 NV Integer Number of level number values 4 L1 Integer First level number .. . . . .. .. 3+NV LNV Integer Last level number Additional pointers as required (see Section 2.2.4.4.2). 615 G.38 (TYPE 406, FORM 26) - PWB DRILLED HOLE G.38 PWB Drilled Hole Property ECO575 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more detail. FORM NUMBER: 26 PWB Drilled Hole The Printed Wire Board Drilled Hole Property is used to identify an entity that locates a drilled hole, and to specify the characteristics of the drilled hole. The DE attribute Level Number is used to specify which physical board layers the drilled hole pierces. The method used to convey this information is as follows: 1. Create a Definition Levels Property (Type 406, Form 1). 2. Include a level number for each physical board layer that the drilled hole is to pierce. 3. Reference the Definition Levels Property from the DE Level field attribute of the PWB Drilled Hole Property through a negated pointer. The values included in the Definition Levels Property are exchange file level numbers. In order to determine the actual physical board layers, the post-processor must refer to the physical layer number in the Level to PWB Layer Map Property (Type 406, Form 24). The PWB Drilled Hole Property should be attached to the following base entities: o Connect Point Entity (Type 132), when the drilled hole is used to define a component thru-pin. o Point Entity (Type 116), when the drilled hole is used to define a via, mounting, or tooling hole. 616 G.38 (TYPE 406, FORM 26) - PWB DRILLED HOLE Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > | ) |< n:a: > |< n:a: > |< n:a: > |**??**** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 26 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Note: The Level is ignored if this Property is subordinate (see Sections 4.78 and 1.7.1). Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=3) 2 DDS Real Drill diameter size 3 FDS Real Finish diameter size 4 FC Integer Function code for the drilled hole: 1 = Nonplated hole for general assembly purposes 2 = Plated hole for general assembly purposes 3 = Nonplated tooling hole 4 = Plated tooling hole 5 = Plated hole for component pins and vias 5001-9999 = Implementor-defined hole types Additional pointers as required (see Section 2.2.4.4.2). 617 G.39 (TYPE 406, FORM 27) - GENERIC DATA G.39 Generic Data Property ECO601 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 27 Generic Data The Generic Data Property is used to communicate information which is defined by the system operator while creating the model. The information is system specific and does not map into one of the predefined properties or associativites. Properties and property values can be defined by multiple instances of this property. An instance of this property must have its Subordinate entity switch set to Physically Dependent; it is dependent upon either a single entity or a group of geometric entities. In cases where the system cannot process operator defined properties, these entities can either be ignored or be inserted as text at some logical location. Definitions. The following definitions and abbreviations are used in the entity description. Property Name (NAME). The Name field is used to identify the property. The Name field is specified by native CAD/CAM system properties, the user, or other means. Property Type (TYP). The Type field is an enumerated list, specifying a particular property type. The list of Type field values may be extended by modification of the specification. ______________________________ |__Value__|Data_Type______|___ | 0 |No value | | 1 |Integer | | 2 |Real | | 3 |Character string | | 4 |Pointer | | 5 |Not used | |____6____|Logical___________|_ Property Value (VAL). Each Value field contains a property value whose type is specified by the associated Type field. 618 G.39 (TYPE 406, FORM 27) - GENERIC DATA Directory Entry ECO610 |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0102** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 27 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values 2 NAME String Property name 3 NV Integer Number of TYPE/VALUE pairs 4 TYP1 Integer First property value data type 5 VAL1 Variable First property value .. . . . .. .. 2+2*NV TYPNV Integer Last property value data type 3+2*NV VALNV Variable Last property value Additional pointers as required (see Section 2.2.4.4.2). 619 G.40 (TYPE 406, FORM 28) - DIMENSION UNITS G.40 Dimension Units Property ECO606 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 28 Dimension Units The Dimension Units Property describes the units and formatting details of the nominal value of a dimension. One or two properties may be associated with the same dimension depending on whether single or dual dimensioning is being used. The Unit Indicator (UI) parameter defines the units to be used for calculating and displaying this dimension value. The following table defines the available units: ________________________________________________ |__Value__|Meaning__________________________|___ | 0 |Use units from Global Section | | 1-11 |see section 2.2.4.2.14 for meaning | | 100 |Degrees | | 101 |Degrees/minutes | | 102 |Degrees/minutes/seconds | | 103 |Radians | | 104 |Grads | | 105 |Feet/inches | |___106___|Key-in_text________________________|_ The CHRSET font characteristic parameter is used in conjunction with USTRING to allow specifi- cation of font characteristic (FC) with special symbols (e.g., the degree symbol). (See General Note Entity (Type 212).) The USTRING will be appended to the numeric value of the dimension to form the value displayed. For dimensions in which multiple numeric values are generated, (e.g., degrees/minutes/seconds), the USTRING consists of n subparts separated by the character "/" (slash). For example, USTRING could be 3H'/" for distances in feet and inches. A single instance of this property may be pointed to by several dimensions. 620 G.40 (TYPE 406, FORM 28) - DIMENSION UNITS Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0202** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 28 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=6) 2 SPOS Integer Position of secondary dimension with respect to primary dimen- sion 0 = This is main text 1 = Secondary dimension before primary dimension 2 = Secondary dimension after primary dimension 3 = Secondary dimension above primary dimension 4 = Secondary dimension below primary dimension 3 UI Integer Units indicator 4 CHRSET Integer Character Set Interpretation (default=1): 1 = Standard ASCII 1001 = Symbol Font 1 1002 = Symbol Font 2 1003 = Drafting Font 5 USTRING String String used in formatting value 6 FFLAG Integer Fraction Flag 0 = Show value as decimal 1 = Show value as fraction 7 PREC Integer Precision/Denominator Number of decimal places when FFLAG=0 Denominator of fraction when FFLAG=1 Additional pointers as required (see Section 2.2.4.4.2). 621 G.41 (TYPE 406, FORM 29) - DIMENSION TOLERANCE G.41 Dimension Tolerance Property ECO606 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 29 Dimension Tolerance The Dimension Tolerance Property provides tolerance information for a dimension. This information can be used by the receiving system to regenerate the dimension. A dimension may point to 0, 1, or 2 Dimension Tolerance Properties. SFLAG indicates whether the property applies to the primary or to the secondary dimension value. TYP indicates which tolerance format should be displayed. Figure G37 illustrates the available tolerance formats. UTOL and LTOL are the upper and lower tolerance values, in the units of the value being toleranced. For bilateral tolerances, UTOL is used as the tolerance value. When only one tolerance value is to be displayed, the other value is ignored. SSPFLG indicates whether the plus sign should be suppressed when the upper tolerance is displayed. TRUE implies suppress the display of the plus sign. When FFLAG is 0, values are displayed as decimal numbers and PREC specifies the number of digits to be displayed to the right of the decimal point. When FFLAG is 1, values are displayed as mixed fractions and PREC specifies the value to be used as the denominator of the fraction. When FFLAG is 2, values are displayed as fractions. The following table illustrates the use of FFLAG and PREC: _________________________________________________________________________ |__PREC__|__Value__|__FFLAG_=_0__|_____FFLAG_=_1__|______FFLAG_=_2__|____ | 0 |2.65 | 3 | 3 | 3 | | | | | | | | 1 |2.65 | 2.7 | 3 | 3_ | | | | | | 1 | | 2 |2.65 | 2.65 | 2 1_ | 5_ | | | | | 2 | 2 | | 2 | 2.4 | 2.40 | 2 1_ | 5_ | | | | | 2 | 2 | | 3 |2.65 | 2.650 | 2 2_ | 8_ | | | | | 3 | 3 | | 3 |1.93 | 1.930 | 2 | 6_ | |___________|_______|________________|_________________|_______3_________| If PREC is 0, then values are displayed as whole numbers. A single instance of this property may be pointed to by several dimensions. 622 G.41 (TYPE 406, FORM 29) - DIMENSION TOLERANCE Directory Entry ECO610 |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0202** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 29 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=8) 2 SFLAG Integer Secondary tolerance flag 0 = Tolerance applies to primary dimension 1 = Tolerance applies to secondary dimension 2 = Display values as fractions 3 TYP Integer Tolerance type (no default) 1 = Bilateral 2 = Upper/Lower 3 = Unilateral upper 4 = Unilateral lower 5 = Range - min before max 6 = Range - min after max 7 = Range - min above max 8 = Range - min below max 9 = Nominal + Range - min above max 10 = Nominal + Range - min below max 4 TPFLAG Integer Tolerance placement (default = 2) 1 = Placement before nominal value 2 = Placement after nominal value 3 = Placement above nominal value 4 = Placement below nominal value 5 UTOL Real Upper or bilateral tolerance value 6 LTOL Real Lower tolerance value 7 SSPFLG Logical Sign suppression flag (TRUE implies suppress the display of the plus sign.) 8 FFLAG Integer Fraction flag 0 = Display values as decimal numbers 1 = Display values as mixed fractions 2 = Display values as fractions 9 PREC Integer Precision for value display Additional pointers as required (see Section 2.2.4.4.2). 623 G.41 (TYPE 406, FORM 29) - DIMENSION TOLERANCE Figure G37. Examples of tolerance formats (UTOL = 0.01, LTOL = -0.02) 624 G.41 (TYPE 406, FORM 30) - DIMENSION DISPLAY DATA G.42 Dimension Display Data Property ECO606 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 30 Dimension Display Data The Dimension Display Data Property is optional but when present must be referenced by a dimen- ECO610 sion entity. The information it contains could be extracted from the text, leader, and witness line data with difficulty. Display data is saved with dimensions by many systems. DT=2 if and only if a Basic Dimension Property (Type 406, Form 31) is also associated with the same dimension. An example of a label in a dimension is "Radius" in "Radius 3 ft.". In this example the preferred label position LP=1 (before) and the label string LS=6HRadius. Had the text instead been "3 Ft. Radius", then LP=2. The word preferred is used because a system may have to place the label above instead of before if the space between the witness lines is too small to accomodate strung out text. CHRSET, the font characteristic for the label, is particularly important when the label is a special character like a diameter symbol that only exists in some fonts. The diameter symbol in font 1003 has the same ASCII code as lowercase "n" in conventional fonts. So CHRSET=1003, LS=1Hn conveys that the label is a diameter symbol. The witness line angle is the angle in dimension definition space (the plane of the dimension text) measured counterclockwise between the first witness line and the line between the arrowheads. TA=0 means that the text is to appear parallel to the XT-axis in dimension definition space. TA=1 means that the text is to run parallel to the line between the two arrowheads. TP=0 means that if the text can fit between the witness lines, then it should be placed there as in Figure G38. TP=1 means that the text ideally belongs outside the first-listed witness line, as in Figure G38. Sometimes extra text called a note is affixed to the dimension. If one or more notes exist, then the Supplemental Note Position (SNP) indicates where each block of text is to be placed relative to the rest of the dimension text. The Note Start (NS) and Note End (NE) fields specify which strings in the General Note, pointed to by the dimension, comprise each supplemental note. The note starts with the NSth string and ends with the NEth, inclusive. An instance of this property can be pointed to by more than one dimension if and only if there are no supplemental notes. A particular dimension entity may reference at most one instance of this property. 625 G.42 (TYPE 406, FORM 30) - DIMENSION DISPLAY DATA Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0202** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 30 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=14) 2 DT Integer Dimension Type 0 = Ordinary 1 = Reference (usually with parentheses) 2 = Basic (boxed) 3 LP Integer Preferred label position 0 = Does not exist 1 = Before measurement 2 = After measurement 3 = Above measurement 4 = Below measurement 4 CHRSET Integer Character Set Interpretation (default=1) Meaningful only if LS is non-empty: 1 = Standard ASCII 1001 = Symbol Font 1 1002 = Symbol Font 2 1003 = Drafting Font 5 LS String e.g., 8HDIAMETER 6 DS Integer Decimal symbol 0 = "." (period) 1 = "," (comma) 7 WLA Real Witness line angle in radians. Default is ss=2. 8 TA Integer Text alignment 0 = Horizontal 1 = Parallel 9 TL Integer Text level 0 = Neither above nor below the leaders(s) (default) 1 = Above 2 = Below 10 TP Integer Preferred text placement 0 = Between the witness lines (default) 1 = Outside, near the first the witness line 2 = Outside, near the second the witness line 11 AH Integer Arrowhead orientation 0 = In, pointing out 1 = Out, pointing in 12 IV Real The primary dimension initial value 13 K Integer Number of supplemental notes, or zero 626 G.42 (TYPE 406, FORM 30) - DIMENSION DISPLAY DATA 14 SNP1 Integer First supplemental note 1 = Before the rest of the dimension text 2 = After, but starting at the same level 3 = Above 4 = Below 15 NS1 Integer First note start index 16 NE1 Integer First note end index .. . . . .. .. 11+3*K SNPK Integer Last supplemental note 12+3*K NSK Integer Last note start index 13+3*K NEK Integer Last note end index Additional pointers as required (see Section 2.2.4.4.2). 627 G.42 (TYPE 406, FORM 30) - DIMENSION DISPLAY DATA Figure G38. Placement of Text Using TP and TL. 628 G.42 (TYPE 406, FORM 31) - BASIC DIMENSION G.43 Basic Dimension Property ECO606 This additional form of the Property Entity (Type 406) is defined below. See Section 4.78 for more details. FORM NUMBER: 31 Basic Dimension The Basic Dimension Property indicates that the referencing dimension entity is to be displayed with ECO610 a box around text. Preprocessors are responsible for providing the coordinates of the box corners. The coordinates may be ignored by postprocessors for systems that support the functionality of a Basic dimension; systems without this intrinsic functionality can draw a box by using the coordinates provided. The coordinates represent an ordered list beginning in the lower left corner proceeding counter- clockwise. A rectangular box is drawn connecting these points, starting and terminating at the first point. This property inherits the Hierarchy attributes (line font, view, level, blank status, line weight, and color number) of the dimension that points to it, and it must have the same transformation matrix processing applied to it. An instance of this property cannot be pointed to by more than one dimension. An instance of this property must have its Subordinate Entity Switch set to Physically Dependent. Directory Entry ECO610 |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 406 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |**0102** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 406 |< n:a: > |< n:a: > | # | 31 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 NP Integer Number of property values (NP=8) 2 LLX Real Coordinates of Lower Left corner 3 LLY Real 4 LRX Real Coordinates of Lower Right corner 5 LRY Real 6 URX Real Coordinates of Upper Right corner 7 URY Real 8 ULX Real Coordinates of Upper Left corner 9 ULY Real Additional pointers as required (see Section 2.2.4.4.2). 629 G.44 PERSPECTIVE VIEW ENTITY (TYPE 410, FORM 1) G.44 Perspective View Entity (Type 410, Form 1) ECO507 This additional form of the View Entity (Type 410) is defined below. See Section 4.80 for more detail. The second form of the View Entity (Type 410) supports a perspective view (see Figure G39). To avoid confusion, DE field 7 (pointer to a Transformation Matrix Entity) must contain the value zero. For systems that require an orthogonal Transformation Matrix Entity (Type 124), see Appendix H for information on how to construct one from the information provided in the Parameter Data record. Any geometric projection is defined by a view plane and the projectors that pass through the view plane. It is instructive to think of projectors as rays of light that form an image by passing through the viewed object and striking the view plane. The view plane is positioned perpendicular to the VIEW PLANE NORMAL vector, at a specified VIEW PLANE DISTANCE from the VIEW REFERENCE POINT. The projectors are defined via a point called the CENTER OF PROJECTION (also known as eye point). In perspective views, all projectors emanate from the center of projection and pass through the view plane, as shown in Figure G39. The view coordinate system is defined to be right-handed, with its origin at the VIEW REFERENCE POINT. The view coordinate system has U, V, and W axes, where the V-axis is formed by ortho- graphically projecting the VIEW UP vector onto the view plane. The U-axis is the cross-product of the V-axis crossed with the view plane normal. The W-axis corresponds to the VIEW PLANE NORMAL, offset to pass through the view reference point. The view coordinate system is used in defining clipping windows and depth planes. The left and right sides of the clipping window are specified in view coordinates along the U-axis. The top and bottom sides of the clipping window are specified in view coordinates along the V-axis. The back and front clipping planes are specified in view coordinates along the W-axis. The use of view coordinates implies that the values for clipping windows and depth planes can be negative. 630 G.44 PERSPECTIVE VIEW ENTITY (TYPE 410, FORM 1) Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 410 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > | 0; ) |< n:a: > |**??01** | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 410 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 VNO Integer View number 2 SCALE Real Scale factor 3 VPNX Real View plane normal vector (model space) 4 VPNY Real 5 VPNZ Real 6 VRPX Real View reference point (model space) 7 VRPY Real 8 VRPZ Real 9 CPX Real Center of projection (model space) 10 CPY Real 11 CPZ Real 12 VUPX Real View up vector (model space) 13 VUPY Real 14 VUPZ Real 15 VPD Real View plane distance (model space) 16 UMIN Real View coordinate denoting left side of clipping window 17 UMAX Real View coordinate denoting right side of clipping window 18 VMIN Real View coordinate denoting bottom of clipping window 19 VMAX Real View coordinate denoting top of clipping window 20 DCI Integer Depth clipping indicator: 0 = No depth clipping 1 = Back clipping plane ON 2 = Front clipping plane ON 3 = Back and front clipping planes ON 21 WMIN Real View coordinate denoting location of back clipping plane 22 WMAX Real View coordinate denoting location of front clipping plane Additional pointers as required (see Section 2.2.4.4.2). 631 G.44 PERSPECTIVE VIEW ENTITY (TYPE 410, FORM 1) Figure G39. Definition of a perspective view. Broken lines indicate projectors. The abbreviations are: CP = center of projection, VPN = view plane normal, VRP = view reference point, and VUP = view up vector. The V-axis is the orthographic projection of the VUP vector onto the view plane. 632 G.45 EXTERNAL REFERENCE ENTITY (TYPE 416, FORM 3) G.45 External Reference Entity (Type 416, Form 3) ECO572 This additional form of the External Reference Entity (Type 416) is defined below. See Section 4.83 for more detail. Form 3 of the External Reference Entity is used when it is assumed that a copy of the subfigure exists in native form on the receiving system; this form can only be used to replace the Subfigure Definition Entity (Type 308) and Network Subfigure Definition Entity (Type 320). Directory Entry |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Ty|peParamet|erStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern | | | Matrix | Display| Number | Number | | | | | | | | | | | | | 416 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |00????00 | D # | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Ty|pe Line | Color |Parameter| Form | Reserved | Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|tNumber | | | Label | Subscript| Number | | | | | | | | | | | | | 416 |< n:a: > |< n:a: > | # | 3 | | | | # |D # + 1 | |_________|_________|__________|_________|_________|__________|_________|_________|__________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 EXTNAM String External Reference Entity Symbolic Name Additional pointers as required (see Section 2.2.4.4.2). 633 G.46 EXTERNAL REFERENCE ENTITY (TYPE 416, FORM 4) G.46 External Reference Entity (Type 416, Form 4) ECO604 This additional form of the External Reference Entity (Type 416) is defined below. See Section 4.83 for more detail. Form 4 of the External Reference Entity is used when it is assumed that a copy of the subfigure exists in native form in a library on the receiving system; this form can only be used to replace the Subfigure Definition Entity (Type 308) and Network Subfigure Definition Entity (Type 320). Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 416 | ) |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |< n:a: > |00????00 | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 416 |< n:a: > |< n:a: > | # | 4 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 LIBNAM String Name of library in which EXTNAM resides 2 EXTNAM String External Reference Entity Symbolic Name Additional pointers as required (see Section 2.2.4.4.2). 634 G.47 VERTEX ENTITY (TYPE 502) G.47 Vertex Entity (Type 502) ECO603 The geometry underlying a vertex is a point in R3. A vertex is the bound of an edge and can participate in the bounds of a face. o There are no default values for the vertex. o Transformations cannot be applied to a vertex. G.47.1 Vertex List Entity (Type 502, Form 1) Form 1 of the Vertex Entity is the Vertex List Entity which contains one or more vertices. The Subordinate Entity Switch must be set to Physically Dependent. (Independent Vertex Lists are not permitted.) To avoid ambiguity, the Vertex List Entity is forbidden to have an associated Transformation Matrix Entity (Type 124). The vertex coordinates are defined in model space such that if they were post- processed as Point Entities (Type 116), they would be properly oriented in 3D space such that tests for verification of tolerance could be performed. The Vertex List Entity requires a list of 3D coordinates. Any properties associated with this entity apply to all vertices in the lists. o The order of vertices in this list is not significant. 635 G.47 VERTEX LIST ENTITY (TYPE 502, FORM 1) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 502 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > | 0; ) |??01??** | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 502 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of vertex tuples in list (N > 0) 2 X1 Real Coordinates of first vertex 3 Y1 Real 4 Z1 Real .. . . . .. .. -1+3*N XN Real Coordinates of last vertex 3*N YN Real 1+3*N ZN Real Additional pointers as required (see Section 2.2.4.4.2). 636 G.48 EDGE ENTITY (TYPE 504) G.48 Edge Entity (Type 504) ECO603 The Edge Entity represents the topological construct corresponding to a line segment between two vertices. The edge is not closed since it does not contain the vertices (V 1 and V 2) which bound it. The start and terminate vertices do not have to be distinct. Underlying curve geometry in R3 is required. These curves must be represented parametrically, and must be continuous and non-self intersecting in the arc of the curve underlying the edge. The natural orientation of the edge is in the same direction as its underlying curve in R3. Thus the edge is traced from start vertex to terminate vertex as the underlying curve is traced in the direction of increasing parameter value. G.48.1 Edge List Entity (Type 504, Form 1) Form 1 of the Edge Entity is the Edge List Entity. The list of curve entity types that may be used with the Edge List Entity are given below: _________________________________________________ | Entity | | |__Type_Number__|__________Entity_Type_______|___ | 100 |Circular Arc | | 102 |Composite Curve | | 104 |Conic Arc | | 106/11 |2D Path | | 106/12 |3D Path | | 106/63 |Closed Planar Curve | | 110 |Line | | 112 |Parametric Spline Curve | | 126 |Rational B-Spline Curve | |________130________|Offset_Curve______________|_ The Edge List Entity must have its Subordinate Entity Switch set to Physically Dependent. (Inde- pendent Edge Lists are not permitted.) Its Hierarchy Flag must be set to 01. The start and terminate vertices are represented by a pointer to the DE of a Vertex List Entity (Type 502, Form 1), and by a list index into the list. The Edge List Entity requires underlying curve geometry in R3. Any properties associated with the entity are associated with all members of the list. o The order of edges in this list is not significant. 637 G.48 EDGE LIST ENTITY (TYPE 504, FORM 1) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 504 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > | 0; ) |??01??01 | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 504 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of edge tuples in list (N > 0) 2 CURV1 Pointer Pointer to the DE of the first model space curve 3 SVP1 Pointer Pointer to the DE of the Vertex List Entity (Type 502, Form 1) for the first start vertex 4 SV1 Integer List Index of the first start vertex in the Vertex List Entity 5 TVP1 Pointer Pointer to the DE of the Vertex List Entity for the first termi- nate vertex 6 TV1 Integer List Index of the first terminate vertex in the Vertex List Entity .. . . . .. .. -3+5*N CURVN Pointer Pointer to the DE of the last model space curve -2+5*N SVPN Pointer Pointer to the DE of the Vertex List Entity for the last start vertex -1+5*N SVN Integer List Index of the last start vertex in the Vertex List Entity 5*N TVPN Pointer Pointer to the DE of the Vertex List Entity for the last terminate vertex 1+5*N TVN Integer List Index of the last terminate vertex in the Vertex List Entity Additional pointers as required (see Section 2.2.4.4.2). 638 G.49 LOOP ENTITY (TYPE 508) G.49 Loop Entity (Type 508) ECO603 Form 1 of the Loop Entity specifies a bound of a face. Typically, a loop represents a connected collection of face boundaries, seams, and poles of a single face (refer to figures in Appendix ??). Its underlying geometry is a connected curve or a single point in R3. This form of the Loop Entity consists of a repeating construct, the edge-use. This construct consists of either an edge, an orientation, and optional parameter space curves, or (in the case of a pole) a vertex and an optional parameter space curve. If the edge-use references an edge, the orientation describes whether the direction of this use of the edge is in agreement with the natural orientation of the edge. An edge-use is only used once in the shell. Let P be a point on the arc of the R3 curve, C, underlying an edge, E. Both P and C lie on surface S. Let N be the vector normal to S at point P . T is a vector at P whose direction is that of C at P . RT is the vector derived by reversing the direction of T . If the edge orientation is true, then the cross product N x T points to the left of E. If the orientation is false, then the cross product N x RT points to the left of the edge. By convention loops are oriented so that the material of the face they bound lies on the left. The loop is represented as an ordered list of edge-uses (EUi; i = 1; n) which has the following properties: o The terminal vertex of EUi is the initial vertex of EUi+1; i = 1; n - 1. o The loop is closed. This implies that the terminal vertex of EUn is the same as the initial vertex of EU1. o The orientation of the loop is defined to be the same as its constituent edge-uses which reference edges. Therefore the direction of the loop at an edge-use which references a vertex, A, can be taken from any edge-use having an underlying edge which has A as either its start or terminate vertex. o Material of the face lies on the left of the edge-uses which make up the loop. This form of the Loop Entity is physically dependent on its parent entity, the Face Entity (Type 510, Form 1). (Independent Loops are not permitted.) Each edge can be represented by either a list index into a Vertex List Entity (Type 502, Form 1), or a list index into an Edge List Entity (Type 504, Form 1). 639 G.49 LOOP ENTITY (TYPE 508) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 508 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > | 0; ) |??01???? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 508 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of edge tuples 2 TYPE1 Integer Type of first edge 0 = Edge 1 = Vertex 3 EDGE1 Pointer Pointer to the DE of the first Vertex List or Edge List Entity 4 NDX1 Integer List Index into Vertex List or Edge List Entity 5 OF1 Logical Orientation flag of first edge with respect to direction of the model space curve(s) (True = agrees) 6 K1 Integer Number of underlying parameter space curves, or zero 7 ISOP11 Logical Isoparametric flag of first parameter space curve (True = curve is isoparametric on the surface underlying the face which this loop bounds) 8 CURV11 Pointer Pointer to the DE of the first parameter space curve in first edge . .. . .. ... 5+2*K1 ISOP1K1 Logical Isoparametric flag of last parameter space curve 6+2*K1 CURV1K1 Pointer Pointer to the DE of the last parameter space curve in first edge .. . . . .. .. M TYPEN Integer Type of last edge 1+M EDGEN Pointer Pointer to the DE of the last Vertex List or Edge List Entity 2+M NDXN Integer List Index into Vertex List or Edge List Entity 3+M OFN Logical Orientation flag of last edge with respect to direction of the model space curve(s) 4+M KN Integer Number of underlying parameter space curves, or zero 5+M ISOPN1 Logical Isoparametric flag of first parameter space curve 6+M CURVN1 Pointer Pointer to the DE of the first parameter space curve in last edge . .. . .. ... 3+M+2*KN ISOPNKN Logical Isoparametric flag of last parameter space curve 4+M+2*KN CURVNKN Pointer Pointer to the DE of the last parameter space curve in last edge Additional pointers as required (see Section 2.2.4.4.2). 640 G.50 FACE ENTITY (TYPE 510) G.50 Face Entity (Type 510) ECO603 Form 1 of the Face Entity is a bound (partial) of R3 which has finite area. The face, F , has an underlying surface, S, and is bounded by one or more loops (Li; i = 1; m). If more than one loop bounds a face, then the loops must be disjoint. The material of the face lies on the left of all the loops bounding the face. See the Loop Entity (Type 508, Form 1) for a definition of left. This form of the Face Entity is physically dependent on its Parent entity, the Shell Entity (Type 514). This form of the Face Entity requires an underlying surface which must be one of the following entity types: ___________________________________________________________ | Entity | | |__Type_Number__|_______________Entity_Type____________|___ | 114 |Parametric Spline Surface | | 118/1 |Ruled Surface | | 120 |Surface of Revolution | | 122 |Tabulated Cylinder | | 128 |Rational B-Spline Surface | | 140 |Offset Surface | | 190 |Plane Surface | | 192 |Right Circular Cylindrical Surface | | 194 |Right Circular Conical Surface | | 196 |Spherical Surface | |________198________|Toroidal_Surface____________________|_ o The portion of the underlying surface of the face covered by the face interior (not including its bounding loops) must be an oriented connected finite 2-manifold having no handles. The surface covered by the faces together with its bounding loops is not so restricted (see Figure ?? in Appendix ??). o The face does not contain its bounds. o The bounds of a face are loops. The outer loop may be chosen arbitrarily by the sending system. o The bounds of a face are disjoint. 641 G.50 FACE ENTITY (TYPE 510) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 510 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > | 0; ) |??01???? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 510 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 SURF Pointer Pointer to the DE of the underlying surface 2 N Integer Number of loops (N > 0) 3 OF Logical Outer loop flag (True implies that the loop identified by LOOP1 is to be considered the outer loop. False implies that no outer loop is identified.) 4 LOOP1 Pointer Pointer to the DE of the first loop of the face .. . . . .. .. 3+N LOOPN Pointer Pointer to the DE of the last loop of the face Additional pointers as required (see Section 2.2.4.4.2). 642 G.51 SHELL ENTITY (TYPE 514) G.51 Shell Entity (Type 514) ECO603 Form 1 of the Shell Entity is a connected entity of dimensionality 2 which divides R3 into two arcwise connected open subsets (parts), one of which is finite. Inside of the shell is defined to be the finite region. The topological normal, N S, of the shell is in the same direction as the normal of any of the surfaces underlying the faces which compose the shell unless the orientation flag associated with the face by the shell is false. In this case the direction of the topological normal can be determined by reversing the direction of the surface normal. o The topological normal at any point on the shell points toward the same part of R3. o The shell must contain at least one use of a face. o Faces used by this form of the shell may not intersect themselves or each other except at their edges. o Edges used by this form of the shell may not intersect except at their vertices. This form of the Shell Entity is physically dependent on its parent entity, the Manifold Solid B-rep Object Entity (Type 186). All Face Entities (Type 510) referenced by this form of the Shell must be Form 1 and have underlying surface geometry. 643 G.51 SHELL ENTITY (TYPE 514) Directory Entry |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |Entity Typ|eParamete|rStructur|eLine Fon|t Level | View |Xformatio|n Label | Status | Sequence| | Number | Data | | Pattern| | | Matrix | Display | Number | Number | | | | | | | | | | | | | 514 | ) |< n:a: > |< n:a: > | #; ) |< n:a: > |< n:a: > | 0; ) |??01???? | D # | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ | | | | | | | | | | | | (11) | (12) | (13) | (14) | (15) | (16) | (17) | (18) | (19) | (20) | |Entity Typ|e Line | Color | Paramete|r Form | Reserved| Reserved| Entity | Entity | Sequence| | Number | Weight | Number |Line Coun|t Number | | | Label | Subscrip|tNumber | | | | | | | | | | | | | 514 |< n:a: > |< n:a: > | # | 1 | | | | # |D # + 1 | |__________|_________|_________|_________|__________|_________|_________|__________|_________|_________|_ Parameter Data Index__ Name____ Type___ Description___ 1 N Integer Number of faces (N > 0) 2 FACE1 Pointer Pointer to the DE of the first face 3 OF1 Logical Orientation flag of first face with respect to the direction of the underlying surface (True = agrees) .. . . . .. .. 2*N FACEN Pointer Pointer to the DE of the last face 1+2*N OFN Logical Orientation flag of last face Additional pointers as required (see Section 2.2.4.4.2). 644 Appendix H. Parallel Projections from Perspective Views ECO507 For those CAD systems that support only parallel projections we recommend using the VIEW REFERENCE POINT, the VIEW UP VECTOR, and the VIEW PLANE NORMAL to construct an analogous view transformation matrix. The process for constructing a suitable transformation matrix is as follows. 1. Perform a translation so that the view reference point becomes the origin. 2. Perform a rotation so that the view plane normal becomes the positive Z-axis. 3. Perform a rotation so that the projection of the view up vector onto the view plane becomes the positive Y-axis. The 4x4 transformation matrix for translating the view reference point to the origin is: 2 3 1 0 0 0 6 0 1 0 0 7 T = 64 0 0 1 0 75 -V RPx -V RPy -V RPz 1 A rotation matrix can be constructed that transforms the view plane normal to the positive Z-axis and the projected view up vector to the positive Y-axis. Let normalized view plane normal = rz = _V_P_N___kV=PZN0k Let cross product of the view up vector with the view plane normal = rx = _V_U_P_x_V_P_N___kV=UXP0x V P N k Let cross product of Z0 with X0 = ry = rz x rx = Y 0 Then the resulting rotation matrix for constructing the view coordinate system is: 2 3 r1x r1y r1z 0 6 r2x r2y r2z 0 7 R = 64 r 7 3x r3y r3z 0 5 0 0 0 1 645 H. PARALLEL PROJECTIONS FROM PERSPECTIVE VIEWS The final transformation matrix is formed by multiplying the translational matrix by the rotational matrix. That is, the general transformation matrix used for creating a parallel view based on the original perspective view parameters is: T x R 646 Appendix I. Deprecated Binary Form ECO529 The formats defined in Section 2.2 and Section 2.3, referred to collectively as the ASCII Form, have character oriented record lines. This Appendix describes a deprecated bit stream binary represen- tation of data used as an alternative format to the ASCII Form. The binary representation of data, including ASCII characters, is organized in multiples of 8-bit bytes. This data is transportable by user selected communication protocols with the data treated as "trans- parent" or bit stream data. All entity parameterizations and data organization are otherwise identical to the ASCII Form. I.1 Constants The following constants need to be represented in the Binary Form: o Integer numbers o Real numbers o String constants o Pointers o Language constants A control byte will precede each value or set of values of the same type unless otherwise specified. The control byte will specify the format of the following value or set of values, the quantity of subsequent values with that format, and whether values other than the initial value following the control byte are present. If the control byte indicates that values subsequent to the initial value of the set are absent, all subsequent values, up to the quantity indicated are assumed to have the same value as the initial value following the control byte. The repetition portion of the control byte is unsigned and biased by 1 so that the true quantity of numbers to which the repetition field applies is one more than the unsigned value of the field. The format of the control byte is shown in Figure I40. I.1.1 Integer Numbers. The structure of an integer number shall be a sign bit followed by a two's complement integer of length I-1 as shown in Figure I41. Two lengths, I, of integer data can be selected by the system which generates the file. 647 I. DEPRECATED BINARY FORM |_1_bito__|_-e_____________o4ebits ________________|_-_________o3ebits ___________|_- |_________|________________________________________|______________________________|_ | P/A | REPETITION | FORMAT | |_________|________________________________________|______________________________|_ P/A = 0 If only the first of a set of repeated values is physically present = 1 If all expected values are physically present REPETITION = (Number of following values - 1) to which this control byte applies FORMAT = 0 If default value is to be used = 1 If single length integer = 2 If double length integer = 3 If single precision floating point = 4 If double precision floating point = 5 If pointer = 6 If text string Figure I40. Format of the Control Byte Used in the Binary Form |__________o8ebits ___________|-1_bito__|_-e__oe I-1 bits _____|_-8N-I_bitso__|_-e |______________________________|_________|_________________________|______________|_ | CONTROL BYTE | SIGN | VALUE | PAD* | |______________________________|_________|_________________________|______________|_ *The PAD of zeroes from 1 to 7 bits is included only if the length I of the integer number is not a multiple of 8 bits Figure I41. Format of an Integer Number in the Binary Form 648 I.1 CONSTANTS The length of single precision data is Is and the length of double precision data is Id, defined in Section I.2.1. I.1.2 Real Numbers. The structure of a real number shall be a sign bit followed by a biased exponent value of NX bits which is a power of 2 and a binary fraction of NF bits. (NX and NF are defined in Section I.2.1.) The value of the number is the sign applied to the fractional part multiplied by two raised to the power specified by the exponent part. The sign field consists of one bit. A sign of 0 indicates a positive number and a sign of 1 indicates a negative number. The exponent field consists of NX bits and is interpreted as an unsigned integer, BX, often referred to as the biased exponent. The value of the exponent is its unbiased value X which is obtained by deducting the bias B=2**(NX-1). The fraction field consists of NF bits interpreted as the low order bits of a normalized (NF+1)- bit fraction part, F. The fraction lies between 0.5 (inclusive) and 1.0 (exclusive). Since the most significant bit of a normalized fraction is always 1, it is not explicitly represented. Numbers with a nonzero biased exponent have a value given by: (-1)SIGN * 2(BX-B) * F The structure of a real number is shown in Figure I42. Two lengths of real data can be selected by specifying the length of each exponent (NX) and the length of each fractional portion (NF). I.1.3 String Constants. Following the control byte will be a character count with a length of Is, defined in Section I.2.1. Where the character count exceeds the capability of an Is length integer, the string is broken up into substrings. In order to indicate that another substring follows the current string, a negative character count is used. The number of characters in the substring is the absolute value of the character count. A positive character count indicates the last substring. The structure of the string constant is shown in Figure I43. I.1.4 Pointers. The structure of a pointer shall be a 32 bit integer. The pointer shall contain the relative byte position of the entity byte count of the DE or PD entity to which it is pointing. A pointer to the first DE entity will have a value of 1. A pointer to the second DE entity will have a value equal to the number of bytes of the first DE entity plus one. A pointer to the first PD entity will have a value of 1. Pointers with values of zero or negative are not actual pointers but may have a default meaning depending upon the context. For example, a defining matrix value of zero would imply that the identity rotation matrix and zero translation vector are used. This case might also be handled by using the control byte to indicate a default value. I.1.5 Language Constants. Language constants are the string constants of the Macro Defini- tion Entity which, in the ASCII Form, are not preceded by nH and are terminated with a record delimiter. In the Binary Form, the format of language constants will be identical to string constants. Each language constant (Macro Statement) will be an individual string constant. 649 I. DEPRECATED BINARY FORM ______oe 8 ______-__o1e____-____oeNX ______-____oeNF ______-8N-(NX+NF+1)_oe ___- | bits | bit | bits | bits | bits | |____________________|_________|__________________|__________________|___________________|_ | | | | | | | CONTROL | SIGN | EXPONENT | BINARY | PAD* | | BYTE | | | FRACTION | | |____________________|_________|__________________|__________________|___________________|_ *The PAD of zeroes from 1 to 7 bits is included only if the length NX+NF+1 of the floating point number is not a multiple of 8 bits Figure I42. Format of a Real Number in the Binary Form 650 I.1 CONSTANTS For_N1_>_0__ ______o8e ______-_____oe IS ______-____o8e ______-_____o8e ______- ______oe8 ______- | bits | bits | bits | bits | | bits | |______________|____________________|_______________|______________|_____ __|_______________|_ | | | | | | | | CONTROL | NUMBER OF | ASCII | ASCII | | ASCII | | BYTE | CHARS (N1) | CHAR 1 | CHAR 2 | @@@@ | CHAR N1 | |______________|____________________|_______________|______________|__ _____|_______________| For_N1_<_0;_._.;.NK__<_0;_NR_>_0___ XK ______o8e ______-_________________________oe (8|N | + I ) bits __________________________-___oe. . . | bits | M S | |______________|___________________________M=1___________________________ __________________|_____ | | | | | | | | CONTROL | NUMBER OF | ASCII | ASCII | | ASCII | | BYTE | CHARS (NM ) | CHAR 1 | CHAR 2 | @@@@ | CHAR |NM | | @@ |______________|____________________|_______________|______________|__ _____|_______________|__ ______________________________________-z_____________________________________" Repeat for NM < 0 (1 M K) . . ._____ IS ______-___________________oe 8NR _____________________- bits | bits | ____________________|____________________________________ __________________|_ | | | | | NUMBER OF | ASCII | ASCII | | ASCII | @@ CHARS (NR ) | CHAR 1 | CHAR 2 | @@@@ | CHAR NR | _______________________|_______________|______________|__ _____|_______________| Figure I43. Structure of a String Constant in the Binary Form |____________________________________________|_ | | | BINARY FLAG SECTION | |____________________________________________|_ | | | START SECTION | | | |____________________________________________|_ | | | GLOBAL SECTION | |____________________________________________|_ | | | DIRECTORY ENTRY SECTION | | | |____________________________________________|_ | | | | | PARAMETER DATA SECTION | | | |____________________________________________|_ | TERMINATE SECTION | |____________________________________________|_ Figure I44. General File Structure in the Binary Form 651 I. DEPRECATED BINARY FORM I.2 File Structure The general file structure is shown in Figure I44 and comprises the following six sections: o Binary Flag Section o Start Section o Global Section o Directory Entry Section o Parameter Data Section o Terminate Section Following each section is zero, one or many 8-bit null padding characters. These characters do not belong to the section and have no meaning. They are provided to assist the creator of a file with physical system limitations such as word or sector boundaries. Following the Terminate Section of the file shall be zero, one, or many null padding characters followed by an 8-bit end of information designator, the ASCII letter E. Any information following the letter E shall be ignored. I.2.1 Binary Flag Section. The format of the Binary Flag Section is shown in Figure I45. The Binary Flag Section contains a letter code indicating that the file is in Binary Form and also contains information required by a postprocessor to decode the file. (In previous versions of this Specification, this section was called the Binary Information Section.) The Binary Flag Section comprises the following data items, all of which are integers unless otherwise specified: o Binary Flag Section identifier consisting of the ASCII letter B. o Binary Flag Section byte count. This byte count (a 32 bit unsigned integer) excludes the 5 bytes required for the section identifier and section byte count. This byte count also excludes any null padding characters. The value of this byte count will be 75. o Length Is of single length integer primitives. o Length Id of double length integer primitives. o Length N Xs of exponent of single precision real primitives. o Length N Fs of binary fraction of single precision real primitives. o Length N Xd of exponent of double precision real primitives. o Length N Fd of binary fraction of double precision real primitives. o ASCII letter B. o Binary Flag Section displacement. This is the byte count of the total length of the Binary Flag Section including all null padding characters. This length is the actual length from the initial B of the Binary Flag Section up to but not including the S of the Start Section. o ASCII letter S. 652 I.2 FILE STRUCTURE ____o8e ____-____oe 32 ______-__o8e ____-__8oe____-__o8e____-__o8e ____-__8oe____-__o8e____- | bits | bits | bits | bits | bits | bits | bits | bits | |__________|___________________|__________|_________|_________|__________|_________|_________| | | | | | | | | | | BINARY FLAG | | | | | | | | | I | I | NX | NF | NX | NF @@ | B | SECTION | S | D | S | S | D | D | | | BYTE COUNT | | | | | | |@ |__________|___________________|__________|_________|_________|__________|_________|_________| ____o8e ____-____oe 32 ______-__o8e ____-____oe 32 ______-__o8e ____-____oe 32 ______- | bits | bits | bits | bits | bits | bits | |__________|___________________|__________|___________________|__________|___________________| | | | | | | | | BINARY FLAG | | START | | GLOBAL @ | B || SECTION || S || SECTION || G || SECTION @@| @@ |DISPLACEMENT | |DISPLACEMENT | |DISPLACEMENT |@ ___________|___________________|__________|___________________|__________|___________________| ____o8e ____-____oe 32 ______-__o8e ____-____oe 32 ______-__o8e ____-____oe 32 ______- | bits | bits | bits | bits | bits | bits | |__________|___________________|__________|___________________|__________|___________________| | | | | | | | | DIRECTORY | | PARAMETER | | TERMINATE @ | D ||ENTRY SECTION || P ||DATA SECTION || T || SECTION @@| @@ |DISPLACEMENT | |DISPLACEMENT | |DISPLACEMENT |@ ___________|___________________|__________|___________________|__________|___________________| ______oe248 ______-__o8e ____-____oe 48 ______-__o8e ____- | bits | bits | bits | bits | |___________________|__________|___________________|__________| | | | | | | | | BLANKS | | @ | UNASSIGNED || B || OR ASCII || 1 || @@ | | ZEROES | | ____________________|__________|___________________|__________| Column 73 Column 80 NOTE: No fields in the Binary Flag Section have control bytes Figure I45. Format of the Binary Flag Section in the Binary Form 653 I. DEPRECATED BINARY FORM o Start Section displacement. This is the byte count of the total length of the Start Section including all control bytes and null padding characters. This length is the actual length from the initial S of the Start Section up to but not including the G of the Global Section. o ASCII letter G. o Global Section displacement. This is the byte count of the total length of the Global Section including all control bytes and null padding characters. This length is the actual length from the initial G of the Global Section up to but not including the D of the Directory Entry Section. o ASCII letter D. o Directory Entry Section displacement. This is the byte count of the total length of the Directory Entry Section including all control bytes and null padding characters. The length is the actual length from the initial D of the Directory Entry Section up to but not including the P of the Parameter Data Section. o ASCII letter P. o Parameter Data Section displacement. This is the byte count of the total length of the Pa- rameter Data Section including all control bytes and null padding characters. This length is the actual length from the initial P of the Parameter Data Section up to but not including the T of the Terminate Section. o ASCII letter T. o Terminate Section displacement. This is the byte count of the total length of the Terminate Section including all null padding characters. This length is the actual length from the initial T of the Terminate Section up to but not including the letter E of the end of information designator. o 31 unassigned bytes. o ASCII letter B. o 6 ASCII blanks or zeroes. o ASCII character 1. No control bytes are applied to this section. Thus the characters in the equivalent of Columns 73 through 80 of the Binary Flag Section are similar in format to the section identification of the ASCII Form and can be used to determine if a file is ASCII or binary. If the file contains an S in Column 73 of its first 80 bytes, it is ASCII (or compressed ASCII if a C). If it contains a B, it is binary. I.2.2 Start Section. The format of the start section is shown in Figure I46. It comprises the following data items: o A Start Section identifier consisting of the ASCII letter S. o Byte count for the Start Section. The byte count excludes the 5 bytes required for the Start Section identifier and section byte count. This byte count also excludes any null padding characters. 654 I.2 FILE STRUCTURE ___oe8 ___-_______oe32 ________- | bits | bits | |_________|______________________|_________________________________________________ | | | | | S* | START SECTION | LANGUAGE/TEXT PRIMITIVES | | | BYTE COUNT* | | |_________|______________________|_________________________________________________| *These fields do not have control bytes Figure I46. Format of the Start Section in the Binary Form o One or more language or text primitives which are logically equivalent to Columns 1 through 72 of the ASCII Form. There is no required physical correspondence between the ASCII Form and language/text primitives. One language/text primitive may contain the equivalent of several complete or partial ASCII records. Carriage return characters may be embedded in the language/text primitives. Control bytes only apply to the language and text primitives. No control bytes precede the section identifier and byte count. I.2.3 Global Section. The format of the Global Section is shown in Figure I47. The Global Section comprises the following data items: o Global Section identifier consisting of the ASCII letter G. o Global Section byte count. This byte count excludes the 5 bytes required for the Global Section identifier and the section byte count. This byte count also excludes any null padding characters. o 24 global parameters. Control bytes apply to only the 24 global parameters. The global parameters have the same sequence and meaning as the ASCII Form Global Parameters with the exception that Global Parameters 1 (parameter delimiter character), 2 (record delimiter), 7 (number of bits for integer representation), 8 (single precision magnitude), 9 (single precision significance), 10 (double precision magnitude), and 11 (double precision significance) shall be ignored in binary form. The Binary Flag Section shall supersede these global parameters. ____8oe____-____oe 32 ______- | bits | bits | |_________|____________________|___________________________________________ ________________________ | | | | | | | | | GLOBAL | GLOBAL | GLOBAL | | GLOBAL | | | | | |@@ @@ | | | G* | SECTION | PARAMETER | PARAMETER | | PARAMETER | | | BYTE COUNT* | 1 | 2 | @ @ | 24 | |_________|____________________|___________________|____________________|__ __|____________________|_ *These fields do not have control bytes Figure I47. Format of the Global Section in the Binary Form 655 I. DEPRECATED BINARY FORM I.2.4 Directory Entry Section. The format of the Directory Entry Section is shown in Fig- ure I48. The Directory Entry Section comprises the following data items: o Directory Entry Section identifier consisting of the ASCII letter D. o Directory Entry Section byte count. This byte count excludes the 5 bytes required for the section identifier and section byte count. This byte count also excludes any null padding characters. o For each directory entry, the following 17 data fields are present: .entity byte count, which is the length in bytes including control bytes, of the subsequent 16 data fields .entity type number .parameter data .structure .line font pattern .level .view .transformation matrix .label display associativity .status number .line weight number .color number .form number .reserved field 1 .reserved field 2 .entity label .entity subscript number Control bytes apply only to the last 16 data fields. The Directory Entry data fields, except for the entity byte count, are identical to and have the same sequence as fields in the ASCII Form. Within a single file, the length of the DE record for each entity (in bytes) shall be consistent. If in the future additional fields are required, it is preferable to increase the number of fields for each Directory Entry and add any new fields subsequent to existing fields. I.2.5 Parameter Data Section. The format of the Parameter Data Section is shown in Fig- ure I49. The Parameter Data Section comprises the following data items: o Parameter Data Section identifier consisting of the ASCII letter P. o Parameter Data Section byte count. This byte count excludes the 5 bytes required for the section identifier and section byte count. This byte count also excludes any null padding characters. 656 I.2 FILE STRUCTURE ____8oe____-______oe 32 ________- | bits | bits | |_________|_________________________|_ | | | | | DIRECTORY | | | | | D* | ENTRY SECTION | | | BYTE COUNT* | |_________|_________________________|_ ______oe 8 ______- | bits | 8 |____________________|_____________________________________________________________ >> | | | | | >>> | | ENTITY | | |@@ >> | ENTITY | | PARAMETER | | >>> |BYTE COUNT* | TYPE | DATA | STRUCTURE >> | | NUMBER | | >>>> |____________________|___________________|____________________|_________________@@_ >>> >>> >>> >>> >>> _____________________|___________________|____________________|___________________|_ >>> @@ LINE | | | TRANSFOR- |@@ >> | | | | >>> | FONT | LEVEL | VIEW | MATION >> | PATTERN | | | MATRIX >>>> @@ |____________________|___________________|____________________|_________________@@_ >>> >>> >>> >>> Repeat >>> _____________________|___________________|____________________|___________________|_ < @@ LABEL | | LINE | |@@ for | STATUS | | COLOR | each >> | DISPLAY | NUMBER | WEIGHT | NUMBER >> |ASSOCIATIVITY | | NUMBER | Entity >>>> @@ |____________________|___________________|____________________|_________________@@_ >>> >>> >>> >>> >>> _____________________|___________________|____________________|___________________|_ >>> @@ | | | |@@ >> FORM | RESERVED | RESERVED | ENTITY | >>> | NUMBER | FIELD 1 | FIELD 2 | LABEL >> | | | | >>>> @@ |____________________|___________________|____________________|_________________@@_ >>> >>> >>> >>> >>> _____________________| >>> @@ ENTITY | >> | *These fields do not have control bytes >>> | SUBSCRIPT | : | NUMBER | @@ |____________________| Figure I48. Format of the Directory Entry (DE) Section in the Binary Form 657 I. DEPRECATED BINARY FORM ____8oe____-____oe 32 ______- | bits | bits | |_________|____________________| | | | | | PARAMETER | | | | | P* |DATA SECTION | | |BYTE COUNT* | |_________|____________________| ______oe 24 ______- ffl_ | bits | | |____________________|_____________________________________________________________ Repeat | | | | | | || | | ENTITY | DIRECTORY | | for __flfi | ENTITY | | | PARAMETER | each | |BYTE COUNT* | TYPE | ENTRY | DATA | | | NUMBER | POINTER | | Entity ||| |____________________|___________________|____________________|___________________|_ ffi_ *These fields do not have control bytes Figure I49. Format of the Parameter Data (PD) Section in the Binary Form o For each Parameter Data entry, the following data fields are required: .entity byte count, which is composed of the lengths, including control bytes, of all subse- quent data fields for this entity .entity type .Directory Entry pointer (relative to Directory Entry section) .Parameter Data. Control bytes apply only to the entity type, Directory Entry pointer and Parameter Data fields. The Parameter Data entry fields, except for the entity byte count, are identical to and have the same sequence as the ASCII Form. I.2.6 Terminate Section. The format of the Terminate Section is shown in Figure I50. The Terminate Section comprises the following data items: o Terminate Section identifier consisting of the ASCII letter T o Terminate Section byte count. This byte count excludes the 5 bytes required for the section identifier and section byte count. This byte count also excludes any null padding characters. o ASCII letter B. o Binary Flag Section byte count, including the section identifier, and section byte count, but excluding any null padding characters. o ASCII letter S. o Start Section byte count, including the section identifier, section byte count, and all control bytes but excluding any null padding characters. 658 I.2 FILE STRUCTURE o ASCII letter G. o Global Section byte count, including the section identifier, section byte count, and all control bytes but excluding any null padding characters. o ASCII letter D. o Directory Entry Section byte count, including the section identifier, section byte count, and all control bytes but excluding any null padding characters. o ASCII letter P. o Parameter Data Section byte count, including the section identifier, section byte count, and all control bytes but excluding any null padding characters. ____o8e____-____oe 32 ______-__o8e____-____oe 32 ______-__o8e____-____oe 32 ______- | bits | bits | bits | bits | bits | bits | |_________|____________________|_________|____________________|_________|____________________| | | | | | | | | TERMINATE | | BINARY | | START | | | | | | @@ | T* | SECTION | B* | SECTION | S* | SECTION | | | BYTE COUNT* | | BYTE COUNT* | | BYTE COUNT* |@ |_________|____________________|_________|____________________|_________|____________________| ____o8e____-____oe 32 ______-__o8e____-____oe 32 ______-__o8e____-____oe 32 ______- | bits | bits | bits | bits | bits | bits | |_________|____________________|_________|____________________|_________|____________________| | | | | | | | | | GLOBAL | | DIRECTORY | | PARAMETER | @ | G* || SECTION || D* ||ENTRY SECTION || P* ||DATA SECTION || @@ | BYTE COUNT* | | BYTE COUNT* | | BYTE COUNT* | __________|____________________|_________|____________________|_________|____________________| *These fields do not have control bytes Figure I50. Format of the Terminate Section in the Binary Form 659 Appendix J. List of References [ANSI68] Code for Information Interchange (X3.4-1968), American National Standards Insti- tute, 1968. [ANSI72] Graphic Symbols for Railroad Maps and Profiles (Y32.7-1972), American National Standards Institute,1972. [ANSI77] Code for Information Interchange (X3.4-1977), American National Standards Insti- tute, 1977. [ANSI78] Programming Language FORTRAN (X3.9-1978), American National Standards In- stitute, 1978. [ANSI79] Line Conventions and Lettering (Y14.2M-1979), American National Standards In- stitute, 1979. [ANSI79a] Graphical Symbols for Pipe Fittings, Valves, and Piping (Z32.2.3-1979), American National Standards Institute, 1979. [ANSI81] Digital Representation for Communication of Product Definition Data, Parts 1,2, and 3, (Y14.26M-1981), American National Standards Institute, 1981. Permanently out of print. [ANSI82] Dimensioning and Tolerancing, (Y14.5M-1982), American National Standards In- stitute, 1982. [ANSI85] Computer Graphics-Graphical Kernel System (GKS), Functional Description, (X3.124-1985), American National Standards, 1985. [ASME87] Digital Representation for Communication of Product Definition Data, (ASME/ANSI Y14.26M-1987), The American Society of Mechnical Engineers or the American National Standards Institute, 1987. [ASME89] Digital Representation for Communication of Product Definition Data, (ASME Y14.26M-1989), The American Society of Mechanical Engineers or the American National Standards Institute, 1989. [DEBO78] deBoor, C., A Practical Guide to Splines, Springer-Verlag, 1978. [DOCA76] DoCarmo, M. P., Differential Geometry of Curves and Surfaces, Prentice Hall, 1976. [FARI88] Farin, G., Curves and Surfaces for Computer Aided Geometric Design, Academic Press, 1988. [FAUX79] Faux, I., and M. J. Pratt, Computational Geometry for Design and Manufacture, John Wiley and Sons, 1979. 660 J. LIST OF REFERENCES [GORD74] Gordon, W. J. and R. F. Riesenfeld, "B-Spline Curves and Surfaces", published in Barnhill, R. E. and R. F. Riesenfeld, ed., Computer Aided Geometric Design, Academic Press, 1974. [GSPC79] Status Report of the Graphics Standards Planning Committee, Computer Graphics 13(3), August 1979. [HILD76] Hildebrand, F., Advanced Calculus for Applications, Prentice Hall, 1976. [HON80] Hon, R. W., and C. H. Sequin, A Guide to LSI Implementation, SSL 79-7, Xerox Palo Alto Research Center, January 1980. [IEEE75] Reference Designators for Electrical and Electronics Parts and Equipment, (IEEE Std 200-1975), Institute of Electrical and Electronics Engineers, 1975. [IEEE76] An American National Standard ASTM/IEEE Standard Metric Practice (IEEE Std 268-1976), Institute of Electrical and Electronics Engineers, 1976. [IEEE84] Standard Dictionary of Electrical and Electronics Terms, (ANSI/IEEE Standard 100-1984), Institute of Electrical and Electronics Engineers, 1984. [IEEE85] Standard for Binary Floating-Point Arithmetic (ANSI/IEEE Std 754-1985), Insti- tute of Electrical and Electronics Engineers, 1985. [IEEE260] IEEE Standard Letter Symbols for Units of Measurement (ANSI/IEEE Std 260), Institute of Electrical and Electronics Engineers, 1978. [IITR68] APT Computer System Manual: Volume 2 - Subroutine Library, Illinois Institute of Technology Research Institute, 1968. [IPCT85] Terms and Definitions for Interconnecting and Packaging Electronic Circuits (ANSI/IPC-T-50C), Institute for Interconnecting and Packaging Electronic Cir- cuits, Revision C, March 1985. [ISO1073] Alphanumeric Character Sets for Optical Recognition - Part II: Character Set OCR- B - Shapes and Dimensions of the Printed Image, (ISO1073/II), International Or- ganization for Standardization, 1976. [ISO7942] Information Processing, Graphical Kernel System (GKS), Functional Description, (ISO7942-1985), International Organization for Standardization, 1985. [JIS6226] Code of the Japanese Graphic Character Set for Information Interchange, (JIS C 6226-1983), Japan Institute for Standardization, 1983. [JOBL78] Joblove, G. H. and D. Greenberg, "Color Spaces for Computer Graphics", SIG- GRAPH Proceedings, 1978. [KAPL52] Kaplan, W., Advanced Calculus, Addison-Wesley, 1952. [MIL12] Abbreviations for Use on Drawings, Specifications, Standards, and in Technical Doc- uments (MIL-STD-12D), U.S. Department of Defense, May 1981. [MIL133] Parameters to be Controlled for the Specification of Microcircuits (MIL-STD-1331), U.S. Department of Defense, August 1970. [MIL195] General Specification for Semiconductors (MIL-STD-19500G), U.S. Department of Defense, August 1987. 661 J. LIST OF REFERENCES ECO609 [NIST90] Initial Graphics Exchange Specification (IGES), Version 5.0, NISTIR 4412, U. S. National Institute of Standards and Technology, 1990. Available from the National Computer Graphics Association (NCGA), Administrator, IGES/PDES Organiza- tion, 2722 Merilee Drive, Suite 200, Fairfax, VA 22031. For copies, contact NCGA Technical Services and Standards, 703-698-9600, extension 325. [NBS80] Initial Graphics Exchange Specification (IGES), Version 1.0, NBSIR 80-1978 (R), U.S. National Bureau of Standards, 1980. Out of print. [NBS83] Initial Graphics Exchange Specification (IGES), Version 2.0, NBSIR 82-2631 (AF), U.S. National Bureau of Standards, 1982. Available from the National Technical Information Service (NTIS) as PB83-137448. [NBS86] Initial Graphics Exchange Specification (IGES), Version 3.0, NBSIR 86-3359, U.S. National Bureau of Standards, 1986. Available from the National Technical Infor- mation Service (NTIS) as PB86-199759. [NBS88] Initial Graphics Exchange Specification (IGES), Version 4.0, NBSIR 88-3813, U. S. National Bureau of Standards, 1988. Available from the National Technical Information Service (NTIS) as PB88-235452. [ROGE76] Rogers, D. F. and J. A. Adams, Mathematical Elements for Computer Graphics, McGraw-Hill, 1976. [SMIT78] Smith, A. R., "Color Gamut Transformation Pairs", Computer Graphics, 1978. [SPICE] Nagel, L. W., SPICE2: A Computer Program to Simulate Semiconductor Circuits, Electronics Research Laboratory Report No. ERL-M520, University of California, 9 May 1975. [THOM60] Thomas, G., Calculus and Analytic Geometry, Addison-Wesley, 1960. [TILO80] Tilove, R. B., and Requicha, A. A. G., "Closure of Boolean Operations on Geometric Entities", Computer Aided Design, Vol. 12, No. 5, September 1980. 662 Appendix K. Glossary The spirit of this Glossary is to provide general, sometimes intuitive information pertaining to certain phrases and concepts either appearing in or alluded to by this document. The spirit is not to provide detailed mathematical definitions such as may be found within the document itself. ANGULAR DIMENSION ENTITY An annotation entity designating the measurement of the angle between two geometric lines. ANNOTATION Text or symbols, not part of the geometric model, which provide information. ARCWISE CONNECTED ECO603 A set is arcwise connected if given two points in the set it is possible to join the two points with a curve such that all points of the curve are in the set. ASSEMBLY ([IEEE75]) A number of basic parts or subassemblies, or any combination thereof, joined together to perform a specific function. ASSOCIATIVITY A structure entity which defines a logical link or relationship between different entities. ASSOCIATIVITY DEFINITION ENTITY A structure entity which designates the type (link structure) and generic meaning of a rela- tionship. (See PREDEFINED ASSOCIATIVITIES) ASSOCIATIVITY INSTANCE ENTITY A structure entity formed by assigning specific values to the data items defining an associativity. ATTRIBUTE Information, provided in specific fields within the directory entry of an entity, which serves to qualify the entity definition. AXONOMETRIC PROJECTION A projection in which only one plane is used, the object being turned so that three faces show. The main axonometric positions are isometric, dimetric, and trimetric. BACK ANNOTATION In electrical engineering, the practice of changing the unique identifier for components noted by symbols on a schematic to match those assigned actual components when the circuit is packaged. 663 K. GLOSSARY BACK POINTER A pointer in the parameter data section of an entity pointing to an associativity instance of which it is a member. BASIC PART ([IEEE75]) One piece, or two or more pieces joined together, which are not normally subject to disassembly without destruction of designed use. BLANK STATUS FLAG A portion of the status number field of the directory entry of an entity designating whether a data item is to be displayed on the output device. BOUNDED PLANE A finite region defined in a plane. BREAKPOINT A member of an increasing sequence of real numbers which is a subsequence of the knot sequence used to specify parametric spline curves. B-SPLINE BASIS A set of functions which form a basis for the set of splines of specified degree on a specified knot sequence. B-spline basis functions are characterized by being splines of minimal support. ECO605 See Appendix B for more details. CENTERLINE ENTITY An annotation entity for representing the axis of symmetry for all symmetric views or portions of views, such as the axis of a cylinder or a cone. CIRCULAR ARC ENTITY A geometric entity which is a connected portion of a circle or the entire circle. CLASS A group of data items pertinent to a common logical relationship in an associativity definition. CLIP To abbreviate or terminate the intended display of an entity along an intersecting curve or surface. CLIPPING BOX A bounding set of surfaces which abbreviate the intended display of data to that portion which lies within the box. CLIPPING PLANE A bounding plane surface which abbreviates the intended display of data to that portion which lies on one or the other side of the plane. CLOSED CURVE A curve with coincident start and terminate points. COMPLEMENTARY ARC Either of the two connected components of a closed, connected, nonintersecting curve which has been divided by two distinct points lying on the curve. 664 K. GLOSSARY COMPONENT Typically a synonym for part (e.g., resistor, capacitor, microcircuit, etc.), but also may refer to a subassembly being treated as a part. The representation of a component may be a collection of entities, associativities, and properties. COMPOSITE CURVE A connected curve which is formed by concatenating one or more curve segments. CONIC ARC ENTITY A geometric entity which is a finite connected portion of an ellipse, a parabola, or a hyperbola. CONNECTED CURVE A curve such that for any two points P1 and P2, one can travel from P1 to P2 without leaving the curve. CONNECTED GRAPH ECO603 A graph is connected if there is a path between any two vertices. CONNECT POINT ENTITY A geometric entity giving the XYZ location and other information (e.g., text labels) of a point of connection. May be independent or subordinate to a Network Subfigure Definition and/or Instance. Used for netlist information. CONSTITUENT A member of a set. CONTROL POINT A point in definition space which appears in the numerator of the expression for a rational B-spline curve or surface. As the weights must all be positive, the resulting curve or surface lies within the convex hull of the control points. Its shape resembles that of the polygon or polyhedron whose vertices are the control points. A control point is sometimes referred to as a B-spline coefficient. See Appendix B for more details. ECO605 COONS PATCH A three dimensional surface. COPIOUS DATA ENTITY A geometric entity sometimes used as an annotation entity, containing arrays of tuples of real numbers to which a specific meaning has been assigned. Each form number corresponds to one special meaning. DEFINITION LEVEL (or DISPLAY LEVEL) The graphics display level (or layer) on which one or more entities have been defined. DEFINITION MATRIX The matrix which transforms the coordinates represented in the definition space into the coordinates represented in the model space. DEFINITION SPACE A local Cartesian coordinate system chosen to represent a geometric entity for the purpose of mathematical simplicity. 665 K. GLOSSARY DEFINITION SPACE SCALE A scale factor applied within an entity definition space. DEVELOPABLE SURFACE A surface which can be unrolled onto a plane. DIAMETER DIMENSION ENTITY An annotation entity designating the measurement of a diameter of a circular arc. DIRECTED CURVE A curve with an associated direction. DIRECTORY ENTRY SECTION The section of an exchange file, consisting of fixed field data items, that forms an index and attribute list of all entities in the file. DIRECTRIX The curve entity used in the definition of a tabulated cylinder entity. DISPLAY SYMBOL A method for graphically representing certain entities (plane, point, section) for identification purposes. DRAWING ENTITY A structure entity which specifies the projection(s) of a model onto a plane, with any required annotation and/or dimension. DRILLED HOLE PROPERTY A predefined property that assigns the physical attribute of a hole that can be made by a drill. May be used in electrical applications to 1) define a via from one printed circuit board, PCB, layer to another, 2) define a plated via hole, and 3) give the first physical drill diameter and/or the finished hole diameters. It is usually attached to a point, circle, subfigure definition, or subfigure instance. EDGE VERTEX A method of geometric modeling in which a two- or three-dimensional object is represented by curve segments (edges of the object) connected to points or vertices of the object. A higher level of topological information can be contained in such a model than is implied by a `wire-frame' terminology, but in the context of this specification the terms are used interchangeably. ENTITY The basic unit of information in a file. The term applies to single items which may be individual elements of geometry, collections of annotation to form dimensions, or collections of entities to form structured entities. ENTITY LABEL A one to eight character identifier for an entity. This term may implicitly include the entity subscript, providing for additional characters. ENTITY SUBSCRIPT A one to eight digit unsigned integer associated with the entity label. The label and subscript specify a unique instance of an entity within an array of entities. 666 K. GLOSSARY ENTITY TYPE NUMBER An integer used to specify the kind of the entity. For example, the Circular Arc Entity has an entity type number of 100. ENTITY USE FLAG A portion of the status number field of the directory entry of an entity to designate whether the entity is used as geometry, annotation, structure, logical, or other. For example, a circle used as part of a point dimension would have an entity use flag which designates annotation. EXTERNAL REFERENCE ENTITY A mechanism for referencing definitions which do not reside in the same exchange file as the instances of those definitions. FACE BOUNDARY ECO603 Within the context of an MSBO, it is a curve along which the face is joined to another. FINITE ELEMENT A small part of a structure defined by the connection of nodes, material, and physical proper- ties. FLAG NOTE ENTITY An annotation entity which takes label information and formats it such that the text is cir- cumscribed by a flag symbol. FLASH ENTITY A geometric entity used for photo-plotting apertures and other filled areas. May be used for representing metallic conductive material on a printed circuit board such as pads and traces. Also, may be used in integrated circuit (IC) chip masks. FLEXIBLE PRINTED CIRCUIT An arrangement of printed circuit and components utilizing flexible base materials with or without flexible cover layers. FLOW ASSOCIATIVITY ENTITY A predefined associativity that represents a flow path. In electrical applications such as schematics and physical descriptions for Printed Wiring Boards, PWB, Printed Circuit Boards, PCB, PCB assemblies, ICs, etc., it presents a common electrical signal (e.g., voltage). In pip- ing applications, it represents a flow path between only one source and sink, but branching is allowed to other Flow Associativities. It provides netlist information for a single flow. FONT CHARACTERISTIC An integer which is used to identify a text font. Font characteristic numbers may be positive which indicate an defined text font or may be negative which is interpreted as a text font definition entity. FORM NUMBER An integer which is used when needed to further define a specific entity. This becomes necessary when there are several interpretations of an entity type. For example, the form number of the conic arc entity indicates whether the curve is an ellipse, hyperbola, parabola, or unspecified. The form number is also used when necessary to supply sufficient information in the directory entry of an entity to allow the structure of the parameters in the parameter data entry to be decoded. 667 K. GLOSSARY GENERAL LABEL ENTITY An annotation entity consisting of a general note with one or more associated leaders. GENERAL NOTE ENTITY An annotation which consists of text which is to be displayed in some specific size and at some specific location and orientation. GENERATRIX The defining curve which is to be swept to generate a tabulated cylinder, or revolved to generate a surface of revolution. ECO603 GENUS The number of handles in a surface. GEOMETRIC Having to do with the shape information (points, curves, surfaces, and volumes), necessary to represent some object. GLOBAL SECTION The section of an exchange file consisting of general information describing the file, the file generator (preprocessor), and information needed by the file reader (postprocessor). ECO603 GRAPH A set of vertices and edges which join pairs of vertices (not necessarily distinct). Vertices which are joined by one edge are adjacent. There may be multiple edges connecting the same two vertices. GRID The set of (ui; vj) where ui and vj are the breakpoints on the u and v coordinates respectively used to specify a parametric spline or rational B-spline surface. The term grid is also applied to the projected image on the spline surface. GROUND PLANE A conductor layer, or portion of a conductor layer (usually a continuous sheet of metal with suitable clearances), used as a common reference point for circuit returns, shieldings, or heat sinking. GROUP ASSOCIATIVITY A predefined associativity for forming any collection of entities. ECO603 HANDLE When a tunnel is drilled through a three-dimensional volume, the corresponding operation on the two-dimensional surface which is the boundary of the volume is adding a handle. This can be thought of as cutting out two disks and connecting their boundaries with a cylindrical tube. For example, adding a handle to a sphere produces a torus. HIERARCHY A tree structure consisting of a root and one or more dependents. In general, the root may have any number of dependents, each of which may have any number of lower-level dependents, and so on, to any number of levels. 668 K. GLOSSARY INSTANCE A particular occurrance of some item or relationship. Several instances may reference the same item. KNOT SEQUENCE A nondecreasing sequence of real numbers used to specify parametric spline curves. LABEL DISPLAY ASSOCIATIVITY A predefined associativity that is used by those entities that have one or more possible displays for their entity label. Entities requiring this associativity will have pointers in their directory entry to a label display associativity instance entity. LEADER ENTITY An annotation entity, also referred to as arrow, which consists of an arrowhead and one or more line segments. In the case of an angular dimension entity, the line segment is replaced by a circular arc segment. In general, these entities are used in connection with other annotation entities to link text with some location. LEVEL An entity attribute which defines a graphic display level to be associated with the entity. LEVEL FUNCTION PROPERTY A predefined property that assigns an "application data base defined functionality" to a level. This property may stand alone (e.g., DE status is independent), that is no other entity points to it. Also, see the level field in directory entry. LINE FONT A pattern for the appearance of a curve. The pattern is a repeating sequence of blanked and unblanked line segments, or of subfigure instances. LINE FONT DEFINITION ENTITY A structure entity which defines a line font. LINE WEIGHT An entity attribute which is used to determine the line display thickness for that entity. LINE WIDENING PROPERTY A predefined property that overrides the line weight given in the directory entry of an entity by providing a physical value for the actual width. May be used in electrical applications to describe metallization on a printed circuit board such as traces and off board connections. Also, see the FLASH and SECTION entities and the Region Fill property. LINEAR DIMENSION ENTITY An annotation entity used to represent a distance between two locations. LINEAR PATH ENTITY A geometric entity that defines a collection of linear segments that form a path. Also, see Copious Data Entity Forms 11 and 12. LIST INDEX ECO603 The index into the list of generic components of the list starting at 1, i.e., List Index 1 refers to the first component of the list. 669 K. GLOSSARY MACRO BODY The portion of a macro definition containing statements which define the action of the macro. MACRO DEFINITION ENTITY The structure entity, containing the macro body within its parameter data section, used to define a specific macro. MACRO INSTANCE ENTITY A structure entity which will invoke a macro which has been defined using a macro definition entity. MIRROR To reflect about an axis. MODEL A particular collection of data in an exchange file that describes a product. MODEL SPACE A right-handed three-dimensional Cartesian coordinate space in which the product is repre- sented. NEGATIVE BOUNDED PLANAR PORTION A hole. NETWORK SUBFIGURE DEFINITION ENTITY A structure entity used to define a schematic symbol, component or pipe in electrical and piping applications. Shall be used whenever associated Connect Point Entities need to be instanced with the Network Subfigure Instance Entity. For physical components, it may have subordinate entities (copious data, simple closed planar curve, subfigure definition or instance, etc.) that have attached a Region Restriction Property giving design rules for auto routing a Printed Circuit Board, PCB. Also, 2-D component outlines and 3-D physical descriptions may be defined. NETWORK SUBFIGURE INSTANCE ENTITY A structure entity used to specify an occurrence of a schematic symbol, component or pipe in electrical and piping applications. It has associated "instanced" Connect Point Entities that give the XYZ model space point of connections. Used in netlist information and part lists. NODAL DISPLACEMENT and ROTATIONAL ENTITY This entity is used to communicate finite element post processing data. It contains the node identifier, original node coordinates, and incremental displacements and rotations for each node for each load case. NODAL LOAD/CONSTRAINT ENTITY An entity used in a finite element model to apply a force, moment, or other loading or con- straints at a specific node. NODE A point in space used to define a finite element topology. 670 K. GLOSSARY NULL ENTITY The Null Entity (Type 0) is intended to be ignored by a processor. A processor should skip over all DE and PD data associated with this entity. ECO540 NULL STRING The null string is an empty PD string parameter. This value is valid for any entity whose PD section contains a string parameter. Example: For specifying a null string within a General Note Entity (Type 212), the number of characters parameter (NC) must be zero, and the Z depth parameter (ZS) must be followed by two parameter delimiters. ORDINATE DIMENSION ENTITY An annotation entity used to indicate dimensions from a common reference line in the direction of the XT or YT axis. ORTHONORMAL A term describing two vectors which are orthogonal and of unit length. PARAMETER DATA SECTION A section of an exchange file consisting of specific geometric or annotative information about the entities or pointers to related entities. PARAMETERIZED SURFACE ECO603 S(u; v) is a parametric representation of a surface if it meets the following criteria: The untrimmed domain of S(u; v) is a rectangle, D, consisting of those points (u; v) such that a u b and c v d for given constant a; b; c; and d with a < b and c < d. The mapping S = S(u; v) = (x(u; v); y(u; v); z(u; v)) is defined for each ordered pair (u; v) in D. It is one-to-one in the interior (but not necessarily on the boundary) of D. It has continuous normal vectors at every point of D except those which map to poles. PARAMETRIC SPLINE CURVE ENTITY A geometric entity consisting of polynomial segments subject to certain continuity conditions. PARAMETRIC SPLINE SURFACE ENTITY A geometric entity which is a surface made from a grid of patches. The patches are regions between the component parametric curves. PARENT CURVE The full curve on which a segment curve lies. PART NUMBER PROPERTY A predefined property that provides one or more text strings giving one to four distinct part numbers (Generic, MIL-STD, Vendor, and/or Internal) to an entity representing a physical part. May be used in electrical, piping or other applications. Usually, it is attached to a subfigure definition and/or instance that represents the part. May be used for part lists. PATCH A surface represented by parametric functions of two parameters which can be viewed as blendings of four given boundary curves. 671 K. GLOSSARY PATH ECO603 If V0 and Vn are vertices of a graph then (V0::Vk::Vn ) is a path if Vk and Vk+1 (k = 0; n - 1) are adjacent. PIN NUMBER PROPERTY A predefined property that provides a text string giving a component pin number value to an entity representing an electrical component. Also, see the CONNECT POINT Entity. PLANE ENTITY A geometric entity consisting of all or a portion of a plane. PLATED-THROUGH HOLE ([IPCT85]) A hole in which electrical connection is made between internal or external conductive patterns, or both, by the deposition of metal on the wall of the hole. POINT ENTITY A geometric entity which has no size but possesses a location in space. POINT DIMENSION ENTITY An annotation entity consisting of a leader, text, and an optional circle or hexagon enclosing the text. POINTER A number that indicates the location of an entity within an exchange file. ECO603 POLE Let P be a point in R3. Then P is a pole of the surface defined by the mapping S(u; v) if any of the following are true: P = S(a; v) for all v such that c v d, P = S(b; v) for all v such that c v d, P = S(u; c) for all u such that a u b, P = S(u; d) for all u such that a u b POSITIVE BOUNDED PLANAR PORTION The top of a peg. POSTPROCESSOR A program which translates an exchange file of product definition data from the form defined by this Specification into the data base form of a specific CAD/CAM system. PREDEFINED ASSOCIATIVITIES Associativities which are defined within this standard. PREPROCESSOR A program which translates a file of product defintiion data from the data base form of a specific CAD/CAM system into the form defined by this Specification. PRINTED BOARD ([IPCT85]) The general term for completely processed printed circuit or printed wiring configurations. It includes rigid or flexible, single, double, or multilayer boards. 672 K. GLOSSARY PRINTED CIRCUIT ([IPCT85]) A conductive pattern comprised of printed components, printed wiring, or a combination thereof, all formed in a predetermined design and intended to be attached to a common base. (In addition, this is a generic term used to describe a printed board produced by any of a number of techniques.) PRINTED CIRCUIT BOARD ([IPCT85]) A part manufactured from rigid base material upon which a completely processed printed circuit has been formed. PRINTED WIRING ([IPCT85]) The conductive pattern intended to be formed on a common base, to provide point-to-point connection of discrete components, but not to contain printed components. PRODUCT DEFINITION Data required to describe and communicate the characteristics of physical objects as manu- factured products. PROPERTY ENTITY A structure entity which allows numeric or text information to be related to other entities. RADIUS DIMENSION ENTITY An annotation entity which is a measurement of the radius of a circular arc. RATIONAL B-SPLINE CURVE A parametric curve which is expressed as the ratio of two linear combinations of B-spline basis functions. Each basis function in the numerator is multiplied by a scalar weight and a vector B-spline coefficient. Each corresponding basis function in the denominator is just multiplied by the corresponding weight. RATIONAL B-SPLINE SURFACE A parametric surface which is expressed as the ratio of two linear combinations of products of pairs of B-spline basis functions. Each product of basis functions in the numerator is multiplied by a scalar weight and a vector B-spline coefficient. Each corresponding product of basis functions in the denominator is multiplied by the corresponding weight. REFERENCE DESIGNATOR PROPERTY A predefined property that provides a text string giving a component reference designator value to an entity representing an electrical component. Also, see the Network Subfigure entity. REGION The bounded area enclosed by a closed curve or a combination of curves. REGION FILL PROPERTY A predefined property that is used to solid fill or unfill (nested) a closed area. May be used for cross-section material representations (i.e., concrete, steel, etc.) and artwork. Also, see the SECTION entity. Also, see the FLASH and SECTION entities and the Line Widening property. 673 K. GLOSSARY REGION RESTRICTION PROPERTY A predefined property that provides design rules in electrical applications. Especially, region restrictions regarding Printed Circuit Board, PCB routing rules for prohibiting or permitting vias and traces under component outlines and placement of components on the printed circuit board. RELATION An aspect or quality that connects two or more things or parts as being or belonging or working together or as being of the same kind. REPEATING PATTERN An ordered sequence of items (elements) which, after a certain point, repeats itself. RIGHT-HANDED CARTESIAN COORDINATE SYSTEM A coordinate system in which the axes are mutually perpendicular and are positioned in such a way that, when viewed along the positive Z axis toward the origin, the positive X axis can be made to coincide with the positive Y axis by rotating the X axis 90 degrees in the counterclockwise direction. RULED SURFACE ENTITY A surface generated by connecting corresponding points on two space curves by a set of lines. ECO603 SEAM Let C be a curve in R3. Then C is a seam of the surface defined by S(u; v) if it is the image in model space of C(v) = S(a; v) for all v such that c v d and C(v) = S(b; v) for all v such that c v d or C(u) = S(u; c) for all u such that a u b and C(u) = S(u; d) for all u such that a u b SECTION ENTITY A pattern used to distinguish a closed region in a diagram. It is represented as a form of the copious data entity. SECTION DISPLAY SYMBOL An arrangement of fonted straight lines in a repetitive planar pattern at a specified spacing ECO526 and angle. ECO525 SIMPLE CLOSED CURVE Informally, a simple closed curve is a curve that may be obtained as follows: (1) join together the two ends of an infinitely thin string of appropriate nonzero finite length; (2) situate the resulting loop so that it does not intersect itself. SINGLE PARENT ASSOCIATIVITY ENTITY A predefined associativity that provides logical grouping of a single parent entity to its many children entities. SPLINE A piecewise continuous polynomial. 674 K. GLOSSARY START SECTION The section of an exchange file containing a human-readable file prologue. SUBASSEMBLY ([IEEE75]) Two or more basic parts which form a portion of an assembly or a unit, replaceable as a whole, but having a part or parts which are individually replaceable. SUBFIGURE DEFINITION ENTITY A structure entity which permits a single definition of a detail to be utilized in multiple instances. SUBFIGURE INSTANCE ENTITY A structure entity which specifies an occurrence of the subfigure definition. SUBORDINATE ENTITY SWITCH A portion of the status number field of the directory entry of an entity. An entity is subor- dinate if it is an element of a geometric or annotative entity structure or is a member of a logical relationship structure. The terms subordinate and dependent are equivalent within this document. SURFACE OF REVOLUTION ENTITY A geometric entity which is a surface generated by rotating a curve, called the generatrix, about an axis, called the axis of rotation. SYSTEM ([IEEE75]) A combination of two or more sets, generally physically separated when in operation, and other such units, assemblies, and basic parts necessary to perform an operational function or functions. TABULAR DATA PROPERTY The tabular data property provides a structure to accommodate point form data. The ba- sic structure is a two-dimensional array containing data list for dependent and independent variable. TABULATED CYLINDER ENTITY A geometric entity which is a surface generated by moving a line segment called the generatrix parallel to itself along a space curve called the directrix. TERMINATE SECTION The final section of an exchange file, indicating the sizes of each of the preceding file sections. TEXT DISPLAY TEMPLATE ENTITY An annotation entity used to define the display location of a text string. In electrical appli- cations, it gives a "relative" mode of location dependent on a connect point for pin number and/or pin function of components (e.g., Integrated Circuit, IC, chip pins). For electrical schematic symbols and physical components, it may give the display location of the reference designator text and/or part number. TEXT FONT The specification of the appearance of the characters. 675 K. GLOSSARY TEXT FONT DEFINITION ENTITY The entity used to define the appearance of characters in a text font. A character is defined by pairing its character code with a sequence of display strokes and positional information. TRANSFORMATION MATRIX ENTITY An entity which allows translation and rotation to be applied to other entities. This is used to define alternate coordinate systems for definition and viewing. TRANSLATION VECTOR A three element vector which specifies the offsets (along the coordinate axes) required to move an entity linearly in space. UNIT ([IEEE75]) A major building block for a set or system, consisting of a combination of basic parts, sub- assemblies, and assemblies packaged together as a physically independent entity. VERSION NUMBER A means for uniquely designating one specification definition or translator implementation from a preceding or subsequent one. VIA HOLE ([IPCT85]) A plated-through hole used as a through connection, but in which there is no intention to insert a component lead or other reinforcing material. VIEW ENTITY A structure entity used to provide the definition of a human-readable representation of a two- dimensional projection of a selected subset of the model and/or nongeometry information. VIEWING BOX The clipping box used to define a view. WEIGHT A positive real number which appears in the numerator and denominator of the expression for a rational B-spline curve or surface. Increasing the weight associated with a particular control point will tend to draw the resulting curve or surface toward that control point. See ECO605 Appendix B for details. WIRE-FRAME A method of geometric modeling in which a two- or three-dimensional object is represented by curve segments which are edges of the object. In the context of this specification, `wire- frame' and `edge-vertex' models are considered as the same technique and the terms are used interchangeably. 676 Appendix L. Index of Entities Absolute Text Display Template Entity (Type 312, Form 0), 248 Angular Dimension Entity (Type 202), 180 Associativity Definition Entity (Type 302), 232 Associativity Group Type Property Entity (Type 406, Form 23), 369, 546 Associativity Instance Entity (Type 402), 283 Attribute Table Definition Entity (Type 322), 254 Attribute Table Instance Entity (Type 422), 392 Basic Dimension Property Entity (Type 406, Form 31), 372.5, 553.12 Block Entity (Type 150), 156 Boolean Tree Entity (Type 180), 175 Boundary Entity (Type 141), 148, 460 Bounded Surface Entity (Type 143), 151, 464 Centerline Entity (Type 106, Form 20-21), 71 Circular Arc Entity (Type 100), 53 Circular Array Subfigure Instance Entity (Type 414), 383 Color Definition Entity (Type 314), 250 Composite Curve Entity (Type 102), 56 Conic Arc Entity (Type 104), 61 Connect Node Associativity Entity (Type 402, Form 11), 299, 448 Connect Point Entity (Type 132), 122 Copious Data Entity (Type 106), 67 Curve Dimension Entity (Type 204), 183, 474 Curve on a Parametric Surface Entity (Type 142), 149 Definition Levels Property Entity (Type 406, Form 1), 317 Diameter Dimension Entity (Type 206), 184 Dimension Display Data Property Entity (Type 406, Form 30), 372.4, 553.8 Dimension Tolerance Property Entity (Type 406, Form 29), 372.3, 553.5 Dimension Units Property Entity (Type 406, Form 28), 372.2, 553.3 Dimensioned Geometry Associativity Associativity Entity (Type 402, Form 13), 301 Dimensioned Geometry Associativity Entity (Type 402, Form 21), 534.5 Drawing Entity (Type 404), 312, 535 Drawing Size Property Entity (Type 406, Form 16), 362 Drawing Units Property Entity (Type 406, Form 17), 363 Drilled Hole Property Entity (Type 406, Form 6), 324 Edge Entity (Type 504), 394.2, 558.3 Element Results Entity (Type 148), 155, 470 Ellipsoid Entity (Type 168), 173 677 L. INDEX OF ENTITIES Entity Label Display Associativity Entity (Type 402, Form 5), 292 External Logical Reference File Index Associativity Entity (Type 402, Form 2), 442 External Reference Entity (Type 416, Form 0-3), 385, 557 External Reference Entity (Type 416, Form 4), 558 External Reference File Index Associativity Entity (Type 402, Form 12), 300 External Reference File List Property Entity (Type 406, Form 12), 358 Face Entity (Type 510), 394.4, 558.7 Finite Element Entity (Type 136), 128, 457 Flag Note Entity (Type 208), 186 Flash Entity (Type 125), 112 Flow Associativity Entity (Type 402, Form 18), 307 Flow Line Specification Property Entity (Type 406, Form 14), 360 General Label Entity (Type 210), 190 General Note Entity (Type 212), 192 General Symbol Entity (Type 228), 224, 494 Generic Data Property Entity (Type 406, Form 27), 372.1, 553.1 Group Associativity Entity (Type 402, Form 1), 285 Group without Back Pointers Associativity Entity (Type 402, Form 7), 295 Hierarchy Property Entity (Type 406, Form 10), 328 Highlight Property Entity (Type 406, Form 20), 366, 543