Jump to content

Search the Community

Showing results for tags 'openfoam'.

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 7 results

  1. 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
  2. Hey all, Is there any documentation for connecting OpenFoam run in WSL? If not, has anyone done this before and could share some tips, Thanks! Bradley
  3. Hello everybody! I have a few days on the openfoam connection, and searching through the forum about it. I'm trying to follow the "Sduct with OpenFOAM" tutorial, to get a grasp of it. I got to the step 10 (triggering the first run). The "stdouterroroutput.redirect" file states the error: "fileName::stripInvalid() called for invalid fileName complete/path/to/Runner For debug level (= 2) > 1 this is considered fatal". This goes for: Exec : blockMesh -dict system/blockMeshDict Exec : snappyHexMesh -overwrite Exec : simpleFoam But in none of these files is there a filename specified, so I got no idea what's happening. Other question: The tutorials and video talk of these "software connector" that has been configured before, is there a tutorial to learn to configure this file? Should I install Helyx-os for handling these files? Or I can do that from CAESES? Cheers, and thanks for your time. Xavier
  4. Hi guys, today I want to share with you my latest feature which creates a bounding box for your OpenFoam internal flow geometry. The idea came, when I struggled with SnappyHexMesh because the edges of the boundaries where not captured correctly, which resulted in a bad prismlayer mesh like this: (image 1) I found out that the reason for this, was the bounding box, where the inlet and outlet boundary do not lay within the first layer of the box like this: (image 2) So I created I bounding box which automatically adjusts with the changing geometry. It calculates the maximum and minimum positions and creates the bounding box with a user specified offset. A nice setup looks like this: (image 3) This setup produces a nice volume mesh with clean prism layers: (image 4) The complete bounding box, where the subdivision in x, y and z coordinates can be specified, looks like this: (image 5) The following picture shows how to connect the BlockMeshDict with the bounding box feature: (image 6)Remember that you have to create an entry for the vertices by selecting these, right click and select new entry: (image 7) This creates a new entry in your config dialog. There you have to change the type to FString: (image 8)Do the same for the line where the blocks are defined (see image 6).Now you have create a new entry for the point in mesh, which you can find in your SnappyHexMeshDict. Follow the same procedure, but just mark the three coordinate like this for a new entry:(image 9)That's it. This is just a first version of the feature. I could imagine to write another feature for the creation of the bounding box for external flows, where you could specify different patches within the BlockMeshDict. Of course you are also welcome to post your features here in the forum. Attached is the feature and an example how to use this feature with a complete software connector. This example by the way couples OpenFoam for Windows with CAESES. Have a nice day Carsten duct_win_forum.fdb OpenFoam_BoundingBox.fdf
  5. 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
  6. Hi together, Please note that CAESES can be utilized as an OpenFOAM GUI (Graphical User Interface). There are free academic versions of the CAESES pro edition for students and PhD students as well as trial licenses with flexible time frames. There are also special editions for small companies, start-ups and freelancers. Compared to other tools in the market, CAESES is good at automation, i.e. if you already have an existing OpenFOAM setup and you want to analyze design variants of your product, then CAESES might be a perfect choice. Especially, if geometry variation plays a major role. In contrast to that, a tool such as HELYX-OS might be a better choice e.g. if you would like to set up an OpenFOAM case from scratch. Here are some CAESES-specific offers: Conveniently configure and manipulate template files (e.g. controlDict or any other ASCII file) in the GUIChange your geometry design and trigger OpenFOAM with a single mouse-click for analysis (i.e. streamline your design process / automation)Use your individual result values such as pressure loss or homogeneity for an objective function in design studies and shape optimizationsPostprocess your simulation data (streamlines, contour plots etc) Here is a video that shows some of the features in CAESES. Cheers Joerg LAST UPDATE FEBRUARY 2018
  7. Hello, This guide will show you how you can connect OpenFOAM to CAESES-FFW or any other application. Using the Software Connector, you need a executable of the Local Application. If you want to start this application with a script, do following: create on your Desktop a text file with the execution command of your desired external application (OpenFOAM) and save as 'adder' add the script 'adder' to your Input Files in the Software Connector and 'double click' it, so that it is copied into the project and is converted to a Template click on computation (in the center of the Software Connector) create a new Local Application (using the green + symbol) define the Executable: write down the name of the Template 'adder' which you have imported in the Input Files run the Computation (click on the play button) check the result in the Task Monitor (on the right side shaded widget) and click the green button in the top left corner to show the finished computations Attached is a little example which shows this. In this example the script adds the Argument of the computation (which is defined by the Variable pm1) to a defined Variable in the script (addend). Best regards The Team of FRIENDSHIP SYSTEMS SoftwareConnectorExecutable.fdb
×
×
  • Create New...