Difference between revisions of "Main ContribSolvers"

From OpenFOAMWiki
(electromagnetics)
m (Solvers that fit into the OpenFOAM classification: added potentialWaveFoam)
Line 6: Line 6:
  
 
=== basic ===
 
=== basic ===
 +
* [[Contrib_potentialWaveFoam|potentialWaveFoam]]: A one-line solver that solves a wave equation, <tt>fvm::d2dt2(phi) == c * c * fvc::laplacian(phi)</tt>.
  
 
=== combustion ===
 
=== combustion ===

Revision as of 07:24, 17 February 2009

Contributed solvers

1 Solvers that fit into the OpenFOAM classification

These solvers fit into the classification, that is given by the directory structure of the solver-sources.

1.1 basic

  • potentialWaveFoam: A one-line solver that solves a wave equation, fvm::d2dt2(phi) == c * c * fvc::laplacian(phi).

1.2 combustion

  • reactingFoam Adding ignition to reactingFoam.
  • alternateReactingFoam A library and a solver based on it that allow the usage of different chemistry engines for reacting flows

1.3 compressible

1.4 DNSandLES

1.5 electromagnetics

  • EHDFoamAn Numerical Model to simulated the multiphase flow in the electricstatic filed based on the Taylor-Melcher Leaky Dielectric Model

1.6 financial

1.7 heat transfer

1.8 incompressible

  • simpleScalarFoam Steady-state incompressible laminar flow solver with scalar transport and mass transfer coefficient and Sherwood number calculation

1.9 multiphase

1.10 stressAnalysis

2 Other

These solvers don't fit into the standard scheme.

2.1 Turbulence Modeling

2.2 Technology Demos

Solvers that demonstrate concepts, but haven't got a fully implemented physics.

  • icoStructFoam Fluid-Structure interaction. Demonstrates the use of two coupled solvers and mesh motion
  • interTrackFoamTracks a moving interface with a moving mesh, so that the mesh boundary remains coincident with the interface.
  • solidParticleFoamA minimalistic code and case set-up as an example of how to use the solidParticleCloud class.

Note to editors: Use the solver name as the page name, when adding a new solver to this page, but prepend custom in order to avoid name clashes