Hi Edscott,

for the properties there is a script in bin/util/. However, the old property macros also still work.

For the problems and spatial params there is the guide in the wiki https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/wikis/Hints/Upgrade-to-Dumux-3

For all other classes that changes there is unfortunately no detailed guide.  But there are plenty of existing model implementations and tests as examples for what the new way looks like.

Timo

On 14.03.19 17:42, Ed Scott Wilson Garcia wrote:
Hi,
I've currently got some programs that run on a dumux-3.0-alpha version (git commit 913003596) and I wonder if there is a roadmap or howto to update the code to the current 3.0 release. What I notice on first observation is that all the properties macros have been replaced by code within the Dumux::Properties::TTag namespace.
That I think I can handle, but other files and classes that used to exist have 
been replaced by others with new templates. For example,  the property 
functionality defined in dumux/discretization/box/properties.hh is now taken 
care of in dumux/discretization/box.hh with the new property paradigm.

Is there a guide or roadmap or howto documentation that points outs what has 
been removed and with what it has been replaced?

  This would make migration less complicated.

Best regards

Edscott
_______________________________________________
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

--
_______________________________________________________________

Timo Koch                              phone: +49 711 685 64676
IWS, Universität Stuttgart             fax:   +49 711 685 60430
Pfaffenwaldring 61        email: timo.k...@iws.uni-stuttgart.de
D-70569 Stuttgart            url: www.hydrosys.uni-stuttgart.de
_______________________________________________________________

_______________________________________________
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Reply via email to