Jump to content

Mr. Heinrich von Zadow

Moderators
  • Content Count

    199
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Mr. Heinrich von Zadow

  1. Dear Solehah, we are awaiting your response on the Ticket you opened. Cheers, Heinrich
  2. Dear Aina, I am happy to take a look but would need the project file and/or the exported IGES you mentioned. From the screenshot it looks as if your geometry is not fully watertight -- that might be a starting point for investigation. Furthermore, the displacement calculation is based on the triangulation settings -- the coarser, the larger the error. But typically the deviations here are not as large as you experienced them. Finally, if you calculate displacement at a certain draft, heel and trim, the order of transformations and the origin you choose may drastically impact the result. I don't know about Numeca, but in CAESES we transform in the order heel, trim, draft and use [0,0,0] as default origin. You can also specify otherwise by using the .getDisplacementOrigin() command. Kind regards, Heinrich
  3. Dear Aina, typically the absolute path to your FineMarine installation followed by a space (" ") and the path to the *.sim file should work. Just check it manually in a terminal window. Best regards, Heinrich
  4. Dear Lixing, The questions you are asking are explained in detail in the type documentation -- just click the icon left of the name of your blade. Also note, that you can choose between different options for the representation of skew and pitch: Best regards, Heinrich
  5. Dear Solehah, thanks for preparing the file. Here's a few comments: 1. I can see that you have a number of individual Trimesh Parts. None of them has a color. Typically what you would want is a watertight geometry of the domain with the individual patches colored (the color names will be exported as the names of your boundary conditions). I recommend you color the individual parts and join them together in a single Trimesh like this: 2. Make sure to reference to the exported geometry in your sim scripts (maybe I just overlookerd it, but I could not find the file names you used for the exports in there. Lines 8-9 in your existingShip.iec file don't look good. 3. Your Connector runs the local Application FineMarine without any additional arguments. I imagine that you either need to specify the sim file as argument or, alternatively come up with a batch file that takes care of running things. 4. If you want to have parameters for certain inputs you will need to assign them to your configuration (i.e. drag & drop): I'll leave it at that for now. If you still run into trouble, I highly recommend you follow through a few tutorials on the subject. The procedure is always very similar. Best regards, Heinrich
  6. Dear Solehah, since this is a forum, I'd would like to ask if you can provide a (possibly simplified) version of your project that you are willing to share with other users? This way we can create a knowledgebase that allows the entire CAESES community to benefit. Best regards, Heinrich
  7. Dear Latoya, thanks a lot for the flowers! Cheers, Heinrich
  8. Dear Solehah, you can refer to the provided tutorials on software connection. The basic principles are always very similar. After you have tested things manually you should know what geometry is needed and in which format. My guess is a colored STL of half the domain with the ship substracted from the domain at roughly the right floating condition. Extra care needs to be take to account for triangular patches as I mentioned in my first post. If you want CAESES to read in pictures generated from Numeca (or any other tool in your chain), PNG works fine. You will want to run Numeca in batch mode to avoid the GUI showing up. Best regards, Heinrich
  9. Dear Solehah, at least I can't see anything that's obviously wrong from the screen shots. If you have an STL I would recommend that you start by setting everything up in Numeca (completely independent from CAESES). Once things are meshing and running/converging the way you want them to, you can go back to testing the CAESES integration. This way it's easier to know where to trouble shoot... Cheers, Heinrich
  10. Hi Gustaf, you can adjust the zoom direction in menu > setting > appearance: Best regards Heinrich
  11. Dear Solehah, A Mesh Engine will only allow you to generate surfaces meshes as you would need them for potential flow simulations i.e. for wave making resistance. To run ranse CFD in Fine/Marine you would need to use their HEXPRESS grid generator and supply the flow domain as an STL. Best regards Heinrich
  12. Dear Aina, it seems that you have not selected any points for the 3 transformations that you have prepared. I attached a small demo of how that's done as well as the modified project. FFDbulb_editPoints.apng Best regards Heinrich freeformdeformationbulb_HvZ.cdb
  13. Dear Aina, have you checked my suggestions from above? If this does not help, feel free to attach the project here and I am happy to take a quick look. Best regards Heinrich
  14. Dear Rizuan, yes, indeed -- an image surface will always be an image of only one individual surface. You can wrap multiple surfaces into a surface group. An image surface group would then allow you to transform all of them at once. Alternatively, you can use a BRep which also accepts transformations and can have multiple sources. Best regards, Heinrich
  15. Hi Osman, you can use a parameters to define the bounds and design variables to scale in-between. See attached example. Cheers, Heinrich parameterScaling.cdb
  16. Hi Carlos, we don't ship anything readily with CAESES but maybe you can start off from an imported geometry -- something like a standard test case (KVLCC2 or similar) and then apply partially parametric modelling techniques such as Free From Deformations or BRep Morphing to vary the shape. Best regards, Heinrich
  17. Dear Kala, I recommend you take a look a the design velocities to understand how a certain design variable impacts the shape. On our channel you can find a video that explains the concept: https://watch.caeses.com/w/tvEDgJu9ThsVZPPDUTCiJJ Cheers, Heinrich
  18. Hi Rizuan, very good. FINE and CAESES are well known combination so hopefully it will be 'smooth sailing'... Cheers, Heinrich
  19. Hi Rizuan, the important thing to note is, that CAESES itself does not offer any sort of CFD computations. If you want to calculate the total resistance Rt you need to connect CAESES to a CFD solver of your choice through the Software Connector. Which CFD code do you typically use or have licenses available for? Best regards, Heinrich
  20. Hi Rizuan, I recommend you start by looking through the tutorials and samples related to hull design. Which software are you planning to use for CFD? Best regards, Heinrich
  21. Dear Milad, If I understand correctly, then yes, that is perfectly normal. The 2000 LHS samples is what you use to train the model. If you'd evaluate your model at these exact points, the prediction would perfectly match the training data (at least for Kriging that is the case). However, the model cannot just predict a pareto front "out of the blue". Usually, what we do is, to run a MOGA (multi objective genetic algorithm) optimization on the model. With large enough populations sizes and number of generations this allows to quickly find pareto-optimal designs (that means that for those designs there is not other designs better in one objective without being worse in an other objective). Best regards, Heinrich
  22. Dear Yuwen, the code is not that straight forward to explain. Mostly it's sine/cosine distribution functions, but there are quite a few additions here and there. Would you not rather need a topology like outlined in the attached project, anyway? Cheers, Heinrich gridDemo.cdb
  23. Dear Yuwen, I'd have to ask a developer to take a look into the code to answer that question. However, I think it might be enough for you to know that the distribution (if not set to be uniform) is dependent on the parametrization of the underlying surface. Hence, by parametrizing the surface differently, you can freely control the distribution of cells. Cheers, Heinrich
  24. What exactly did you do when "running Dakota". Did you run an optimization or just calculated one set of pareto designs? Could it be that the blue dots in the second plot are additional samples that where generated before the generation of the first Surrogate?
  25. Hi Milad, I am not quite sure if I understand the question. You mean that out of the 2000 LHS samples only a few are shown after you have calculated the pareto designs? Do you create the plots in Excel and add the pareto designs from the finaldata file? Cheers, Heinrich
×
×
  • Create New...