Re: [petsc-dev] proposed minor PetscPartitioner changes

Matthew Knepley writes: > On Wed, Nov 8, 2017 at 2:27 PM, Jed Brown wrote: > >> Matthew Knepley writes: >> >> > On Wed, Nov 8, 2017 at 1:49 PM, Jed Brown wrote: >> > >> >> Matthew Knepley writes: >> >> >> >> >> > No, this is the right structure. >> >> >> >> >> >> Oh come on. You're defending

Re: [petsc-dev] ISGetIndices

> We could consider this, but really IS is intended to be a static object, not > a dynamic one. > I think Jed's SegBuffer is supposed to be dynamic, and could underlie a > dynamic index > object. I could be wrong, but my recollection is that the initial reason for the index sets was the bound

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 2:27 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Wed, Nov 8, 2017 at 1:49 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> >> > No, this is the right structure. > >> >> > >> >> Oh come on. You're defending a quadratic algorithm. > >> >> > >> >

Re: [petsc-dev] proposed minor PetscPartitioner changes

Matthew Knepley writes: > On Wed, Nov 8, 2017 at 1:49 PM, Jed Brown wrote: > >> Matthew Knepley writes: >> >> >> > No, this is the right structure. >> >> >> >> Oh come on. You're defending a quadratic algorithm. >> >> >> >> ierr = ParMETIS_V3_PartKway(vtxdist, xadj, adjncy, vwgt, adjwgt,

Re: [petsc-dev] ISGetIndices

On Wed, Nov 8, 2017 at 2:09 PM, Munson, Todd wrote: > > > On Nov 8, 2017, at 10:32 AM, Matthew Knepley wrote: > > > > On Wed, Nov 8, 2017 at 11:21 AM, Munson, Todd > wrote: > > > > I had a question. There is VecGetArrayRead and VecRestoreArrayRead. > However, the > > sameconcept does not appea

Re: [petsc-dev] ISGetIndices

> On Nov 8, 2017, at 10:32 AM, Matthew Knepley wrote: > > On Wed, Nov 8, 2017 at 11:21 AM, Munson, Todd wrote: > > I had a question. There is VecGetArrayRead and VecRestoreArrayRead. > However, the > sameconcept does not appear with IS. Is there a reason for not having > ISGetIndicesRead a

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 1:49 PM, Jed Brown wrote: > Matthew Knepley writes: > > >> > No, this is the right structure. > >> > >> Oh come on. You're defending a quadratic algorithm. > >> > >> ierr = ParMETIS_V3_PartKway(vtxdist, xadj, adjncy, vwgt, adjwgt, > >> &wgtflag, &numflag, &ncon, &np

Re: [petsc-dev] proposed minor PetscPartitioner changes

Matthew Knepley writes: >> > No, this is the right structure. >> >> Oh come on. You're defending a quadratic algorithm. >> >> ierr = ParMETIS_V3_PartKway(vtxdist, xadj, adjncy, vwgt, adjwgt, >> &wgtflag, &numflag, &ncon, &nparts, tpwgts, ubvec, options, &edgeCut, >> assignment, &comm); >>

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 1:02 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Wed, Nov 8, 2017 at 10:04 AM, Vaclav Hapla > > > wrote: > > > >> > >> 8. 11. 2017 v 15:59, Matthew Knepley : > >> > >> On Wed, Nov 8, 2017 at 9:14 AM, Vaclav Hapla > > >> wrote: > >> > >>> > >>> 8. 11. 2017 v 1

Re: [petsc-dev] proposed minor PetscPartitioner changes

Matthew Knepley writes: > On Wed, Nov 8, 2017 at 10:04 AM, Vaclav Hapla > wrote: > >> >> 8. 11. 2017 v 15:59, Matthew Knepley : >> >> On Wed, Nov 8, 2017 at 9:14 AM, Vaclav Hapla >> wrote: >> >>> >>> 8. 11. 2017 v 14:52, Jed Brown : >>> >>> Matthew Knepley writes: >>> >>> On Wed, Nov 8, 2017 a

Re: [petsc-dev] ISGetIndices

On Wed, Nov 8, 2017 at 11:21 AM, Munson, Todd wrote: > > I had a question. There is VecGetArrayRead and VecRestoreArrayRead. > However, the > sameconcept does not appear with IS. Is there a reason for not having > ISGetIndicesRead and ISRestoreIndicesRead? > Actually, ISGetIndices() is always

