Interpretation of Topography Optimization Results

The autobead feature of OSSmooth allows OptiStruct topography optimization results to be interpreted as one or two level beads.

Figure 1 shows the level of detail captured in both cases; while the 2-level approach captures more details, it is more complicated to manufacture than the 1-level interpretation, often without significant performance gain.


Figure 1. Autobead Interpretation of Topography Optimization Result

Example: Autobead Result from Topograph Optimization

#general parameters
input_file            decklid
output_file           decklid.fem
output_code           1 

#specific parameters
autobead              1  0.300  1
remesh                1
Figure 2. Parameter File


Figure 3. Autobead Result from Topography Optimization

Example: 2-Layer Autobead Result from Topography Optimization

Some topography performances are relying on the half translation part. OSSmooth can interpolate topography optimization results to 2-layer autobead (autobead third argument 2).
#general parameters
input_file            decklid
output_file           decklid.nas
output_code           1 

#specific parameters
autobead              1  0.300  2
Figure 4. Parameter File


Figure 5. 2-Layer Autobead Result From Topography Optimization