Users:HowToUseCarat
(→Input Blocks) |
|||
(12 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[Category: Users:HowToUseCarat]] | [[Category: Users:HowToUseCarat]] | ||
− | == Step 1: | + | == Step 1: Get Carat++ == |
+ | |||
+ | === User === | ||
Carat++ will be available as a precompiled executable here (for academic use, for exercises to specific courses, etc.). Just download the version that you need: | Carat++ will be available as a precompiled executable here (for academic use, for exercises to specific courses, etc.). Just download the version that you need: | ||
Line 12: | Line 14: | ||
** TODO other Linux distributions | ** TODO other Linux distributions | ||
+ | === Developer === | ||
+ | |||
+ | * [[Users:HowToUseCarat/InstallationWindows|Windows]] | ||
+ | * [[Users:HowToUseCarat/InstallationLinux|Linux]] | ||
== Step 2: Run Carat++ via Shell or Command Line == | == Step 2: Run Carat++ via Shell or Command Line == | ||
Line 40: | Line 46: | ||
** an list of parameters with an assigned value | ** an list of parameters with an assigned value | ||
* In general, the order of the blocks in the input file(s) does not matter. | * In general, the order of the blocks in the input file(s) does not matter. | ||
+ | |||
+ | It is recommended to add comments in the input file since they support readability and comprehensibility. Comments can be added starting with '!'. | ||
+ | <pre> | ||
+ | ! cantilever modeled by shell elements with tipload. | ||
+ | !=================================================================== | ||
+ | PC-PROBLEM | ||
+ | MASTERJOB = PC-ANALYSIS 1 ! Analysis with ID 1 is used | ||
+ | </pre> | ||
=== Input Blocks === | === Input Blocks === | ||
Line 50: | Line 64: | ||
* ND-BLOCK | * ND-BLOCK | ||
* EL-BLOCK | * EL-BLOCK | ||
− | **[[Users:General FEM Analysis/Elements Reference| | + | **[[Users:General FEM Analysis/Parts|Parts]] |
+ | **[[Users:General FEM Analysis/Element Topologies|Topologies]] | ||
+ | **[[Users:General FEM Analysis/Elements Reference|Element (Properties)]] | ||
**[[Users:General FEM Analysis/Materials Reference|Materials]] | **[[Users:General FEM Analysis/Materials Reference|Materials]] | ||
* [[Users:Geometry Generation/NURBS|NURBS-BLOCK]] | * [[Users:Geometry Generation/NURBS|NURBS-BLOCK]] | ||
Line 57: | Line 73: | ||
** [[Users:Geometry Generation/Design_BRep_Elements|Design BRep Elements]] | ** [[Users:Geometry Generation/Design_BRep_Elements|Design BRep Elements]] | ||
** [[Users:Geometry Generation/Refinement|Design Refinement]] | ** [[Users:Geometry Generation/Refinement|Design Refinement]] | ||
− | ** Design Loads | + | ** [[Users:Geometry Generation/Design_Loads|Design Loads]] |
− | ** Design | + | ** [[Users:Geometry Generation/Design_Supports|Design Supports]] |
** [[Users:General FEM Analysis/Overview_design|Design Overview]] | ** [[Users:General FEM Analysis/Overview_design|Design Overview]] | ||
* [[Users:General FEM Analysis/BCs Reference/Dirichlet|BC-BLOCK]] | * [[Users:General FEM Analysis/BCs Reference/Dirichlet|BC-BLOCK]] | ||
Line 84: | Line 100: | ||
=== Parameter Input Files === | === Parameter Input Files === | ||
− | Carat++ input files give also the possibility to define a parametric simulation. In order to add some parameters, PC-PARAMETERS has to be added. It defines the name and the value. The value can either be directly defined or by a placeholder. This placeholder can be replaced in a parameter study, e.g. by a python-script. Some templates for that are provided on the server F_Users\statik\Forschung\_Carat++\UsefulScripts\RunCarat | + | Carat++ input files give also the possibility to define a parametric simulation. In order to add some parameters, PC-PARAMETERS has to be added. It defines the name and the value. The value can either be directly defined or by a placeholder. This placeholder can be replaced in a parameter study, e.g. by a python-script. Some templates for that are provided on the server F_Users\statik\Forschung\_Carat++\UsefulScripts\RunCarat. |
<pre> | <pre> | ||
PC-PARAMETERS | PC-PARAMETERS | ||
PAR=par1 VAL= 2 | PAR=par1 VAL= 2 | ||
PAR=par2 VAL= VAR_PAR2 | PAR=par2 VAL= VAR_PAR2 | ||
− | + | ||
− | ! | + | ! APPLICATION in input {@par1* 2.0} {@par2} |
− | PC-PROBLEM | + | |
− | + | ! e.g.: | |
+ | |||
+ | !PC-PROBLEM | ||
+ | ! MASTERJOB = PC-ANALYSIS {@par2} | ||
</pre> | </pre> |
Latest revision as of 10:36, 17 February 2017
Contents |
Step 1: Get Carat++
User
Carat++ will be available as a precompiled executable here (for academic use, for exercises to specific courses, etc.). Just download the version that you need: (If you do not have a tool to unzip the file, go e.g. to http://www.7-zip.org/)
- Windows, academic version (tested on Windows XP, Windows Vista, Windows 7):
- TODO request executable
- Linux, academic version:
- TODO Ubuntu request executable
- TODO other Linux distributions
Developer
Step 2: Run Carat++ via Shell or Command Line
- Start the shell (in case of Linux) or the command line (in case of Windows):
- Hint for Windows 7: Go to "Start"(Windows Icon), type "cmd" in the search window, press "Enter".
- Browse to directory of your input file
- Start Carat++:
- on Windows: "CARAT_EXE_PATH\Carat.exe INPUT_FILE_NAME.DAT" (CARAT_EXE_PATH stands for the path to the Carat++ executable, INPUT_FILE_NAME.DAT is a placeholder for the input file name)
- on Linux: user@machine:~/INPUT_FILE_DIRECTRORY> CARAT_EXE_PATH/carat.exe INPUT_FILE_NAME.DAT
if CARAT_EXE_PATH is exported in .bashrc (export PATH=CARAT_EXE_PATH:$PATH) it can be omitted in the input line - Hint for Windows: You can also drag and drop the input file onto the Carat++ executable.
Input example for simple linear static analysis. TODO LINK TO FILE
Input File
A Carat++ input file can be generated manually or with a plug-in
Here a overview of the Carat++ input file will be given.
Carat++ offers an own input file format. This makes sense, as Carat++ offers methods and algorithms that are not available in any other code. In general, this wiki describes all examples in the Carat++ format.
- Information in the input file is grouped in input blocks
- Input blocks consist of:
- an block type name (optional with an specification)
- an block ID (in general)
- an list of parameters with an assigned value
- In general, the order of the blocks in the input file(s) does not matter.
It is recommended to add comments in the input file since they support readability and comprehensibility. Comments can be added starting with '!'.
! cantilever modeled by shell elements with tipload. !=================================================================== PC-PROBLEM MASTERJOB = PC-ANALYSIS 1 ! Analysis with ID 1 is used
Input Blocks
- PC-BLOCK
- ND-BLOCK
- EL-BLOCK
- NURBS-BLOCK
- DESIGN-BLOCK
- BC-BLOCK
- LD-BLOCK
- OPT-BLOCK
More info still to come.
Use of Multiple Input Files
Carat++ can treat multiple input files. A PC-INCLUDE Block has to be added to the PC-BLOCK.
Hint: For better readability of large examples, the lenghty blocks of node coordinates or element topology can be written in a separate file.
The following shows a separation of input data into 4 additional files:
PC-INCLUDE mesh.dat boundaryConditions.dat loads.dat nodeSets.dat
Parameter Input Files
Carat++ input files give also the possibility to define a parametric simulation. In order to add some parameters, PC-PARAMETERS has to be added. It defines the name and the value. The value can either be directly defined or by a placeholder. This placeholder can be replaced in a parameter study, e.g. by a python-script. Some templates for that are provided on the server F_Users\statik\Forschung\_Carat++\UsefulScripts\RunCarat.
PC-PARAMETERS PAR=par1 VAL= 2 PAR=par2 VAL= VAR_PAR2 ! APPLICATION in input {@par1* 2.0} {@par2} ! e.g.: !PC-PROBLEM ! MASTERJOB = PC-ANALYSIS {@par2}
Whos here now: Members 0 Guests 0 Bots & Crawlers 1 |