On Thu, Aug 23, 2012 at 2:08 PM, Chris Eldred wrote:
> Awesome- that is easy. How do I access that SF?
I destroy it inside DMComplexPreallocateOperator(), but we can preserve it.
Matt
> On Thu, Aug 23, 2012 at 12:54 PM, Matthew Knepley
> wrote:
> > On Thu, Aug 23, 2012 at 1:42 PM, Chris E
On Thu, Aug 23, 2012 at 1:42 PM, Chris Eldred wrote:
> I need the adjacency relations discussed in my other post- the only
> one that is not part of closure(p) U star(p) is: U
> cone(support(edge)). Given an edge p, I need all of the edges that
> cover the same cell as edge p.
Okay, then for par
On Thu, Aug 23, 2012 at 12:26 PM, Chris Eldred wrote:
> Yes- I am implementing the TriSK scheme
> (www.mmm.ucar.edu/people/skamarock/Ringler_et_al_JCP_2009.pdf) on
> arbitrary Voronoi meshes. In order to do wind/flux reconstruction at
> the cell edges, it needs to know about the edges of adjacent
Awesome- that is easy. How do I access that SF?
On Thu, Aug 23, 2012 at 12:54 PM, Matthew Knepley wrote:
> On Thu, Aug 23, 2012 at 1:42 PM, Chris Eldred
> wrote:
>>
>> I need the adjacency relations discussed in my other post- the only
>> one that is not part of closure(p) U star(p) is: U
>> con
I need the adjacency relations discussed in my other post- the only
one that is not part of closure(p) U star(p) is: U
cone(support(edge)). Given an edge p, I need all of the edges that
cover the same cell as edge p.
On Thu, Aug 23, 2012 at 12:17 PM, Matthew Knepley wrote:
> On Thu, Aug 23, 2012
On Thu, Aug 23, 2012 at 12:12 PM, Chris Eldred wrote:
> Thanks- that helps a lot. If I need stencils that are larger than
> closure(p) U star(p) (for a higher-order finite difference method, for
> example), I assume that I need to create my own PetscSF's that
> describe which points need to be gho
Yes- I am implementing the TriSK scheme
(www.mmm.ucar.edu/people/skamarock/Ringler_et_al_JCP_2009.pdf) on
arbitrary Voronoi meshes. In order to do wind/flux reconstruction at
the cell edges, it needs to know about the edges of adjacent cells-
which are outside of closure(p) U star(p).
On Thu, Aug
Thanks- that helps a lot. If I need stencils that are larger than
closure(p) U star(p) (for a higher-order finite difference method, for
example), I assume that I need to create my own PetscSF's that
describe which points need to be ghosted?
Is there some documentation or example code that explain
On Sat, Aug 18, 2012 at 4:11 PM, Chris Eldred wrote:
> Yes I think that makes sense. How do you access the associated PetscSF
> for the DMComplex? Is it possible to define multiple PetscSF's for a
> given DMComplex, each associated with different PetscSections?
>
1) DMGetDefaultSF() for the one f
Yes I think that makes sense. How do you access the associated PetscSF
for the DMComplex? Is it possible to define multiple PetscSF's for a
given DMComplex, each associated with different PetscSections?
My current understanding of using DMComplex is (for the serial case):
1) Create a DMComplex ob
On Fri, Aug 17, 2012 at 1:21 PM, Chris Eldred wrote:
> I was wondering how ghost values were handled when creating a
> distributed (global) vector from a specific PetscSection over a
> DMComplex object- ie what defines the stencils used to figure out
> which values need to be ghosted? What about l
I was wondering how ghost values were handled when creating a
distributed (global) vector from a specific PetscSection over a
DMComplex object- ie what defines the stencils used to figure out
which values need to be ghosted? What about local vs. global indexes?
-Chris
--
Chris Eldred
DOE Computa
12 matches
Mail list logo
