Corba based integration of simulation workflows
Download
1 / 54

CORBA-based integration of automated simulation workflows - PowerPoint PPT Presentation


  • 342 Views
  • Uploaded on

CORBA-based Integration of Simulation Workflows. A. Holtz, S. Kolibal, J-V. Peetz, A. Weihermüller, K. Wolf Institute for Algorithms and Scientific Computing (SCAI) GMD- German National Research Center for Information Technology. Overview. Definition of our Problem Area

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'CORBA-based integration of automated simulation workflows' - HarrisCezar


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Corba based integration of simulation workflows l.jpg

CORBA-based Integration of Simulation Workflows

A. Holtz, S. Kolibal, J-V. Peetz, A. Weihermüller, K. Wolf

Institute for Algorithms and Scientific Computing (SCAI)

GMD- German National Research Center for Information Technology


Overview l.jpg
Overview

  • Definition of our Problem Area

  • Iterative Modifications in Large Engineering Simulations

  • Object Oriented Data Structures

  • CORBA and JAVA as Implementation Layer

  • System Architecture

  • Going through an Example

  • Conclusion


Slide3 l.jpg

www.

.de


Definition of our problem area l.jpg

Definition of ourProblem Area


Application fields l.jpg

Engineering Departments

Design and construction

Simulation and optimisation

Industrial Branches

Automotive

Aircraft

Mechanical Engineering

…...

Application Fields


Simulation areas l.jpg

Numerical Simulation Disciplines

Structural Analysis

Crash Simulation

Metal Forming

..

Computational Fluid Dynamics

Electro-Mechanical

...

Simulation Areas


Engineering tools l.jpg

Commercial Tools without Source Code Access

CAD

Preprocessing, Mesh-Generator

Assembly

Simulation

Optimisation and Postprocessing

Visualisation and VR

...

Engineering Tools


What is the problem l.jpg

Variety of proprietary tools

Designed for standalone interactive use

In binary and with poor programming interfaces

Established at end-users sites

Lots of non-matching data-formats

Syntactically incompatible

Semantically loss of information through converting

Engineering Data Flow

Existing only in the hands & heads of the engineers

What is the Problem


What is our goal l.jpg

Easy exchange of information between tools

Overall definition of data organisation

Tool independent

Based on small units

Providing hierarchical organisation schemes

Central point of view and control

Distributed workflow

Easy adaptation of proprietary tools

What is our Goal


Iterative modifications in large engineering simulations l.jpg

  • Definition of our Problem Area

  • Object Oriented Data Structures

  • CORBA and JAVA as Implementation Layer

  • System Architecture

  • Going through an Example

  • Conclusion

Iterative Modifications inLarge Engineering Simulations


Distributed working l.jpg

Machine 1

Machine 2

Machine 3

Machine 4

Distributed Working

User

Tool

Network

Host

Disk


Iterative modification l.jpg
Iterative Modification

Car Design by Microsoft


Complexity of structural analysis l.jpg
Complexity of Structural Analysis

2 Million

Car Design by BMW


Data sets used for 1 part l.jpg

1 Subset for each

simulation discipline

Data Sets used for 1 Part

CAD Construction

Definition of Material

Numerical Model

Loads

Boundary Conditions

Example: Fuel Tank

Simulation Results

Optimisation Parameters

Visualisation Data


Working with local parts l.jpg
Working with local Parts

yesterday

today

tomorrow




Object oriented data structures l.jpg

  • Definition of our Problem Area

  • Iterative Modifications in Large Engineering Simulations

  • CORBA and JAVA as Implementation Layer

  • System Architecture

  • Going through an Example

  • Conclusion

Object Oriented Data Structures


Concepts for integration of data l.jpg

Object-oriented data organisation

Interface specification in CORBA/IDL

Direct access to each data item

System implemented through CORBA components

Easy extensions through modular architecture

Adapter-Libraries for CAE-Tools

Concepts for Integration of Data


Problems l.jpg

Different interpretations of model quantities

e.g. ‘Stress’ in Crash and Metal forming

Different material data bases

Different views on hierarchies

e.g. ‘Parts’ or ‘Configuration Groups’

Different numerical models

e.g. element definitions are not compatible

Problems


Solution l.jpg

Data organisation does not define any physics

Definition of a minimal set of very basic objects

