.
Sylvain
From: Derek Gaston [fried...@gmail.com]
Sent: Thursday, February 09, 2012 11:18 AM
To: Roy Stogner
Cc: libmesh-users@lists.sourceforge.net
Subject: Re: [Libmesh-users] Coupling variables with different dimensions
On Feb 8, 2012, at 6:14 PM, Roy Stogner wrote:
> Only with some diffic
On Thu, 9 Feb 2012, Derek Gaston wrote:
On Feb 9, 2012, at 9:28 AM, Roy Stogner wrote:
There are lots of places where we build an FEBase object of
mesh_dimension() and then assume that we can use it on every element,
for starters.
Well… of course the user doing this would have to be aware o
>> This is a great idea but would almost certainly break on
>> find_neighbors().
>
> Interesting - I hadn't thought of that. Well, if find_neighbors() breaks you
> should still be able to have a separate piece of the mesh that is 1D and copy
> values back and forth between the two pieces. You ca
On Feb 9, 2012, at 9:28 AM, Roy Stogner wrote:
> There are lots of places where we build an FEBase object of
> mesh_dimension() and then assume that we can use it on every element,
> for starters.
Well… of course the user doing this would have to be aware of what they are
doing and do the right
On Thu, 9 Feb 2012, Derek Gaston wrote:
On Feb 8, 2012, at 6:14 PM, Roy Stogner wrote:
Only with some difficulty; it'd be the first time we put variables on
elements that didn't technically exist.
It'd be easier (though still quite difficult) to do something we've
been wanting to for a while
> You might even be able to tie them together by using the same nodes (so that
> the solutions are continuous and the sparsity pattern is correct).
>
> You might not be able to read this mesh from a file (although I think Exodus
> supports it). But if you just manually add a 2D element to a mesh
On Feb 8, 2012, at 6:14 PM, Roy Stogner wrote:
> Only with some difficulty; it'd be the first time we put variables on
> elements that didn't technically exist.
>
> It'd be easier (though still quite difficult) to do something we've
> been wanting to for a while: extend libMesh to handle Mesh ob
On Wed, 8 Feb 2012, David Knezevic wrote:
> On 02/08/2012 06:09 PM, Mauro Werder wrote:
>> I've never done it but here my thoughts: It should be possible to
>> assemble the 1D system when looping over the boundary elements of the
>> 2D mesh (as is usually done for the BCs) as all the machinery is
On 02/08/2012 06:09 PM, Mauro Werder wrote:
> I've never done it but here my thoughts: It should be possible to
> assemble the 1D system when looping over the boundary elements of the
> 2D mesh (as is usually done for the BCs) as all the machinery is in
> place to do this.
All the machinery is the
I've never done it but here my thoughts: It should be possible to
assemble the 1D system when looping over the boundary elements of the
2D mesh (as is usually done for the BCs) as all the machinery is in
place to do this.
Mauro
At Wed, 8 Feb 2012 22:07:16 +,
Sylvain Vallaghe wrote:
>
> Hi,
>
On 02/08/2012 05:07 PM, Sylvain Vallaghe wrote:
> I'm trying to implement a 2d problem in libmesh where I have two scalar
> variables : one is 2d in the whole domain, the other is 1d and mapped on one
> of the boundaries of my domain. These two variables are coupled due to the
> global variati
Hi,
I'm trying to implement a 2d problem in libmesh where I have two scalar
variables : one is 2d in the whole domain, the other is 1d and mapped on one of
the boundaries of my domain. These two variables are coupled due to the global
variational formulation. I don't know how to define my 1d va
12 matches
Mail list logo
