[hani]

It is our pleasure to announce the release of the foam-extend-3.1 code.

The code is available here:
https://sourceforge.net/p/openfoam-e...i/master/tree/
Descriptions are available here:
http://sourceforge.net/p/openfoam-extend/wiki/Home/
A simpler URL brings also brings you directly to the foam-extend-project:
http://foam-extend.org/

The release notes are available here:
http://sourceforge.net/p/openfoam-ex...leaseNotes.txt
(In $WM_PROJECT_DIR/ReleaseNotes.txt)

Installation instructions can be found here:
https://sourceforge.net/p/openfoam-e...dInstructions/
(In $WM_PROJECT_DIR/doc/buildInstructions)
Report installation problems. See BUG REPORTS below.
Contribute with additional build instructions. See BUG REPORTS below.
Run the testHarness, following the instructions in $WM_PROJECT_DIR/testHarness/README.txt. Report fails, including URL to test results. See BUG REPORTS below.

The foam-extend workflow:
The master branch is updated with bug fixes, but no new features – stable.
The nextRelease branch is updated both with bug fixes and new features – semi-stable.
The installation instructions are for the master branch.

You are encouraged to continuously contribute to the nextRelease branch according to the instructions at:
https://sourceforge.net/p/openfoam-e...wToContribute/

