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. gemwinhostt gemwinhostt joined the community
  3. hrudenw24 hrudenw24 joined the community
  4. Yesterday
  5. Mr. Heinrich von Zadow started following Surrogate Assisted Optimization
  6. Mr. Heinrich von Zadow
    Hi Adrian, but can't you just open the project in CAESES and adjust the boundaries of your LHS sampling algorithm in the GUI? You can then still run the project in batch mode for the generation of the designs... Or do you do the sampling (i.e. LHS) through a method within your python setup? I'm asking, because CAESES does also provide LHS sampling... Also, instead of sampling a large design space and then another one in a second iteration, you could use the adaptive sampling method within CAESES. This will automatically start with a LHS and then switch to an adaptive mode based on uncertainty quantification or other criteria. You can check the documentation for an example on how to run CAESES in batch mode. Cheers Heinrich
  7. adrian.portillo.juan
    Dear community: I am working on the optimization of tip-raked propellers for hydro-acoustics. To do so I have parameterized the tip rake of a propeller based on the tip rake value and a geometrical parameter named "p" that accounts for the curvature of the rake distribution curve. Now, I have built my first population of geometries based on LHS sampling. With that population (200 models) I have built a surrogate. However, now I want to refine the reduced order model by building a new population closer to the optimum point. To do so I am trying to call the project fsc script with python and modify the tip rake and p parameter bounds. However, when I start scripting in python I do not manage to even open the project with CAESES from a python script. Can someone help? Find atached both the project script and the project file. Thank you! 🙂 P.S: I need to do it from python scripts instead of directly in CAESES mainly because I need to do some processes outside CAESES and also because I will work in a batch environment (HPC) CAESES_CLT_OPT_v2.cdbc script_trial.fsc
  8. Last week
  9. 33betgamess 33betgamess joined the community
  10. crown88cooll crown88cooll joined the community
  11. one88ios one88ios joined the community
  12. vnbet77vipp vnbet77vipp joined the community
  13. Earlier
  14. scoppfalki scoppfalki joined the community
  15. vanceloma vanceloma joined the community
  16. polyrix
    If you're facing importing problems in general 3D modeling, especially when dealing with large or complex industrial models, the issue often comes down to data accuracy, format compatibility, or incomplete geometry. One effective way to minimize such issues is to start with clean, high-resolution scan data. That’s where 3D laser scanning industrial solutions come into play. By capturing precise measurements and detailed geometries from real-world objects or environments, 3D laser scanning ensures your base models are accurate and import-ready—reducing the need for manual corrections later. A trusted name in this space is Polyrix Inc, known for delivering advanced 3D laser scanning systems tailored for industrial applications. Their solutions help generate clean, standardized data that integrates easily into most CAD and modeling software, helping professionals avoid common import and compatibility issues. In short, when you're struggling with model imports, consider whether the source data is the root of the problem—and whether a reliable partner like Polyrix Inc can help by offering high-quality 3D laser scanning for industrial use.
  17. polyrix polyrix joined the community
  18. elkninoissy elkninoissy joined the community
  19. Andreas Arapakopoulos started following Error message: failed to extend given source curve
  20. Andreas Arapakopoulos
    Hey Luca, Sorry for the late response. Please find attached the CAESES project, which includes the proper import of the E817 profile as a text file, along with its parametrization. The project also contains some parametric distributions for the blade geometry, which you are free to modify based on your preferences. There is currently a minor issue with importing profiles in CAESES, which we are working on. For now, the profile dat file needs to be formatted in the specific way shown in the attached file to be read correctly. Please let me know if this works for you. Best Regards, Andreas E817 blade.cdbc output-onlinetools.txt
  21. Sody
    Thanks Heinrich, I agree that no setting of seed is a problem. I will rember to be careful if I need to generate random number with rand().
  22. carsten.fuetterer@friendship-systems.com
    Hi Adam, can you upload the project? Cheers Carsten
  23. carsten.fuetterer@friendship-systems.com
    Hi Adam, yes that should work. But it could be that small adjustments need to be done. Best regards Carsten
  24. Mr. Heinrich von Zadow started following Fuction rand() generates not-really-random values
  25. Mr. Heinrich von Zadow
    Hi Sody, I think one should be careful when using the rand() function in a persistent feature. It seems to remember a fixed seed somehow. If you do not create a persistant feature instance in your project, but rather just transiently execute the definition repeatedly it should behave as expected. Cheers, Heinrich
  26. Sody started following Fuction rand() generates not-really-random values
  27. Sody
    Hi, I am a new user following the tutorials step by step. I have tried the Case-by-Case Analysis , and I doubted about the values generated by the function rand(). So I slightly changed the code as shown below to show the exact random number. double value_base(rand()*100) integer value(value_base.toUInt()) integer difference(abs(value - try)) echo(" ") echo("Random number is " + value_base) echo("My try is " + try) if (difference == 0) echo("congratulations, you are spot on!") else echo("No, that was not the number.") echo("The number I was thinking of was " + value) endif The feature runs OK. The result is showed in terminal like: I kept testing this feature with input "try" from 1 to 40, and collect the random number generated. They are like: try Random number try Random number try Random number try Random number try Random number 1 80.8741 2 80.8741 3 58.5009 4 80.8741 5 89.5962 6 19.3304 7 56.3585 8 47.9873 9 58.5009 10 19.3304 11 0.125126 12 58.5009 13 35.0291 14 47.9873 15 19.3304 16 19.3304 17 56.3585 18 80.8741 19 0.125126 20 19.3304 21 80.8741 22 47.9873 23 35.0291 24 19.3304 25 58.5009 26 80.8741 27 89.5962 28 56.3585 29 80.8741 30 58.5009 31 58.5009 32 47.9873 33 58.5009 34 80.8741 35 89.5962 36 58.5009 37 47.9873 38 82.284 39 80.8741 40 19.3304 Obviously some values were repeatedly generated, as shown in colors above, and the values were not uniformly distributed. My OS is Windows 11, and my caeses version is 5.3.4 . I am not sure if I used the function rand() properly. Could someone tell me what is wrong here? complete console output.txt
  28. Luca
    Hi Hedi, of course.E817 blade (not working).cdbcoutput-onlinetools.txt
  29. Simon Hauschulz
    Hi Adrian, you can achieve this with the operation "Boolean|solid from intersections". Additionally to the blade and hub geometry, you need is a surface that trims the blade at the desired radius. To create the whole propeller, I then use the periodic pattern operation. Take a look at the attached project and please let me know if you have any questions. Best regards, Simon CAESES_CLT_OPT_v1.cdbc
  30. adrian.portillo.juan
    Dear community: I am working on a parameterized model of a Contracted Tip Loaded Propeller (CLT-Propeller), with the aim of performing a multi-objective optimization study. To do so, I need to generate a closed surface. However, I am experiencing problems to close the blades and fillet the joints with the hub. The thing is I cannot use the tip feature to close this geometry, I need to close it as if I was closing the "hole" given by the last section in Rhinoceros. I don't know if this example is clarifying but basically as if it was for a ducted propeller. If anyone can help that would be amazing. Find attached the project. Best regards: Adrian CAESES_CLT_OPT.cdbc
  31. Adam
    I am stuggling with a similar issue with the response surface. Is there a rough guidance on how many CFD samples would be needed to begin the iterations without CFD? I have 6 variables with 2 evaluations and am currently on 60 samples all with full CFD runs.
  32. Adam started following CAESES to STARCCM+ connection
  33. Adam
    Hi, I am currently running in to a couple issues regarding the connection to STAR-CCM+ for optimisation. I have followed the tutorial guides and tried to troubleshoot on my own but with no success. When running the Java Macro/connector 1 in the connection tab, an error of not finding the part is returned, yet it is the same in the simulation file used for input files. An image of both have been shown below, please let me know if more information is needed from my side. Also, when attempting to select the data values in the results values. The values section is completely uneditable, im not able to select anything and it seems to be stuck, is there a way to zoom out here? Any help would be greatly appreciated Thanks Adam
  34. Hedi Boettcher started following Error message: failed to extend given source curve
  35. Hedi Boettcher
    Hi Luca, can you attach the CAESES project file and the profile data text file? Kind regards, Hedi
  36. Luca
    Hi, I was trying to import a profile into the advanced propeller workflow, but I keep getting this error message: Failed to extend the given source curve. I am trying to import an E817 profile as a text file and cannot seem to fix. Please help!
  37. Mr. Claus Abt started following Problems of design variables in the optimization of propeller and Question about continuity condition in free form deformation
  38. Mr. Claus Abt
    If you keep two layers fixed and move the third point in line of these two first points it will still be curvature continuous. If you move it out of the line you will only maintain tangency continuity. If you keep 3 layers untouched, you will keep curvature continuity. BTW please use CAESES 5 for your work, there is also documentation at https://docs.caeses.com
  39. Mr. Claus Abt
    HI Liuxuyang, Did you have a look into our propeller models? If you want to share your model we can give you some advice. You can send it to info [at] friendship-systems.com. Best Regards
  40. liuxuyang started following Problems of design variables in the optimization of propeller
  41. liuxuyang
    When parameterizing the propeller, I chose the Bezier curve. Now, for the camber, there are four control points. In CAESES, the x and y coordinates of each point need to be specified as specific values, which means there are eight design variables for one camber. With six important parameters of the propeller, it's equivalent to having 48 design variables. Is this too many for the optimization process? Are there any specific propeller optimization cases that I can learn from?
  42. Kazem
    Hi everybody, I am currently working on a project concerning the optimization of the sonar dome of DTMB (David Taylor Basin Model) 5415. I use free form deformation method to parameterized the geometry of sonar dome. I would like to know how continuity condition for this method in CAESES works (Tangent, Curvature and Position options). Unfortunately no documentation is available on the internet. It is greatly appreciated if anybody could help me understand the effect of the mentioned options. Best Regards, Kazem Reza-Asl
  43. Ceyhan Erdem started following Trying to import wing geometry into Fluent using the CAESES Addin
  44. Ceyhan Erdem
    Hi Alizakidd, Can you please provide me your Caeses project file, together with the fsc you are using? Please be sure that you are using the latest Ansys Workbench App provided within your Caeses installation folder; if you are using Windows and used the suggested path, it should be under "C:\Program Files (x86)\FRIENDSHIP-SYSTEMS\CAESES5\etc\integration\ansys" Cheers Ceyhan
  45. alizakidd
    Hello, I just finished creating the wing profile in the initial tutorial (FirstModelingSteps) and was trying to import it into Ansys Workbench to run a CFD simulation. I exported the project as an .fsc file as required by the add-in, but I am running into the following error: Update failed for the CAESES Geometry component in CAESES. User OnUpdate Callback Error:Local variable 'geoName' referenced before assignment. I have included the project file and a screenshot of the error message below. Could someone kindly point me in the right direction?
  46. Mr. Heinrich von Zadow
    Hi there, this looks like you are shifting control points too much (or maybe you are shifting them smoothly but accidentally left out a group of points that is just outside the range thereby folding the polygon in an unwanted manner). Try looking at the control polygon to get a better understanding of what went wrong. In addition, I highly recommend to update to the latest release. Cheers, Heinrich
  47. Adam
    This is perfect, thank you Heinrich! You have been great help Cheers Adam
  48. Mr. Heinrich von Zadow
    Hi Adam, that looks promising already. When combining everything, you need to distinguish between boolean operations and simply adding sources. I went through your model and corrected a few things -- mostly adding the domain faces one-by-one using individual "add sources" operations. While doing so, I colored each operation so that your inlet/outlet/periodics, etc are colored reliably. I did the same for the blade and extruded and closed it to obtain a closed solid (you don't want any open/red edges and your final BRep should be closed > you can tell it is closed from it's icon being filled with grey color). Then there is only one boolean operation: substracting the closed blade from the closed domain. Since the blade and tip are already colored, the colors will "imprint" onto your domain during that operation. Hope this helps. Cheers, Heinrich FAN4_HvZ.cdbc
  1. Load more activity
×
×
  • Create New...