CFD-Wiki - User contributions [en]

Codes

2013-01-08T12:43:30Z

Florent:

An overview of both free and commercial CFD software. Here you will find short descriptions of codes along with links to resources.

'''Note to contributers:''' Please try to keep descriptions short and to the point (approximately 200 words) and avoid long lists of features or capabilities. Also keep in mind that all contributions are considered to be released under the GNU Free Documentation License 1.2 (see [[Project:Copyrights]] for details). Also note that all information should be verifiable and objective truths that also competitors to the code in question will agree upon. This is especially important if you are an employee of the company selling the code. See the [[CFD-Wiki:Policy]] for further information.

== Free codes ==

This section lists codes that are in the public domain, and codes that are available under GPL, BSD or similar licenses.

=== Solvers ===
{| class="wikitable"
|- align="center"
! Solver !! Mesh type(s) supported
|- align="center"
|- align="center"
| align="left" |ADFC -- [http://adfc.sourceforge.net/index.html ADFC homepage]||
|- align="center"
| align="left" |Applied Computational Fluid Dynamics -- [http://www.partenovcfd.com Solver homepage]||
|- align="center"
| align="left" |arb -- [http://www.chemeng.unimelb.edu.au/people/staff/daltonh/downloads/arb/ arb homepage]||GMSH (.msh)
|- align="center"
| align="left" |CalculiX -- [http://www.dhondt.de/ CalculiX homepage]|| internal
|- align="center"
| align="left" |CFD2D -- [http://sourceforge.net/projects/cfd2d/ a 2D-solver for incompressible Navier-Stokes homepage]||Based on Triangle grid generator (see table below)
|- align="center"
| align="left" |CFD2k -- [http://www.cfd2k.eu/ CFD2k: a 2D-solver for compressible ideal gases - homepage]||
|- align="center"
| align="left" |[http://www.cfdpack.net/ cfdpack] -- A collection of academic codes | 2D/3D, FV, unstr, incomp, adjoint, parallel || GMSH (.msh)
|- align="center"
| align="left" |Channelflow -- [http://www.cns.gatech.edu/channelflow/ Channelflow: a spectral Navier-Stokes simulator in C++ homepage]||
|- align="center"
| align="left" |CLAWPACK -- [http://www.amath.washington.edu/~claw/clawpack.org CLAWPACK homepage]||
|- align="center"
| align="left" |Code_Saturne -- [http://www.code-saturne.org/ Code_Saturne homepage]||I-DEAS®, GMSH, Gambit®, Simail®, Salomé, Harpoon®, ICEM
|- align="center"
| align="left" |COOLFluiD -- [http://coolfluidsrv.vki.ac.be/coolfluid COOLFluiD homepage]||
|- align="center"
| align="left" |Diagonalized Upwind Navier Stokes -- [http://duns.sourceforge.net DUNS homepage]||
|- align="center"
| align="left" |[[Dolfyn]] -- [http://www.dolfyn.net/dolfyn/index_en.html dolfyn a 3D unstructured general purpose solver - homepage]|| GMSH (.msh)
|- align="center"
| align="left" |[[Edge]] -- [http://www.foi.se/edge Edge homepage: 2D & 3D compressible RANS / Euler flow solver on unstructured and hybrid grids]||.bmsh
|- align="center"
| align="left" |[[ELMER]] -- [http://www.csc.fi/elmer/ ELMER homepage]|| .unv (also with multiple body / surface attribution)
|- align="center"
| align="left" |[[FDS]] -- [http://www.fire.nist.gov/fds/ FDS homepage]||
|- align="center"
| align="left" |Featflow -- [http://www.featflow.de Featflow homepage]||
|- align="center"
| align="left" |Femwater -- [http://www.epa.gov/ceampubl/gwater/femwater/index.htm Femwater code]||
|- align="center"
| align="left" |FreeFEM -- [http://www.freefem.org FreeFEM homepage]||
|- align="center"
| align="left" |[[HiFlow³]] -- [http://www.hiflow3.org HiFlow³ homepage]||
|- align="center"
| align="left" |[[Gerris Flow Solver]] -- [http://gfs.sourceforge.net/ Gerris Flow Solver homepage]||
|- align="center"
| align="left" |hit3d -- [http://hit3d.googlecode.com/ hit3d homepage]||
|- align="center"
| align="left" |IMTEK Mathematica Supplement (IMS) -- [http://www.imtek.uni-freiburg.de/simulation/mathematica/IMSweb/ IMTEK Mathematica Supplement (IMS) homepage]||
|- align="center"
| align="left" |iNavier -- [http://inavier.com/ iNavier Solver Home Page]||
|- align="center"
| align="left" |ISAAC -- [http://isaac-cfd.sourceforge.net ISAAC Home Page]||
|- align="center"
| align="left" |Kicksey-Winsey -- [http://justpmf.com/romain/kicksey_winsey/ Kicksey-Winsey Home Page]||
|- align="center"
| align="left" |MFIX -- [https://mfix.netl.doe.gov Computational multiphase flow homepage]||
|- align="center"
| align="left" |[[NaSt2D-2.0]] -- [http://home.arcor.de/drklaus.bauerfeind/nast/eNaSt2DA.html NaSt2D-2.0 homepage]||
|- align="center"
| align="left" |[[NEK5000]] -- [http://nek5000.mcs.anl.gov NEK5000 homepage]||
|- align="center"
| align="left" |[[NSC2KE]] -- [http://www-rocq1.inria.fr/gamma/cdrom/www/nsc2ke/eng.htm NSC2KE homepage]||
|- align="center"
| align="left" |NUWTUN -- [http://nuwtun.berlios.de NUWTUN Home Page]||
|- align="center"
| align="left" |[[OpenFlower]] -- [http://sourceforge.net/projects/openflower/ OpenFlower homepage]||GMSH (.msh)
|- align="center"
| align="left" |[[OpenFOAM]] -- [http://www.openfoam.com/ OpenFOAM homepage]|| Internal "foam" format; convert from ansys, cfx4, dat, fluent3d, fluentMesh, gambit, gmsh, ideasUnv, kiva, msh, netgenNeutral, plot3d, samm, star3, star4, tetgen
|- align="center"
| align="left" |[[OpenLB]] -- [http://www.openlb.net/ OpenLB homepage]||
|- align="center"
| align="left" |OpenFVM -- [http://openfvm.sourceforge.net/ OpenFVM homepage]|| GMSH (.msh)
|- align="center"
| align="left" |PETSc-FEM -- [http://www.cimec.org.ar/petscfem PETSc-FEM homepage]|| Application-specific input (.dat)
|- align="center"
| align="left" |PP3D -- [http://www.featflow.de/ parpp3d++ homepage]||
|- align="center"
| align="left" |[[Semtex]] -- [http://users.monash.edu.au/~bburn/semtex.html Semtex homepage: 2D/3D spectral element/Fourier DNS]|| Unstructured quad meshes
|- align="center"
| align="left" |SLFCFD -- [http://slfcfd.sourceforge.net SLFCFD homepage]||
|- align="center"
| align="left" |[[SSIIM]] -- [http://folk.ntnu.no/nilsol/cfd/ CFD at NTNU]||
|- align="center"
| align="left" |[[SU2]] -- [http://su2.stanford.edu/ Stanford University Unstructured Homepage]|| Internal "su2" format and cgns format
|- align="center"
| align="left" |[[Tochnog]] -- [http://tochnog.sourceforge.net Tochnog homepage]||
|- align="center"
| align="left" |TYCHO -- [http://tycho-cfd.at/ TYCHO homepage]||
|- align="center"
| align="left" |Typhon solver -- [http://typhon.sf.net Typhon solver homepage]||
|- align="center"
| align="left" |Uintah Computational Framework -- [http://www.uintah.utah.edu Uintah homepage] || Structured
|- align="center"

|}

=== Grid generation ===
{| class="wikitable"
|- align="center"
! Generator !! Mesh type(s) supported !! Input filetypes supported
|- align="center"
| align="left" |[[Delaundo]] -- [http://www.cerfacs.fr/~muller/delaundo.html Delaundo homepage]||.pts
|- align="center"
| align="left" | Engrid -- [http://engrid.sourceforge.net Engrid homepage]||
|- align="center"
| align="left" | GMSH -- [http://www.geuz.org/gmsh/ GMSH hompage]||.msh
|- align="center"
| align="left" | gridgen -- [http://code.google.com/p/gridgen-c gridgen homepage]||
|- align="center"
| align="left" | IA-FEMesh -- [http://www.ccad.uiowa.edu/mimx/IA-FEMesh IA-FEMesh homepage]||ABAQUS
|- align="center"
| align="left" | NETGEN -- [http://www.hpfem.jku.at/netgen/ NETGEN homepage]|| Neutral, Fepp2D, surfacemesh, solution||.stl, .iges, .csg, .step
|- align="center"
| align="left" | SALOME -- [http://www.salome-platform.org SALOME homepage]||MED, UNV, DAT, STL ||IGES, STEP, BREP
|- align="center"
| align="left" | TETGEN -- [http://tetgen.berlios.de/ TETGEN hompage]||.off, .mesh, .smesh, .ele||.node, .poly, .off, .stl, .mesh, .smesh, .ply
|- align="center"
| align="left" |[[Triangle]] -- [http://www.cs.cmu.edu/~quake/triangle.html Triangle homepage]||(2D only) .node, .ele, .poly, .area
|}

=== Visualization ===
*[[DISLIN]] -- [http://www.mps.mpg.de/dislin/server.html DISLIN homepage]
* GMV -- [http://www-xdiv.lanl.gov/XCM/gmv/ GMV homepage]
*[[Gnuplot]] -- [http://www.gnuplot.info/ gnuplot homepage]
* GRI -- [http://gri.sourceforge.net/ GRI homepage]
*[[Mayavi]] -- [http://mayavi.sourceforge.net/ MayaVi homepage]
*[[OpenDX]] -- [http://www.opendx.org OpenDX homepage]
*[[ParaView]] -- [http://www.paraview.org/HTML/Index.html ParaView homepage]
*[[Tioga]] -- [http://www.kitp.ucsb.edu/~paxton/tioga.html Tioga homepage]
*[[VAPOR]] -- [http://www.vapor.ucar.edu VAPOR homepage]
*[[Vigie]] -- [http://www-sop.inria.fr/sinus/Softs/vigie.html Vigie homepage]
*[[Visit]] -- [http://www.llnl.gov/visit Visit homepage]
*[[vtk]] -- [http://www.vtk.org vtk homepage]
*[[vtk.Net]] -- [http://vtkdotnet.sourceforge.net/ vtk.Net homepage]

=== Miscellaneous ===

*[[Engauge Digitizer]] -- [http://digitizer.sourceforge.net Engauge Digitizer homepage]
*[[Ftnchek]] -- [http://www.dsm.fordham.edu/~ftnchek/ ftnchek homepage]
*[[g3data]] -- [http://www.frantz.fi/software/g3data.php g3data homepage]
* GIFMerge -- [http://www.the-labs.com/GIFMerge/ GIFMerge homepage]
*[[Gifsicle]] -- [http://www.lcdf.org/~eddietwo/gifsicle/ Gifsicle homepage]
*[[ImageMagick]] -- [http://www.imagemagick.org ImageMagick homepage]
* nnbathy (natural neighbor interpolation) -- [http://code.google.com/p/nn-c/ nnbathy home page]
*[[OpenPALM]] -- [http://www.cerfacs.fr/globc/PALM_WEB OpenPALM homepage]
* [[OpenGPI]] (Generic Parameter Interface) -- [http://www.opengpi.org OpenGPI homepage]

== Commercial codes ==

=== Solvers ===
* 6sigmaDC -- [http://www.futurefacilities.com Future Facilities homepage]
* Applied Computational Fluid Dynamics -- [http://www.partenovcfd.com Solver homepage]
* AcuSolve -- [http://www.acusim.com/ ACUSIM Software's homepage]
* ADINA-F -- [http://www.adina.com/index.html ADINA's homepage]
* ADINA-FSI -- [http://www.adina.com/index.html ADINA's homepage]
* ANANAS -- [http://www.lemma-ing.com/index.html LEMMA's homepage]
* ANSWER -- [http://www.acricfd.com/ ACRi's homepage]
* Azore -- [http://www.azoretechnologies.com Azore Technologies, LLC homepage]
*[http://www.cfd-online.com/W/index.php?title=CFD%2B%2B CFD++] -- [http://www.metacomptech.com Metacomp Techonlogies' homepage]
* CFD2000 -- [http://www.adaptive-research.com/ Adaptive Research's homepage]
*[[CFD-FASTRAN]] -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]
* CFD-ACE -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]
* CFdesign -- [http://www.cfdesign.com CFdesign's homepage]
* CFX -- [http://www.ansys.com/ ANSYS homepage]
* CharLES -- [http://www.cascadetechnologies.com/ Cascade Technologies homepage]
* COMSOL Multiphysics -- [http://www.comsol.com/ COMSOL's homepage]
* COMSOL Multiphysics CFD Module -- [http://www.comsol.com/products/cfd/ COMSOL's CFD Module]
* Coolit -- [http://www.daat.com/ Daat Research's Coolit homepage]
* CoolitPCB -- [http://www.coolitpcb.com/ Daat Research's CoolitPCB homepage]
* DLR - TAU -- [http://tau.dlr.de/ TAU's homepage]
* DQMoM -- [http://www.cmclinnovations.com/userstories/userstory9.html cmcl innovations' product page]
* EasyCFD -- [http://www.easycfd.net EasyCFD homepage]
*[[FENSAP-ICE]] -- [http://www.newmerical.com/ NTI' homepage]
* FINE/Hexa -- [http://www.numeca.be/ Numeca's homepage]
* FINE/Turbo -- [http://www.numeca.be/ Numeca's homepage]
* FIRE -- [http://www.avl.com/ AVL's homepage]
*[[FLACS]] -- [http://www.gexcon.com/index.php?src=flacs/overview.html GexCon's homepage]
* FloEFD -- [http://www.mentor.com/products/mechanical/products/floefd Mentor's FloEFD homepage]
* FloTHERM-- [http://www.mentor.com/products/mechanical/products/flotherm Mentor's FloTHERM homepage]
* FloVENT-- [http://www.mentor.com/products/mechanical/products/flovent Mentor's FloVENT homepage]
* FLOW-3D -- [http://www.flow3d.com/ Flow Science's homepage]
* FLOWVISION -- [http://www.fv-tech.com FlowVision's homepage]
* Flowz--[http://www.zeusnumerix.com Zeus Numerix's homepage ]
*[[FLUENT]] -- [http://www.fluent.com Fluent's homepage]
* [[FLUIDYN]] -- [http://www.fluidyn.com Fluidyn's homepage]
* FluSol -- [http://www.cfd-rocket.com FluSol's hompage]
* GASP-- [http://www.aerosoftinc.com AeroSoft homepage]
*[[J-FLO]] -- [http://www.newmerical.com NTI's homepage]
* Kameleon FireEx - KFX -- [http://www.computit.com ComputIT's homepage]
* KINetics Reactive Flows -- [http://www.ReactionDesign.com Reaction Design's homepage]
* KIVA--[http://www.lanl.gov/orgs/t/t3/codes/kiva.shtml Los Alamos homepage]
*[[NOGRID FPM]] -- [http://www.no-grid.com NOGRIDS's homepage]
* NX Electronic Systems Cooling -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=69&Itemid=237 MAYA's NX ESC page]
* NX Advanced Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=1&Itemid=115 MAYA HTT's NX Adv. Flow page]
* NX Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=2&Itemid=116 MAYA HTT's NX Flow page]
* MicroFlo -- [http://www.iesve.com/Software/VE-Pro/MicroFlo homepage]
*[[PHOENICS]] -- [http://www.cham.co.uk CHAM's homepage]
*[[PHYSICA]] -- [http://physica.co.uk PHYSICA's homepage]
* PowerFLOW -- [http://www.exa.com/pages/pflow/pflow_main.html Exa PowerFLOW homepage]
* PumpLinx -- [http://www.simerics.com Simerics' homepage]
* Range Software -- [http://www.range-software.com Range' homepage]
*[[RheoChart]] -- [http://www.rheochart.com RheoChart Homepage]
* [[Siemens PLM Software CFD]] -- [http://www.plm.automation.siemens.com/en_us/products/nx/simulation/advanced/index.shtml Siemens PLM Software NX CAE page]
*[[Smartfire]] -- [http://fseg.gre.ac.uk/smartfire Smartfire Homepage]
* [[Solution of Boltzmann Equation]] -- [http://www.elegant-mathematics.com/ Elegant Mathematics homepage]
*[[SPLASH]] -- [http://www.panix.com/~brosen SPLASH's homepage]
*[[srm suite]] -- [http://www.cmclinnovations.com/products/srmsuite cmcl innovations' product page]
* STALLION 3D -- [http://www.hanleyinnovations.com/stallion3d.html Hanley Innovations' STALLION 3D homepage]
*[[STAR-CD]] -- [http://www.cd-adapco.com CD-adapco's homepage]
*[[STAR-CCM+]] -- [http://www.cd-adapco.com CD-adapco's homepage]
*[[Tdyn]] -- [http://www.compassis.com CompassIS' homepage]
* TMG-Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=82&Itemid=283 MAYA HTT's CFD page]
* Turb'Flow -- [http://www.fluorem.com Fluorem's hompage]
* TURBOcfd -- [http://adtechnology.co.uk/products/turbocfd/ TURBOcfd's hompage]

=== Grid generation ===

* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]
* ANAMESH -- [http://www.lemma-ing.com/index.html LEMMA's homepage]
* ANSA -- [http://www.beta-cae.gr/ BETA-CAE's homepage]
* AutoMesh4G -- [http://www.numeca.be/ Numeca's homepage]
* [[BOXERMesh]] -- [http://www.cambridgeflowsolutions.com/ Cambridge Flow Solutions homepage]
* Centaur -- [http://www.centaursoft.com CentaurSoft homepage]
*[[CFD-GEOM]] -- [http://www.esi-group.com/ ESI's homepage]
*[[CFD-VISCART]] -- [http://www.esi-group.com/ ESI's homepage]
* CFDExpert-GridZ --[http://www.zeusnumerix.com/ Zeus Numerix's homepage]
*[[Cubit]] -- [http://www.csimsoft.com/ csimsoft's homepage]
*[[Gridgen]] -- [http://www.pointwise.com/ Pointwise's homepage]
*[[ GridPro]] -- [http://www.gridpro.com/ PDC's homepage]
* Harpoon -- [http://www.sharc.co.uk/ Harpoon's homepage]
* HyperMesh -- [http://www.altairhyperworks.com/ Altair HyperWorks' homepage]
* ICEM CFD -- [http://www.ansys.com/ ANSYS' homepage]
*[[Pointwise]] -- [http://www.pointwise.com/ Pointwise's homepage]
*[[RBF Morph]] -- [http://www.rbf-morph.com/ RBF Morph homepage]
* +ScanFE -- [http://www.simpleware.com/ Simpleware's homepage]
* SolidMesh -- [http://www.simcenter.msstate.edu/docs/solidmesh/ SolidMesh homepage]
* Tommie -- [http://www.cascadetechnologies.com/ Cascade Technologies homepage]

=== Visualization ===

* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]
*[[CFD-VIEW]] -- [http://www.esi-group.com/ ESI's homepage]
* CFView -- [http://www.numeca.be/ Numeca's homepage]
* CFX-Post -- [http://www.ansys.com/ ANSYS' homepage]
* COMSOL -- [http://www.comsol.com/ COMSOL's homepage]
* CoolPlot -- [http://www.daat.com/ Daat Research's homepage]
* COVISE -- [http://www.visenso.de/ Visenso's homepage]
* EnSight -- [http://www.ensight.com/ CEI's homepage]
* Fieldview -- [http://www.ilight.com/ Intelligent Light's homepage]
* HyperView -- [http://www.altairhyperworks.com/ Altair HyperWorks' homepage]
*[[Tecplot]] -- [http://www.tecplot.com/ Tecplot's homepage]
* VU -- [http://www.invisu.ca/ inVisu's homepage]
*ViewZ -- [http://www.zeusnumerix.com/ Zeus Numerix's homepage]

=== Systems ===

* ADINA -- [http://www.adina.com/index.html ADINA's homepage]
* FINE/Design3D -- [http://www.numeca.be/ Numeca's homepage]
* Flowmaster -- [http://www.flowmaster.com/index.html Flowmaster's homepage]
* Flownex -- [http://www.flownex.com/ Flownex's homepage]

O-PALM

2011-07-27T21:45:40Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

- first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

- based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name OpenPALM.

== External Web Links ==
[http://www.cerfacs.fr/globc/PALM_WEB OpenPALM homepage]

[http://www.cerfacs.fr/globc/PALM_WEB/EN/BECOMEAUSER/instructions.html OpenPALM download page]

Fluid-structure interaction

2011-07-27T21:44:43Z

Florent:

Fluid-structure interaction (FSI) simulations are coupled CFD (fluids) and [[FEM]] (mechanics) cases. FSI is a part of [[mulitphysics simulations]] and an actual main focus in CFD development. As these solvers use different methods and codes, the transfer of the boundary conditions at the interface is an important feature of an FSI solution.

== Coupling ==
=== 1-way FSI ===
1-way FSI typically describes the pure mapping of physical properties resulting from the analysis of a CFD-/FE-model to another FE-model. The two models typically do not rely on matching meshes (e.g. mapping aerodynamic pressure distribution onto a structural Finite Element model). However in the case of 1-way FSI the mapping of the physical properties does not include the modification of any of the meshes.

=== 2-way FSI ===
In the case of 2-way FSI the mapping is done in an iterative loop i.e. the results of the first model are mapped to the second model and these results are mapped back to the first model and so on until convergence is found or the process is stopped manually. Very often in the case of 2-way FSI one of the mapping steps involves the modification/morphing of the mesh of one or both of the models (e.g. mapping deformations coming from aerodynamic loads back to the CFD-model and re-evaluating the CFD-model in the deformed configuration).

== Mesh Morphing ==
In most cases FSI is quite simple to realize even employing meshes not matching. However as soon as mesh-morphing is needed the whole process gets much more difficult and only few software solutions are around that can handle this. They key-problems with mesh-morphing are:

* Performance: Typical CFD-models as employed today in Formula 1 or Aerospace require very efficient morphing algorithms. A lot of the straight-forward approaches are not able to handle CFD-models consisting of several millions of cells.
* Surface Quality: For calculating pressure distributions in aerodynamics the surface quality in terms of continuity has to be quite high. Otherwise one starts to observe oscillations in the pressure fields. This is namely a challenge in the case where the mesh providing the deformation (typically the structural FE-mesh) is significantly coarser then the surface mesh of the CFD-model (which is quite common).

== Applications ==

* Biomechanical Engineering
* Airfoil Aerodynamics
* Aero-elasticity

== Commercial codes ==
*[http://www.adina.com/fluid-structure-interaction.shtml ADINA FSI homepage]
*[http://www.ansys.com/solutions/fsi.asp Ansys' FSI homepage]
*[http://www.even-ag.ch/index.php/software/colyx CoLyX - FSI and mesh-morphing from EVEN - Evolutionary Engineering AG]
*[http://www.mscsoftware.com/Products/CAE-Tools/Dytran.aspx MSC.Software Dytran]

== Open Source codes ==
*[http://www.cerfacs.fr/globc/PALM_WEB/EN/APPLICATIONS/gallery.html - OpenPALM]

{{stub}}

O-PALM

2011-02-03T08:29:12Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

- first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

- based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

== External Web Links ==
[http://www.cerfacs.fr/globc/PALM_WEB O-PALM homepage]

[http://www.cerfacs.fr/globc/PALM_WEB/EN/BECOMEAUSER/instructions.html O-PALM download page]

O-PALM

2011-02-03T08:28:56Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

- first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

- based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

== External Web Links ==
[http://www.cerfacs.fr/globc/PALM_WEB O-PALM homepage]
[http://www.cerfacs.fr/globc/PALM_WEB/EN/BECOMEAUSER/instructions.html O-PALM download page]

O-PALM

2011-02-03T08:26:59Z

Florent:

O-PALM

2011-02-03T08:26:42Z

Florent:

O-PALM

2011-02-03T08:26:17Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:26:05Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:25:45Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

== Headline text ==
1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:25:17Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

<nowiki>1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.</nowiki>

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:24:48Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:24:08Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

[[Image:Example.jpg]]1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:23:39Z

Florent:

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:

1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.

2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

O-PALM

2011-02-03T08:22:52Z

Florent: New page: At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR. The head of the MERCATOR project of the time, Philippe Courtier, su...

At the origin of the PALM project, if we go as back as 1996, we find the operational ocean forecasting project MERCATOR.
The head of the MERCATOR project of the time, Philippe Courtier, suggested that a data assimilation suite could be designed and implemented as a coupling. The different tasks - running a forecast, apply the observation operator, computing the misfit, approximate the error statistics, invert matrices, minimize a cost function and so on - were to be thought of as independent pieces of code to be assembled within a portable, flexible and efficient framework. Since most of the data assimilation algorithms can be implemented as a different sequence of the same functional units (cf. Lagarde, Piacentini, Thual, A new representation of data assimilation methods: the PALM flow charting approach, Q.J.R.M.S., 127 (2001), 189-207), this approach was the most suitable for a research and development context, where many methods were to be implemented and compared.

The PALM Team at CERFACS was in charge of the development of the software backbone of the project. It was a technological challenge: to develop a dynamic parallel coupler and its user interface that had to be used on a variety of platforms under the efficiency constraints of operational applications.
Such a challenging task was carried on in two steps:
1) first a fully featured prototype was implemented using the available technology at the end of the 90's. At the issue of this phase an MPI1 based version of the coupler was released with the name PALM_RESEARCH afterwards changed to PALM_SP.
2) based on the expertise developed on the prototype, the final MPI2 based version of PALM was designed and implemented. It was released with the name PALM MP.

Thanks to the flexibility of the approach, the non-specific formalism used to describe the coupling interfaces and the portability of the software, PALM established itself as a natural choice for all sorts of dynamic parallel coupling and code assembling projects.
In particular, PALM has been adopted for a number of multiphysics simulations in computational fluid dynamics. To answer the requirements of the future multiphysics high performance simulations, PALM has integrated the CWIPI communication and interpolation library developed by ONERA.
To make this and any future collaboration easier, PALM is currently distributed as an open source application under the LGPL v3 license, with the name O-PALM.

Codes

2011-02-03T08:19:03Z

Florent: Add O-PALM

An overview of both free and commercial CFD software. Here you will find short descriptions of codes along with links to resources.

'''Note to contributers:''' Please try to keep descriptions short and to the point (approximately 200 words) and avoid long lists of features or capabilities. Also keep in mind that all contributions are considered to be released under the GNU Free Documentation License 1.2 (see [[Project:Copyrights]] for details). Also note that all information should be verifiable and objective truths that also competitors to the code in question will agree upon. This is especially important if you are an employee of the company selling the code. See the [[CFD-Wiki:Policy]] for further information.

== Free codes ==

This section lists codes that are in the public domain, and codes that are available under GPL, BSD or similar licenses.

=== Solvers ===
* ADFC -- [http://adfc.sourceforge.net/index.html ADFC homepage]
* Applied Computational Fluid Dynamics -- [http://www.partenovcfd.com Solver homepage]
* CFD2k -- [http://www.cfd2k.eu/ CFD2k: a 2D-solver for compressible ideal gases - homepage]
* Channelflow -- [http://www.cns.gatech.edu/channelflow/ Channelflow: a spectral Navier-Stokes simulator in C++ homepage]
* CLAWPACK -- [http://www.amath.washington.edu/~claw/clawpack.org CLAWPACK homepage]
* Code_Saturne -- [http://www.code-saturne.org/ Code_Saturne homepage]
* COOLFluiD -- [http://coolfluidsrv.vki.ac.be/coolfluid COOLFluiD homepage]
* Diagonalized Upwind Navier Stokes -- [http://duns.sourceforge.net DUNS homepage]
* [[Dolfyn]] -- [http://www.dolfyn.net/dolfyn/index_en.html dolfyn a 3D unstructured general purpose solver - homepage]
*[[Edge]] -- [http://www.foi.se/edge Edge homepage: 2D & 3D compressible RANS / Euler flow solver on unstructured and hybrid grids]
*[[ELMER]] -- [http://www.csc.fi/elmer/ ELMER homepage]
* [[FDS]] -- [http://www.fire.nist.gov/fds/ FDS homepage]
* Featflow -- [http://www.featflow.de Featflow homepage]
* Femwater -- [http://www.epa.gov/ceampubl/gwater/femwater/index.htm Femwater code]
* FreeFEM -- [http://www.freefem.org FreeFEM homepage]
*[[Gerris Flow Solver]] -- [http://gfs.sourceforge.net/ Gerris Flow Solver homepage]
* [[GPDE]] -- [http://www.gpde.net Discrete adjoint flow field computation | 2/3D FV, unstr, incomp, F90]
* IMTEK Mathematica Supplement (IMS) -- [http://www.imtek.uni-freiburg.de/simulation/mathematica/IMSweb/ IMTEK Mathematica Supplement (IMS) homepage]
* iNavier -- [http://inavier.sourceforge.net/ iNavier Solver Home Page]
* ISAAC -- [http://isaac-cfd.sourceforge.net ISAAC Home Page]
* Kicksey-Winsey -- [http://justpmf.com/romain/kicksey_winsey/ Kicksey-Winsey Home Page]
* MFIX -- [https://mfix.netl.doe.gov Computational multiphase flow homepage]
*[[NaSt2D-2.0]] -- [http://home.arcor.de/drklaus.bauerfeind/nast/eNaSt2DA.html NaSt2D-2.0 homepage]
*[[NEK5000]] -- [http://nek5000.mcs.anl.gov NEK5000 homepage]
*[[NSC2KE]] -- [http://www-rocq1.inria.fr/gamma/cdrom/www/nsc2ke/eng.htm NSC2KE homepage]
* NUWTUN -- [http://nuwtun.berlios.de NUWTUN Home Page]
*[[OpenFlower]] -- [http://sourceforge.net/projects/openflower/ OpenFlower homepage]
*[[OpenFOAM]] -- [http://www.openfoam.org/ OpenFOAM homepage]
*OpenLB -- [http://www.openlb.net/ OpenLB homepage]
* OpenFVM -- [http://openfvm.sourceforge.net/ OpenFVM homepage]
* PETSc-FEM -- [http://www.cimec.org.ar/petscfem PETSc-FEM homepage]
* PP3D -- [http://www.featflow.de/ parpp3d++ homepage]
* SLFCFD -- [http://slfcfd.sourceforge.net SLFCFD homepage]
*[[SSIIM]] -- [http://folk.ntnu.no/nilsol/cfd/ CFD at NTNU]
*[[Tochnog]] -- [http://tochnog.sourceforge.net Tochnog homepage]
* Typhon solver -- [http://typhon.sf.net Typhon solver homepage]

=== Grid generation ===
*[[Delaundo]] -- [http://www.cerfacs.fr/~muller/delaundo.html Delaundo homepage]
* GMSH -- [http://www.geuz.org/gmsh/ GMSH hompage]
* NETGEN -- [http://www.hpfem.jku.at/netgen/ NETGEN homepage]
* SALOME -- [http://www.salome-platform.org SALOME homepage]
* TETGEN -- [http://tetgen.berlios.de/ TETGEN hompage]
*[[Triangle]] -- [http://www.cs.cmu.edu/~quake/triangle.html Triangle homepage]
* gridgen -- [http://code.google.com/p/gridgen-c gridgen homepage]
* IA-FEMesh -- [http://www.ccad.uiowa.edu/mimx/IA-FEMesh IA-FEMesh homepage]
* Engrid -- [http://engrid.sourceforge.net Engrid homepage]

=== Visualization ===
*[[DISLIN]] -- [http://www.mps.mpg.de/dislin/server.html DISLIN homepage]
* GMV -- [http://www-xdiv.lanl.gov/XCM/gmv/ GMV homepage]
*[[Gnuplot]] -- [http://www.gnuplot.info/ gnuplot homepage]
* GRI -- [http://gri.sourceforge.net/ GRI homepage]
*[[Mayavi]] -- [http://mayavi.sourceforge.net/ MayaVi homepage]
*[[OpenDX]] -- [http://www.opendx.org OpenDX homepage]
*[[ParaView]] -- [http://www.paraview.org/HTML/Index.html ParaView homepage]
*[[Tioga]] -- [http://www.kitp.ucsb.edu/~paxton/tioga.html Tioga homepage]
*[[VAPOR]] -- [http://www.vapor.ucar.edu VAPOR homepage]
*[[Vigie]] -- [http://www-sop.inria.fr/sinus/Softs/vigie.html Vigie homepage]
*[[Visit]] -- [http://www.llnl.gov/visit Visit homepage]
*[[vtk]] -- [http://www.vtk.org vtk homepage]
*[[vtk.Net]] -- [http://vtkdotnet.sourceforge.net/ vtk.Net homepage]

=== Miscellaneous ===

*[[Engauge Digitizer]] -- [http://digitizer.sourceforge.net Engauge Digitizer homepage]
*[[Ftnchek]] -- [http://www.dsm.fordham.edu/~ftnchek/ ftnchek homepage]
*[[g3data]] -- [http://www.frantz.fi/software/g3data.php g3data homepage]
* GIFMerge -- [http://www.the-labs.com/GIFMerge/ GIFMerge homepage]
*[[Gifsicle]] -- [http://www.lcdf.org/~eddietwo/gifsicle/ Gifsicle homepage]
*[[ImageMagick]] -- [http://www.imagemagick.org ImageMagick homepage]
* nnbathy (natural neighbor interpolation) -- [http://code.google.com/p/nn-c/ nnbathy home page]
*[[O-PALM]] -- [http://www.cerfacs.fr/globc/PALM_WEB O-PALM homepage]

== Commercial codes ==

=== Solvers ===
* 6sigmaDC -- [http://www.futurefacilities.com Future Facilities homepage]
* EasyCFD -- [http://www.easycfd.net EasyCFD homepage]
* Applied Computational Fluid Dynamics -- [http://www.partenovcfd.com Solver homepage]
* AcuSolve -- [http://www.acusim.com/ ACUSIM Software's homepage]
* ADINA-F -- [http://www.adina.com/index.html ADINA's homepage]
* ADINA-FSI -- [http://www.adina.com/index.html ADINA's homepage]
* ANSWER -- [http://www.acricfd.com/ ACRi's homepage]
*[http://www.cfd-online.com/W/index.php?title=CFD%2B%2B CFD++] -- [http://www.metacomptech.com Metacomp Techonlogies' homepage]
* CFD2000 -- [http://www.adaptive-research.com/ Adaptive Research's homepage]
*[[CFD-FASTRAN]] -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]
* CFD-ACE -- [http://www.esi-group.com/SimulationSoftware/advanced.html ESI Group's homepage]
* CFdesign -- [http://www.cfdesign.com CFdesign's homepage]
* CFX -- [http://www.ansys.com/ ANSYS homepage]
* Coolit -- [http://www.daat.com/ Daat Research's Coolit homepage]
* CoolitPCB -- [http://www.coolitpcb.com/ Daat Research's CoolitPCB homepage]
* DLR - TAU -- [http://tau.dlr.de/ TAU's homepage]
* DQMoM -- [http://www.cmclinnovations.com/userstories/userstory9.html cmcl innovations' product page]
*[[FENSAP-ICE]] -- [http://www.newmerical.com/ NTI' homepage]
* FINE/Hexa -- [http://www.numeca.be/ Numeca's homepage]
* FINE/Turbo -- [http://www.numeca.be/ Numeca's homepage]
* FIRE -- [http://www.avl.com/ AVL's homepage]
*[[FLACS]] -- [http://www.gexcon.com/index.php?src=flacs/overview.html GexCon's homepage]
* COMSOL Multiphysics -- [http://www.comsol.com/ COMSOL's homepage]
* COMSOL Multiphysics CFD Module -- [http://www.comsol.com/products/cfd/ COMSOL's CFD Module]
* FloEFD -- [http://www.mentor.com/products/mechanical/products/floefd Mentor's FloEFD homepage]
* FloTHERM-- [http://www.mentor.com/products/mechanical/products/flotherm Mentor's FloTHERM homepage]
* FloVENT-- [http://www.mentor.com/products/mechanical/products/flovent Mentor's FloVENT homepage]
* FLOW-3D -- [http://www.flow3d.com/ Flow Science's homepage]
* FLOWVISION -- [http://www.fv-tech.com FlowVision's homepage]
*[[FLUENT]] -- [http://www.fluent.com Fluent's homepage]
* [[FLUIDYN]] -- [http://www.fluidyn.com Fluidyn's homepage]
* FluSol -- [http://www.cfd-rocket.com FluSol's hompage]
* Flowz--[http://www.zeusnumerix.com Zeus Numerix's homepage ]
* GASP-- [http://www.aerosoftinc.com AeroSoft homepage]
*[[J-FLO]] -- [http://www.newmerical.com NTI's homepage]
* Kameleon FireEx - KFX -- [http://www.computit.com ComputIT's homepage]
* KINetics Reactive Flows -- [http://www.ReactionDesign.com Reaction Design's homepage]
* KIVA--[http://www.lanl.gov/orgs/t/t3/codes/kiva.shtml Los Alamos homepage]
*[[NOGRID FPM]] -- [http://www.no-grid.com NOGRIDS's homepage]
* NX Electronic Systems Cooling -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=69&Itemid=237 MAYA's NX ESC page]
* NX Advanced Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=1&Itemid=115 MAYA HTT's NX Adv. Flow page]
* NX Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=2&Itemid=116 MAYA HTT's NX Flow page]
* MicroFlo -- [http://www.iesve.com/Software/VE-Pro/MicroFlo homepage]
*[[PHOENICS]] -- [http://www.cham.co.uk CHAM's homepage]
* PowerFLOW -- [http://www.exa.com/pages/pflow/pflow_main.html Exa PowerFLOW homepage]
* PumpLinx -- [http://www.simerics.com Simerics' homepage]
* Range Software -- [http://www.range-software.com Range' homepage]
*[[RheoChart]] -- [http://www.rheochart.com RheoChart Homepage]
* [[Siemens PLM Software CFD]] -- [http://www.plm.automation.siemens.com/en_us/products/nx/simulation/advanced/index.shtml Siemens PLM Software NX CAE page]
*[[Smartfire]] -- [http://fseg.gre.ac.uk/smartfire Smartfire Homepage]
* [[Solution of Boltzmann Equation]] -- [http://www.elegant-mathematics.com/ Elegant Mathematics homepage]
*[[SPLASH]] -- [http://www.panix.com/~brosen SPLASH's homepage]
*[[srm suite]] -- [http://www.cmclinnovations.com/products/srmsuite cmcl innovations' product page]
* STALLION 3D -- [http://www.hanleyinnovations.com/stallion3d.html Hanley Innovations' STALLION 3D homepage]
*[[STAR-CD]] -- [http://www.cd-adapco.com CD-adapco's homepage]
*[[STAR-CCM+]] -- [http://www.cd-adapco.com CD-adapco's homepage]
*[[Tdyn]] -- [http://www.compassis.com CompassIS' homepage]
* TMG-Flow -- [http://www.mayahtt.com/index.php?option=com_content&task=view&id=82&Itemid=283 MAYA HTT's CFD page]
* Turb'Flow -- [http://www.fluorem.com Fluorem's hompage]
* TURBOcfd -- [http://adtechnology.co.uk/products/turbocfd/ TURBOcfd's hompage]

=== Grid generation ===

* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]
* AutoMesh4G -- [http://www.numeca.be/ Numeca's homepage]
* Centaur -- [http://www.centaursoft.com CentaurSoft homepage]
*[[CFD-GEOM]] -- [http://www.esi-group.com/ ESI's homepage]
*[[CFD-VISCART]] -- [http://www.esi-group.com/ ESI's homepage]
* CFDExpert-GridZ --[http://www.zeusnumerix.com/ Zeus Numerix's homepage]
*[[Gridgen]] -- [http://www.pointwise.com/ Pointwise's homepage]
*[[ GridPro]] -- [http://www.gridpro.com/ PDC's homepage]
* Harpoon -- [http://www.sharc.co.uk/ Harpoon's homepage]
* ICEM CFD -- [http://www.ansys.com/ ANSYS' homepage]
* +ScanFE -- [http://www.simpleware.com/ Simpleware's homepage]
* ANSA -- [http://www.beta-cae.gr/ BETA-CAE's homepage]
* SolidMesh -- [http://www.simcenter.msstate.edu/docs/solidmesh/ SolidMesh homepage]
*[[RBF Morph]] -- [http://www.rbf-morph.com/ RBF Morph homepage]

=== Visualization ===

* ADINA-AUI -- [http://www.adina.com/index.html ADINA's homepage]
*[[CFD-VIEW]] -- [http://www.esi-group.com/ ESI's homepage]
* CFView -- [http://www.numeca.be/ Numeca's homepage]
* CFX-Post -- [http://www.ansys.com/ ANSYS' homepage]
* COMSOL -- [http://www.comsol.com/ COMSOL's homepage]
* CoolPlot -- [http://www.daat.com/ Daat Research's homepage]
* COVISE -- [http://www.visenso.de/ Visenso's homepage]
* EnSight -- [http://www.ensight.com/ CEI's homepage]
* Fieldview -- [http://www.ilight.com/ Intelligent Light's homepage]
*[[Tecplot]] -- [http://www.tecplot.com/ Tecplot's homepage]
* VU -- [http://www.invisu.ca/ inVisu's homepage]
*ViewZ -- [http://www.zeusnumerix.com/ Zeus Numerix's homepage]
* CFDsoft Viewer -- [http://www.cfdsoft.com/ CFDsoft Viewer homepage]

=== Systems ===

* ADINA -- [http://www.adina.com/index.html ADINA's homepage]
* FINE/Design3D -- [http://www.numeca.be/ Numeca's homepage]
* Flowmaster -- [http://www.flowmaster.com/index.html Flowmaster's homepage]
* Flownex -- [http://www.flownex.com/ Flownex's homepage]