dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #21539
Re: Blueprint for 0.9.10: Attaching subdomains to form
-
To:
dolfin@xxxxxxxxxxxxxxxxxxx
-
From:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
Date:
Tue, 22 Feb 2011 08:52:55 +0000
-
In-reply-to:
<20110222075129.GA4767@eowyn.Belkin>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
On 22/02/11 07:51, Anders Logg wrote:
> I'd like to implement this blueprint for 0.9.10:
>
> https://blueprints.launchpad.net/dolfin/+spec/attach-subdomains-to-form
>
> In addition, I'd like to remove the cell_domains,
> exterior_facet_domains and interior_facet_domains arguments from the
> assembler. It seems overkill to have three different ways to specify
> the domains and the logic becomes complex for handling which data
> overrides if many are specified. We could also remove these arguments
> from VariationalProblem.
>
> We would then have two ways to specify the subdomains:
>
> 1. As part of the Mesh (MeshData)
>
> 2. As part of the form
>
> The SystemAssembler would then need to rely on (1).
>
> Comments and objections?
>
What's the advantage of having two methods? Why not just have one?
I'd would be happy to see subdomains as part of MeshData, but I would be
reluctant to use the existing data structures because I find them cryptic.
We could have cell domains become part of the mesh .xml files - this
would be helpful because mesh generators can often define domains, and
it would be handy to use this data easily (by supporting it in
dolfin-convert).
Garth
> --
> Anders
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help : https://help.launchpad.net/ListHelp
Follow ups
References