OpenFOAM用户指南：个人学习与实践经验分享

流体计算软件

需积分: 50 7 浏览量更新于2024-07-16 收藏 3.42MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

cd ∼/ OpenFOA M

rm -rf OpenFOAM -2. 0.1

rm -rf user -2.0 .1

rm -rf ∼/. Ope n FOAM

Listing 7: Removing OpenFOAM

cd ∼/ OpenFOA M

ls -1

user -2.0. x

user -2.1. x

OpenFOAM -2.0. x

OpenFOAM -2.1. x

ThirdP arty -2.0. x

ThirdP arty -2.1. x

Listing 8: Content of ~/OpenFOAM

Another thing to remove is the entry in the .bashrc ﬁle in the home directory. Delete the line shown in

Listing 3.

3.6 Install several versions of OpenFOAM

It is possible to install several versions of OpenFOAM on the same machine. However due to the fact that Open-

FOAM relies on some environment variables some precaution is needed. See http://www.cfd-online.com/

Forums/blogs/wyldckat/931-advanced-tips-working-openfoam-shell-environment.html for detailed in-

formation about OpenFOAM and the Linux shell.

The most important fact about installing several versions of OpenFOAM is to keep the seperated.

4 Updating the repository release of OpenFOAM

4.1 Version management

OpenFOAM is distributed in two diﬀerent ways. There is the repository release that can be downloaded using

the Git repository. The version number of the repository release is marked by the appended x, e.g. OpenFOAM

2.1.x. This release is updated regularly and is in some ways a development release. Changes and updates are

released quickly, however, there is a larger possibility of bugs in this release. Because this release is updated

frequently an OpenFOAM installation of version 2.1.x on one system may or will be diﬀerent to another instal-

lation of version 2.1.x on an other system. Therefore, each installation has an additional information to mark

diﬀerent builds of OpenFOAM. The version number is accompanied by a hash code to uniquely identify the

various builds of the repository release, see Listing 9. Whenever OpenFOAM is updated and compiled anew,

this hash code gets changed. Two OpenFOAM installations are on an equal level, if the build is equal.

Build : 2.1. x -9 d344f6ac6a f

Listing 9: Complete version identiﬁcation of repository releases

Apart from the repository release there are also pack releases. These are upadated periodically in longer

intervals than the repository release. The version number of a pack release contains no x, e.g. OpenFOAM

2.1.1. In contrast to the repository release all installations of the same version number are equal. Due to the

longer release cycle the pack release is regarded to be less prone to software bugs.

There are several types of those releases. The are precompiled packages for widely used Linux distributions

(Ubuntu, SuSE and Fedora) and also a source pack. The source pack can be installed on any system on which