[petsc-dev] ISGetIndices

I had a question. There is VecGetArrayRead and VecRestoreArrayRead. However, the sameconcept does not appear with IS. Is there a reason for not having ISGetIndicesRead and ISRestoreIndicesRead? Thanks, Todd.

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 10:04 AM, Vaclav Hapla wrote: > > 8. 11. 2017 v 15:59, Matthew Knepley : > > On Wed, Nov 8, 2017 at 9:14 AM, Vaclav Hapla > wrote: > >> >> 8. 11. 2017 v 14:52, Jed Brown : >> >> Matthew Knepley writes: >> >> On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla >> wrote: >> >> >>

Re: [petsc-dev] proposed minor PetscPartitioner changes

> 8. 11. 2017 v 15:59, Matthew Knepley : > > On Wed, Nov 8, 2017 at 9:14 AM, Vaclav Hapla > wrote: > >> 8. 11. 2017 v 14:52, Jed Brown > >: >> >> Matthew Knepley mailto:knep...@gmail.com>> writes: >> >>> On Wed, Nov 8, 2017 at 4:52 A

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 9:14 AM, Vaclav Hapla wrote: > > 8. 11. 2017 v 14:52, Jed Brown : > > Matthew Knepley writes: > > On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla > wrote: > > > 8. 11. 2017 v 9:06, Lisandro Dalcin : > > On 8 November 2017 at 05:51, Smith, Barry F. wrote: > > > On Nov 7, 201

Re: [petsc-dev] proposed minor PetscPartitioner changes

> 8. 11. 2017 v 14:52, Jed Brown : > > Matthew Knepley mailto:knep...@gmail.com>> writes: > >> On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla >> wrote: >> >>> 8. 11. 2017 v 9:06, Lisandro Dalcin : On 8 November 2017 at 05:51, Smith, Barry F. wrote: > >> On Nov 7, 2017,

Re: [petsc-dev] proposed minor PetscPartitioner changes

Matthew Knepley writes: > On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla > wrote: > >> >> > 8. 11. 2017 v 9:06, Lisandro Dalcin : >> > >> > On 8 November 2017 at 05:51, Smith, Barry F. wrote: >> >> >> >>> On Nov 7, 2017, at 1:33 AM, Lisandro Dalcin wrote: >> >>> >> >>> The only concern I have ab

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla wrote: > > > 8. 11. 2017 v 9:06, Lisandro Dalcin : > > > > On 8 November 2017 at 05:51, Smith, Barry F. wrote: > >> > >>> On Nov 7, 2017, at 1:33 AM, Lisandro Dalcin wrote: > >>> > >>> The only concern I have about PetscPartitioner is that the API de

Re: [petsc-dev] proposed minor PetscPartitioner changes

On Wed, Nov 8, 2017 at 4:52 AM, Vaclav Hapla wrote: > > > 8. 11. 2017 v 9:06, Lisandro Dalcin : > > > > On 8 November 2017 at 05:51, Smith, Barry F. wrote: > >> > >>> On Nov 7, 2017, at 1:33 AM, Lisandro Dalcin wrote: > >>> > >>> The only concern I have about PetscPartitioner is that the API de

Re: [petsc-dev] proposed minor PetscPartitioner changes

On 8 November 2017 at 12:52, Vaclav Hapla wrote: > > I propose > - to rename Mat Partitioning to just Partitioning/-er or take over the name > PetscPartitioner, > - what is now PetscPartitioner would be MeshPartitioning/-er and it would > become sort of adapter from DMPlex meshes to general grap

Re: [petsc-dev] proposed minor PetscPartitioner changes

> 8. 11. 2017 v 9:06, Lisandro Dalcin : > > On 8 November 2017 at 05:51, Smith, Barry F. wrote: >> >>> On Nov 7, 2017, at 1:33 AM, Lisandro Dalcin wrote: >>> >>> The only concern I have about PetscPartitioner is that the API depends >>> on DM (PetscPartitionerPartition_ routines). Maybe >>> P

Re: [petsc-dev] proposed minor PetscPartitioner changes

On 8 November 2017 at 05:51, Smith, Barry F. wrote: > >> On Nov 7, 2017, at 1:33 AM, Lisandro Dalcin wrote: >> >> The only concern I have about PetscPartitioner is that the API depends >> on DM (PetscPartitionerPartition_ routines). Maybe >> PetscPartitioner should eventually move to became more