Jump to content
The search index is currently processing. Activity stream results may not be complete.

All Activity

This stream auto-updates     

  1. Today
  2. Hi Etienne, I would like to add two questions: 1. Does the CAESES-console display any errors after you start CAESES? 2. Could you run the command getGLInfo() in the CAESES-console and send us the output? Best regards, Erik
  3. Last week
  4. Hi Etienne, I need a bit of clarification. Are all your displayed surfaces shown in red color or only the selected surfaces by you are showing this behaviour? Cheers Ceyhan
  5. Hello, I am following some tutorials and modifying the basic hull sample file. For some reason all my surfaces are always displayed with the color red, regardless of what settings for color I use. See the attached image. I also tried opening other CAESES sample files with the same result, all surfaces are red. Any idea what this could be? Regards, Etienne Duchateau
  6. 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
  7. Hello everyone, I came across an interesting article about Level Order Traversal in Binary Trees. I found it quite informative and was wondering what benefits this method has compared to other traversal methods. Can anyone share their experience with using Level Order Traversal in their coding projects? Are there any specific scenarios where this method has proved to be particularly useful? Looking forward to hearing your thoughts and experiences on this topic. Thank you!
  8. Hi Katherine, I don't think there is a command to set just the path, not the name. In that case you would simply have to set the full name and path but keep using the same name. The commands available in fsc scripts are basically the same as in CAESES with the exception of things that require a GUI (e.g. screenshots are not available in batch mode). You can learn about most types and available commands through the Type documentation: Also, if you start typing a command (even if it is just a "." behin a certain object) you can always use ctrl + space in CAESES and see what the auto-completion has to offer: A third option many newcomers like to use is, to set things up in the GUI and then select a certain object or a whole bunch and right-click > Create Feature Definition: This will give you a new feature definition containing everything you had selected. BR, Heinrich
  9. Earlier
  10. 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
  11. Hi Katherine, maybe it is easier if you just run the fsc script in a unique directory for each design you want to generate -- this way also any other files generated by CAESES are taken care of. However, you can also adjust the name trough the fsc script. I'm guessing you set up your export by providing a scope (folder) in CAESES which contains the geometry you want to export and for which you have set a custom file name like this: Inside your fsc script you should be able to just change that name if you add a line like this: 19_export.setExportFileName("changeThisNameAsYouLike") You can also provide a fullName (incl. absolute path) if you want. BR, Heinrich
  12. 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
  13. 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
  14. Hi, Recently, I connected CAESES to a CFD software. I manage to run a Design Engine by this connection. However, 50% of the time I will get error as shown below while it worked without problem as well 50%. I am not sure that it randomly occur or what is the reason behind this. If anyone could help and have some idea thanks. [xcb] Unknown request in queue while dequeuing [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that.
  15. Hi Claus, At my work we have both versions, but since I'm relatively new to use CAESES and my "mentor" has not used C5 yet, we decided that I should use C4 while I'm learning our templates for ship hulls. I have started to use C5, though, and my plan is to only use C5 very soon. Kind regards, Gustaf
  16. Hey Gustaf, is there any reason why you stick to CAESES 4?
  17. Hi again Mr. Claus Abt, I cannot find the "Weight in Tree" setting in CAESES 4, but I find it in CAESES 5, so I guess this is a new feature only available in C5!? Kind regards, Gustaf
  18. Hi Mr. Claus Abt, Thank you for the reply and description of how to organize the contents. Kind regards, Gustaf
  19. Hi Gustaf, currently you can only use appropriate names to sort the scopes alphabetically or, use weights for the items, see attachments.
  20. Dear CAESES users, I would like to organize the object tree, but the usual "drag & drop" feature does not work and I cannot find another way, like an "edit-mode", that allows me to move, for example, FScopes and FParameters up and down in the object tree and thereby organize the contents. If there is a way to organize the object tree, I would be very grateful if someone could enlighten me. Thanks, Kind regards, Gustaf Magnander
  21. Hi Katherine, of course, you can remove a face. In case of you model I would just recommend to this after joining the parts via boolean sum. You can choose any method to remove the face. Personally, for this case I would probably reference the face by color or via reference point. BR, Heinrich
  22. 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
  23. Hi The problem is solved because the parameter which controls the distances of box layers from surface was set wrong by myself. 😅
  24. Hi Katherine, for the boolean oyu want the 3 parts closed and distictly overlapping (no co-planar faces). Also, in you first add sources operation you accidentally added the tank and inlet instead of only the tank. See attached file for a working model... Cheers, Heinrich Simple_test_geometry_ver4_redo_mod.cdb
  25. 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
  26. Hi I'm trying to set an offset FFD box around a plane. After translating, a disorder plane was got as shown in the figure below. I have got a desired plane if the sweep or rectangular box was employed. Could you please help find out why the offset box does not work? Thanks a lot. Best regards Junb Liu
  27. Hi Carlos, what's meant is an operation: Cheers, Heinrich
  1. Load more activity
  • Create New...