CAESES + Fluent integration

[CAESES + Fluent integration]

Hello

 

Thank you for this example. It was very helpful in connecting CAESES with Fluent and the Mesher I am using (Pointwise) together. I am wondering if using a batch file is the only way to connect the two together. My first attempt was to create two separate connections for Fluent and Pointwise but I was unclear on how to get them to run sequentially, mesher and then solver. 

 

HOWEVER, I have 2 secondary issues.

 

1) The parameters I have created for result values are not updating properly and read as nan.

 

2) When I try running a Sobol engine to conduct a design study it runs Pointwise to mesh the first one, then runs fluent to solve it but starts running pointwise again and then fluent again for the second design before the first one has finished solving. This causes several instances of Fluent which drastically slows the computation down. In addition to this the evaluation parameters give nan values. I tried it with asynchornous update on and off and specifying the maximum number of running instances of the local application which is the batch file. Any ideas on how to get CAESES to wait for Fluent to finish solving the first design before starting to mesh and solve the second design? Is it the batch file which effectively finishes once it starts Fluent so it begins the next one? I have tried using START /wait in the batch file in stead of call but that has not worked. Also why are the evaluation parameters not updating? 

 

Any help is appreciated :)

NACA4DS_Connection_Test.fdbc

[Integration with Pointwise and CAESES]

Hello Karsten

 

Thank you for that. The connection now successfully works. Now I just need to create a second connection to Fluent. Just to clarify for anyone else who uses this information you should only delete the -b in the arguments field but leave the glyph script. I tried without the whole argument statement and all it did was open Pointwise. 

 

Thank you again for your help. 

 

Edan

[Integration with Pointwise and CAESES]

Hello Mr. Takamichi Hiroi

 

Thank you for this example. I tried applying what I could understand from your example to my own Glyph script created using the journal function in Pointwise to mesh a 2D airfoil. However when I tried to run it I encountered an error with the following output. 

 

Moving C:/Users/FSAE/Documents/RFR Engineering 2015/Systems/Aero/CAESES/NACA/NACA66-416/manual_results/baseline/Runner/input/2D_Airfoil_CGrid_Extrusion_Mesh.glf to C:/Users/FSAE/Documents/RFR Engineering 2015/Systems/Aero/CAESES/NACA/NACA66-416/manual_results/baseline/Runner//2D_Airfoil_CGrid_Extrusion_Mesh.glf

Moving C:/Users/FSAE/Documents/RFR Engineering 2015/Systems/Aero/CAESES/NACA/NACA66-416/manual_results/baseline/Runner/input/Airfoil to C:/Users/FSAE/Documents/RFR Engineering 2015/Systems/Aero/CAESES/NACA/NACA66-416/manual_results/baseline/Runner//Airfoil

 

[Captured output from application C:/Program Files (x86)/Pointwise/PointwiseV17.3R3/win64/bin/Pointwise.exe]

 

Fatal:  Usage:

Pointwise.exe 

        ?-usage?

        ?-version?

        ?-language spec?

        ?-tbbinit num?

        ?-dirmode current | saved?

        ?-noshaders

        ?-environment env_file?

        ?startup_script | file?

 

 

Do you or anyone else on this forum have any idea what might have caused this? I've been struggling with figuring out how connections work and connecting to Pointwise and Fluent so I would greatly appreciate any ideas and suggestions I would receive from the CAESES community.  I have attached my project so you can see what I have done. 

 

Thank you in advance

NACA66-416.fdbc

[How to avoid geometry overlap?]

Thank you Stefan and Mattia for your responses. Stefan could you elaborate on how I would avoid running a computation on an undesirable design? Is it not possible for the Sobol to reject a design that does not meet the constraints? If so is it possible to create a function that would check the Sobol designs for invalid designs and then delete those and run the sobol again until there were enough valid designs. 

[How to avoid geometry overlap?]

Hello

 

I am attempting to model a 2-dimensional, 3-element airfoil and have the Sobol engine create variants. I was wondering how I could ensure that the sobol engine doesn't create two of the elements on top of each other. In other words I don't want a variant to have overlapping or intersecting airfoil profiles. Is it possible for CAESES to verify if two curves are intersecting and avoid creating a sobol variant if that is the case? I have defined each airfoil with a 4 parameters: chord (scale), angle of attack (rotation), x and y position (translation). 

 

Thank you in advance for you help.