BUG REPORTS:
Report bugs in the bug-tracker:
http://sourceforge.net/p/openfoam-ex...extendrelease/
Give an URL to testHarness fails, if applicable.
Paste a patch for small bug fixes or feature additions (see https://sourceforge.net/p/openfoam-e...wToContribute/)

The foam-extend administrators.

[gschaider]

Originally Posted by hani

BUG REPORTS:
Report bugs in the Mantis bug-tracker:
http://sourceforge.net/apps/mantisbt/openfoam-extend
Give an URL to testHarness fails, if applicable.
Paste a patch for small bug fixes or feature additions (see https://sourceforge.net/p/openfoam-e...wToContribute/)

What Hakan didn't know at the time of writing: the Mantis-Bug-Tracker will be discontinued in the next day by Sourceforge. Nevertheless: keep using it. Sourceforge will provide a backup which will be used to set up the new bug-tracker. All data entered into Mantis will be available there (with a slightly different user interface). Bug numbers will be the same

Once the new bug-tracker is up an announcement here will follow. But let me repeat: data entered into the current Bug-Tracker will not be lost

For clarification: this is only about the Mantis bug-tracker for the openfoam-extend on SourceForge. The Mantis bug-tracker for OpenFOAM provided by OpenCFD is unaffected

[gschaider]

Originally Posted by gschaider

What Hakan didn't know at the time of writing: the Mantis-Bug-Tracker will be discontinued in the next day by Sourceforge. Nevertheless: keep using it. Sourceforge will provide a backup which will be used to set up the new bug-tracker. All data entered into Mantis will be available there (with a slightly different user interface). Bug numbers will be the same

Once the new bug-tracker is up an announcement here will follow. But let me repeat: data entered into the current Bug-Tracker will not be lost

For clarification: this is only about the Mantis bug-tracker for the openfoam-extend on SourceForge. The Mantis bug-tracker for OpenFOAM provided by OpenCFD is unaffected

The new bug-tracker is now online at https://sourceforge.net/p/openfoam-e...extendrelease/ The bugs from Mantis have been migrated to it

[ngj]

Thank you all for the effort.

I have just completely the compilation process, and it was just a matter of executing the Allwmake-script. I feel that it is getting easier every time - even waves2Foam compiled straight out of the box with no additions needed.

Kind regards

Niels

[hani]

Thanks Niels,

We did run through the compilation process on many architectures during the testing, and we did fix some issues. The more people who help us test, the more issues are resolved.

Håkan

[jhoepken]

I just wanted to follow Niels and say that I've successfully completed building foam-extend-3.1 on my Mac, running OS X 10.9 using "standard" gcc (4.2). I'll give gcc-4.8 a try later on.

Thanks for all your work!

[egp]

I compiled foam-extend-3.1 on several different Macs (desktop imac and MacBookPro) and found the 1.6-ext instructions on the openfoamwiki by Bernhard Grieser to work very well:

http://openfoamwiki.net/index.php/In...enFOAM-1.6-ext

Only modifications are to pull extend-3.1, and ignore the patches (no need since they are in the repo).

[Linse]

I am just in the process of compiling on Fedora 17. Up to now I have read some adventurous spelling in warning messages (e.g. grovvyBC instead of groovyBC) and quite some messages of the "could not open"-type during swak4foam-compilation, which did not yet stop compilation. I will report, if compilation fails.

Just one thing which would avoid quizzed looks: Please change the instruction for the read-only git-download on Sourceforge to end up in the file foam/foam-extend-3.1, as this is the standard location required in Allwmake.firstInstall .

Cheers,
Bernhard

Edit1: It seems the compilation completed successfully. Testharness to be run...

[hani]

We are working on even better installation instructions.

It seems like it is not possible to change that information directly in SourceForge. It is automatically generated.

Bernhard Gschaider has to answer anout GroovyBC and swak4Foam. If it compiles it should be fine, I guess. But the error messages should be minimized.

[ngj]

Good evening,

Just to share my two cents on (some) of the error messages in the compilation of swak4Foam. There is e.g. an error message as follows:

could not open file mappedFvPatch.H for source file plugins/FieldValuePluginFunction.C

On inspection, it is seen that the specific file mappedFvPatch.H is present in e.g. OF2.3.0, but not in foam-extend-3.1, so this particular error message and likely quite some others "missing" files is due to cross-version compatibility of swak4Foam.

I have seen the same type of warnings with the compilation of waves2Foam across multiple versions of OF, and I suspect that the creation of the dependency list (somewhere in wmake/src/wmkdependParser.cpp) neglects of pre-processor statements, which is needed to allow for cross-version compatibility. So for these specific type of errors, I am afraid that a revision of wmake and the creation of the dependency list is needed.

Kind regards,

Niels

[gschaider]

Originally Posted by ngj

Good evening,

Just to share my two cents on (some) of the error messages in the compilation of swak4Foam. There is e.g. an error message as follows:

could not open file mappedFvPatch.H for source file plugins/FieldValuePluginFunction.C

On inspection, it is seen that the specific file mappedFvPatch.H is present in e.g. OF2.3.0, but not in foam-extend-3.1, so this particular error message and likely quite some others "missing" files is due to cross-version compatibility of swak4Foam.

I have seen the same type of warnings with the compilation of waves2Foam across multiple versions of OF, and I suspect that the creation of the dependency list (somewhere in wmake/src/wmkdependParser.cpp) neglects of pre-processor statements, which is needed to allow for cross-version compatibility. So for these specific type of errors, I am afraid that a revision of wmake and the creation of the dependency list is needed.

Exactly. Thanks for answering this.

"#ifdef is unfoamy"

[BernhardGrieser]

Originally Posted by egp

I compiled foam-extend-3.1 on several different Macs (desktop imac and MacBookPro) and found the 1.6-ext instructions on the openfoamwiki by Bernhard Grieser to work very well:

http://openfoamwiki.net/index.php/In...enFOAM-1.6-ext

Only modifications are to pull extend-3.1, and ignore the patches (no need since they are in the repo).

Thanks for the credits and the feedback, Eric! Glad I could contribute.
Cheers,
Bernhard

[behzad-cfd]

Hi
I need POD (proper orthogonal decomposition) functionality that is provided in 1.6 extend version. is extend 3.1 include POD too?

[gschaider]

Originally Posted by behzad-cfd

Hi
I need POD (proper orthogonal decomposition) functionality that is provided in 1.6 extend version. is extend 3.1 include POD too?

Yep. I see it in the sources and tutorials (haven't used it myself)

[Dothan]

Hi,
I'm looking at 3.1 ext dictionaries but I can't realize which OpenCFD version Zagreb is based on.
Please, someone can elucidate me?
Thank you in advance.

[gschaider]

Originally Posted by Dothan

Hi,
I'm looking at 3.1 ext dictionaries but I can't realize which OpenCFD version Zagreb is based on.
Please, someone can elucidate me?
Thank you in advance.

That is not a simple question to answer. A mix of various versions and own stuff added I'd say

[Dothan]

Originally Posted by gschaider

That is not a simple question to answer. A mix of various versions and own stuff added I'd say

gschaider thank you for your reply.
I notice some dictionary differencies between ext versions and other versions, and sometime it's very tricky to find the correct dictionary, at times trasform a OF case from a version to another is very time consuming and one have to remember all small changes between versions...but that is.
Source code in those case is the best friend

thank you.

[samiam1000]

Dear All,

not sure this is the right place to post this question, but probably yes: I would like to know if the extend version of OpenFOAM include the solver developed by Stephanie Geier and presented here: http://sourceforge.net/projects/open...7.pdf/download

Thanks a lot,
Samuele

[wyldckat]

Originally Posted by samiam1000

I would like to know if the extend version of OpenFOAM include the solver developed by Stephanie Geier...

Quick answer:

1. If we check the release notes:
   1. http://sourceforge.net/p/openfoam-ex...leaseNotes3.0/
   2. http://sourceforge.net/p/openfoam-ex...leaseNotes.txt
   There is no indication of this.
2. If we then check the contributors list: http://sourceforge.net/p/openfoam-ex...OfContributors - neither one of the names in the presentation, is in the list of contributors.

Therefore, I would say that the answer is: no, it is not present in foam-extend 3.1.
After a little search, the possible contact for this might be possible if you contact the secretary at the aforementioned institute in the presentation: http://www.imvt.uni-stuttgart.de/

[samiam1000]

Hi Bruno and thanks a lot for your help.

Can I ask you to help me in implementing what the 2 german people have done in the beamer I attached?

Thanks a lot,
Samuele.