Leaderboard

Hi Thomas, Your code seems to work fine and sets the knot vector correctly for the b-spline curve. However, the display field of double series attributes in feature definitions has a small bug. So to see the values of the knotVector doubleseries you can drag and drop the "knotVector" into the console field and press enter. Cheers, Hedi

Hi CJ, if you check the documentation for "units" you should find this: Cheers, Heinrich

Hi, you can select the option "Response Surface Optimization in the Optimization workspace. Afterwards, you can check the option "Use Result Pool" It will ask you to select the pools which you want to utilize for the surrogate based optimization after starting the design engine. Please note that if you do not have sufficient samples in your result pool, it will do additional samples before starting the optimization. It will then perform the optimization on the surrogate in the background without calling CFD. After that, a new design will show up in CAESES, which is then evaluated using the CFD to check if it matches the prediction from the surrogate.

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

HI everyone， I'm having a hard time. I created the blades and tips. As shown in Fig. However, when I create the propeller with Model-propeller-propller, I only get incomplete blades. The tips were not created together. This is shown in the image below. Also, due to the language, I may have a problem with the description not being clear, so please forgive me. Looking forward to your answer. prop_para.cdbc

Hi CJ Coll, I edited the feature so that the labels are not on top of each other anymore and the points are removed inside the profile view. You can find the edited linesplan feature attached to this reply. To toggle the visibilty of the orientation points from the group section curves, you can use the command .setShowOrientation(true/false). If you want to further edit the feature yourself, you can access the it in your CAESES installation directory under "CAESES...\etc\features\features\Maritime". To add a line that follows the topdeck, my solution was to create an image curve from the hull's surface/brep upper edge. I hope that solves your problem. If not, don't hesitate to ask. Linesplan_edited.fde

Hi Furkan, at the computation object, there is an option to set a list of constraints. If one of these constraints is violated, the computation will not be executed for that design. Cheers, Mattia

Hi Yukai, The force in the last line is the converged value from the solver. I would suggest to use a python code only for post-processing. For example, if you want to plot the convergence history of the forces over OpenFOAM iterations. By parsing various values, such as force in x-axis to parameters and establishing a robust integration CAESES with OpenFOAM, then you can continue with a Design of Experiments and/ or with a Optimization process. Best Regards, Andreas

Hi Yukai, OpenFOAM is notably complex when it comes to managing numerous processed files. To address this complexity, I've included a screenshot featuring a standard connection input file, geometries, output files, and corresponding values. It's advisable to consistently employ relative paths by utilizing the subfolder option, as illustrated in the second screenshot. To extract parameters from the force.dat file, you can directly navigate to the last line, which typically represents the converged value from OpenFOAM. This can be achieved using the -1 option in the command line. Moreover, consider incorporating a Python file for post-processing and integrating it into your connection. This can be facilitated by incorporating the Python script as a command line within the Allrun.sh executable file. Best Regards, Andreas

Hi Carlos, In principle you are right. The SSH Resource Manager is part of the "entire functionality of CAESES". However, due to the low demand and the current revision of that piece of software, we only grant access on request. So please write your demand via email at license@friendship-systems.com with a short explanation on what you want to achieve with it. And please remind: "CAESES® must be installed on a personal PC/notebook rather than on University computers." "By granting you this free license we expect you to send us a summary report of the work that you have accomplished with CAESES® or a PDF copy of your thesis if applicable." Best, Carl

Hi CJ, from visual diagnostic, it looks like a misplaced point - maybe a sign error or a bad dependency? Actually It depends on how you set up the keel line, especially the point or curve, which is going crazy. You can take a deeper look at the faulty design(s) by double clicking on it at the Result Table, or below the Object Tree at the Optimize workspace. BUT only apply changes the baseline design - every change you make inside an other design than the baseline, will not be considered for further design engines - these are always based on the baseline. But you can try out solutions by unlocking the design -> Search for your keel line and its sources. You can check the dependencies of the problematic curve. Right click on the object inside the Object Tree and select "Show Dependencies" - at the upper left corner of the Dependencies window you can switch "Show Clients" or "Show Supplier". Hope that helps, Best, Carl

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

