Re: [petsc-dev] DMPlexAddBoundary

2014-05-21 Thread Matthew Knepley
On Wed, May 21, 2014 at 10:21 PM, Adrian Croucher wrote: > hi > > On 21/05/14 22:43, Matthew Knepley wrote: > > On Wed, May 21, 2014 at 12:46 AM, Jed Brown wrote: > >> Adrian Croucher writes: >> > In the 'PhysicsCreate' functions there are calls to DMPlexAddBoundary(), >> > which takes an arr

Re: [petsc-dev] DMPlexAddBoundary

2014-05-21 Thread Adrian Croucher
hi On 21/05/14 22:43, Matthew Knepley wrote: On Wed, May 21, 2014 at 12:46 AM, Jed Brown > wrote: Adrian Croucher mailto:a.crouc...@auckland.ac.nz>> writes: > In the 'PhysicsCreate' functions there are calls to DMPlexAddBoundary(), > which takes an arra

Re: [petsc-dev] DMPlexAddBoundary

2014-05-21 Thread Matthew Knepley
On Wed, May 21, 2014 at 12:46 AM, Jed Brown wrote: > Adrian Croucher writes: > > In the 'PhysicsCreate' functions there are calls to DMPlexAddBoundary(), > > which takes an array of IDs; e.g. in PhysicsCreate_SW() the IDs are > > {100,101,200,300}. It looks like these IDs define where the BCs ar

Re: [petsc-dev] DMPlexAddBoundary

2014-05-20 Thread Jed Brown
Adrian Croucher writes: > In the 'PhysicsCreate' functions there are calls to DMPlexAddBoundary(), > which takes an array of IDs; e.g. in PhysicsCreate_SW() the IDs are > {100,101,200,300}. It looks like these IDs define where the BCs are > applied, but what do these numbers actually refer to?

[petsc-dev] DMPlexAddBoundary

2014-05-20 Thread Adrian Croucher
hi I'm trying (and so far failing) to understand how the locations for setting boundary conditions are defined in the TS ex11 example. In the 'PhysicsCreate' functions there are calls to DMPlexAddBoundary(), which takes an array of IDs; e.g. in PhysicsCreate_SW() the IDs are {100,101,200,300