Numerical Models: nodes, elements, subsets, ..

Element definition: using an element catalogue

Material: IDs referring to tool specific data bases

Definition of Links between objects

definition of different basic link types

e.g. loads, weld types, boundary conditions, ...

Solution


Assembly groups units and links l.jpg
Assembly Groups, Units and Links

Assembly-

Group

Assembly-

Group

Link

Link

Link

Assembly-

Unit

Link

Assembly-

Unit

Assembly-

Unit

Assembly-

Unit

Set

Model

Result

Properties

Link Stub


Adaptive models in assembly units l.jpg

Set

Set

Set

Model

Model

Model

Result

Result

Result

Properties

Properties

Properties

Link Stub

Link Stub

Link Stub

Set

Set

Set

Result

Result

Result

Properties

Properties

Properties

Link Stub

Link Stub

Link Stub

Set

Set

Set

Result

Result

Result

Properties

Properties

Properties

Link Stub

Link Stub

Link Stub

Adaptive Models in Assembly Units

Assembly-

Unit


Interface specification 1 l.jpg

createAssemblyGroup()

initModel()

putCoor()

putElements()

closeModel()

initResult()

put-NodeResult()

putElementResult()

closeResult()

delete AssemblyGroup()

Interface Specification (1)


Interface specification 2 l.jpg

getAssemblyGroup()

getAssemblyUnits ()

getResultDescriptors ()

getCoor ()

getElements ()

getElementResult ()

getNodeResult ()

Interface Specification (2)


Corba and java as implementation layer l.jpg

  • Definition of our Problem Area

  • Iterative Modifications in Large Engineering Simulations

  • Object Oriented Data Structures

  • System Architecture

  • Going through an Example

  • Conclusion

CORBA and JAVAas Implementation Layer


Why corba l.jpg

Industrial middleware standard for client-server applications

Transparent access to services (like compute services)

No essential performance degradation

Object oriented interfaces (CORBA-IDL)

Why CORBA?


Corba schematic view l.jpg
CORBA Schematic View applications



Application layer l.jpg

Workflow Management System TENT applications

1999 first implementation by GMD & DLR

Further Development by DLR SISTEC

Applications in Aeronautics, Automotive and others

http://www.sistec.dlr.de/tent

Application Layer


System architecture l.jpg

  • Definition of our Problem Area applications

  • Iterative Modifications in Large Engineering Simulations

  • Object Oriented Data Structures

  • CORBA and JAVA as Implementation Layer

  • Going through an Example

  • Conclusion

System Architecture


Data management component system l.jpg

BrowserGUI applications

BrowserGUI

BrowserGUI

BrowserGUI

CAE Tool

CAE Tool

CAE Tool

CAE Tool

Wrapper

Wrapper

Wrapper

Wrapper

DataServer

AVS

Import/Export

Import/Export

Import/Export

Import/Export

VTK

Reduce

… PostProc

Data ManagementComponent System

Integration Platform: TENT 0.9

Middleware: JAVA 1.2, CORBA


Basic components l.jpg

System Services applications

Extended Name Service

Factories and Job Management

DataServer

Central Component acting as data cache

Putting data items into the right place

File Management

writing and reading the actual data to a file

Basic Components


Cae tool wrapper l.jpg

Based on I/O Communication applications

Starting tools in batch-mode

Co-Processes as CORBA-adapters

communication via Files

using IPC

Direct Adaptation of Tools

CORBA-main using the tool as a library

Tool main routine calls CORBA library

CAE Tool-Wrapper


Format import and export l.jpg

Proprietary Formats applications

Reading and writing

Extracting data

Composing input decks from collected informations

Temporary Files

Additional files for internal use

Data Base

Persistent data bases (e.g. material definitions)

Format Import and Export


Importing native file formats l.jpg

InputData applications

Common Data

AssemblyUnit

$ENTER COMPONENT NAME = Konsole DOFTYPE = DISP MATH

$STRUCTURE

$COOR

305 1.559560E+03 -4.738740E+02 3.945060E+02

306 1.556520E+03 -4.759290E+02 3.945120E+02

307 1.554500E+03 -4.789900E+02 3.945160E+02

...

$ELEMENT TYPE = QUAD4

545 866 1025 909 855

546 864 910 1025 866

