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

All Activity

This stream auto-updates     

  1. Today
  2. qz9li5sq qz9li5sq joined the community
  3. Yesterday
  4. bfiu91gi bfiu91gi joined the community
  5. j3oglbeb j3oglbeb joined the community
  6. Last week
  7. eugenewright eugenewright joined the community
  8. muncqebc muncqebc joined the community
  9. billierios billierios joined the community
  10. Alex
    Hi Carl, thanks for the tips. With this i made a code in feature definitions to get the x,y,z coordinates of a single line, but i want to do this for multiple lines in a section Group. how do i explode a section group, because i can't GetObject the section group. and how do i run through multiple lines to get the coordinates. point_extraction.fdf
  11. Aurora Aurora joined the community
  12. Earlier
  13. Praveen
    Image didn't attach properly. Here you go
  14. Praveen
    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?
  15. jelinah211 jelinah211 joined the community
  16. Praveen
    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.
  17. Praveen
    Attached is the CAESES geometry file for reference Trial2.cdbc
  18. Praveen
    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.
  19. Praveen
    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.
  20. Ceyhan Erdem
    Hi Praveen, Do you still face the same problem? Is it possible that somehow mistakenly you have assigned the same domain color to a boundary? Cheers Ceyhan
  21. Ceyhan Erdem
    Hi Praveen, If you are using SpaceClaim as your default geometry editor in Ansys Workbench, you need to disable the "Use SpaceClaim Color Tones" option. It is mentioned in the CAESES Workbench App Tutorial. Please revise the mentioned tutorial and repeat your process. Cheers Ceyhan
  22. Mr. Heinrich von Zadow started following CAESES to ANSYS Workbench Boundary Colors Issue
  23. Mr. Heinrich von Zadow
    Hi Praveen, how did you label/color the subsequent BRep faces? Have you tried to export and import back to CAESES to verify the colors are there? Cheers, Heinrich
  24. Praveen started following CAESES to ANSYS Workbench Boundary Colors Issue
  25. Praveen
    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?
  26. Dennis W Dennis W joined the community
  27. Alex
    hello to everyone, i am trying to make a code to extract point from multiple frames and translate these to x,y,z coordinates. the first thing that i tried is to use the connect window and then use as input file my python code and as input geometry my multiple frames but it doesn't work. does anyone have any tips for me?
  28. Omer Omer joined the community
  29. Piero Favero
    Yes, sure! This was working! Now I went around the issue, so I don't really need support to sort it out. I would just like to understand if there is some specific case in which you cannot do something like: a = a + b Or if this is always allowed. function lininterpolSAC (Farray2D<double> SAC, double point_x, integer pos) : double integer i(0) double interpolatedvalue () if (point_x != 0) While (SAC.at(i , 0) <= point_x) i = i + 1 endwhile Else i = 1 Endif interpolatedvalue = SAC.at(i-1, pos) + (point_x - SAC.at(i - 1, 0)) / (SAC.at(i, 0) - SAC.at(i - 1, 0)) * (SAC.at(i, pos) - SAC.at(i-1, pos)) return (interpolatedvalue) Endfunction Thank you!!
  30. Praveen
    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.
  31. Ceyhan Erdem
    Hi Praveen, Please revise the tutorial for the ACT Connection. Within the mentioned document, it should clearly mention that, if SpaceClaim is your default geometry editor you beforehand have to open SpaceClaim and under options unselect the option "Use SpaceClaim Color Tones". Once this little procedure is completed, you can create and start the ACT procedure. Also, as mentioned within the tutorial, if SpaceClaim is your default geometry editor, please do not forget to assign a color to your BREp geometries. This will serve as named selection/s assigned to your domains. Cheers Ceyhan
  32. Mr. Heinrich von Zadow started following Difference between i=i+1 and i+=1
  33. Mr. Heinrich von Zadow
    Hi Piero, that should definitely work. My best guess is that the problem arises somewhere else in you feature. Could you post the complete Feature definition? Cheers, HEinrich
  34. Praveen started following Geometry not transfering to Ansys workbench
  35. Praveen
    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
  36. Piero Favero
    I have a While loop where an index i needs to be incremented by 1 at each loop. I used the notation i=i+1 as like more this clear notation. Funny enough the loop worked fine for some days but since today my index i refuses to increment (!!!) and the loop iterates endlessly. I know it's weird, but I am sure. it worked fine until this morning!! I didn't touch this function at all! I replaced i=i+1 with: i+=1 and now it works 😞 😞 I also noted that within the same function, since today, another instruction i=1 was systematically ignored and i remained at 0. Just a code like: i=1 echo ("i = " +i) would return i=0 😞 😞 For a while I got the feeling that in-place operations did not work with features programming. or they worked "when they wanted". But today, in the same feature, I tested: Fdouble test (0) test = test + 2 test = test * 2 echo ("test = " + test) and I got a nice 4.... So how come i=i+1 does not work? Thanks! Piero
  37. Ceyhan Erdem
    Hi TomasJ, Please use the attached ACT App. This is an updated version for Ansys 2024R2. Cheers Ceyhan CAESES_Workbench_App_23_09_2024_v2.wbex
  38. Praveen
    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
  39. Praveen
    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)
  40. Carl Benz
    Hi Fan, I hope you could find a way to build a periodic flow domain. The segments of the geometry are part in all our samples about fans, propellers and other rotating blades. As the boundary surface creation is dependend on the use case and as some meshing software finds its own periodic surface, we do not worked out THE "best practice" method for creating such a surface. I attached the axial-fan-sample with an extended boundary surface, which is hopefully what you were looking for. Best, Carl axialfan_extBoundarySurface.cdb
  41. Carl Benz
    Hi Chris, Sorry for the late response! Could you resolve the issue already? It seems that there is/was a problem by your graphics driver, which needs to support OpenGL. How is your setup, could you resolve it already? Best, Carl
  42. Mr. Heinrich von Zadow
    Hi WX, have you been able to resolve the issue in the meantime? Does it start the allrun script from within CAESES and have you set up any result values or files such that CAESES would know what to look for and when to consider the computation finished? Cheers, Heinrich
  43. robinoliver
    I need it too
  1. Load more activity
×
×
  • Create New...