THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#275 - Easier handling of boundary conditions and sources User who did this - Bernd Flemisch (bernd) ---------- I somehow would like to get a python interface in the long run. Most likely, something in this direction will be done in one of Dune's Google Summer of Code projects and we can profit from the experiences made there. There's no need to rush this. "Somehow" means that I also share Christoph's opinion. I think that a Python interface will not be of too much use for our PhD students. Maybe even a burden because some of them additionally have to learn Python. On the other hand, I can imagine quite a benefit for persons who only want to "use" Dumux, whatever that means. And that would include (some/most of) our Bachelor and Master students. As an intermediate step, I was thinking of defining some common boundary condition types like "no flow", "fully saturated hydrostatic", "all constant Dirichlet values", ... and providing a possibility to set them for every dof / scvf or also for something like the top/bottom/front... of the domain. I'm unsure if this is worth the effort. ---------- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=275#comment694 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______________________________________________ Dumux mailing list [email protected] https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
