-
Content Count
210 -
Joined
-
Last visited
-
Days Won
12
Posts posted by Ceyhan Erdem
-
-
Hi Christian,
When I deal with an airfoil I always start with one that has a chord length of 1.
So in most databases the airfoil point data has an aligned chord to x-axis that has a length of 1, starting from 0 and ending at 1.
You can either modify the feature "parameterize curve" to fit into your dimensions, or scale the airfoil data so that it has a chord of 1 and aligned to x axis.
Cheers
Ceyhan
-
Hi Christian,
Please find the attached project.
Please note that this is rather a simple case that can further be improved.
Please let me know if you have further questions.
The feature that reads the point data needs a file where x y z coordinates are provided only. You can modify the feature with respect to your needs.
Cheers
Ceyhan
-
Hi Christian,
What you you have to do first is to redefine the airfoil curve as a combination of thickness distribution and camber distribution curves.
Parameterizing these two curves in an automated way would provide you a way to approach your goal.
Let me prepare a simple project where one can read point cloud data; convert it to an interpolation curve; redefine it as camber distribution and thickness distribution curves and finally parameterize those curves in a simple and easy way.
If I find time today, will be posting here.
Cheers
Ceyhan
-
Hi Bastian,
If you would like to, you can send your project to erdem@friendship-systems.com
I can take a look in your model.
Cheers
Ceyhan
-
Hi Bastian,
That is a good question indeed.
In a BRep the number of edges for a geometry variation of a certain object does not necessarily remain constant. Depending on your split method it may vary.
So I would suggest you to use the source, which most probably is a surface.
mySurface.getEdge1() or 2,3,4
would provide you the necessary edge.
If you have further questions, please let me know.
Cheers
Ceyhan
-
Hi Zhongwen,
Can you please give a try the attached Feature Definition?
For the time being the dropdown menu contents are not suitable for the user to be modified. But I can suggest you a workaround that may help you for the time being.
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi Elysse,
Is it possible for you to share your project file, so that I can give a look?
Cheers
Ceyhan
-
Hi Steven,
Good to hear that you have resolved it.
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi William,
A "Geometry" component cannot be linked with another "Geometry" component within Ansys Workbench. It can be linked to Meshing, etc.. components however.
The so called "Ansys Geometry" component within ACT app acts in a same manner as a default Ansys Geometry component.
And I would not suggest and guarantee the success of linking the "Caeses Geometry" component with any other components. Please use the "Ansys Geometry" component for linking purposes.
What I can observe from your project file is that when you play with the above mentioned parameter, some unconnected edges appear. You can see them as red curves within the BRep.
Please check the attached picture for some hints.
Cheers
Ceyhan
-
Hi Chun,
As mentioned on the previous post, you should be having Shipflow installed on your computer. If that is the case you can find the the mentioned file as specified within the referred tutorial.
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi Steven,
Please check the attached project.
I have observed that, your function curve which is supposed to provide the x-position is not defined correctly. What the curve engine does is from the abcissa value (depending on your coordinate system) obtain the ordinate and provide this value as an input.
I have created a new function curve and got rid of the scale parameter.
Coming to your second question, when I use the command;
CL_midsurface.ft(0,20) ; I assume 20 is the starting x-position
I obtain the correct value for position parameter which is 0.
Cheers
Ceyhan
-
Hi William,
Sorry for the late answer, I was on vacation last week.
Can you please link the "ANSYS Geometry" but not the "CAESES Geometry" task to the "Geometry" task of the "Static Structural" system?
The "CAESES Geometry" is only an input task and would not work properly as desired if linked with any other system/task.
The reason to have the "ANSYS Geometry" is to create the so called "Named Selections" for boundary names, calibrate the geometry for different unit systems, etc..
Depending on your preferred Geometry tool within ANSYS Workbench (Under Workbench options, this can be modified) you can review the geometry either on "SpaceClaim" or "DesignModeler".
Please check the instructions how to utilize the ACT App, which can be found under CAESES Tutorials.
Please let me know if you have further questions. We can arrange a web-meeting.
Cheers
Ceyhan
-
Hi Gabrielle,
There seems to be a problematic fspline curve "bottom" within your Feature Definition "AFT".
The Area value seems to be not correct which causes the problem.
When I dig into the feature definition I can see that you are directly assigning the Sectional Area Curve value that you obtain from the computation to the fspline area. But you also have to take into consideration the normalization factor.
Please check the attached project and let me know if you have further questions.
Cheers
Ceyhan
-
Hi Justin,
Sorry for the late answer.
I would recommend you to perform the basic tutorials first so that you can have an idea how CAESES works. Then you can start using some Blade specific features that would enable you to create the desired geometry in a faster way.
You are highly encouraged to ask more specific questions with regards to parametric blade creation.
If you are planning to use ANSYS WB in conjunction with CAESES you can use the CAESES ACT App that comes with the CAESES installation files. You can also find the latest version of the ACT app within ANSYS ACT library.
Cheers
Ceyhan
-
Hi Michael,
Yes the "union" command within BRep is a solid command. Therefore you should have a water-tight geometry.
Cheers
Ceyhan
-
-
Hi Michael,
Please find attached the updated model.
A boolean "Unite" operations is a solid operation. Therefore you should have your geometry water-tight. For each part I have added the "Close Planar Holes" operation which converted them to water-tight geometries and then created a new BRep in which I have performed the Union operation.
Cheers
Ceyhan
-
Hi Michael,
Is it possible for you to share the geometry if it is not confidential? It would be easier and faster for me.
Cheers
Ceyhan
-
Hi Daphne,
Within the project you have provided, I can see that no points were selected for the free form deformation operations.
When you select the necessary points and play with the design variable "Angle_Rotation" you will notice that any geometry the free form deformation is assigned to, will be modifying.
Cheers
Ceyhan
-
Hi Daphne,
Can you please share your project?
It is not quite possible to come to conclusions from the provided picture.
Cheers
Ceyhan
-
Hi All,
And also a simple case created for a case of a volute.
After having obtained the section, I move it to the principal plane and then calculate the necessary values.
Cheers
Ceyhan
-
Hi Karl,
Thank you for reporting the crash. I was able to recreate the problem.
Now there is a ticket created for the developers to figure out the root cause of the crash.
Cheers
Ceyhan
-
Hi Tran,
I guess within STAR-CCM+ there must be a way to hook or compile so called "User Defined Functions (UDF)" as it is the case in ANSYS Fluent. But I believe CAESES forum is not likely the best place to address this question unless you would like to parameterize the velocity definition.
Maybe you would be more interested to dig into STAR-CCM+ Forums?
Cheers
Ceyhan
-
Hi Chien,
Sorry for the late reply, I was on vacation.
Can you please send your project to erdem@friendship-systems.com, so that I can give a look?
Cheers
Ceyhan
UPDATE: Parametric Multi-Element
in Variation & Optimization
Posted · Report reply
Please find below the point cloud data that I have used. As I said you can modify the "ReadData" feature Definition wrt your needs.
1.000000 0.000000 0.000000
0.950200 0.008912 0.000000
0.900500 0.017584 0.000000
0.850700 0.026352 0.000000
0.800800 0.035078 0.000000
0.750500 0.043616 0.000000
0.700900 0.051586 0.000000
0.650800 0.059006 0.000000
0.600600 0.065628 0.000000
0.550300 0.071270 0.000000
0.500000 0.075742 0.000000
0.449600 0.078800 0.000000
0.399200 0.080180 0.000000
0.348800 0.080320 0.000000
0.300000 0.078760 0.000000
0.250000 0.076000 0.000000
0.200000 0.071660 0.000000
0.175000 0.068800 0.000000
0.150000 0.065400 0.000000
0.125000 0.061386 0.000000
0.100000 0.056496 0.000000
0.075000 0.050484 0.000000
0.050000 0.042726 0.000000
0.037500 0.037762 0.000000
0.025000 0.031500 0.000000
0.012500 0.022728 0.000000
0.005000 0.014580 0.000000
0.002000 0.009474 0.000000
0.000000 0.000000 0.000000
0.002000 -0.005484 0.000000
0.005000 -0.008754 0.000000
0.012500 -0.013108 0.000000
0.025000 -0.017282 0.000000
0.037500 -0.020250 0.000000
0.050000 -0.022680 0.000000
0.075000 -0.026610 0.000000
0.100000 -0.029720 0.000000
0.125000 -0.032260 0.000000
0.150000 -0.034368 0.000000
0.175000 -0.036120 0.000000
0.200000 -0.037440 0.000000
0.250000 -0.039360 0.000000
0.300000 -0.039900 0.000000
0.348800 -0.039420 0.000000
0.399200 -0.037900 0.000000
0.449600 -0.035574 0.000000
0.500000 -0.032588 0.000000
0.550300 -0.029338 0.000000
0.600600 -0.025976 0.000000
0.650800 -0.022670 0.000000
0.700900 -0.019420 0.000000
0.750500 -0.016202 0.000000
0.800800 -0.012994 0.000000
0.850700 -0.009776 0.000000
0.900500 -0.006536 0.000000
0.950200 -0.003272 0.000000
1.000000 0.000000 0.000000