On Thu, Aug 30, 2012 at 11:49 AM, Chris Eldred wrote:
> That is what I have already been doing- so that is good! As far as the
> ordering convention goes, for a 2D mesh I should have vertices, faces
> (what I have been calling cells) and then edges? Ex. for the doublet
> mesh it would be 0,1,2,3 (
Oh ok that makes sense. The nomenclature was confusing me.
On Thu, Aug 30, 2012 at 10:53 AM, Matthew Knepley wrote:
> On Thu, Aug 30, 2012 at 11:49 AM, Chris Eldred
> wrote:
>>
>> That is what I have already been doing- so that is good! As far as the
>> ordering convention goes, for a 2D mesh I
That is what I have already been doing- so that is good! As far as the
ordering convention goes, for a 2D mesh I should have vertices, faces
(what I have been calling cells) and then edges? Ex. for the doublet
mesh it would be 0,1,2,3 (vertices); 4,5 (faces); 6,7,8,9,10 (edges)?
On Wed, Aug 29, 20
On Wed, Aug 29, 2012 at 1:35 PM, Chris Eldred wrote:
> DMComplexGetTransitiveClosure (and Restore) work fine now. What are
> the new restrictions on numbering mentioned in
> src/dm/impls/complex/examples/tests/ex2f90.F?
>
In the original Sieve, you could use any id for any point. This is very
fle
DMComplexGetTransitiveClosure (and Restore) work fine now. What are
the new restrictions on numbering mentioned in
src/dm/impls/complex/examples/tests/ex2f90.F?
On Tue, Aug 28, 2012 at 8:16 PM, Matthew Knepley wrote:
> On Tue, Aug 28, 2012 at 5:01 PM, Chris Eldred
> wrote:
>>
>> On Tue, Aug 28,
On Tue, Aug 28, 2012 at 5:01 PM, Chris Eldred wrote:
> On Tue, Aug 28, 2012 at 3:49 PM, Matthew Knepley
> wrote:
> > On Tue, Aug 28, 2012 at 4:39 PM, Chris Eldred
> > wrote:
> >>
> >> DMComplexGetTransitiveClosure does not appear to have the calling
> >> sequence (DM dm, PetscInt p, PetscBool us
On Tue, Aug 28, 2012 at 4:39 PM, Chris Eldred wrote:
> DMComplexGetTransitiveClosure does not appear to have the calling
> sequence (DM dm, PetscInt p, PetscBool useCone, PetscInt *numPoints,
> PetscInt *points[]) indicated in the documentation- instead it has DM
> dm, PetscInt p, PetscBool useCon
On Tue, Aug 28, 2012 at 3:49 PM, Matthew Knepley wrote:
> On Tue, Aug 28, 2012 at 4:39 PM, Chris Eldred
> wrote:
>>
>> DMComplexGetTransitiveClosure does not appear to have the calling
>> sequence (DM dm, PetscInt p, PetscBool useCone, PetscInt *numPoints,
>> PetscInt *points[]) indicated in the
DMComplexGetTransitiveClosure does not appear to have the calling
sequence (DM dm, PetscInt p, PetscBool useCone, PetscInt *numPoints,
PetscInt *points[]) indicated in the documentation- instead it has DM
dm, PetscInt p, PetscBool useCone, PetscInt *points[]. In addition, it
does not appear to be r