Hi CJ, I guess I would just create a planar BRep intersection (BRep-based curves) and from this get the area. See attached project... Cheers, Heinrich fishingVessel.cdb

Hi Carlos, unfortunately, I cannot give you any hints regarding the integration of the .jar libraries in CAESES. Generally, a typical approach would be to - keep the setup (*.jar / *.java) on the cluster separate from CAESES. - just create a text file with all variables to be edited by CAESES and write that to the cluster. - Use a bash wrapper similar to the attached example for SLURM to fetch the setup and launch the runs. This script is called from the CAESES software connector. It is important that the bash script stays alive as long as the run in active as CAESES will be monitoring it and look for the results as soon as it ends. Hope this helps. Cheers, Hannes slurmExample.tar.gz

Hi Carlos, Yes. A student license includes the complete functionality of CAESES. See https://www.caeses.com/products/caeses/editions/#students . Cheers, Carl

Hi Carlos, please use a personal message (click on my profile -> message). Out of your last question about starting CAESES in Baseline or in designOfExperiments I assume, that you made a lot of work not with the baseline design. For CAESES each design is its own instance, and they are not connected with each other. So if you doubleclick on a design from a design engine the name of the design on top of the objecteditor gets a green background with a (by default) closed lock. For sure you can make some changes by unlocking the design, but as I said already it will not infect the baseline design. As any design engine starts from the baseline design, this might be the cause for the original issue you reported. If you want to continue working on a specific design from a design engine, you need to make it the baseline-design first: Go inside the design you want to make baseline (doubleclick -> green bar) and "Save Current Design As" a new clean project (without results from the previous design engines). I hope this helps. Best, Carl

Hi Carlos, Please make sure, that you have created an evaluation parameter which takes a value from a result file (@ 5:00 of the video tutorial) and make sure that you have set this parameter as an evaluation in the sobol settings (@6:54). If the parameter has a fix value and no reference like: Runner.getResults().getTable("cd.csv").getElementAt("cd") you may get the Message "There are evaluations that are not influenced by any design variable.". CAESES checks every dependency before running software-connections in an optimization algorithm. It is to save resources. If there is no reference to any value from a resulting file of a software-connection, this application will not be executed. Best, Carl

Hi Carlos, there are two ways to do that: 1) You could write a script that sends the computation to the cluster, waits until it is finished and copies the result back. You can run this as a local computation on your workstation where CAESES is installed. 2) You can install CAESES in your cluster, there is a CRT version, that does not require a GUI (CAESES runs in batch mode). Then you can start design engine runs from the command line. Note, that you have to set up an appropriate software connector before, e.g. if you use a resource manager to submit the computations you need a script that submits the job and waits for the result to come back. Best regards, Hedi

Hi Carlos, the SSH Resource manager is an addon to CAESES which has to be purchased separately. After purchase, the SSH Resource Manager Server must be installed on a host in your network, e.g. the cluster main node. If you have installed this already, please ask your network manager where it is installed. Best regards, Hedi

Please insert a reasonable knotspacing value in the BRep and datareduction afterthe transformation. The transformation might otherwise rip the geometry apart, since it moves the control points of the vessels representation. In the flat of bottom area there might be only a few and that needs to be refined. Cheers Claus

The model is unfortunately very bad. There are big gaps between several surfaces. I will see if I can find a repaired one. Best Regards Claus

Hello, Lately, I’ve been trying to run CAESES coupled with StarCCM+ in batch mode for Linux. Checking previous discussions, is it possible to reactivate again for downloading the zip file with the example on how to run CAESES in batch mode? and if you have suggestion please feel free to tell me Thanks in advance, Best, Nuttarat

Sorry Christina, if you set up the linesplan, you can export the feature to IGS, that will write out the lines as curves, but not the label.