Carl Benz

Hi, CAESES locks academic projects to not beeing used commercially. Best, Carl

Hi Alex, See Best, Carl

Hi Alex, If you need to use a sectionGroup as source you can access the sections via .getSections(). But a section of a section group is no smooth curve, it is of type FOffset wich is in principle a polyline. And a polyline holds a number of points you can access by .getData() . To go through these points: objectlist seclist(secgroup.getSections()) # put sections in a list foreach(foffset sec in seclist) # looking for each element of type foffset inside seclist objectlist veclist(sec.getData()) # put point data (fvector3) into a list foreach(fvector3 pos in veclist) # go through point data file.writeLine(\ pos.getX().toString("f",5) + "\t" + \ pos.getY().toString("f",5) + "\t" + \ pos.getZ().toString("f",5)) endfor endfor Please check out the type documentation in CAESES to understand the different types. What is the source of your frames? Maybe there is a more elegant way to get data from you geometry. Best, Carl

Hi Fan, I hope you could find a way to build a periodic flow domain. The segments of the geometry are part in all our samples about fans, propellers and other rotating blades. As the boundary surface creation is dependend on the use case and as some meshing software finds its own periodic surface, we do not worked out THE "best practice" method for creating such a surface. I attached the axial-fan-sample with an extended boundary surface, which is hopefully what you were looking for. Best, Carl axialfan_extBoundarySurface.cdb

Hi Chris, Sorry for the late response! Could you resolve the issue already? It seems that there is/was a problem by your graphics driver, which needs to support OpenGL. How is your setup, could you resolve it already? Best, Carl

Hi Ruhanii, You are right, it is not discussed and not included in the samples. The raw creation of a flow domain for fan like geometries in caeses is usally based on these general steps: creation of a boundary surface between two blades rotate this surface accordingly to the number of blades to get a periodic sector (at the sample axial fan, a sector of the fan is created somehow similar) create the faces at shroud and hub radius (e.g. using surface of revolution, or cutting images from existing hub and shroud surfaces (take care of the edges!)) create a Brep and close planar faces to build a solid (extend and trim surfaces, if needed) build a solid from the blade to cut out the blade from the flow domain (both flow domain and fan need to be a solid (closed Brep)) color the faces during brep operations to give them labels A more complex and advanced example for an impeller pump is provided here. There, the flow domain is build via feature definition. Hope that gives you some inspiration. Best Carl

Hello Yasin, As you asked at the helpdesk as well - here the answer public for everyone. Sometimes it can happen, that the license stuck on a PC/Node. For this case, you can release the license on your own: Best, Carl

Hi Yuvrai, The sobol you would like to run, needs to be called in the fsc script as well. Insert below the exports |<NameOfDesignEngine>.run() , e.g. |sobol1.run() . If you use the auto generation of fsc scripts in CAESES only the current state of the project will be implemented (1st open project file, 2nd set design variables). All actions you want to be done additionally you need to add into the script manually. But the lines added in the fsc are only called once. So if you want to export each design geometry of a design engine you need to use a software connector instead. best, Carl

Hi CJ, the Brep-Operation "faces from planar curves" is not working, if the source curve is not planar. If you close the deck edge without extrusion the source curve can be seen as planar within the given tolerance. If you extrude to y=0 it will simply add a line parallel to the y axis at the start and end point. You get a non-planar loop. You could try closing the deck by using the operation "extrude edges to plane": Best, Carl

Hi Carlos, Sorry, for the late response. There are two documents available at the installation folder at CAESES5\tools\sshResourceManager\doc. The admin guide for installation and administration and the quick guide for setting up your ressources. Best, Carl

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, I moved your question here, because it is more related to this topic. You have two possibilities to change the domain: A: Add an Operation to your surface (Operation -> More -> Domain) B: Create an ImageSurface of your NURBS surface. To reverse the direction, simply change from [0,1] to [1,0]. You can also swap the domain (u->v / v->u). But be careful with to order of doing it. Cheers, Carl

Hi Carlos, you get the message about not influenced evaluations, because you called a sobol to minimize the parameter eval_rt. As a sobol is only a randomized design engine and no optimization algorithm, the message is true and informing. If you click "Yes", it will simply run the sobol. If you don't want to get this message you have to set the objective to "observer" (default). I can't reproduce your simulation, because of the .sim file, which is only referenced and not attached in your project. But the reference itself is not set correctly. If you want to call the .sim file for each design inside the results directory (as you set in the argument section of you computation) you simply need to empty the string of the "Save directory". Then CAESES copies the file from "Filename"-location to "Save directory" which is always relative to the design folder. PS: To test, if a software connection has all inputs (referenced or edited files) needed to be ready for any design engine, it is helpful to delete the "manual_results/baseline/<connection>" folder (or make a backup if you think you need it) and let CAESES do the job. If any file is missing (or wrong referenced), you will notice. Best, Carl

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