Altair India

HYPERWORKS FOR STUDENTS

Projects using HyperWorks Process Manager

Automating Post-Processing - H3D Export





Areas covered:

How to use the HyperView Player to post-process using a Browser.

Post-processing using HyperView.

Capabilities of the GUI Toolkit.

Description of the Problem: We know that the results-interpretation stage is critical in any CAE work, since diligence is essential to trap mistakes that may have crept into the models. Unfortunately, post-processing often gets short shrift since the experts who need to review the results are often unfamiliar with the software used. Further, if post-processing ties up a license of the software, things get worse. There's always pressure to create more models, which requires licenses. An engineer who wants to pore over the results, but who is under pressure for the license, may (perhaps unconsciously!) hurry through this phase. To address this, HyperWorks provides a results-viewer, the HyperView Player that requires no license. An engineer who is familiar with the software can use HyperView to create H3D files that contain various views of the results. These can be embedded in a HTML Browser or in PowerPoint files for independent review and evaluation - no HyperWorks licenses are tied up. In this project we look at ways to automate the process of generation of reports from analysis results.

Creation of a Material Library





Areas covered:

Material-data specification using HyperMesh, including the units-neutral nature .

Record-and-modify method to create macros.

Addition of buttons to the User-page.

TCL and TK to create interactive applications.

Description of the Problem: HyperMesh is units neutral - it relies on the user to use a consistent set of units. When the FE model is constructed, data comes from three sources. The first is the geometry which usually comes from a CAD modeler. Next is data that is created explicitly by the user but is not displayed graphically - material properties and geometric data such as the thickness of shell elements. The last is data such as nodes and elements which are created interactively. Most engineers rely on readily available material data, often paying little attention to the fact that such data in a production environment must come from verifiable sources, not from "references". Further, even experienced engineers can get trapped in the units muddle. Our aim is to provide an application that addresses both problems: we want to reduce the tedium of looking up and entering material data, and we also want to avoid the scope for error in units.

Back Page.