KNL21

Hi again, I have a bit of a follow-up to this topic: I would like to export STL's using the STL (Extract Colors) functionality. To export with Cases, there must be a name given for "file name", which serves as a prefix for all of the STL's I am exporting by color. Is there a way to get rid of this prefix, and to only have the names given by color used for the STL's? For example, in the attached screenshot when I use the file name ".stl", geometries are exported with names like "_leftInlet.stl", etc. - I would like to have the name be exported only as "leftInlet.stl" but the underscore that is attached to the prefix remains. Any help would be greatly appreciated. Thank you! Best, Katherine

Hi Heinrich, Perfect, thank you so much for this information, it is very helpful for getting started. I will check it out and try out the feature definition tip as well. Thank you! Best, Katherine

Hi Heinrich, Thanks very much for your response! Yes you are right, running the script in a separate directory is perhaps the best way to go about achieving what I want. I did try out adjusting the name through the script (I did export a scope as you mentioned) using the "setExportFileName" command and it works for me. Just a quick final question: I also had success with providing a fullName including an absolute path with something like: 19_export.setExportFileName("~\absolute_path\NewFileName") but is there also a separate command that sets the path? Is there perhaps a way to learn what the commands are available in Caeses scripts too? Thanks again for your help, Katherine

Hello, I'm working on a project where Caeses is used to modify geometry parameters easily, but an external optimization script will generate new parameter inputs and Caeses will be used to generate the new geometry (e.g., new .stl files). To accomplish this, I have setup a case, exported a *.fsc script from it, modified a design variable in that script, and then executed it with "CAESES_crt.exe" to save the geometry as .stl files. Everything works perfectly and I am happy with this setup, but there is one thing I would like to improve upon. I would like to save the base filename for the modified .stl files generated after externally modifying the .fsc script. So for example, the scope from the project I am working in that I want to export has "mixerExported" as the base .stl file name (I am using "exportStlExtractColors" to extract a separate .stl file for each geometry partitioned into their respective colors), so the files generated are called "mixerExported_outletTopCyl.stl", etc. My question is: is it possible to change this base .stl file name in the .fsc script generated from the same project file? I do not need to generate separate project files, but rather I am looking to just modifying several design parameters and generate a new geometry for each of these modifications. Is it possible then to generate geometries from running the script and also changing the baseline filename they are saved from, just through modifying the .fsc file (and not the project file)? There are lines commented in the script file that specify a path, but it doesn't seem like they are being read: // CAESES Executable C:\Program Files (x86)\FRIENDSHIP-SYSTEMS\CAESES5\bin\win64\CAESES.exe // CAESES Project ~\CAESES\simple_test_geometry_export_demo\Simple_test_geometry_final_export.cdb // Design Name baseline // Project Units meters The outputs are saved in a folder created called "/manual_results/baseline/input". It would be great if there could be a way to generate a new folder called "/manual_results/mod1/input" etc. I'm not sure if this is something to be done just with the script, or if the project file does need to be modified, but I thought I would post it here for some advice or inputs from the experts. Thanks very much for your time! Best, Katherine

Hi Heinrich, Perfect, removing it after joining by referencing the face color works exactly as I wanted. Thanks so much for your help! Best, Katherine

Hi Heinrich, Thank you so much for your help. I see now that the geometry is working with the edits you shared. I have one more question: you mention that the three parts must be closed and overlapping for the boolean operation to work Does this mean that I can't delete a face on the attached cylinder? I would like to remove the outer face but when I do this I also encounter an error. Thanks again, Katherine

Hello, I am trying to create a simple geometry in which a tank has both an inlet and outlet cylinder attached to it. To do this, I created a rectangular profile for the tank and two cylinders at the top and bottom for the inflow/outflow. I want to merge the cylinders with the main tank. The boundary representation I created for the surface defining the tank is used as the source, and I want to use the boolean operation to merge the tank and cylinders in order to cut out the face between the two. This works exactly as intended for the bottom cylinder, but there is a segmentation fault when I try to use the boolean operation on the top cylinder in creating the final surface. I have not been able to debug this issue myself and would like to ask if anyone has any advice or insight into what the problem might be. I've attached the project file here for reference as well. Thank you for your time. Best, Katherine Simple_test_geometry_ver4_redo.cdb

Hi, I'm a new user to Caeses and have been working through the "first modeling steps" tutorial available here to get familiar with the software: https://watch.caeses.com/w/1vmuNq5DMJoyecvp9Xk6uA I'm having an issue with the last step in the "final domain" portion, where a fillet is created from the two brep's for the intakeCylinder and ductClosed, respectively. When I activate the filleting option and enter any value in the "Radius/Distance", no fillet is created but instead an error comes up that the filleting operation failed and the duct geometry is no longer shown (see image). I've attached the project file here as well. I've gone through the tutorial several times now and seem to be following the steps correctly for the last segment, but I haven't been able to debug this issue myself yet. Any help or advice would be greatly appreciated. Thank you in advance! Best, Katherine FirstModelingSteps_Fillet.cdb