Jump to content

Search the Community

Showing results for tags 'CAESES'.

The search index is currently processing. Current results may not be complete.


More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CAESES®
    • General Modeling
    • Software Connections
    • Variation & Optimization
    • Post-Processing
    • Feature Programming
    • Installation
    • Miscellaneous
    • Ideas and Suggestions
    • FAQ

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Blogs

  • Mr. Arne Bergmann's Blog
  • FSYS DAEHWAN PARK
  • Mr. Arne Bergmann's Blog
  • Rel 3.1
  • Joerg Palluch's Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 23 results

  1. Hello there! I am planning to run an optimization study of my CAESES geometry with ANSYS OptiSlang 2024R2. We are aware that there is an in-built software integration of CAESES in OptiSlang. I am having trouble invoking CAESES to run in batch mode and send the FSC and ACIS file to SpaceClaim. Any guidance to succeed in these sequence steps would be most beneficial.
  2. Hi everybody, I can't pass the boundary conditions of a 2D model to Ansys Workbench SCDM, even though I've defined inlets, walls, outlets with colors and imported Workbench by ACT APP.
  3. Hello everyone I built a parametric propeller model using Caeses and imported it into the Workbench platform, meshed it with Fluent Meshing, solved it with Fluent, and I had a problem with solving failures. I named the propeller surface "wall_prop" and selected all the wall_prop named faces in fluent to establish the output as thrust and moment. However, whenever the parameter points are changed and the mesh is updated, the original name will become wall_prop_1, wall_prop_2...... the original name will disappear, and the output torque and force will not automatically select the new name, resulting in the calculated thrust and torque being wrong or the software directly reporting an error. I don't know how to solve this problem so that the automated simulation can continue.
  4. We can draw a number of curve and use FPolyCurve to fuse them into a "smooth" curve. An old post has discussed this question here. However, my model required a 2D "not smooth" enclosed curve made with three curves as below. It requires more than 2 intermediate points, therefore we can't use Multi Segmented Smooth Curve. And it's not a "smooth curve" therefore we abandoned the 2D interpolation curve. Therefore, I used poly curve, and results looks like this. To zoom in, we found flaws at corners. This flaws blocks me from moving forward in modeling. Get rid of the top line and the polyCurve seems work normal. My guess for the cause of the problem is the discontinuity, not a jump point but a removable discontinuous point. Please let me know if there is a way to deal with non-smooth multi-segmented curves. Any inputs are appreciated! WX
  5. Hi together, The software CAESES is a CAD and optimization platform. For students and PhD students there are free non-commercial licenses available. In addition, there are low-price offers for start-ups and smaller companies. CAESES can be used for 2D and 3D parametric modeling, see this link for some information about its CAD capabilities. Here are some screenshots: Compared to traditional CAD systems, CAESES is a bit different. It comes with a strict object-oriented approach, i.e. the user sets up dependencies between objects and these dependencies are then kept. This makes it easy to automate the geometry generation process. Here are some features of CAESES: Full 2D and 3D modeling capabilities (NURBS-based)Roughly 20 curve types and 15 surface typesStandard transformations (translation, rotation, scaling)Writing of custom features and functionsBoolean operationsTrimmingFillets between surfacesMorphing functionality for deformation of existing geometrySurface tessellation control through e.g. trimesh objects to create and fine-tune custom STL dataCommon import and export formats e.g. IGES, STEP, PARASOLID, STLIndustry-specific modules for blade and ship designBatch mode for non-GUI (hidden) geometry generation in the background Cheers Joerg LAST UPDATE: NOV 2017
  6. Hi, This is an example of integration with Pointwise and CAESES. First of all create a Glyph file by using Pointwise function "Script -> Begin to Journaling". Use your your Glyph file (e.g. roPaxLowerBulbScript.glf) as argument for the computation. The leading -b starts Pointwise in batch mode. Best regards, Takamichi Hiroi roPaxLowerBulb.fdb
  7. Hi everybody, I recently tried my hands on integrating CAESES with fluent and i think its worth sharing for those who work with fluent and will like to use CAESES parametric models. Please find attached a copy of my project file. its a simple meta-surface elbow i designed with an ellipse curve.Functions for the "width and "height" of the curve are defined. you can have a look at how parameters are set from function curves. I used ICEMCFD as my meshing tool and Fluent as CFD solver. specific files such as the *.rpl and *.jou were used as input files( checkout the attachments). Absolute paths should be changed to relative paths via "getdesigndir()...." (not all paths are necessary!). A *.bat file, RunFluent.bat, was used to run both ICEMCFD and Fluent in batch mode. Snapshots, graphs etc from fluent can be included as results files for post processing. Details on post processing can be found in CAESES tutorials " getting started". You can have a look. Suggestions are welcome. Best regards, Richard "N.B: CAESES is one of the most powerful softwares for tight integration with CFD softwares for DoE and Optimization. All you need to know is to understand how your External CFD software handles its files to know exactly which input and result files to use. it must also have the capability of running in batch mode." Project1_elbow.fdbc
  8. Hi, After a few days trying I have successfully set up the SSHresource manager with a Postgres DB back end. CAESES can communicate with the server but when I attempt to execute a hexpress job it fails. Does anyone have suggestions on a) what the application executable calls for Hexpress and FineMarine should look like in the SSHresourceManager and B) any suggestions on custom canceller classes for SSHresource manager for these tools? I am running the solver/meshers on Linux Centos X64. Thanks for any advice, Britton Ward
  9. Hi everyone, I coupled CAESES and Starccm+. I'm trying a cycle out. As you can see on screenshot, it says n/a for "eval_coeff"; but when i click on created design, i can see the value on the left side. It does not count in the "eval_coeff" value when making evaluation. How can I overcome this problem? Any idea?
  10. Hi, I have just started learning CAESES. I would like to use STAR CCM+ installed in the university supercomputer and integrate it with CAESES. There is a tutorial on how to integrate CAESES/ FFW with STAR CCM+ using GUI based Java macro, but I was wondering if it is possible to do the same in the console environment in Linux installed in the supercomputer. If there is any tutorial available for connecting the cluster using SSH and then connecting the STAR CCM+ simulation to the CAESES/FFW, please let me know. Else, I would appreciate if someone can give me a detailed guideline to set up the simulation. Thank you for your time and help. Sincerely, Amitava
  11. Hello, I am really new to CAESES and I tried the s-duct tutorial, followed all steps but I am getting an message: External process start failure [Starting process C:/Users/HP/Desktop/skola/DP/sduct/sduct/manual_results/baseline/Runner//Allrun failed: Process failed to start:] Currently using OpenFOAM v1912 installed on Ubuntu 18.04 for Windows 10, Allrun and stdouterroroutput files are attached. I will really appreciate any help! stdouterroroutput.redirect Allrun
  12. Hey Guys I tried installing Caeses/FFW 3.0 for 64bit linux distributions. I extract the tar.bz2 file, and from there I cant find any documentation on how to install, readme.txt, install.txt etc. so i tried; ./compile make sudo make install but this does not work, my Ubuntu skills are pretty average and i don't know where to go next. any chance you guys could give me some pointers? cheers James
  13. We can make a multi-segmented smooth curve from Feature Definitions -> Hull Design -> Multi Segmented Smooth Curve. The issue is I can only define '2' intermediate points in a curve. I want to join many multi-segmented curves to create a single curve. How do I do it ? I am a beginner in CAESES. I could not find it in documentation. Please help.
  14. Hello Everyone, I've tried my hands on CAESES+CFX integration and i think its worth sharing for those interested in using Ansys CFX. This was done with ICEMCFD as the mesh tool (rpl script file). The key files needed from CFX are the *.pre and *.cse. Ive attached a project file that shows how the integration was done. To run in batch mode, you'll need to call cfx5pre, cfx5solve and cfx5post executable( please check attachment). I've also attached a process workflow to describe how the integration works. To post process in CAESES, you can check the tutorials for more details. (C:\Program Files (x86)\FRIENDSHIP-SYSTEMS\CAESES\tutorials\01_getting_started\postprocessing.pdf). Cheers, Richard Project1_elbow.fdbc
  15. Hello everyone. In the attached file, there are an sample hull, feature definition for connection to Maxsurf to get Large Angle Stability results. When I click to run button, console says that "Initializing BentleyStability - please be patient ... ... initializing BentleyStability failed - aborting" Anyone knows how to fix this? Thank you in advance... shiphull.fdbc
  16. Hello to everyone. Is there anyone who's made integration between Caeses and Maxsurf Stability/ Maxsurf Resistance before? If any, can you please share it to me to learn how to make it? Regards, Hasan.
  17. How to determine a spiral volute casing (turbocharger, pump) cross sectional decrease in value? I am trying to design a volute casing. Problem is, I don't know how much its cross sectional area decreases over time. For instance starting cross sectional area (0 degrees) is 100 cm^2, what will it be when it reaches 45, 90 degrees and so on? Is there any way to calculate it? I am sure that knowing starting and finishing cross sectional areas size (btw I know them) and just connecting them isn't a correct way.
  18. Hello friends,   Currently, I can use CAESES to read the points of a curve (function (x,y)) and then export into csv file. Is it possible to further calculate the slope or derivative of this function using CAESES programming and then export a csv file? Or any other way to do this without programming? Thank you guys.    
  19. Hi, Please find attached a feature definition that you can use for exporting blades into the geomturbo file format. Note that this export will be included in one of the next CAESES releases (menu > feature definitions > tools). If you need it right now: Just put the definition into the feature user directory (e.g. C:\Users\name\AppData\Roaming\friendship\features) to directly access it through the menu in CAESES. Cheers Joerg PS: Check also this related post for importing geomturbo files, as well as our company blog post about this topic. GeomTurboExport.fdf
  20. Hi folks please find attached a Feature Definition for a "Bulbous Bow Shape Analysis" and a Feature Definition which can be used in a CurveEngine for creating a MetaSurface. shapeAnalysis_Bulbous_Bow.fdf bulbous_bow_section.fdf [edited 05.10.14 - tangent analysis included] In order to replace a Bulbous-Bow-IGES-Import by a fully parametric MetaSurface you can use this Feature by execute the following steps: Create a Surface Group including all the IGES-surfacesCreate a new Feature Definition and reload the Analysis-Feature, apply and create the Feature by right click on the Feature Definition>Create FeaturePass the Surface Group to the Analysis-Feature and enter (if necessary) start- and end-position in x-direction of the bulbous bowAdditionally give a number of offsets (30-50 should be a good choice)Run the Feature This will create function curves which can be used to create a MetaSurface. The next steps should be: Re-model the function curves by e.g. FSplineCurvesCreate parameters for some values of the new curves, like start/end position, start/end tangent or area Create a CurveEngineCreate a new Feature Definition, reload the Section-Feature and applySelect the Bulbous-Bow-Section-Feature and pass the new function curves to the EngineAdditionally you can set start- end end-tangent valuesCreate a MetaSurface, select the Curve Engine and set the base positions according to the start- and end-position in x-directionNow you will have a single Metasurface, which is parametric and ready for a design study. Cheers Matthias
  21. Hi all, I'm doing an optimisation on an axisymmetric body. I have manually generated the coordinates of the profile by variating the parameters and put them in individual CSV files(got 200 of them!!!). I want CAESES to generate the geometry for each CSV file and run the analysis in Star CCM+ automatically and save the results. I want to know if this is possible or not, if yes then please please guide me :)
  22. Ladies and Gentlemen I have a short introduction about the evaluation project of propeller open water test using CAESES + STARCCM+. You can find the whole contents at the link below. GO :D
  23. Hi All, Recently I wanted to investigate the use of OpenFOAM for CFD calculations for a model built in CAESES and perform an optimization at a later stage. Although the OpenFOAM is a C++ library meant to be run in Linux systems, I wanted to test the configuration on my Windows pc and I found this compiled OpenFOAM 2.3 version available. After installing the software as instructed I had to change a little bit the configuration of the software connector in CAESES. Basically, I called the mintty.exe terminal application and run a modified version of the Allrun.sh shell script, as demonstrated at the ahmed body sample. You can find attached a picture of the LocalApplication and its arguments, the modified shell script Allrun.sh and the modified project file of the Ahmed Body sample provided with CAESES installation. Please notice that I have configured the OpenFOAM calculation to run on a single processor and deactivated any parallel computing, because of my restricted resources, but you could easily restore that back. I had also to change some points in the RunFunctions file located in /opt/OpenFOAM/OpenFOAM-2.3.x/bin/tools and you can find attached this new file too. If you are interested in learning how to manipulate OpenFOAM or try some simple simulations on your windows machine, you can give it a try. Cheers, Ilias. ahmedbody.fdbc Allrun.zip
×
×
  • Create New...