Hi Everyone, Merry Xmas and pappy new year 2016&2017&2018&2019
============ updated (2018-12-29) ==================
Cfd workbench will be in maintenance mode, I do not have enough spare time to support feature development. However, I will make Cfd workbench work in stable FreeCAD release like v0.17, and later 0.18, etc. You can fire bug at my https://www.github.com/qingfengxia/Cfd/issues
, I can get email to response as I have no time to check this forum.
I hope to get resource as an academic staff soon and sponsorship from industry to complete more feature. I had a meeting with Prof Jasak, the original author of OpenFOAM. We were particularly interested in CAE automation, it will be part of my future research direction. So I spend most of time to develop a multiphysics FEM solver (https://www.github.com/qingfengxia/FenicsSolver
), and coupling FEM and OpenFOAM in 2018.
Last Xmas, I make some work to let Cfd work on win10 WSL. Recently in this Xmas time, I make Cfd workbench working with external meshing tools like Salome mesh, as a complementary to Gmsh integrated mesher. see http://www.iesensor.com/blog/wp-content ... _mesh.webm
I also make a new boundarycondtion in python, user can provide/edit (in QTableView) each variable boundary condition as a raw python dict, see below.
Besides, I had FemInitialValue and FemBodySource feature submit to Fem Workbench, see
============== updated (2017-05-16) ====================
I am not available until July 2017 to work on this project. In the future I will focus on non-gui part, "FoamCaseBuilder" which can work without FreeCAD in text mode.
please refer to this post for new feature fork.
Port of CFD called CFDFoam https://forum.freecadweb.org/viewtopic.php?f=18&t=21576
They have more resource than me, hopefully, they can mature this workbench asap.
Their boundary setting class is implemented in python, so it is kind of self-contained. This is a be good choice, as FEM workbench is changing very fast to maintain CFD workbench and dev in C++ is more painful.
My current day-work project is using Fenics to solve multiphysics problem, once some one can export FreeCAD fem mesh to FEnics, we can solve more physics problem easily.
==================== update on 2016-04-17 ======================
OpenFOAM for FreeCAD finishes stage II development
This is an early preview, only for people with experience of OpenFoam.
Test instruction could be found at
https://github.com/qingfengxia/FreeCAD/ ... /Readme.md
I would love to see some feedback for stage III development, see roadmap:
https://github.com/qingfengxia/FreeCAD/ ... roadmap.md
A video preview of OpenFoam plugin for FreeCAD Fem workbench
http://www.iesensor.com/FreeCADDoc/oepn ... engXIA.mp4
The code will attempt to merge with master for version 0.17 after review. However, the OpenFoam related code is independent from CalculiX, except for the Material class. I plan to developed a general FemMaterial model (not yet finished), ultimately for multiphysics modeling in FreeCAD. Rebase to master will be easier than before.
=====================Phase I (2015 Dec) =================
Phase 1 finishes UNV meshing writing, and a simple OpenFOAM case writing up. Various boundary conditions are not implemented by reuse the FemConstraint. I have added one essential new FemConstraint: FemConstraintsymmetry , see https://github.com/qingfengxia/FreeCAD/ ... rc/Mod/Fem
, I am not good at the C++, I hope a subtype PropertyEnumeration could be added , to distinguish the special boudnary type: symmetry, FSI, axis-symmetry, freestream, etc and give diff color.
https://github.com/qingfengxia/FreeCAD/ ... rc/Mod/Fem
There are plenty of GUI work (left to phase II), I do not expect to complete. I will focus on text interface to build up case: FoamCaseBuilder package.
I have done phase I work, according to my roadmap. https://github.com/qingfengxia/FreeCAD/ ... roadmap.md It is NOT ready to test
(compilation may fail), but code preview. (After rebase on 2016-01-01, it is not fully tested even on my PC) A tutorial will needed for 3rd party test, as it is not intuitive to test the GUI code.