547 1025 1026 908 909

548 910 911 1026 1025

...

$GEODAT SHELL CONT = THICK

P1 2.000000E+00 2.000000E+00 2.000000E+00

& 2.000000E+00

P2 2.000000E+00 2.000000E+00 2.000000E+00

& 2.000000E+00

P3 1.500000E+00 1.500000E+00 1.500000E+00

& 1.500000E+00

...

$MATERIAL NAME = M1_8 TYPE = ISO

!

$ELASTIC GENERAL INPUT = DATA

2.100000E+05 3.000000E-01

!

$DENSITY GENERAL INPUT = DATA

7.850000E-15

!

$END MATERIAL

GeoDatSymbolTable

Codespecific Data

MaterialSymbolTable

Importing Native File Formats


Graphical user interface l.jpg

Browsing and Modification of Information applications

Name service

Data contents

Controlling Tools

Setting parameters

Starting tools

Runtime control and job monitoring

Graphical User Interface


Additional postprocessors l.jpg

Based on simulation results additional post -processing can easily be realised

Reduction Algorithms

Analysing tools

Public Domain Visualiser

High End VR

...

Additional Postprocessors


Going through an example l.jpg

  • Definition of our Problem Area easily be realised

  • Iterative Modifications in Large Engineering Simulations

  • Object Oriented Data Structures

  • CORBA and JAVA as Implementation Layer

  • System Architecture

  • Conclusion

Going through an Example


Tools in the workflow l.jpg

CAD easily be realised: Geometries in CATIA-native

Preprocessing: FE-Modelling with MEDINA

Configuration: with Assembler/CrashViewer

Simulation: Structural Analysis with PERMAS

Visualisation: AVANGO, AVS oder VTK

Integration: DataServer and CORBA-Wrappers

Tools in the Workflow


Slide41 l.jpg

DS* easily be realised

DS*

DS*

DS*

Material-Database

(ASCII)

<*>.matdb

CAD Geometry

(CATIA Modell)

<AssUnit>.model

Attributs

(ASCII)

<AssUnit>.attrib

Structural Organi-

sation(ASCII)

<AssGroup>.struct

Linklist Definitions

(ASCII)

<AssGroup>.linklist

Weldpoints, Weldtype IDs,

other Linktypes, Loads

Boundary Conditions

Description of Geometry

including internal sets

Materialsa and

their Properties

Material ID, Wall Thickness,

Fe-Element Types

Hierarchical Organisation

of Parts

Weldtype-Database

(ASCII)

<*>.weldtype

Elementtypes including physical

Properties, max. Distance

of Weldsurfaces

FEA

FE-Modell

Assembler

Importer

n

n

DataServer

Example Dataflow


Nameserver l.jpg
NameServer easily be realised


Data browser l.jpg
Data-Browser easily be realised


Indeed l.jpg
INDEED easily be realised


Permas control l.jpg
Permas-Control easily be realised


Reduce l.jpg
Reduce easily be realised


Avs and virtual reality l.jpg
AVS and Virtual Reality easily be realised


Jobs control l.jpg
Jobs-Control easily be realised


Jobs control49 l.jpg
Jobs-Control easily be realised


Codine control l.jpg
Codine-Control easily be realised


Conclusion l.jpg

  • Definition of our Problem Area easily be realised

  • Iterative Modifications in Large Engineering Simulations

  • Object Oriented Data Structures

  • CORBA and JAVA as Implementation Layer

  • System Architecture

  • Going through an Example

Conclusion


Conclusion 1 l.jpg

Status of DataManagement-System easily be realised

Consistent Definition of Data-Structures

Open Interface in IDL

Modular SW-Architecture

Easy Extendibility for new CAE-Tools

Performance of DataServer has to be improved

Connection to PDM-Systems t.b.d.

CAE-file Formats not yet fully supported

Conclusion (1)


Conclusion 2 l.jpg

Integration of CAE-Workflows means Integration of Data-Flows easily be realised

Consistent Data Organisation Necessary

Data-Management Toolset has to be customised to realise an application specific working environment

Conclusion (2)


Customising our pse l.jpg
Customising our PSE easily be realised

Application Definition

Data Flow Analysis

Mapping Data Flow onto DataServer Formats

Realisation of File Format Support

GUI Adaptation

Basic Components


ad