Jump to content

Mr. Carsten Fuetterer

Moderators
 View Profile  See their activity

  • Content Count

    167

  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Mr. Carsten Fuetterer

  3. Posted · Report reply

    Hi there,

     

    thanks Paulo for helping out with this interesting papers.

     

    The term impeller is just a general description for turbomachinery blades. Turbine blades are also some kind of impeller.

     

    With the method described in the video, you can create turbine-, compressor- & fan blades. The stream section, which is used to create the camber surface, allows you to set the flow angles (beta angles) or the wrap angles (theta angle).

     

    best regards

     

    Carsten

  7. Posted · Report reply

    Hello Tariq,

     

    I think it is still not clear to us. Here is what I understand:

     

    • you have a baseline geometry and perform a Moga study and you come up with a pareto front
    • now you pick a design from this run (not on the pareto front) and perfom another MOGA with the same variable setup and come up with another pareto front
    • now you are wondering why the designs of the two pareto fronts look different?

    best regards

     

    Carsten

    • Upvote 1

  8. Posted · Report reply

    Hi Bodo,

     

    an image curve will be default be the exact curve as the source curve. When you change the parametrization to e.g. "Unit Speed", then the curve will be approximated with new control points to fit the original curve within a certain approximation tolerance.

     

    The command .setNumberOfEvaluationForParametrization() is not used anymore and should not have any effect on the curve.

     

    The default value of the approximation tolerance is 1e-5

    post-85-0-51458200-1510589664_thumb.png

     

    best regards

     

    Carsten

    • Upvote 1

  15. Posted · Report reply

    Hi,

     

    the surface sensitivity gives you a scalar field, which describes the amount you have to push or pull the surface cell inwards or outwards to lower the objective function.

     

    The design velocities in CAESES gives you the information how one design variable changes the shape normal to the surface.

     

    In CAESES you then combine the surface sensitivity with the design velocities, and you will get the parametric sensitivities of each design variable, which describes the gradient of objective function change to design variable change. This means you know then how much you have to change one design variable to change the objective function. You also know the influence of each design variable on the objective function.

     

    best regards

     

    Carsten

  18. Posted · Report reply

    Hi Hamidreza,

     

    you are right, Maxsurf doesn't provide a batch mode.

     

    What you could do is to prepare an master project from where you trigger the project with the com integration. In that way you could use the software connector in the master project and the standard design engines. You would need to control CAESES with an fsc file.

     

    With that you could trigger as many CAESES instances as you have CAESES licenses.

     

    best regards

     

    Carsten

  20. Posted · Report reply

    Hello Hamidreza,

     

    at the moment it is not possible to trigger multiple COM applications at the same time. In general this would be possible to implement it into CAESES, but at the moment this is not at high priority.

     

    In most cases COM connections are pretty fast, so that there is not a big need to run it in parallel. But we can think about it, to implement it in future releases.

     

    best regards

     

    Carsten

  23. Posted · Report reply

    Hi,

     

    if you want to read data from text or csv files it's fairly simple to do it in a feature definition.

     

    We use a simple file like this:

     

    post-85-0-15039300-1503303904_thumb.png

     

    To start we create a new feature definition:

     

    post-85-0-77015200-1503304079_thumb.png

     

    In the "create function" tab, we can use the code templates to create a basic control structure:

     

    post-85-0-46379700-1503304316_thumb.png

     

    The variable "FilePath" is not defined and has to be supplied with an argument. In this case I want the object "file" as an argument. So I comment the first line from the feature and create an new argument:

     

    post-85-0-20593800-1503306529_thumb.png

     

    The feature code looks like this:

     

    post-85-0-48507700-1503306458_thumb.png

     

    You can see that a string is  create for each line of the file. So now we have to split this string in order to access the double values. Therefor I use the split command, which has the output of an objectlist. Then I create a point, which accesses each value of that object list:

    post-85-0-07589800-1503306464_thumb.png

     

    Now we have to store the points for each line inside an extra objectlist.Therefor we create a new list and add the point:

     

    post-85-0-22296100-1503306470_thumb.png

     

    Finally we create fore example an bsplinecurve, with the new list of points. Additionally encapsulated the while loop into a persistent section in order to visualize the points for each loop. Otherwise we would just see the last point.

     

    post-85-0-28079900-1503306477_thumb.png

     

    Now we create the feature from the feature definition:

     

    post-85-0-95433300-1503306124_thumb.png

     

     

    We set the path to the reference file:

    post-85-0-26076600-1503306842_thumb.png

     

     

    This nice dialog only appeared, because we didn't allow expressions for the argument inside the feature definition:

    post-85-0-24005500-1503306853_thumb.png

     

    The final curve:

    post-85-0-65761700-1503306617_thumb.png

     

    I hope this helps you to create you own custom file reader.

     

    best regards

     

    Carsten

     

     

     

     

     

    readTextFile.fdb

    data.zip

×
×
  • Create New...