[gschaider]

A new release of swak4Foam can now be downloaded through the usual channels (SVN).

New features are:
- global variables
- functionObjects that allow the inclusion of Python-Code
- a variant of the coded-functionObject that cooperates with swak (only for OF 2.)
- functionObjects that solve the laplacian and the transport equation

Further details on these new features can be found in the 2nd part of the presentation that is found here: http://openfoamwiki.net/index.php/Fi...Leoben2011.pdf

Bernhard

[gschaider]

Forgot to mention it here (notifications already reached other channels - had so much fun playing with the new Social-media button on the network): a new release of swak4Foam ist out

Major improvements are:

• extension of the Field-parser to allow surface-fields and tensors
• conditional function objects (execute function objects on demand)
• improved Allwmake (catches common compilation problems)
• finiteArea now also supports the PDF-functionObjects
• and several other improvements

There are separate branches for the 1.x and the 2.x line of OpenFOAM (yes. 2.1 is supported)

PS: I was notified that this is going to be my 2001st post on the message board. In the honor of this this will be the first swak4Foam-release with a release name: "Kubrick"

[mai]

Hi Bernhard,

concerning the conditional functionsObjects I a question.
Is it also possible to created a condition that calls the functionsObjects at a specific position of the solver, for example in the outer pressure correction loop of the pimple based solvers?

Martin

[gschaider]

Originally Posted by mai

Hi Bernhard,

concerning the conditional functionsObjects I a question.
Is it also possible to created a condition that calls the functionsObjects at a specific position of the solver, for example in the outer pressure correction loop of the pimple based solvers?

Martin

No. The problem is that functionObjects are only called at the end of a time-loop when the time is increased.

I THINK something like you want to could be achieved by specifying a second functionObjectList and calling it in the appropriate places. But you'd have to modify the solver code for that and it could lead to all kinds of weird behaviour for some function objects as they sometimes can't deal with being called twice for the same time-value

[mai]

Hi Bernhard,

thanks for the reply. Could you please give me a hint what needs to be done in order to define a second functionObjectList. How is the "normal" functionObjectList defined in the code and how is this list executed from the solver?

Martin

[gschaider]

Originally Posted by mai

Hi Bernhard,

thanks for the reply. Could you please give me a hint what needs to be done in order to define a second functionObjectList. How is the "normal" functionObjectList defined in the code and how is this list executed from the solver?

Martin

The normal functionObjectList is defined in the Time-class/object. The constructor for FOL (one of them) assumes that he gets a dictionary with one entry "functions" from which he constructs the list. An example of the "non standard" usage of that have a look in the conditional functionObjects-part of the simpleFunctionObjects

Bernhard

[mai]

Hi Bernhard,

thanks for your answer. I wil have a look át the conditional FunctionObjects and try to understand how it works.

Martin

[gschaider]

Last friday (the 13th) a new release of swak4Foam hit the servers. One of the big innovations of this release is that I implemented a system that allows identifying consecutive releases by a system of ascending numbers. This system should make it easier to identify releases and find out whether the current release is the newest. I will call these numbers "version numbers" (not yet trademarked). I think this system is very useful in a lot of contexts. Feel free to use it for your own projects (reference to the place you saw it first would be nice).

The new release will receive the number 0.2.0 (previous releases have been numbered with 0.1.x)

Other new features are
- temporal operators ddt and oldTime. Other operators from fvc are added
- functions for location of minimum and maximum
- Field-parser now supports tensors and pointFields
- New variables for Python-integration
- boundary conditions groovyBCDirection and groovyBCJump
- fully parallel compilation
(see README for a full list).

Downloading is described at http://openfoamwiki.net/index.php/Co...am#Downloading

[romant]

Hej,

I wanted to use the bug report on the sourceforge website, but somehow it is not accepting my login (I used the openID login) and when I go to the bug report website you give in openfoamwiki contrib I get redirected and it does not fulfill my wishes, therefore I would like to report the bug here :-)

anyway, the pow() function has a problem with the parser, the second variable can not be set with a alphanumerical variable but has to be a value.

[gschaider]

Originally Posted by romant

Hej,

I wanted to use the bug report on the sourceforge website, but somehow it is not accepting my login (I used the openID login) and when I go to the bug report website you give in openfoamwiki contrib I get redirected and it does not fulfill my wishes, therefore I would like to report the bug here :-)

anyway, the pow() function has a problem with the parser, the second variable can not be set with a alphanumerical variable but has to be a value.

That was "by design". The original parser (then only called funkySetFields) was constructed from the table of functions in the ProgrammersGuide and that said that the exponent can not be field. The Programmers Guide has not been updated for a long time and I don't want to go back through the sources to check if that restriction was really there at the time.

I'll make a note and hope that I don't forget (BTW: Sourceforge seems to have fixed their server-problem so maybe you can log in now)

PS: there is a part in me that says "don't do it. This is madness. Remember all the times people 'reported bugs' but in reality where using the pow-function wrong. And this will become 'easier' if the exponent is calculated too" but I guess the part that wants a 'complete' grammar is going to be stronger

[romant]

Thank you. Hope that the source forge works again, but I had problems before.

[ziemowitzima]

Hi
First , thanks for groocyBC,
I would like to use groovyBCDirection
Is there any example how to use them ?

Thanks

[gschaider]

Originally Posted by ziemowitzima

Hi
First , thanks for groocyBC,
I would like to use groovyBCDirection
Is there any example how to use them ?

Thanks

