Jump to content

Mr. Heinrich von Zadow

Moderators
  • Content Count

    194
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Mr. Heinrich von Zadow

  1. Hi CJ, you can set constraints to your computation. If violated, the computation will not be executed. Of course, this only works if the constraint can actually be evaluated before the CFD ran. Cheers, Heinrich
  2. Hi CJ, this question is a bit unusual. Maybe if you explain why you want only specific variants out of a Sobol I can try and come up with a better way to approach your problem. Technically though: you can select specific variants, export them as csv from the table and then use a Design Assembler (which allows to import said csv again). Cheers, Heinrich
  3. Hi CJ, if you check the documentation for "units" you should find this: Cheers, Heinrich
  4. Hi Furkan, if you have set the constraints in the Design Engine, the algorithm predicts an optimum within the feasible domain. However, predicting constraints (which is technically the same as predicting objectives) comees with uncertainty and hence, sometimes none of the predicted optimal designs is actually feasible. What might help is, to set a narrower margin in the Design Engine and try again. Cheers, Heinrich
  5. Hi Furkan, If you set up a "Response Surface Optimization" and choose to "use result pool", a surroate will be created (if your pool is large enough, otherwise samples will be added first). An optimization on that surrogate is performed automatically in the background (a Genetic Algorithm is used here) and the optimal candidate (or multiple if you choose so for a multi-objective problem) is returned. The design you see created in CAESES is therefore either an additional sample or already the potential optimum. Check the dakota.out file in your design directory to see the details. Also, the finaldata file will show you the predicted performance of the optimum... If you keep this Algorithm running, the actual (CFD) result(s) of the optimum-candidate(s) will be added to the pool for the next iteration and the process repeats. Cheers, Heinrich
  6. Hi Yukai, yes, both will start a new run counting the designs from desing0000 and onwards. It's just that in case 1: the designs (in terms of values of the design variables) that are created are the exact same you would have seen if your initial Sobol ran through. In case 2 things will start from the beginning again, but the designs you have already run a CFD for will be linked instead of re-run. You can just grab an easy and fast example (e.g. the Jumper Sample) and play around a little to get familiar. Cheers, Heinrich
  7. Hi Sisi, just a quick comment on that: the propeller object (type FPropeller in CAESES) does not support an actual tip. It is a type ment specifically to work with the PFF format (and be exported as such). If you want a closed, solid geometry including a tip checking out the sample mentioned by Andreas is the right way. Cheers, Heinrich
  8. Hi Yukai, There are 2 options in your case: 1. Set the Sequence Start Index of the Sobol to 10 (or wherever it stopped the first time) so that it does not start from the beginning when you run it the second time. 2. Select the result pool from the first run when starting the second one. This way, the results will be linked and the CFD is not re-run. Cheers, Heinrich
  9. Hi Ramond, the project shown in the first post cannot be shared publicly, unfortunately. I am happy to provide some guidance and assistance if one of you wants to take on a similar task. Cheers, Heinrich
  10. Hi Joshua, if you want to change the positioning, number, shape and size of the holes shown in your screenshot I would indeed recommend, to re-model this part from scratch instead of morphing/deforming/shifting it... I guess I'd start with a bare tube (i.e. a circle which you use in a BRep and extrude it) and then a parametric (in number, positioning, shape, size etc.) description for the holes (which I would create via a boolean operation). I just created a very simple example for you to explain the basic process, hope this helps to get you started. Cheers, Heinrich demoTubeWithHoles.cdb
  11. Hi there, unfortunately the project you are referring to cannot be shared publicly. However, if you have a fixed blade geometry and want to investigate a variation of the cooling channels, a model can probably be set up quite easily. If you have something to work with, feel free to share it here and I'll take a look. Cheers, Heinrich
  12. Hi Susan, I don't have any experience with Sesam, but I'll assume it depends on (any number of) input files and input geometry and after running the tool in batch mode there will be (again, any number of) results files. If that is the case, the connection through the Software Connector should be basically the same, as any other. I recommend you start by looking at the respective Tutorials (e.g. Jumper, StarCCM+). Cheers, Heinrich
  13. Hi CJ, sounds like CAESES is waiting for StarCCM+ to return the results files. You can either follow the output in the CAESES Task Monitor, or navigate to the current design directory (if you manually execute the connector this would be .../manual_results/baseline/Runner) and see what's happening in there. Basically, the directory should include everything you need to run the external computation. Just give it a try and make sure it is working (by manually calling the script or StarCCM+ with the corresponding macro inside that directory). Once you have confirmed the computation runs independent of CAESES, you can come back and trouble shoot the connection set-up in CAESES. Cheers, Heinrich
  14. Hi Ail, there should be a generic integration of external tools into heeds that is based on running the external tool in batch mode via a script. CAESES wise things look good -- by changing the values in your fsc file you willl be able to create different geometry variants. You will probably need to define an export, though. How to actually trigger thigs from HEEDS' side is probaby a question their support can help you with. Btw: from the fsc file you attached, I take it that you still run a very old CAESES 4 installation -- I hihly recommend you to upgrade to the latest 5.x. Cheers, Heinrich
  15. Hi Susan, If you use this method "smooth joint to stem" for the selected surface in your screen shot you will have to make sure the adjacent surface is defined such that it results in the same shape along the joint edge (possibly you will also want continuity accross the edge -- that would be another thing to keep in mind). What about you trim the upper surface and extend the lower one all the way to the max height? BTW: Which version of CAESES are you working with? Looks like a 4.x to me. I definitely recommend to update to the latest 5.2.4 -- there is years of development in between them. Cheers, Heinrich
  16. Hi Susan, I'd recommedn to start with these: (they are part of any CAESES installation)
  17. There is plenty of material. Have you had a look into the documentation?
  18. That sounds like a good start. I'd start importing it and look into partially parametric modelling techniques. BRep morphing, Free Form Deformations, Delta Shifts all work well in different areas of hull design. If you have specific questions regarding particular shape variations, feel free to ask. A lot also depends on constraints and the objective of your optimization problem.
  19. Hi Susan, do you have something to start with (an existing CAD file, hull lines, etc.)?
  20. Hi Gustaf (sorry for misspelling your name repeatedly!), with .getmax(2,true) you can return the max value along the z-axis of a curve (the "true" will return the parameter position of that max value, instead of the value itself). This parameter can now be used again, to acces the position of the curve at that parameter with .getPos() This should be what you need -- see attached project again for your specific example. planing_hull_v03.cdb
  21. Hi Gustav, well, that's the x-value 😉 See attached project... Cheers, Heinrich planing_hull_v03.cdb
  22. Hi Gustav, in your case you would have to us p2:z as elevation for the fv command: point p1(curve.fv(2,p2:z)) let me know if this explains it -- otherwise feel free to attach your particular example and I'll quickly modify it. Cheers, Heinrich
×
×
  • Create New...