[home icon] GEHAEUSE.EXE

GEHAEUSE.EXE (96K) is a self-extracting archive that contains three IGES files for use in testing postprocessors. They are all based on the IGES test file used to demonstrate vendor interoperability at AUTOFACT-6 in Anahiem, CA in 1983, the original part being a "housing" created on a CAD system by an engineer at Messerschmitt in Germany.

The part represented by these IGES test files has appeared in technical papers at seminars and in professional journals. It is referred to as "MBB Gehaeuse" (Messerschmitt-Bölkow-Blohm Housing) in a paper by Ernst Schlechtendahl, et.al., in IEEE COMPUTER GRAPHICS AND APPLICATIONS, Vol. 9 Num. 5 (ISSN 0272-1716) Sep'89. Renderings of this part have also been used in the advertisements for several CAD/CAM vendors and graphics terminal vendors.

These test files were packaged and distributed by WiZ WORX, offering software imagineering since 1983. The renderings were generated using IGESDRAW™. For information on WiZ WORX products, visit our homepage or send e-mail to Dennette@WiZ-WORX.com. Share & Enjoy!


A MIL-D-28000 Class II (Engineering Drawing) IGES Subset conformant file. It contains a 3D wire-frame model of the MBB Gehaeuse part and two Drawing Entities (Type 404) that specify D size sheets (44x34 inches). The first Drawing Entity (named "FIRST" in the IGES file) references three View Entities (Type 410) that define top, front, and side views of the part with beaucoup dimensions (see DRAWING.IGS). The second Drawing Entity (named "SECOND") references a single View Entity that defines an isometric view of the part with no annotation (see MODEL.IGS).

TESTAF6.IGS is a practical, robust test for IGES postprocessors. At the very least, 2D systems that do not support models and views should be able to blow the geometry through the transformation matrices (once for each View) and display the annotation. (Such a postprocessor might create distinct CAD system files for each drawing.) Note that some of the General Note Entities (Type 212) use the Drafting Symbol Font Code (FC 1003), and the multi-view drawing contains subordinate annotation (the sheet border and text in the corners of the sheet).

This file has beau coup annotation entities:

    67 = 106:0040 Copius Data:Witness Line                     
     2 = 202:0000 Angular Dimension                            
     1 = 206:0000 Diameter Dimension                           
    57 = 212:0000 General Note:Simple Note (default)           
    79 = 214:0002 Leader/Arrow:Triangle                        
    32 = 216:0000 Linear Dimension:Undetermined (default)      
     9 = 222:0000 Radius Dimension:Single Leader Format        
     4 = 228:0000 General Symbol:General Symbol (default)      

TESTAF6.IGS is a real widow-maker, but unlike the IGES Files From Hell that we sometimes encounter, everything in this file conforms to the standard. All of the major CAD/CAM systems can read this file, and most will write it back to IGES with the same structure. In short, if your IGES postprocessor chokes on it, then you should suggest that the implementor perform some enhancements.

This is a MIL-PRF-28000B Class 2 (Engineering Drawing) Subset IGES file.


TESTAF6.IGS - Correctly processed drawing with 3 views


TESTAF6.IGS - 3D rendering of correctly processed drawing with 3 views ... this is the output of IGESDRAW™ with the -3D option.


A 3D wire-frame model of the test part. This file is the result of processing with a filter that removed all annotation, leaving just 3D curve entities, e.g.,

    79 = 100:0000 Circular Arc                                        
     6 = 104:0001 Conic Arc:Ellipse                                   
   160 = 110:0000 Line                                                
    23 = 124:0000 Transformation Matrix:Right-handed        
     2 = 126:0000 Rational B-Spline Curve 

This is a MIL-PRF-28000B Class 7 (3D Geometry) Subset IGES file.


GEHAEUSE.IGS - 3D wireframe geometry (no annotation)

15-Aug-96 - Rotate the 3D model with Java!


A 2D annotated rendering of the part on a drawing sheet with orthogonal views. This file is the result of applying one of the IGES file flattening tools to TESTAF6.IGS. It represents the drawing with three orthographic views (named "FIRST") projected onto the zed nought plane (as the British call Z=0). It contains only 2D entities, i.e., circular arcs, 3D splines, and dimensions have been converted to strings of 2D line segments. DRAWING.IGS is not a MIL-D-28000 Class I (Technical Illustration) IGES Subset conformant file, but it's close enough; any flat-earth CAD system or display tool that claims to support IGES should be able to postprocess this file and give you a pretty picture:

    64 = 100:0000 Circular Arc                               
   292 = 106:0011 Copius Data:Piecewise Linear Curve (2D)    
   606 = 110:0000 Line                                       
   169 = 212:0000 General Note:Simple Note (default)         

This is a MIL-PRF-28000B Class 1 (Technical Illustration) Subset IGES file.


DRAWING.IGS - 2D rendering of test part with 3 orthogonal views and annotation ... a Class 1 IGES file as rendered by IGESGUMP™

2009-12-21: Rotate correct 3D rendering with Java (model & annotation projected through multiple views)


A 2D isometric rendering of the test part. This file is the result of the same processing as DRAWING.IGS, except that the drawing with one isometric view (named "SECOND") was selected. MODEL.IGS can be used as a sanity-check for what the second drawing in TESTAF6.IGS should look like when correctly processed.

This is 2D Etch-a-sketch at its most primitive:

    89 = 106:0011 Copius Data:Piecewise Linear Curve (2D)       
   164 = 110:0000 Line                                          

This is a MIL-PRF-28000B Class 1 (Technical Illustration) Subset IGES file.


MODEL.IGS - 2D rendering of test part with a single isometric view ... a Class 1 IGES file as rendered by IGESGUMP™


A Very Bad rendering of the test part. This file is the result of what an un-named (because they have since corrected it) IGES Translator from Hell generated as output, and is a good example of what happens when IGES translators go bad. The problem is that it did not support the View Entity (Type 410), so all of the annotation is placed in model space, and not projected through the view's matrix to orient correctly on the X/Y plane.


THIRD.IGS - 3D rendering of an IGES Translator from Hell

2010-03-16: Rotate incorrect 3D rendering with Java (all annotation in model space)

[WiZ WORX HomePage] Last update: 2010-02-05 by Dennette@WiZ-WORX.com