| ... | @@ -24,6 +24,14 @@ Pre-compiled binaries are currently available for the following systems: |
... | @@ -24,6 +24,14 @@ Pre-compiled binaries are currently available for the following systems: |
|
|
| [Windows](/precompiled/windows) |
|
|
| [Windows](/precompiled/windows) |
|
|
|
| [Docker](/precompiled/docker) |
|
|
| [Docker](/precompiled/docker) |
|
|
|
|
|
|
|
|
|
|
|
|
|
 The packages do ***not*** contain
|
|
|
|
_visualization_ (eg, ParaView/runTimePostProcessing) or
|
|
|
|
_external-solver_ (eg, PETSc) modules: <br/>
|
|
|
|
see the [corresponding **FAQ**](/precompiled/#frequently-asked-questions)
|
|
|
|
|
|
|
|
----
|
|
|
|
|
|
|
Ubuntu and openSUSE generally receive first attention:
|
|
Ubuntu and openSUSE generally receive first attention:
|
|
|
|
|
|
|
|
1. Ubuntu is a very popular distribution with OpenFOAM users.
|
|
1. Ubuntu is a very popular distribution with OpenFOAM users.
|
| ... | @@ -156,10 +164,48 @@ reference purposes, and to help when scripting: |
... | @@ -156,10 +164,48 @@ reference purposes, and to help when scripting: |
|
|
| Docker | | [run script][run-script] |
|
|
| Docker | | [run script][run-script] |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Frequently Asked Questions
|
|
|
|
|
|
|
|
- <em>I like using cfMesh, is it included in the precompiled packages?</em><br/>
|
|
|
|
Yes it is included.
|
|
|
|
|
|
|
|
- <em>Why isn't ParaView included in the precompiled packages?
|
|
|
|
This would be much more convenient than having to compile it myself!</em><br/>
|
|
|
|
Some more details are given in
|
|
|
|
[modules/visualization](/modules/visualization), but essentially
|
|
|
|
the paraview version distributed with the operating system or a
|
|
|
|
[newer binary package][link paraview] is likely
|
|
|
|
[fully adequate for your needs][faq paraview].
|
|
|
|
We would prefer to focus on extending and improving the OpenFOAM
|
|
|
|
support in ParaView/VTK directly since this provides the best
|
|
|
|
long-term and most universal solution.
|
|
|
|
|
|
|
|
- <em>So a binary download of paraview makes sense,
|
|
|
|
but runTimePostProcessing (or Catalyst) will work with that?</em><br/>
|
|
|
|
There is unfortunately no easily achievable and unique solution
|
|
|
|
that will satisfy all user requirements (eg, llvm pipelines,
|
|
|
|
virtual graphics, etc). Coping with this diversity is _exactly_
|
|
|
|
the reason that the visualization module was split off from the main
|
|
|
|
OpenFOAM source tree in the first place.
|
|
|
|
If you do have a good recipe for incorporating a reasonably flexible
|
|
|
|
packaged runTimePostProcessing or Catalyst, we would be happy to
|
|
|
|
incorporate that into our builds. Please use the regular issue
|
|
|
|
tracker.
|
|
|
|
|
|
|
|
- <em>Why is the external-solver (PETSc) module not included?</em><br/>
|
|
|
|
While this could make some sense, the default system installations
|
|
|
|
for PETSc may be using a different MPI (eg, mpich vs openmpi etc)
|
|
|
|
that would be incompatible with how OpenFOAM has been compiled.
|
|
|
|
The range of solver types included in a system installation of
|
|
|
|
PETSc may or may not correspond to your requirements.
|
|
|
|
|
|
|
----
|
|
----
|
|
|
|
|
|
|
|
Copyright (C) 2020-2021 OpenCFD Ltd.
|
|
Copyright (C) 2020-2022 OpenCFD Ltd.
|
|
|
|
|
|
|
|
[foam-repo]: https://develop.openfoam.com/Development/openfoam/
|
|
[foam-repo]: https://develop.openfoam.com/Development/openfoam/
|
|
|
[foam-issues]: https://develop.openfoam.com/Development/openfoam/-/issues
|
|
[foam-issues]: https://develop.openfoam.com/Development/openfoam/-/issues
|
|
|
[run-script]: https://develop.openfoam.com/packaging/containers/-/raw/main/openfoam-docker
|
|
[run-script]: https://develop.openfoam.com/packaging/containers/-/raw/main/openfoam-docker
|
|
|
|
|
|
|
|
[link paraview]: https://www.paraview.org/download/
|
|
|
|
[faq paraview]: https://discourse.paraview.org/t/i-want-to-visualize-my-openfoam-simulation-results-with-paraview-but-im-confused-which-version-should-i-use |