the source codes compile (usually all kinds of Linux running computers, e.g. high performance computing

clusters, or even computers running other operation systems, e.g. Mac OSX

or even Windows

See http://openfoamwiki.net/index.php/Howto_install_OpenFOAM_v21_Mac

See http://openfoamwiki.net/index.php/Tip_Cross_Compiling_OpenFOAM_in_Linux_For_Windows_with_MinGW

This oﬀering is not approved or endorsed by ESI® Group, ESI-OpenCFD® or the OpenFOAM®

Foundation, the producer of the OpenFOAM® software and owner of the OpenFOAM® trademark.

4.2 Check for updates

If OpenFOAM was installed from the repository release, updating is rather simple. To update OpenFOAM

simply use Git to check if there are newer source ﬁles available. Change in the Terminal to the root directory

of the OpenFOAM installation and execute git pull.

If there are newer ﬁles in the repository Git will download them and display a summary of the changed ﬁles.

user @ host :∼$ cd $ FOAM_INST_DIR

user @ host :∼/ Ope n FOAM$ cd OpenFO AM -2 .1. x

user @ host :∼/ Op e nFOAM / OpenFOAM -2.1 . x$ git pull

rem ote : Cou n ting o b jects : 67 , done .

rem ote : Compre s s ing obj ects : 100% (13 /13) , done .

rem ote : T otal 44 ( delta 32) , reused 43 ( delta 31)

Unpa c king objects : 100% (44/44) , done .

From git :// g ithub . com / Op e nFOAM / OpenFOAM -2.1. x

72 f00f7 ..21 ed37 f master -> origin / m aste r

Upda ting 72 f00f7 ..21 e d37f

Fast - f orward

.../ ext rude / e x t r u d e T o R e g i o n M e s h / c r eateShellMesh . C | 10 + -

.../ ext rude / e x t r u d e T o R e g i o n M e s h / c r eateShellMesh . H | 7 + -

.../ extrudeToRegionMesh / extrudeToRegionMesh . C | 157 ++++++++ - - - - -

.../ Temp l ates / Ki n e m a t i c Cloud / Kinematic C l o u d .H | 6 + -

.../ Temp l ates / Ki n e m a t i c Cloud / KinematicCl o u d I .H | 7 +

.../ baseC l a s ses / kinemat i c C l o u d / kinematicCloud .H | 47 ++++++ -

6 files changed , 193 ins e r tions (+) , 41 d e letions ( -)

Listing 10: There are updates available

If OpenFOAM is up to date, then Git will output a corresponding message.

user @ host :∼/ Op e nFOAM / OpenFOAM -2.1 . x$ git pull

Alr eady up -to - date .

Listing 11: OpenFOAM is up to date

4.3 Check for updates only

If you want to check for updates only, without actually making an update, Git can be invoked using a special

option (see Listings 12 and 13). In this case Git only checks the repository and displays its ﬁndings without

actually making any changes. The option responsible for this is --dry-run. Notice, that git fetch is called

instead of git pull

user @ host :∼$ cd OpenF O AM / OpenFOAM -2.0. x/

user @ host :∼/ Op e nFOAM / OpenFOAM -2.0 . x$ git fetc h -- dry - run -v

rem ote : Cou n ting o b jects : 189 , done .

rem ote : Compre s s ing obj ects : 100% (57 /57) , done .

rem ote : T otal 120 ( delta 89) , reused 93 ( delta 62)

Rece i ving objects : 100% (1 20/120) , 1 7.05 KiB , done .

Reso l ving deltas : 100% ( 89/89) , c omplete d with 56 local ob jects .

From git :// g ithub . com / Op e nFOAM / OpenFOAM -2.0. x

5 ae28 02 .. 97 cf67d m aster -> orig in / master

user @ host :∼/ Op e nFOAM / OpenFOAM -2.0 . x$

Listing 12: Check for updates only – updates available

user @ host :∼$ cd OpenF O AM / OpenFOAM -2.1. x/

user @ host :∼/ Op e nFOAM / OpenFOAM -2.1 . x$ git fetc h -- dry - run -v

From git :// g ithub . com / Op e nFOAM / OpenFOAM -2.1. x

= [ up to date ] mas ter -> o rigin / mas ter

user @ host :∼/ Op e nFOAM / OpenFOAM -2.1 . x$

Listing 13: Check for updates only – up to date

git pull calls git fetch to download the remote ﬁles and then calls git merge to merge the retrieved ﬁles with the local ﬁles.

So checking for updates is actually done by git fetch.

This oﬀering is not approved or endorsed by ESI® Group, ESI-OpenCFD® or the OpenFOAM®

Foundation, the producer of the OpenFOAM® software and owner of the OpenFOAM® trademark.

4.4 Install updates

After updates have been downloaded by git pull the changed source ﬁles need to be compiled in order to

update the executables. This is done the same way as is it done when installing OpenFOAM. Simply call

./Allwmake to compile. This script recognises changes, so unchanged ﬁles will not be compiled again. So,

compiling after an update takes less time than compiling when installing OpenFOAM.

4.4.1 Workﬂow

Listing 14 shows the necessary commands to update an existing OpenFOAM installation. However this applies

only for repository releases (e.g. OpenFOAM-2.1.x). The point releases (every version of OpenFOAM without

an x in the version number) are not updated in the same sense as the repository releases. For simplicity an update

of a point release (OpenFOAM-2.1.0 → OpenFOAM-2.1.1) can be treated like a complete new installation, see

Section 3.6.

The ﬁrst two commands in Listing 14 change to the directory of the OpenFOAM installation. Then the

latest source ﬁles are downloaded by invoking git pull.

The statement in red can be omitted. However if the compilation ends with some errors, this command

usually does the trick, see Section 4.5.2. The last statement causes the source ﬁles to be compiled. If wclean all

was not called before, then only the ﬁles that did change are compiled. If wclean all was invoked then

everything is compiled. This may or will take much longer.

If there is enough time for the update (e.g. overnight), then wclean all should be called before compiling.

This will in most cases make sure that compilation of the updated sources succeeds.

cd $ F O A M _ I N ST_DIR

cd OpenFOAM - 2.1. x

git pull

wclean all

./ Allw make

Listing 14: Update an existing OpenFOAM installation. The complete workﬂow

4.4.2 Trouble-shooting

If compilation reports some errors it is helpful to call ./Allwmake again. This reduces the output of the

successful operations considerably and the actual error messages of the compiler are easier to ﬁnd.

4.5 Problems with updates

4.5.1 Missing packages

If there has been an upgrade of the operating system

it can happen, that some relevant packages have been

removed in the course of the update (e.g. if these packages are only needed to compile OpenFOAM and the OS

’thinks’ that these packages aren’t in use). Consequently, if recompiling OpenFOAM fails after an OS upgrade,

missing packages can be the cause.

4.5.2 Updated Libraries

When libraries have been updated, they have to be recompiled. Otherwise solvers would call functions that are

not (yet) implemented. In order to avoid this problem the corresponding library has to be recompiled.

wcl ean all

Listing 15: Prepare recompilation with wclean

The brute force variant would be, to recompile OpenFOAM as a whole, instead of recompiling a updated

library.

An upgrade of an OS is indicated by a higher version number of the same (Ubuntu 11.04 → Ubuntu 11.10). An update leaves

the version number unchanged.

This oﬀering is not approved or endorsed by ESI® Group, ESI-OpenCFD® or the OpenFOAM®

Foundation, the producer of the OpenFOAM® software and owner of the OpenFOAM® trademark.

4.5.3 Updated sources fail to compile

In some cases, e.g. when there were changes in the organisation of the source ﬁles, the sources fail to compile

right away. Or, if there is any other reason the sources won’t compile and the cause is not found, then a complete

recompilation of OpenFOAM may be the solution of choice. Although compiling OpenFOAM takes its time,

this may take less time than tracking down all errors.

To recompile OpenFOAM the sources need to be reset. Instead of deleting OpenFOAM and installing it

again, there is a simple command that takes care of this.

git clean - dfx

Listing 16: Reset the sources using git

The command listed in Listing 16 causes git to erase all ﬁles git does not track. That means all ﬁles that

are not part of the git-repository are deleted. In this case, this is the oﬃcial git-repository of OpenFOAM. git

clean removes all ﬁles that are not under version control recursively starting from the current directory. The

option -d means that also untracked folders are removed.

After the command from Listing 16 is executed, the sources have to be compiled as described in Section 3.3.

4.5.4 Own code fails to run

Updating your repository release of OpenFOAM leads to interesting eﬀects. When libraries of OpenFOAM are

updated, their implementation might change. Even if the updated code is fully compatible with the previous

one, the compiled libaries might look diﬀerent after the update. Thus, even if the update maintains code-

compatibility

, the update might break binary compatibility. Thus, a recompilation of your own code following

the update of the underlying OpenFOAM installation is required.

Lost binary compatibility after an update of OpenFOAM leads to segmentation faults when loading a library

with lost binary compatibility. This happens because our own solvers dynamically load the required libraries of

OpenFOAM at start-up and the memory layout of certain objects of the library has changed since the update.

See the following resources for further information on this topic:

• https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B

• https://en.wikipedia.org/wiki/Binary_code_compatibility

• https://en.wikipedia.org/wiki/Source_code_compatibility

Losing binary compatibility happens not after every update, and it also does not happen to every library.

Thus, you may encounter such problems long after the update, and after you successfully used other solvers

and libraries of your creation. Thus, the source of the issues described in this Section may not be immediately

clear to the user. Thus, if your code suddenly fails to run properly for no good reason, recomile and see what

happens.

5 Install third-party software

The software presented in this section is optional. Without this software OpenFOAM is complete and perfectly

useable. However, the software mentioned in this section can be very useful for speciﬁc tasks.

5.1 Install pyFoam

See http://openfoamwiki.net/index.php/Contrib_PyFoam#Installation for the instructions on the instal-

lation of pyFoam.

5.2 Install swak4foam

See http://openfoamwiki.net/index.php/Contrib/swak4Foam for instructions on installing swak4foam.

This is the general behaviour of an update. In an ideal world only newer versions are allowed to introduce incompatibility.

This oﬀering is not approved or endorsed by ESI® Group, ESI-OpenCFD® or the OpenFOAM®

Foundation, the producer of the OpenFOAM® software and owner of the OpenFOAM® trademark.

剩余299页未读，继续阅读

cainiao_10

粉丝: 0
资源: 3

OpenFOAM用户指南：个人学习与实践经验分享

OpenFoam用户手册（中文翻译版）

OpenFOAM编程指南中文版

User_Manual_for_Using_OpenOCD_v0.02.doc

pfm_test.csv

为什么出现[Errno 2] No such file or directory: 'pfm_train.csv'

ref_depth_est = read_pfm(os.path.join(out_folder, 'depth_est/{:0>8}.pfm'.format(ref_view)))[0]

生成图片的pfm格式

PWM PFM控制器

ssh -l pfm

llc谐振变换器工作原理

LLC谐振变换器原理

单目深度估计中的.pfm文件是干什么的

max7219点阵屏fpga

基于stc11f04e编写一个用电位器控制输出PFM的程序

最新资源