[BhaluBear]

I'm fairly new to CFD software and I'm hoping to use a GUI that eases the process of running simulations. I've seen a lot of talk about Helyx and Salome but I'm not sure which to use.

Could someone explain what the differences between each option are? One issue I have is that I have found more youtube tutorials using Salome compared to Helyx OS so I am inclined to use Salome.

Any additional information on the topic is greatly appreciated because I am very new to all of this. Thanks!

[gkarlsen]

Originally Posted by BhaluBear

I'm fairly new to CFD software and I'm hoping to use a GUI that eases the process of running simulations. I've seen a lot of talk about Helyx and Salome but I'm not sure which to use.

Could someone explain what the differences between each option are? One issue I have is that I have found more youtube tutorials using Salome compared to Helyx OS so I am inclined to use Salome.

Any additional information on the topic is greatly appreciated because I am very new to all of this. Thanks!

I would recommend Salome for generating your geometries and exporting each of the patches as STL files. Then I like to do the meshing in Helyx-os. Those tools complement each other, and one can not (as far as I know) replace the other. Only a subset of solvers and boundary conditions is available through Helyx-os currently. If your solver is supported it is also great for case setup... However, I think you will find that you still need to work with the text based dict files from time to time. I know those are intimidating at first, but it is not that bad really

Good luck!

[elvis]

Hi,

take a look at http://openfoamwiki.net/index.php/GUI not mentioned seems to be cfMesh that was introduced at 9th OF workshop in Zagreb

there is also engrid that helps you meshing and solving your case for OpenFOAM and SU^2, for Geometry creation Blender scripts are available.
Helyx-os is Gui for SnappyHexMesh(SHM).
There is a python script to convert salome meshes to OF that python script seems to be more usefull as "ideasUnvToFoam" does not support all mesh information salome provides. pythonflu with a direct salome link to OF is not actively developed

[newoscar]

As one of the creators of simFlow I'm probably biased but I'll give you my two cents.

• User interface
  We put a lot of attention on the ease of use. This gives you the fastest workflow with CFD software.
• OpenFOAM integration
  Seamless OpenFOAM integration. If you know some basics of that software, you will have familiar feel, but now in a great graphical inerface
• video tutorials
  We are committed to make video tutorials with free access for all of our users. Some of them are already on Youtube. More on the way.
• Free to use
  Our free version has little limitations. Check by yourself what it can give you: Free simFlow license

What we tried to do differently?

• Be available - We have a great support with committed guys on the other side of email
• Listen to users and change in the direction of their needs. After all it is created for them.

Thanks!
Oskar

[Linse]

Hi there,

I only can tell some things about Salome.
A first point: Salome is NOT an interface for OpenFOAM like it is the case for Helyx! Salome is a geometry and mesh generation software toolbox, but as soon as you have your mesh exported to OpenFOAM, you will have to continue the case setup as usual.

Nevertheless in my opinion Salome is really great software, as it provides much more flexible meshing than the OpenFOAM-tools I know. Mesh import is no problem. The publicly available script salomeToOpenFOAM.py can be called from within the Salome GUI and will provide you with a complete OpenFOAM polyMesh folder. Sometimes changes are necessary within the polyMesh/boundary-file, but that is true for many tools.
The other option I use at the moment is creation of STL-files with Salome and using these STL-files as input for snappyHexMesh. But as soon as I learn to properly use Salome's HexaBlock-module, I will be returning to that one, I guess.

Enough said, in case of further questions, just ask!

Cheers,
Bernhard

[wyldckat]

Originally Posted by elvis

take a look at http://openfoamwiki.net/index.php/GUI not mentioned seems to be cfMesh that was introduced at 9th OF workshop in Zagreb

FYI: The GUI made by Creative Fields is named cfSuite; it's their mesher that is named cfMesh.

[franjo_j]

Thanks Bruno,

cfSuite is GUI framework aimed at quick implementation of OpenFOAM utilities and solvers into a simple-to-use GUI application. We are aware that every user has its specific utilities and problems, and the application allows to create custom versions for our users. It is primarily designed to simplify creation of patches and other entities needed to generate simulation-ready meshes.

cfMesh was also mentioned here. It is an open-source library for mesh generation for OpenFOAM. The library allows for implementation of various meshing workflows for generation of various types of meshes, ie. hex-dominant, tetrahedral and 2D hex-dominant. We also plan to release a polyhedral meshing workflow in the near future. Our experience shows that cfMesh is about 10-20 faster than snappyHexMesh for most cases, requires less settings, and uses 3-4 times less memory for mesh generation. It does not yet support multi-material meshing, and we hope to overcome that this year.

Regarding GUIs - my experience is that GUI is crucially important when meshing complex geometries. Most people I know learned to set solver parameters quite quickly.

1. Salome is a well-established tool with lot of functionality. I do not have experience with the block-mesher and the tet meshing tools.
2. Helyx indeed complements with Salome, but rudimentary when you need to mesh complex geometries with a low number of cells.
3. CastNet -
4. simFlow -
5. Visual-CFD - is the interface developed by the ESI group. It seems very flexible. Has anyone used it?
6. cfSuite - I am biased about it.
7. EnGrid - it is a tet meshing tool with advanced boundary layers.

Regards,

Franjo

[elvis]

Originally Posted by franjo_j

7. EnGrid - it is a tet meshing tool with advanced boundary layers.

according to tweet (11. Juli 2013)
https://twitter.com/engits/status/355373321505869825
=>A first step has been made to handle polyhedral cells directly inside enGrid
But you quoted correct that enGrid "1.2" uses the Netgen library for tetrahedral grid generation.

CastNet is a commercial tool, it supports various CAD Kernels such as "Parasolid, ACIS and Granite" so geometry import from a range of CAD programms comes with this programm.

