Page 1/16
virtual product development
Efficient Work with Code_Aster –Symbiotic Combination of HyperWorks with a Non-Commercial Solver
Various well-established commercial FEM-software packages exist (e.g. Abaqus, ANSYS or MSC.MARC). The licenses for these softwares as well as the maintenance and support contracts are usually extremelycost-intensive.In contrary open source FEM-solvers can be an appealing alternative and potential possibility to lower oreven avoid these financial burdens. One of these solvers is Code_Aster which is developped by Electricitéde France (EDF) and published under the GNU General Public License. Since Code Aster offers only a solver functionality, additional powerful pre- and postprocessing tools are necessary to handle projectsefficiently. As a commonly used software-suite Altair HyperWorks provides the necessary interfaces for a cost- and time-saving work in combination with Code_Aster.This presentation gives a review about the workflow and the possible customization of HyperWorks withregard to the usage of Code_Aster.
Author: Benjamin Nerstheimerhme GmbH – engineering office for technical simulationsKässbohrerstraße 18, 89077 Ulm (Germany)[email protected]
Abstract
Page 2/17
virtual product development
Diploma thesis: Code Aster applicable at hme GmbH?
Benchmark of Code_Aster against ANSYS and Abaqus:
Estimation of results, computational time and handling
Adoption of Altair HyperWorks instead of OpenSource tools
for pre- and postprocessing
Customization of pre-/postprocessing interfaces
Conclusion: Enhanced workflow
Possible future tasks
Overview
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Page 3/17
virtual product development
Widespread
Accredited and reliable
No limitations
Powerful performance
Mostly user-friendly
Helpful support
License fees
Maintenance contracts
Support costs
Rarely known
Therefor not accredited
Node- or DOF-limitations
Performance problems
Moderate user-friendliness
Support hardly available
Completely for free
No contract obligations
-
Introduction - OpenSource Tools
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Commercial FEA-Software - OpenSource FEA-Software
Page 4/17
virtual product development
Code Aster: Overview
Developed by Electricité de France (EDF)
Continuous enhancements and updates
DIN certification
Published under GNU General Public License in October 2001
~ 1.2 million lines of source code
~ 14 000 pages online documentation
Current stable versions: STA10.0 stand-alone andSTA9.4 on Ubuntu 8.04 LTS 64bit distribution
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Page 5/17
virtual product development
Code Aster: Features & Possibilities
Code_Aster offers:
Linear and non-linear static and dynamic analyses
Modal and harmonic response analyses
Thermal analyses
Fluid-structure-interface with Code_Saturn
Consideration of contact
No node or DOF-limitations
Multiple CPU support
OpenSource pre- and postprocessors available
Matching results to commercial Softwares
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Page 6/17
virtual product development
Complicated Work-Flow
Integrated OpenSource Pre- and Postprocessors: Salomé, Gmsh, Grace & Stanley
Under steady development, but still very limited features regarding
Geometry treatment
Mesh control
Setting up loads and boundary conditions
Visualisation, animation and export of results
User-friendliness
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
PerspectiveCompetetive FEA results but enourmous
handicap in everyday‘s work
Combination of professional, easily operated and efficient pre-/postprocessors with Code_Aster solver
Problem
Solution
pre
post
Page 7/17
virtual product development
Solution: Approach with Altair HyperWorks
Requested Work-Flow:
Preprocessing:Altair HyperMesh
FEA: Code_Aster
Postprocessing:Altair HyperView
creating and exportingmesh file compliant to Code Aster requirements
exporting resultsto shared EnSightdata format
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
familiar operationmethods
Page 8/17
virtual product development
Preprocessing in HyperMesh
Preprocessing as usual:
Preparing the geometry
Meshing
Creating contact andother surface effect elements
Defining entity sets
Describingcoordinate systems
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Page 9/17
virtual product development
Costomizing HyperMesh *.unv-Interface based on IDEAS Template
Some of the necessary actions for the mesh file to be readable in Code_Aster:
Changing normal directionsChange and update all element properties to preset valueDeleting all empty componentsRenumbering all nodes and elementsChanging set names to UPPERCASERight-aligning text information in *.unv-fileChanging numeric format of numbers
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Choose the self-writtenTCL/TK Code Aster
template from the menu
Page 10/17
virtual product development
Setting up Code_Aster for correct File Formats
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
IMPR_RESU(INFO=1,RESU=_F(MAILLAGE=mesh),UNITE=31,MODELE=model,RESULTAT=solution,FORMAT='ENSIGHT', );
PRE_IDEAS(CREA_GROUP_COUL='NON',UNITE_MAILLAGE=20,UNITE_IDEAS=19, );
Defining: Material and element propertiesLoads and boundary conditionsSolution and solver settingsRunning the simulation
Importing the customized*.unv-file at the beginning
of the simulation
Setting up the analysisin Code_Aster
Exporting the results intoEnSight data format at the
end of the simulation
Page 11/17
virtual product development
Short Introduction to EnSight Data Format
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Scalar value files:Each file contains one result value
e.g. Solution.DISP.MAGSolution.DISP.DXSolution.DISP.DYSolution.DISP.DZSolution.STRESS.S1 Solution.STRESS.S2Solution.STRESS.S3Solution.STRESS.VMIS
…
*.case-file
*.geo-file= Geometry or mesh file
EnSight Data
Page 12/17
virtual product development
Code_Aster File Formats
Overview
Introduction
Code Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Code_Aster
*.med
*.gibi
*.gmsh*.unv
Input data
Output data
*.resu *.unv
*.case
*.med
*.gmshCombination IDEAS to
EnSight leads to wrong nodenumbering in *.geo-file
Page 13/17
virtual product development
Code Aster: Problem generating EnSight *.geo-file
IDEAS to EnSight leads to destroyed EnSight mesh file:wrong element connectivities due to internal node numbering error
This affects only *.geo-file, result scalar value files are correct!
Overview
Introduction
Code Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
PerspectiveRepairing or re-creating *.geo-fileSolution
Page 14/17
virtual product development
Programming of EnSight Mesh Interface
Solution: Exporting the mesh file via customized TCL/TK export template:Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Preprocessing:Altair HyperMesh
FEA: Code Aster
Postprocessing:Altair HyperView
creating and exportingmesh file compliant to Code Aster requirements
exporting resultsto shared EnSightdata format
Formerlycreatedmesh file
Self-writtenEnSight interfacefor producing *.geo-file
Change dedicated*.geo-file in EnSight*.case-file
Page 15/17
virtual product development
Postprocessing with HyperView 10.0
Postprocessing as usual: Visualisation of Results
DisplacementsStressesStrainsPressuresEnergiesGaps or penetrations
- No scaling of deformed shape- No animation- No export options
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
Page 16/17
virtual product development
Conclusion
Preprocessing:
HyperMesh fully applicable due to customizeable *.unv-interfaceTaking advantage of powerful mesh options
FEA:
Calculating results in most common application fields with Code_AsterSaving costs with this powerful OpenSource tool
Postprocessing:
HyperView 10.0 supports EnSight data formatComfortable working but limited display options at this stage
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective Compared to OpenSource pre-/postprocessing tools, Altair HyperWorks significantly enhances the work-flow
when being used for Code Aster model processing.
Page 17/17
virtual product development
Perspective
Possible next steps are:
Enhancing the customized *.unv-interface --- hme
Automated generating of Code Aster input data decks, including loads, boundary conditions, surface effect elementsand solver settings
Enhancing the functionalities of the EnSight data reader --- Altair
scalable resultsanimated results
Enhancing obsolete Code Aster *.unv-result interface --- EDF
implementing modern and correct datablocks
Overview
Introduction
Code_Aster
Pre: HyperMesh & unv-Interface
Post: HyperView & EnSight- Interface
Conclusion
Perspective
virtual product development
Q + A
Thank you for your attention!
Any Questions?
Author: Benjamin Nerstheimerhme GmbH – engineering office for technical simulationsKässbohrerstraße 18, 89077 Ulm (Germany)[email protected]