Jump to content

Mr. Heinrich von Zadow

  • Content Count

  • Joined

  • Last visited

  • Days Won


Mr. Heinrich von Zadow last won the day on November 23

Mr. Heinrich von Zadow had the most liked content!

Community Reputation

7 Neutral

1 Follower

About Mr. Heinrich von Zadow

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2217 profile views
  1. 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
  2. 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
  3. 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
  4. 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
  5. Hi Susan, I'd recommedn to start with these: (they are part of any CAESES installation)
  6. There is plenty of material. Have you had a look into the documentation?
  7. 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.
  8. Hi Susan, do you have something to start with (an existing CAD file, hull lines, etc.)?
  9. 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
  10. Hi Gustav, well, that's the x-value 😉 See attached project... Cheers, Heinrich planing_hull_v03.cdb
  11. 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
  12. Hi Gustav, you could create a point through the console with: point p(curve.fv(2,zVal)) Instead of "curve" you'll have to choose your particular curve and zVal would be your z value. "2" corresponds to the z-axis (0=x, 1=y, 2=z).
  13. Hi Yukai, generally, during an optimization CAESES automatically changes Design Variables to create different shapes. Hence, you should see a change in the evaluations/objectives from your external computation. You can also create screen shots of the different variants and look at them (as well as post processing data) in the Design Viewer to compare different shapes. I recommend the Tutorial Basics/Geometry Variation and Asessment to get a good first insight. Best regards, Heinrich
  14. Hi Yukai, you can set the sub folder by adding it to the file name of your template like this: If you have an allrun script which you execute for each design this would normally be executed in the same location as your STL file is exported to. Hence, typically referring to it by its name instead of full path works. Alternatively, you could add an entry an specify a path with getResultsDir() to have it adjust dynamically... Cheers, Heinrich
  • Create New...