PS: I am not biased ;-) I am just a OpenFOAM user

[chegdan]

@franjo_j

Correction.

Originally Posted by franjo_j

2. Helyx-OS indeed complements with Salome, but rudimentary when you need to mesh complex geometries with a low number of cells.

HELYX uses a different mesher than HELYX-OS (that uses standard snappyHexMesh), without spamming this thread with bias I wanted to correct that note

[anmsg]

Visual-CFD is quite customizable and supports multi-domain meshing. Please contact any of the ESI Group sales person (refer www.esi-group.com site for location nearest to you)

[af631717]

We use CastNet from http://www.dhcae-tools.com/CastNet.html since many years. For us it’s perfect: Direct CAD model import (we use Solidworks), good and fast CFD mesher and we can run cases (including monitoring) on Windows with BlueCFD or Linux. OpenFOAM case setup is very easy by using a template approach.

BR
Achim

[stawrogin]

We also use CastNet from DHCAE Tools (in combination with PTC-Creo/Pro-E) and are also very satisfied. It reads our Creo data directly and transfers automatically parts into regions for multi-domain modelling (e.g.CHT). Furthermore it supports a number of OpenFOAM versions from 2.1 to 2.4. This is quite important for us as company to move with our older cases to new OF versions while still having the option to run them with the older versions. The supported functionality is very good, the guys from DHCAE Tools are also quite fast with their updates in case of OpenFOAM changes (e.g. modified keywords) and finally offer a good and fast support for their software and OpenFOAM in general.

Stawrogin

[jake.yun]

It's an old thread.
But if there is anyone who still has interest, I've released an OpenFOAM GUI recently.
It's released under GPL and completely free without any restriction.

In addition, Windows installer is provided for convenience.
Please check it here.

Any feedback is welcomed.
Thank you.

[rahulshivanathri]

I tried script salomeToOpenfoam.py to import my mesh into openfoam which has pyramids.I get the following message in the console.Can you please help me






SalomeOutsideGUI: no selection mechanism available outside GUI
You have to select a mesh object and then run this script.
or run the export function directly from TUI
import SalomeToOpenFOAM
SalomeToOpenFOAM.exportToFoam(mesh, path)

[jake.yun]

I have no experience in Salome. But, from the message you've got and the quote from salomeToOpenFOAM github, a suggestion or question has risen in my mind.

Suggestion: You have to load a mesh first. You may have two options.
1. follow the error message you've got. ie. write a script that has following.
import SalomeToOpenFOAM
SalomeToOpenFOAM.exportToFoam(mesh, path)
or 2. load a mesh in salome environment and run the salomeToOpneFOAM.py script.

If you can send me the mesh, one of my colleagues may be able to handle it.

[Alczem]

Originally Posted by jake.yun

It's an old thread.
But if there is anyone who still has interest, I've released an OpenFOAM GUI recently.
It's released under GPL and completely free without any restriction.

In addition, Windows installer is provided for convenience.
Please check it here.

Any feedback is welcomed.
Thank you.

Hey! I am checking your software out, is there a way to use a more recent version of OpenFoam ? Thanks!

[jake.yun]

Hello, Alczem.
Actually, BARAM is already using the latest OpenFOAM.
Have you found any difference?

[phsieh2005]

Originally Posted by jake.yun

Hello, Alczem.
Actually, BARAM is already using the latest OpenFOAM.
Have you found any difference?

Hi, Jake,


Good to see another open source GUI for openFoam.



I just downloaded BARAM. I have a couple of questions:
1 is there any documentation that I can follow?
2. is there an user forum that users can ask questions or discuss specific topics?
3. what are the differences between 6.4.3 and 6.4.5?
4. does the current version support adding solid particles?



Pei-Ying

[phsieh2005]

Originally Posted by jake.yun

Hello, Alczem.
Actually, BARAM is already using the latest OpenFOAM.
Have you found any difference?

looks like BARAM is based on OpenFOAM-6 and requires that OpenFOAM-6 already installed, correct?


Pei-Ying

[phsieh2005]

Originally Posted by jake.yun

I have no experience in Salome. But, from the message you've got and the quote from salomeToOpenFOAM github, a suggestion or question has risen in my mind.

Suggestion: You have to load a mesh first. You may have two options.
1. follow the error message you've got. ie. write a script that has following.
import SalomeToOpenFOAM
SalomeToOpenFOAM.exportToFoam(mesh, path)
or 2. load a mesh in salome environment and run the salomeToOpneFOAM.py script.

If you can send me the mesh, one of my colleagues may be able to handle it.

When I tried to install baram, I got the following errors:
Collecting tables==3.7.0
Using cached tables-3.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.9 MB)
ERROR: Could not find a version that satisfies the requirement vtk==9.1.0 (from versions: 9.2.0rc2, 9.2.2)
ERROR: No matching distribution found for vtk==9.1.0
(venv) phsieh@CAE:~/baram$ gcc -o solvers/openfoam/bin/baramd misc/baramd.c
(venv) phsieh@CAE:~/baram$ python3 convertUi.py
>> Convert qrc files
Converting... resource.qrc -> resource_rc.py
sh: 1: pyside6-rcc: not found

>> Convert ui files
[1/83] Converting... case_wizard.ui -> case_wizard_ui.py


--sh: 1: pyside6-uic: not found
[83/83] Converting... selector_dialog.ui -> selector_dialog_ui.py
sh: 1: pyside6-uic: not found

All done
(venv) phsieh@CAE:~/baram$ python3 main.py
Traceback (most recent call last):
File "/home/phsieh/baram/main.py", line 9, in <module>
import qasync
ModuleNotFoundError: No module named 'qasync'
(venv) phsieh@CAE:~/baram$