Leaderboard

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

Hi Adam, take a look at BReps -- they are the way to go when combining, uniting, substracting, etc. various parts of your geometry. For boudary conditions you can make use of colors (their names) which can be applied robustly even when topologiacal changes occur in the model during shape variation. You should be able to find everything to get started within the help menu of CAESES. Cheers, Heinrich

Hi Manoj, You can access the CAESES documentation in the Help section in the software CAESES. In the documentation you will find the "Fine Marine Pre-Processing" tutorial under Tutorials > Maritime > Software Connection > Fine Marine Pre-Processing. Cheers, Hedi

Hi Manoj, usually, you start with a working setup that is capable to be run from the command line. This is entirely FM-specific and outside of CAESES. In the current version of CAESES we provide a tutorial on the geometry preparation for FM, based on the Maritime Workflow introduced in CAESES 5.3. Assuming you've got the latest version of CAESES installed, you can find it here: http://localhost:65038/tutorials/maritime/software-connection/fine-marine-pre-processing . This geometry should be exported either as parasolid or as multibody stl. At this point the above-mentioned workflow comes in. Please identify all relevant input files and provide them from the software connector. Define case-specific values by parameters. Put the command you used to run the setup from the command line into "ExecutionSettings|Arguments" (possibly preceded by "bin/bash"). Run the case for one geometry from the software connector and define all relevant result files within the software connector for further post-processing. Hope this helps! Cheers, Hannes

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).

My doubt is actually not hard, but with the actualization i lose a feature i used to use. Here is the situation: I need to create some points on this curve and each point on the top has its correspondent on the bottom exactly on the same elevation in X axis. To do this i need to use the parameter witch corresponds to the elevation required, but in X axis the curve has 2 possible coordinates so that once i insert the function related to the creation of the point only one coordinate (on the top) is selected. Previously i could use "PointIntersection2D" and select a index, witch allowed me to choose any intersection the function would find. Here is an Image of the situation: The question is: is there any function or any oder way to select another index on the curve? P.S.: I could split the curve in two new curves, and repeat the steps, but i'd like to know if there is a solution like the feature i used to use.