CAESES® focuses on automation within CAE workflows. In particular, the geometry generation can be fully automated. A slick GUI (Graphical User Interface) supports you in automating these tasks. However, CAESES® is also able to completely run in batch mode, without the need for a user interface.
Everything is Command-Driven
Due to the automation goal, CAESES® is a command-driven platform, where the commands are triggered in the background of the GUI. All commands can be directly accessed by yourself to fully script, automate and customize the use of CAESES®. This includes the command-based creation of
- File I/O (e.g. import and export of proprietary file formats)
- Control statements (loops, functions, etc.)
- Customization of the graphical user interface.
Comprehensive scripting capabilities for:
- User-defined functions and custom geometry
- Customization of the graphical user interface and widgets
- Process automation
The geometry generation process of complex models can be fully scripted and included in an automated design process. Use CAESES® as a geometry engine in your existing workflows, to robustly generate new design candidates of a geometry model. The robustness of the models and the mechanisms to automate everything are the core capabilities of CAESES®. More information about geometry scripting can be found in the blog post “Quick Guide: Geometry Scripting“.
Easy-To-Use Scripting Environment
The integrated and intuitive scripting language is easy to learn. It provides you a powerful tool for pretty much any task you have to solve in CAESES®. There is a programming window which comes with auto-completion, syntax highlighting and even a debugger for finding errors and mistakes in your command sequences and definitions.
An example for a user-defined export format is given in the article GeomTurbo Export for Blade Designs. Basically, one defines the input and the output of a so-called feature (here: an export object) as well as a command sequence that opens a file and writes the input geometry data into it.
CAESES® does not need to run in the GUI mode. You can trigger it in batch mode, simply controlled by an ASCII file, called fsc-script (this can also be exported from within the GUI). With just a few clicks, the batch mode capability integrates CAESES® into your existing workflow as a powerful geometry engine. As an example, you can read in geometry data from your data base (e.g. point data), fit it into an existing parametric CAESES® model, and run an optimization. This can all be done with a single click! See the case study from SIEMENS to learn more about these use cases.
Solid Geometry from ASCII Files
Another automation example where geometry is generated from an ASCII file is described in the article “Automated Solid Generation for Structural Analysis at MTU Friedrichshafen“. Simple geometry data is read using a proprietary format. From the data, a solid geometry is created automatically. The entire process is scripted and automated in CAESES® by using feature definitions and functions for I/O, loops, control statements and geometry creator methods (API).