Geom­Turbo Export for Blade Designs

In one of our last posts we briefly touched the topic of writing a custom export in CAESES®, e.g. to make use of pro­pri­etary export formats. Our cus­tomers use a variety of export formats, and even ​“standard” formats are often used in dif­fer­ent versions and with dif­fer­ent options. Hence, we decided to support only a subset of the common export formats that are in the market, but also offer a very simple way for our users to realize almost any type of (ASCII-based) file format.

In this short article, we give you an example of the *.geom­turbo format, that is used by Autogrid5 (NUMECA). This format has been requested from several users within the last months, and we have now put a basis version of it into the next CAESES® release. You will find it in the menu, features > tools, see the fol­low­ing screenshot: 

For the geom­turbo format, several options and con­fig­u­ra­tions are possible, and we have handed over some of them to the user, see the next screen­shot. There are controls for the number of points per section, the number and the radial dis­tri­b­u­tion of sections, expan­sion factors for extend­ing the blade into the hub and shroud region, as well as the pos­si­bil­ity to extend the hub and shroud contours. 

This export works quite nice, and it can be readily used. However, the great thing is that a user is still able to modify the entire export routine — just via editing the feature def­i­n­i­tion. With this, CAESES® users are inde­pen­dent of our activ­i­ties and devel­op­ment sched­ules. We tried to make the syntax of our feature pro­gram­ming language as simple as possible, so that everyone can learn it quickly. The last screen­shot shows a code snippet of this feature definition. 

Batch Mode Run

Many of our users run CAESES® in batch mode, i.e. without a graph­i­cal user inter­face, con­trolled by external opti­miza­tion tools such as optiS­Lang, Optimus or Mod­e­FRON­TIER. In order to create the geom­turbo file in auto­mated processes for dif­fer­ent design can­di­dates of impellers, you simply have to add the feature run() command to the fsc-script:

More Infor­ma­tion

Here is a link to the CAESES® com­mu­nity forum where we posted this feature def­i­n­i­tion. You can directly download and use it for your own blade design projects.

Writing export routines in CAESES® is just a very tiny piece of func­tion­al­ity, and it is extremely helpful — but probably not super amazing ;-) For more rather amazing stuff, check out the product pages of CAESES®. If you are using ANSYS Tur­bo­grid for meshing your blade geome­tries, you might find this Tur­bo­Grid blog post interesting. 

Learn More