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.

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.

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.

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.

Image didn't attach properly. Here you go

Quick update since yesterday: Good news: The BRep bodies are coming in as Body Named Selections into Space Claim. Still some concerns: For InletBod BRep, all face boundaries are also being read into SpaceClaim (Inlet, interface, periodics) In the RotorBod BRep however, I do see the right colors come in, but the Named Selection I assigned for those colors aren't populated. For example: I labeled the BRep face of the blade as 'Blade' colored 'black' in CAESES, and is coming in as so. So is the interface color going out and connecting to the OutletBod BRep. But, again, no Named Selection populated. Is there a restriction on the kind of color assignation for a boundary face in CAESES which cannot be exported?

Heinrich, To answer the second question.. Yes, after specifying all BRep body and boundary colors, I ran the exportSat export function and then exported a new FSC file. I then close out of CAESES. After opening CAESES and ask it to run the FSC file, CAESES crashes.

Attached is the CAESES geometry file for reference Trial2.cdbc

Hello Ceyhan! Yes I already double-checked that I disabled the ' Use SpaceClaim Color Tones' option in SpaceClaim options. This issue happens even after doing that.

Hello Heinrich! I started by labeling the BRep bodies by clicking on the BRep itself and specifying color names in the Display Options. For the faces, I then proceed by selecting them from the Graphics window. They end up looking like tesselated entities. Here's an example of selecting the faces and specifying them as 'Inlet' boundary condition.

Hello Everyone! I've been using CAESES to limited success in creating a blade geometry (single blade segment, having three domains: Inlet, Rotor, Outlet). During creation of BRep solids, the solid color (Fluid volume Named Selections) are transferring to ANSYS Workbench after running the exportSat in Export options, and saving the FSC file. However, when labeling subsequent BRep face color (boundary Named Selections) and utilizing the same steps for exportSat and writing FSC file, they don't appear in SpaceClaim. Steps were taken an double-checked while reading through the ANSYS Workbench Software Connections. - Is there a character limit that we must be aware of when exporting boundary Named Selections from CAESES? - Is there a prescribed order of operations to be followed to ensure that all volums and faces are named appropriately?

Thank you for your reply on this, Ceyhan! Quick update: Read through the Software Connector tutorial for SpaceClaim import. After following the steps, re-read the FSC file into the CAESES Geometry reader extension in WB 2024R2. SpaceClaim now shows Named Selections of face boundaries. However, when assigning color to the volume, some of the face boundaries don't seem to import into SpaceClaim.

Update: After downloading the 2024R2 extension for Workbench from Ceyhan, the CAESES geometry does upload into SpaceClaim. The concern now is, the boundary Name selections do not appear in SpaceClaim groups. I went ahead and re-did the coloring operations and BRep operations in the CAESES project, and then exported to a .sat file of just the BRep itself. Also, went ahead and over-wrote the existing .fsc file to be read into WB using the CAESES extension. Made sure to enable the 'Named Selection' filter during ANSYS Geometry import (named all boundaries using the NS filter so that ANSYS can read them in). I've attached the CAESES project file pertaining to these operations. What would be the best practice strategy to start coloring face and BRep boundary colors to mitigate this issue? Trial1.cdbc

Hello there! I recently designed a blade geometry with a fluid domain, and want to import into ANSYS Workbench 2024R2. I installed the ANSYS Extension in <Caeses Installation Folder>/CAESES5/etc/ansys Workbench fails to read in the .fsc file and crashes. I also tried running the .fsc file on a fresh instance of CAESES, and CAESES itself crashes. Attached are the .fsc and .cbdc files in question. We'd like to resolve this issue, as this design will be used for optimization purposes. Please let us know if anything additional is required. Tomas, could you also elaborate the Space Claim import options that needed to be modified to resolve this issue? Trial1.fsc Trial1.cdbc

Hello, Carl! I've been trying to find some resources for this exact situation. There is a feature definition that already exists for creating flow domain sector (single blade segment) for centrifugal impellers, but not anything equivalent for axial fans or marine propellers. We'd like to know further steps in this process, such as extending faces to have inlet and outlet segments, and splitting them before and after the fan geometry (to use MRF interfaces in CFD solvers)