Hi Roy,
Regarding the thread below: I wasn't interested in adaptive p-refinement
per se in this case, instead my motivation was to enable different variable
orders in different regions of a mesh. One use-case for this is to have 2nd
order beam elements and 1st order shell elements in the same mesh
On Fri, Mar 9, 2018 at 2:53 PM, Roy Stogner
wrote:
>
> On Fri, 9 Mar 2018, David Knezevic wrote:
>
> - If I were to look into adding a special case for non-uniform 1st
>> to 2nd order refinement for LAGRANGE variables, do you think this
>> would be of interest to include that in libMesh, or would
On Fri, 9 Mar 2018, David Knezevic wrote:
- If I were to look into adding a special case for non-uniform 1st
to 2nd order refinement for LAGRANGE variables, do you think this
would be of interest to include that in libMesh, or would it be too
specific to include? (I'd like to know if it's poten
On Fri, Mar 9, 2018 at 2:21 PM, Roy Stogner
wrote:
> p-refinement is supported, but adaptive p-refinement currently isn't.
> We require basis functions to be hierarchic (not necessarily
> HIERARCHIC) to generate constraint equations between neighboring
> elements of different p refinement levels.
p-refinement is supported, but adaptive p-refinement currently isn't.
We require basis functions to be hierarchic (not necessarily
HIERARCHIC) to generate constraint equations between neighboring
elements of different p refinement levels.
So you can do uniform refinement for error estimation, but
I'm using LAGRANGE variables for an elasticity problem and I'd like to be
able to increase the variable order from 1 to 2 specified elements. Is it
possible to do this using p-refinement in libMesh?
I had a vague impression that p-refinement was only supported for
discontinuous or hierachic basis
On Fri, 15 May 2015, Kameeko Kiwi wrote:
> If I made a HIERARCHIC variable and a SCALAR variable, how would the
> two variables know that they should be continuous at the interface
> of the subdomains?
They wouldn't. You'd need to manually add constraints (or a penalty
term) to enforce (or wea
If I made a HIERARCHIC variable and a SCALAR variable, how would the two
variables know that they should be continuous at the interface of the
subdomains? Or is there a way to make one variable be of different FEFamily
types in different subdomains?
On Fri, May 15, 2015 at 7:16 AM, Roy Stogner
wr
On Thu, 14 May 2015, Kameeko Kiwi wrote:
> Is there a way to have a variable be constant in one part of the domain and
> non-constant in the rest, remaining continuous along the interface of the
> two regions? I believe p-refinement is supported for p>0, but not if one is
> starting p=0?
The onl
Hello,
Is there a way to have a variable be constant in one part of the domain and
non-constant in the rest, remaining continuous along the interface of the
two regions? I believe p-refinement is supported for p>0, but not if one is
starting p=0?
Thanks,
Harriet
--
On Thu, 28 Feb 2008, Lorenzo Botti wrote:
> I've found the problem affecting the p refinement in my elliptic_dg
> code...
> In fe_boundary.C the method void FE::reinit(const Elem* elem,
> const unsigned int s, const Real tolerance)
> will initialize the shape functions if ((this->get_type() != el
Hi all,
I've found the problem affecting the p refinement in my elliptic_dg
code...
In fe_boundary.C the method void FE::reinit(const Elem* elem,
const unsigned int s, const Real tolerance)
will initialize the shape functions if ((this->get_type() != elem-
>type()) || (s != last_side) || this
12 matches
Mail list logo
