How the GiD Graphical User Interface communicates with Kratos

From KratosWiki
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
==General Concepts==
 
==General Concepts==
==Input files generation (GiD ProblemType language)==
 
==Input files generation (Tcl/Tk)==
 
==Launching the calculation==
 
 
 
Any Graphical User Interface (GUI) for Kratos must be able to:
 
Any Graphical User Interface (GUI) for Kratos must be able to:
  
Line 14: Line 10:
  
 
It is common to have a ''KratosOpenMP.py'' as a main Python script when OpenMP parallelism has been chosen in the options, or ''KratosMPI.py'' when MPI parallelism has been chosen. Other similar options are possible.
 
It is common to have a ''KratosOpenMP.py'' as a main Python script when OpenMP parallelism has been chosen in the options, or ''KratosMPI.py'' when MPI parallelism has been chosen. Other similar options are possible.
 +
 +
==Input files generation (GiD ProblemType language)==
 +
==Input files generation (Tcl/Tk)==
 +
==Launching the calculation==

Revision as of 22:34, 28 June 2014

Contents

General Concepts

Any Graphical User Interface (GUI) for Kratos must be able to:

1- Generate the files which are necessary for Kratos to run. These files are usually .mdpa input files that contain the geometrical data, and other .py input files that contain parameters/options important for the run.

It is common to use the naming Case_nameFluid.mdpa, Case_nameStructural.mdpa for the .mdpa files, and ProjectParameters.py for the .py file.


2- Start the run by calling Python plus a main script.

It is common to have a KratosOpenMP.py as a main Python script when OpenMP parallelism has been chosen in the options, or KratosMPI.py when MPI parallelism has been chosen. Other similar options are possible.

Input files generation (GiD ProblemType language)

Input files generation (Tcl/Tk)

Launching the calculation

Personal tools
Categories