swak4foam and pyfoam

News and updates on swak4foam and PyFoam - software packages to support working with OpenFOAM
Follows @[email protected] (Mastodon)

[swak4foam and pyfoam @swakPyFoam]

https://t.co/a4pGFVBOHD
The @of_ws #ofw18 (that is the #OpenFOAM Workshop) is starting
The location is cool. But unfortunately not very cool

[swak4foam and pyfoam @swakPyFoam]

https://t.co/o0oReuBooE
Looking forward to the talk at 18th OpenFOAM Workshop later today on "Parameterized cases with pyFoamPrepareCase" . #OFW18 #OpenFOAM @of_ws

[swak4foam and pyfoam @swakPyFoam]

Especially as there will be a pyFoamPrepareCase training on the first day
#PyFoam #ofw18
https://t.co/XBEBt8lHNp

[OpenFOAM Workshop @of_ws]

The 18th OpenFOAM Workshop #OFW18 starts tomorrow.

Be there or be square!

[swak4foam and pyfoam @swakPyFoam]

https://t.co/C4z2Ic7A5s
#PyFoam release

The new release 2023.7 of #PyFoam has been uploaded
Most important change ist the support of the Jinja2 template library.
More about this at my talk at the @of_ws tomorrow
Install with
pip install pyfoam

[swak4foam and pyfoam @swakPyFoam]

https://t.co/IwBGDVyEuN
The development branch of #swak4foam compiles with the latest #OpenFOAM release v2306 from ESI (but also v10 of the Foundation and foam-extend 5 work)

[swak4foam and pyfoam @swakPyFoam]

https://t.co/uZbkGQhUji
The "Universal #OpenFOAM build scrpt based on Ansible" https://t.co/dV9HQE2S88 has a new release and supports the recewntly Released #OpenFOAM version 2306 from ESI (and also the v10 from the foundation branch and version 5 of foam-extend)

[swak4foam and pyfoam @swakPyFoam]

@_Philippose_ Yep. I get a mail when a commits get uploaded
More by mail

[swak4foam and pyfoam @swakPyFoam]

Just pushed version 2022.9 of #PyFoam to pypi
This version has only small fixes. Most notably it fixes a problem with OF 10 were a change in the output broke the plotting utilities
Upgrade with
pip install --upgrade PyFoam

[swak4foam and pyfoam @swakPyFoam]

@_Philippose_ Just got notified of your push to the Mercurial repo. Will look at it in the next days. But beware: there will be questions ;)

[swak4foam and pyfoam @swakPyFoam]

@_Philippose_ Definitely interested. There is an interest in a Windows-port .... just not by me ;)
Do you have you changes alredy under hg-control?
I take them either from any publicly accessible hg-server or bundles sent to me via "hg bundle"

[swak4foam and pyfoam @swakPyFoam]

https://t.co/SxAJYk4svH

Pushed some changes to the #PyFoam development repository that allow https://t.co/L4Q0cgZEW5 the popular #Jinja2 as a templating language instead of the built-in #pyratemp

Will be in the #nextRelease

[swak4foam and pyfoam @swakPyFoam]

https://t.co/bgCuUwdb3c

Just pushed a new develop-branch to the #swak4Foam repository.
This one compiles with
- #OpenFOAM v2212
- #OpenFOAM v10
- #foamExtend 5.0
(the latest of each of these 3 distros)
Compiles. Seems to work. But no thorough testing

[swak4foam and pyfoam @swakPyFoam]

@xuegy I've pushed a branch feature/port/p2212 to the Mercurial repository that compiles with v2212
It compiles but I have not done much testing yet

[swak4foam and pyfoam @swakPyFoam]

https://t.co/txSSH0CwaK

Currently struggling to port #swak4foam to #OpenFOAM 10
Don't mind porting for new features but there are lots of non-sensical changes to the public API (renaming of classes, moving methods from public to protected) that make it a pain
Wondering: should…

[swak4foam and pyfoam @swakPyFoam]

@jprince549 If #PyFoam was developed with the same attitude it would break frequently for users: "I like this new feature of Python 3.10 - everybody should upgrade" "Lets rename half of the CLI-options" "I don't like the name this had for 10years"

[swak4foam and pyfoam @swakPyFoam]

@jprince549 #PyFoam is not affected as long as there are no major changes to the file formats and output
I don't mind changes that improve stuff. But there are lots like "WE don't need this method in the public interface. So nobody does. Lets make it protected". Those break #swak4Foam

[swak4foam and pyfoam @swakPyFoam]

Yep. foam-extend should be supported (last checked for 4.1. Checking 5.0 is planned for this week)

[S. Waldmeister @lessergen]

@swakPyFoam "Never ever break user experience"! Never understood why do heavy renaming in a production code. Extend still supported? I'm using ESI and extend by now.

[swak4foam and pyfoam @swakPyFoam]

https://t.co/kxbKVOIOqy

Planing to propose two trainings on #swak4Foam or #pyfoam for #ofw18 to the @of_ws
- a basic training on both
- one advanced topic
Any suggestions/demands/wishes on a topic from you guys?

[swak4foam and pyfoam @swakPyFoam]

https://t.co/psJYPHp9hP

Officially opening Mastodon account @swakPyFoam for #swak4foam and #pyfoam
All toots will be mirrored to the Twitter account @swakPyFoam

[swak4foam and pyfoam @swakPyFoam]

https://t.co/ehjrS9Xtac

Testing the connection from the new Mastodon account to Twitter

[hrvoje_jasak @HrvojeJasak]

Announcing official release of foam-extend-5.0 https://t.co/vcozXJy99l New models, tutorials and physics modelling in 5500 git commits. I hope it was worth the wait - for the future, we shall switch to a 6-monthly release schedule. Happy FOAMing! #OpenFOAM #foamExtend #CFD