There is an example case Examples/tests/directionMixedBendPipe. Apart from that there are no examples.

The boundary condition is based on the directionMixed-BC (the same way groovyBC is based on the mixed-BC) so look for documentation on this

[gschaider]

Hi!

A new release of swak4Foam has hit the repositories (mercurial and SVN)

For general information on this swak-thing see http://openfoamwiki.net/index.php/Contrib/swak4Foam

The most notable changes in this version are:

• Possibility to add functions to the grammars via plugins that are loaded at run-time. This allows adding very special functionality without modifying the core of swak. Examples are:
  • Functions that return the mesh-quality fields (non-orthogonality etc)
  • Functions that allow using differential operators but allow chosing the discretization scheme in the function call
  • Functions that "project" sampledSets and sampledSurfaces into the volume
  • Getting the source terms of a lagrangian cloud that is derived from one of the basic intermediate classes
• Delayed variables: these can be used like regular variables for writing. If they are read (used) they give back the value they had X seconds ago. This allows boundary conditions with delayed reactions
• Function objects that create and evolve clouds of lagrangian particles
• Improved the scripts for compilation. Checking of versions of prerequisites.
• On OpenFOAM 2.x there are now source terms derived from basicSource. So all OpenFOAM-solvers that support runtime-selectable source terms via that class can now use sources that use swak-expressions
• Changes to the grammar to support more operations (especially more tensor operations, but also does the pow-function now support non-uniform exponents)

A full list of the changes (and bugs fixed) in this version can be found in the History section of http://openfoamwiki.net/images/e/e6/...oam_README.pdf (for OpenFOAM 1.x) or http://openfoamwiki.net/images/8/81/...README_2.x.pdf (for OpenFOAM 2.x - contents are slightly different). The list is seven pages long in the PDF so there is more than the above highlights.

Have fun and don't hurt yourself

Bernhard

[gschaider]

New version of swak4Foam (0.2.2) is available. As usually it contains bug-fixes (yeah. There were bugs. Unbelievable, but true) and several enhancements. For details see the README that comes with it.

For those who don't want to download it without knowing what is new here is an incomplete list of new features:

- several enhancements to the python-integration. Amongst other things: variables that have fields are now availoable to the python-code as numpy.-arrays
- expressions now can access fields from a different case. This makes it possible to easily use funkySetFields to compare cases
- Patch-expressions now support mappedPatches
- Plugin functions to access fields from the radiation mode or the combustion model (for instance the reaction rates)
- Enhancements to the build-scripts
- The start of a reference-manual (Only the first part. In org-mode. Not proofread)

For information on downloading see:
http://openfoamwiki.net/index.php/Contrib/swak4Foam

Unfortunately the SVN is still not available (everybody say "Thank you, ANSYS") but there are tarballs to download at the above link

[gschaider]

Originally Posted by gschaider

New version of swak4Foam (0.2.2) is available. As usually it contains bug-fixes (yeah. There were bugs. Unbelievable, but true) and several enhancements. For details see the README that comes with it.

Two things about this new release:
- As I found out afterwards the release doesn't compile on 1.6-ext. This is fixed in the development version (mercurial repository on sourceforge. See Wiki-page for details)
- One week after the release OF 2.2 came out. The current release of swak4Foam does not compile with it. But I already fixed it and pushed the fixes to the development repository into a special branch (see https://twitter.com/swakPyFoam/statu...94954107031552). The fixes seem to work OK but I plan to test them and then merge them into the regular 2.x-branch. Updates on this work and info which branch is the "better" one for 2.2 will be posted on the above Twitter-channel

[gschaider]

The last release 0.2.2 will go down in history as one of the shortest-lived swak-releases: as Version 2.2 of OF came out the week after that and as this release makes it necessary to do some changes on the swak-sources this release was rushed out to allow people to go on swaking on 2.2.

In addition the compilation on 2.0 and 1.6-ext were fixed (1.7 and 2.1 were working all the time)

Apart from the support for various OF-versions there are not many additional features:
- support for eigenValues and eigenVectors of tensors
- accessing a full row of a tensor with .x, .y and .z
- writing out sampled surfaces and sets that were specified by swak-functionObjects

For details have al look at the README

[tomf]

Bernhard,

Thanks a lot for all the work making swak available for the new release so soon. I was wondering on one particular new feature.

In the readme file it is mentioned that it is now possible to access the internalField from different cases. Does this mean it is limited to the internalField, or is it also possible to access patches from a different case to use in a groovyBC?

I am wondering if it is possible to use the fields at an outlet as an inlet condition for a different case using this framework?

Regards,
Tom

[gschaider]

Originally Posted by tomf

Bernhard,

Thanks a lot for all the work making swak available for the new release so soon. I was wondering on one particular new feature.

In the readme file it is mentioned that it is now possible to access the internalField from different cases. Does this mean it is limited to the internalField, or is it also possible to access patches from a different case to use in a groovyBC?

I am wondering if it is possible to use the fields at an outlet as an inlet condition for a different case using this framework?

Interesting idea, but: No. Only complete fields I'm afraid

I developed this because I wanted to compare results from different cases (or different time in the same case). It basically is the functionality of the mapFields-utility.

For different cases the mappedPatch-functionality won't help you either I'm afraid. If there is nothing in OF that supports this it is rather unlikely that such a feature will turn up in swak (will have a look at it when I or someone I work for needs it)

[tomf]

Hi Bernhard,

Thank you for the clarification. That will save me some trial and error. Maybe I can find another solution.

Regards,
Tom