Jump to content
The search index is currently processing. Activity stream results may not be complete.

All Activity

This stream auto-updates     

  1. Last week
  2. blackscreen1 blackscreen1 joined the community
  3. Manoj started following Hannes
  4. Manoj
    Thank for your help. I can't able to open and see the link you(HANNES) gave in the above post. Will u help by sharing in any other way.
  5. filehik558 filehik558 joined the community
  6. kmvadhk5 kmvadhk5 joined the community
  7. Ceyhan Erdem started following Read data from Excel file
  8. Ceyhan Erdem
    Hi Aniepark, Please find attached a simple example that may help you. Cheers Ceyhan excel_write_objectData.cdb
  9. aniepark
    Could you please tell me how to read data from Excel file ? I know CAESES could do that through COM. Thanks
  10. aniepark aniepark joined the community
  11. Hannes
    Hi Manoj, usually, you start with a working setup that is capable to be run from the command line. This is entirely FM-specific and outside of CAESES. In the current version of CAESES we provide a tutorial on the geometry preparation for FM, based on the Maritime Workflow introduced in CAESES 5.3. Assuming you've got the latest version of CAESES installed, you can find it here: http://localhost:65038/tutorials/maritime/software-connection/fine-marine-pre-processing . This geometry should be exported either as parasolid or as multibody stl. At this point the above-mentioned workflow comes in. Please identify all relevant input files and provide them from the software connector. Define case-specific values by parameters. Put the command you used to run the setup from the command line into "ExecutionSettings|Arguments" (possibly preceded by "bin/bash"). Run the case for one geometry from the software connector and define all relevant result files within the software connector for further post-processing. Hope this helps! Cheers, Hannes
  12. pdp.aero
    Hi I recently switched to 5.3 and now when I launch CAESES it opens for a second then it gets segmentation fault I appreciate if you let me know what is the problem. Thank you. 5.2.6 works though If you have crashes using a custom file dialog (PDF generation or OpenProject) add "-style plastique" to your start script Fontconfig error: Cannot load default config file: No such file: (null) CAESES 5.3.3 loading plugin libraries ... plugbase - ok plugblade - ok plugdakota - ok plugfeature - ok pluggenericintegration - ok plugkspline - ok plugmeta - ok plugopt - ok plugoptmo - ok plugsshrm - ok plugxffl - ok shfctrl - ok initializing types ... plugins - ok basic object types - ok entity types - ok *** INFO REPORTSERVER : started [port: 12345] view types - ok initializing commands ... Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/pdp/soft/caeses/CAESES_5.3.3_Linux.x86_64/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/pdp/soft/caeses/CAESES_5.3.3_Linux.x86_64/bin/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/pdp/soft/caeses/CAESES_5.3.3_Linux.x86_64/bin/libexec/qtwebengine_dictionaries' all *** INFO DOCUSERVER : started [port: 34709] - ok initializing configuration ... updating geometry - ok QImage::scaleWidth: Image is a null image QOpenGLWidget: Already initialized, setting the format has no effect QOpenGLWidget: Already initialized, setting the format has no effect /home/pdp/soft/caeses/CAESES_5.3.3_Linux.x86_64/CAESES: line 115: 1344215 Segmentation fault (core dumped) ${FS_INSTALL_DIR}/bin/CAESES $ARGS "$@"
  13. Manoj
    Hello all, I'm currently working to connect the FINEMARINE software with the CAESES software to optimize a sample hull model. I don't know where to start and all. I have went through your Q&A session regarding the same field. Kindly give some instructions on 1.Geometry input: Whether it should be meshed and given or else only domain subtracted with hull model would be used How the domain should be imported .,i.e, in what format Which one to be used eiether Hexpressx86_64.exe or finemareinex86_64.exe in Local Application for computation? 2.Input File: Input.txt as .sim and .iec of previously runned files What would be the possible input and logics Any other files to be included 3. Result values : output.txt Thanking you in advance, hoping your suggestions would help me to complete my college project
  14. Manoj started following CAESES with FINE MARINE
  15. Manoj
    Hello all, I'm currently working to connect the FINEMARINE software with the CAESES software to optimize a sample hull model. I don't know where to start and all. I have went through your Q&A session regarding the same field. Kindly give some instructions on 1.Geometry input: Whether it should be meshed and given or else only domain subtracted with hull model would be used How the domain should be imported .,i.e, in what format Which one to be used eiether Hexpressx86_64.exe or finemareinex86_64.exe in Local Application for computation? 2.Input File: Input.txt as cwizard.input What would be the possible input and logics Any other files to be included 3. Result values : output.txt Thanking you in advance, hoping your suggestions would help me to complete my college project
  16. Earlier
  17. Manoj Manoj joined the community
  18. caycanhhanoi caycanhhanoi joined the community
  19. Praveen
    All, The workaround for this issue was: - Have the blade surface be slight extended above the shroud curve, and slightly below the hub curve. - Have the Suction and Pressure side curves extracted on the un-extended blade surface for sources - Have leading edge and trailing edge curves extracted - Ideally, using trimmed blade surfaces by domain extents (U,V) - Having these, you can define your TurboGrid export options, and would translate into ANSYS Workbench with no issues.
  20. Amir Amir joined the community
  21. AMIRUDEEN AMIRUDEEN joined the community
  22. pythonsevenmentor pythonsevenmentor joined the community
  23. 7zatpvz1 7zatpvz1 joined the community
  24. orborneroberts
    thanks
  25. Mr. Heinrich von Zadow started following CAESES outputs NAPA-format hull line file
  26. Mr. Heinrich von Zadow
    Hi there, a few users have successfully implemented such features with varying degree of complexity. If you are familiar with NAPA definitions you can easily write a custom export in CAESES. However, there is no solution readily available in CAESES. Kind regards, Heinrich
  27. Ceyhan Erdem started following TurboGrid export erroring out in Workbench
  28. Ceyhan Erdem
    Hi Praveen, Can you please be sure that your fsc file is up to date and the project saved. After this check, if you still face the same problem, can you please provide me your project file? You can send the file to erdem@friendship-systems.com. Cheers Ceyhan
  29. Mr. Chang Xie
    Good day. For ship engineer, hull line need to be imported into NAPA for ship stability calculation and subsequent construction. So NAPA-format hull line file is important for ship engineer to edit in NAPA. I want to export NAPA-format hull line file (see attached) from CAESES based on a hull surface (Brep surface or Trimesh sufface), which is a txt file, not iges or stl. Have you developed an output feature yet? Can you provide me with a reference? Thank you. KCS_hull_SVA_Napa.txt
  30. Praveen
    This is the entire transcript of the Workbench Extension log : Extensions Log File 12/3/2024 4:28:58 PM Resetting id_tg_task2 Deleting id_tg_task2 CALLING onaftertaskreset_TG(task) CALLING get_system_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) onaftertaskreset_TG id_tg_task2 end of onaftertaskreset_TG(task) CALLING createWorkFlow(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) CALLING get_system_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) counterTG = 0 counter = 1 finished creating workflow end of createWorkFlow(task) CALLING createParameterSet_TG(task) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord1 : 47.4911) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord2 : 65.3502) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord3 : 77.6049) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord4 : 81.0107) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord5 : 83.8507) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal1 : 32.607) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal2 : 33.3391) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal3 : 37.167) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal4 : 38.4693) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal5 : 32.6073) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting1 : 20.4546) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting2 : 23.7288) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting3 : 21.2557) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting4 : 25.5824) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting5 : 27.5514) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger1 : 20.6363) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger2 : 35.4184) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger3 : 40.3953) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger4 : 39.9846) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger5 : 39.2039) DP SET: |V2Opti|BladedComponent1|MeridionalContours|01_hubContour|radius2Factor : 1) DP SET: |V2Opti|BladedComponent1|MeridionalContours|02_shroudContour|radius2Factor : 1) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posHub : 0.05) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posShroud : 0.05) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt1 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt2 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt3 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaShroud : -20) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist1 : 6.83) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist2 : 6.83) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist3 : 6.83) DP SET: |V2Opti|NOB : 3) CALLING create_parameter_object(task) added chord1 47.4911 CALLING create_parameter_object(task) added chord2 65.3502 CALLING create_parameter_object(task) added chord3 77.6049 CALLING create_parameter_object(task) added chord4 81.0107 CALLING create_parameter_object(task) added chord5 83.8507 CALLING create_parameter_object(task) added metal1 32.607 CALLING create_parameter_object(task) added metal2 33.3391 CALLING create_parameter_object(task) added metal3 37.167 CALLING create_parameter_object(task) added metal4 38.4693 CALLING create_parameter_object(task) added metal5 32.6073 CALLING create_parameter_object(task) added setting1 20.4546 CALLING create_parameter_object(task) added setting2 23.7288 CALLING create_parameter_object(task) added setting3 21.2557 CALLING create_parameter_object(task) added setting4 25.5824 CALLING create_parameter_object(task) added setting5 27.5514 CALLING create_parameter_object(task) added stagger1 20.6363 CALLING create_parameter_object(task) added stagger2 35.4184 CALLING create_parameter_object(task) added stagger3 40.3953 CALLING create_parameter_object(task) added stagger4 39.9846 CALLING create_parameter_object(task) added stagger5 39.2039 CALLING create_parameter_object(task) added radius2Factor 1 CALLING create_parameter_object(task) added radius2Factor 1 CALLING create_parameter_object(task) added posHub 0.05 CALLING create_parameter_object(task) added posShroud 0.05 CALLING create_parameter_object(task) added thetaInt1 0 CALLING create_parameter_object(task) added thetaInt2 0 CALLING create_parameter_object(task) added thetaInt3 0 CALLING create_parameter_object(task) added thetaShroud -20 CALLING create_parameter_object(task) added dist1 6.83 CALLING create_parameter_object(task) added dist2 6.83 CALLING create_parameter_object(task) added dist3 6.83 CALLING create_parameter_object(task) added NOB 3 finished reading params end of createParameterSet(task) CALLING update_TG(task) CALLING onbeforetaskupdate_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) onbeforetaskcreation id_tg_task2 end of onbeforetaskupdate_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) CALLING get_system_TG(task) CALLING getProcessName_TG(task) getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName_TG(task) CALLING updateUnits_TG(task) end of updateUnits_TG(task) CALLING createParameterSet_TG(task) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord1 : 47.4911) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord2 : 65.3502) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord3 : 77.6049) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord4 : 81.0107) DP SET: |V2Opti|BladedComponent1|Fan|Functions|chord|chord5 : 83.8507) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal1 : 32.607) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal2 : 33.3391) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal3 : 37.167) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal4 : 38.4693) DP SET: |V2Opti|BladedComponent1|Fan|Functions|metal|metal5 : 32.6073) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting1 : 20.4546) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting2 : 23.7288) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting3 : 21.2557) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting4 : 25.5824) DP SET: |V2Opti|BladedComponent1|Fan|Functions|setting|setting5 : 27.5514) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger1 : 20.6363) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger2 : 35.4184) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger3 : 40.3953) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger4 : 39.9846) DP SET: |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger5 : 39.2039) DP SET: |V2Opti|BladedComponent1|MeridionalContours|01_hubContour|radius2Factor : 1) DP SET: |V2Opti|BladedComponent1|MeridionalContours|02_shroudContour|radius2Factor : 1) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posHub : 0.05) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posShroud : 0.05) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt1 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt2 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt3 : 0) DP SET: |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaShroud : -20) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist1 : 6.83) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist2 : 6.83) DP SET: |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist3 : 6.83) DP SET: |V2Opti|NOB : 3) end of createParameterSet(task) inputParams : inCAESES_chord1 47.4911 inputParams : inCAESES_chord2 65.3502 inputParams : inCAESES_chord3 77.6049 inputParams : inCAESES_chord4 81.0107 inputParams : inCAESES_chord5 83.8507 inputParams : inCAESES_metal1 32.607 inputParams : inCAESES_metal2 33.3391 inputParams : inCAESES_metal3 37.167 inputParams : inCAESES_metal4 38.4693 inputParams : inCAESES_metal5 32.6073 inputParams : inCAESES_setting1 20.4546 inputParams : inCAESES_setting2 23.7288 inputParams : inCAESES_setting3 21.2557 inputParams : inCAESES_setting4 25.5824 inputParams : inCAESES_setting5 27.5514 inputParams : inCAESES_stagger1 20.6363 inputParams : inCAESES_stagger2 35.4184 inputParams : inCAESES_stagger3 40.3953 inputParams : inCAESES_stagger4 39.9846 inputParams : inCAESES_stagger5 39.2039 inputParams : inCAESES_radius2Factor 1.0 inputParams : inCAESES_radius2Factor 1.0 inputParams : inCAESES_posHub 0.05 inputParams : inCAESES_posShroud 0.05 inputParams : inCAESES_thetaInt1 0.0 inputParams : inCAESES_thetaInt2 0.0 inputParams : inCAESES_thetaInt3 0.0 inputParams : inCAESES_thetaShroud -20.0 inputParams : inCAESES_dist1 6.83 inputParams : inCAESES_dist2 6.83 inputParams : inCAESES_dist3 6.83 inputParams : inCAESES_NOB 3.0 CALLING get_system(task) CALLING getProcessName(task) getProcessName id_tg_task2 getProcessName task.Name at getProcessName= id_tg_task2 Geom_comp_name at getProcessName= id_tg_task2 end of getProcessName(task) os_ver: Win64 fscName=V2-Opti baseline name=baseline proj_type=cdbc loading plugin libraries ... plugbase - ok plugblade - ok plugcom - ok plugdakota - ok plugfeature - ok pluggenericintegration - ok plugkspline - ok plugmeta - ok plugnax - ok plugopt - ok plugoptmo - ok plugsshrm - ok plugxffl - ok shfctrl - ok initializing types ... plugins - ok basic object types - ok entity types - ok initializing commands ... console cmds - ok initializing configuration ... *** INFO REPORTSERVER : started [port: 12345] *** INFO Open project : V2-Opti [3.736 secs cputime | 3.7353 secs in worldtime] true |V2Opti|BladedComponent1|Fan|Functions|chord|chord1 |V2Opti|BladedComponent1|Fan|Functions|chord|chord2 |V2Opti|BladedComponent1|Fan|Functions|chord|chord3 |V2Opti|BladedComponent1|Fan|Functions|chord|chord4 |V2Opti|BladedComponent1|Fan|Functions|chord|chord5 |V2Opti|BladedComponent1|Fan|Functions|metal|metal1 |V2Opti|BladedComponent1|Fan|Functions|metal|metal2 |V2Opti|BladedComponent1|Fan|Functions|metal|metal3 |V2Opti|BladedComponent1|Fan|Functions|metal|metal4 |V2Opti|BladedComponent1|Fan|Functions|metal|metal5 |V2Opti|BladedComponent1|Fan|Functions|setting|setting1 |V2Opti|BladedComponent1|Fan|Functions|setting|setting2 |V2Opti|BladedComponent1|Fan|Functions|setting|setting3 |V2Opti|BladedComponent1|Fan|Functions|setting|setting4 |V2Opti|BladedComponent1|Fan|Functions|setting|setting5 |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger1 |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger2 |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger3 |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger4 |V2Opti|BladedComponent1|Fan|Functions|stagger|stagger5 |V2Opti|BladedComponent1|MeridionalContours|01_hubContour|radius2Factor |V2Opti|BladedComponent1|MeridionalContours|02_shroudContour|radius2Factor |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posHub |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|posShroud |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt1 |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt2 |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaInt3 |V2Opti|BladedComponent1|MeridionalContours|04_leadingEdge|thetaShroud |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist1 |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist2 |V2Opti|BladedComponent1|MeridionalContours|05_trailingEdge|dist3 |V2Opti|NOB *** INFO Exporting : V2-Opti/manual_results/baseline/input/export_Blade_1.tin true ***Caeses Error*** Error when invoking function 'update_TG'. Traceback (most recent call last): File "C:\Users\gambhirp\AppData\Roaming\Ansys\v242\ACT\extensions\CAESES_Workbench_App_23_09_2024_v2\turbo.py", line 430, in update_TG StandardError: Exception has been thrown by the target of an invocation. Traceback (most recent call last): File "C:\Users\gambhirp\AppData\Roaming\Ansys\v242\ACT\extensions\CAESES_Workbench_App_23_09_2024_v2\turbo.py", line 430, in update_TG UnboundLocalError: Local variable 'file_name' referenced before assignment.
  31. Praveen started following TurboGrid export erroring out in Workbench
  32. Praveen
    Hello, All! I've been using the latest version of CAESES. I designed an axial fan blade, and using the Surface method in the TurboGrid export feature, created a CAESES FSC file. When reading in the FSC file into the CAESES TurboGrid engine in ANSYS Workbench, the ANSYS extension log gives out this error: Please let me know if there is a workaround for resolving this issue.
  33. Mr. Heinrich von Zadow started following RSM from CAESES
  34. Mr. Heinrich von Zadow
    Hi Yuvraj, if everything else is set up correctly, you should be able to abort the CFD run and just take a look at the 'finaldata' file that is written by Dakota. This contains the predicted optimal design (or Pareto set, if multi-objective) and the predicted evaluations. Kind regards, Heinrich
  35. yuvraj
    Hello Caeses Team I am trying to make surrogate model by importing the result pool, but when I run the optimization (RSMO) on it , it gives me points to test by CFD run , but I need data from the response surface, how to tackle this problem. Eagerly waiting for the reply Regards Yuvraj
  36. radleymartinez
    Contact me
  37. Weber
    Hi Raj Dave, Unfortunately the updated versions of the samples "axial compressor" and the "axial fan" inside our sample page (accessible through Help > Samples > Samples) are using the airfoil method, which directly maps the airfoil from 2D to 3D space alongside a defined stacking curve. The advantage here is, that the blade is modelled by the airfoiles being directly stacked onto a 3-dimensional stacking line axis. To get familiar with this approach, we uploaded a tutorial video, which can be accessed here. With the camber-based blade approach, when using the stream section to generate camber lines, all meridional contours as well as the stacking line must be defined in 2D-space -- the XZ-plane to be precise -- and the stacking line must be defined from hub to shroud or otherwise errors in the camber line generation might occur. Often, the stream section/camber based approach is used when designing radial turbomachines. Nevertheless, it can also be used to model axial turbomachinery. To understand what is happening when choosing between the different modes of the stream section (beta vs. m', theta vs. m' etc.) I recommend looking into the blade modeling section in the help section, which can be accessed through Help > Geometry Modeling > Blade Modeling. Also we uploaded a video, where the stream section was used to generate camberlines which can be found here. In addition to that, the newest version of CAESES includes a newly developed turbo machine workflow, which is a step-by-step guide to quickly model turbomachinery parts in CAESES. The two videos linked above are also explaining how to use this new workflow. I hope the material explains everything you needed to know about stream sections. If not, please don't hesitate to ask further questions. Best regards, Johannes
  38. Raj Dave
    Hello, I am currently developing a single-stage axial fan blade using the Stream Section curve. While I have been able to generate the blade surface, I am encountering challenges in understanding the camber lines produced by the Stream Section curve. Additionally, I am having trouble locating the Stream Section sample referenced by @Jörg in his post, "Axial Compressor Blade via Stream Section Curve." My objective is to generate blades by specifying beta (flow) and stagger angles. I would greatly appreciate any guidance or insights from the experts in this community. Thank you for your assistance.
  39. Ceyhan Erdem started following CAESES Integration with ANSYS OptiSlang 2024R2
  40. Ceyhan Erdem
    Hi Praveen, I will suggest we have a web-meeting. Please write to "erdem@friendship-systems.com" about your availibility for the upcoming days. To be honest, it is been a while since the development of the CAESES integration of Optislang and I am not sure about its compatibility with the new versions of Optislang. But I guess, we can resolve the issue directly through Ansys Workbench. Cheers Ceyhan
  41. Praveen
    Hello there! I am planning to run an optimization study of my CAESES geometry with ANSYS OptiSlang 2024R2. We are aware that there is an in-built software integration of CAESES in OptiSlang. I am having trouble invoking CAESES to run in batch mode and send the FSC and ACIS file to SpaceClaim. Any guidance to succeed in these sequence steps would be most beneficial.
  42. Mr. Heinrich von Zadow
    Hi Praveen, thanks for the update, much apprechiated. Indeed, surfaces do not propagate their colors, BReps do. Cheers, Heinrich
  43. Praveen
    Hello Heinrich! I believe the problem has been resolved. The thing is to assign BReps of all the surfaces (inlet, outlet, periodics, hub and shroud, interfaces) and assign colors to the BReps. I've changed from using the surfaces themselves to using the BReps of these surfaces to perform 'Solids from Intersections' Also, the Boolean features when creating solids, and creating a BRep color for that operation ensured that the Blade was labeled. This sequence of operations ensured I' m retaining colors when transferring to ANSYS Workbench.
  44. dominicgarcia
    Use the Transform or Array feature in CAESES to create copies of your single blade. This allows you to replicate the geometry while maintaining links to the original parameters. If your propeller has a specific number of blades (e.g., 3, 4, 5), you can set up an array transformation to position the copies correctly around the hub.
  45. Carl Benz

    Fdbc to fdb

    Carl Benz replied to Alex's topic in Installation

    Hi, CAESES locks academic projects to not beeing used commercially. Best, Carl
  1. Load more activity
×
×
  • Create New...