June 2012 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] SNESLineSearchApply_BT logic divergence
by Matthew Knepley 15 Jun '12

15 Jun '12

On Sat, Jun 16, 2012 at 12:03 AM, Daniel Lowell <redratio1(a)gmail.com> wrote: > Hey Satish, > > So I'm having an issue with this function: > > *#define PetscObjectComposedDataGetReal <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>(obj,id,data,flag) \**((((obj)->realcomposedstate && ((obj)->realcomposedstate[id] == (obj)->state))? \**(data = (obj)->realcomposeddata[id],flag = PETSC_TRUE <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>) : (flag = PETSC_FALSE <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>)),0)* > > > Called from VecNorm which is called from SNESLineSearchApply_BT > > I have two examples running one is the vanilla ex14 using my GPU vector > and matrix type. The other example is a variant of ex14test where I am > implementing GPU formfunction and formjacobian. > ex14 vanilla runs through correctly, however ex14test diverges in the > logic within VecNorm, specifically line 164: > /* > * Cached data? > */ > if (type!=NORM_1_AND_2) { > ierr = PetscObjectComposedDataGetReal > ((PetscObject)x,NormIds[type],*val,flg);CHKERRQ(ierr); > if (flg) PetscFunctionReturn(0); > } > > The ex14 detects there is a "real" part, however the ex14test does not and > VecNorm returns. > > "val" in VecNorm is PetscReal gnorm = fnorm defined in > SNESLineSearchApply_BT. > For ex14: val[0]=3.44e-317, val[1]: 0.580 > For ex14test: val[0]=3.44e-317, val[1]: 0.029 > > > This difference makes SNESLineSearchApply_BT branch into different > execution paths. > > I'm not sure where the issue could have come from. Any ideas? > If you change values in a Vec, you must increment the internal state, since we cache norms. The internal functions for array getting do this automatically, so I am not sure why this is messing up. Did you bypass them? Matt > > -- > Daniel Lowell > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

SNESLineSearchApply_BT logic divergence
by Daniel Lowell 15 Jun '12

15 Jun '12

Hey Satish, So I'm having an issue with this function: *#define PetscObjectComposedDataGetReal <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>(obj,id,data,flag) \**((((obj)->realcomposedstate && ((obj)->realcomposedstate[id] == (obj)->state))? \**(data = (obj)->realcomposeddata[id],flag = PETSC_TRUE <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>) : (flag = PETSC_FALSE <http://www.mcs.anl.gov/petsc/petsc-current/include/petsc-private/docs/manua…>)),0)* Called from VecNorm which is called from SNESLineSearchApply_BT I have two examples running one is the vanilla ex14 using my GPU vector and matrix type. The other example is a variant of ex14test where I am implementing GPU formfunction and formjacobian. ex14 vanilla runs through correctly, however ex14test diverges in the logic within VecNorm, specifically line 164: /* * Cached data? */ if (type!=NORM_1_AND_2) { ierr = PetscObjectComposedDataGetReal ((PetscObject)x,NormIds[type],*val,flg);CHKERRQ(ierr); if (flg) PetscFunctionReturn(0); } The ex14 detects there is a "real" part, however the ex14test does not and VecNorm returns. "val" in VecNorm is PetscReal gnorm = fnorm defined in SNESLineSearchApply_BT. For ex14: val[0]=3.44e-317, val[1]: 0.580 For ex14test: val[0]=3.44e-317, val[1]: 0.029 This difference makes SNESLineSearchApply_BT branch into different execution paths. I'm not sure where the issue could have come from. Any ideas? -- Daniel Lowell

1 0

Re: [petsc-dev] How to dump matrix in petsc
by Dave Nystrom 15 Jun '12

15 Jun '12

Thanks. Jed Brown writes: > src/ksp/ksp/examples/tutorials/ex10.c > > On Fri, Jun 15, 2012 at 8:20 AM, Dave Nystrom <dnystrom1(a)comcast.net> wrote: > > > Jed Brown writes: > > > On Sun, Jun 10, 2012 at 10:07 AM, Dave Nystrom <dnystrom1(a)comcast.net > > >wrote: > > > > > > > Is there an easy way to dump a matrix and rhs in petsc? I have a > > > > particular > > > > system that has been challenging to solve with petsc other than using > > > > direct > > > > solves. Also, if I could dump the linear system, is it acceptable to > > post > > > > it > > > > on this email list so that someone who knows more about petsc and > > linear > > > > solvers could investigate it if they had the time and inclination? > > > > > > > > > > Run with -ksp_view_binary (it produces a file called 'binaryoutput') > > > > > > Don't email large files to the list. You can send up to a few MB to > > > petsc-maint. If you can't host larger files yourself, anonymous ftp to > > > ftp.mcs.anl.gov, cd incoming, and upload the file (preferably with a > > unique > > > name), then tell us the file name. > > > > Once I have my 'binaryoutput' file, is there a petsc example that shows how > > to read this file back into petsc and use it? I'm not finding online > > documentation about this option. > >

1 0

Re: [petsc-dev] How to dump matrix in petsc
by Jed Brown 15 Jun '12

15 Jun '12

src/ksp/ksp/examples/tutorials/ex10.c On Fri, Jun 15, 2012 at 8:20 AM, Dave Nystrom <dnystrom1(a)comcast.net> wrote: > Jed Brown writes: > > On Sun, Jun 10, 2012 at 10:07 AM, Dave Nystrom <dnystrom1(a)comcast.net > >wrote: > > > > > Is there an easy way to dump a matrix and rhs in petsc? I have a > > > particular > > > system that has been challenging to solve with petsc other than using > > > direct > > > solves. Also, if I could dump the linear system, is it acceptable to > post > > > it > > > on this email list so that someone who knows more about petsc and > linear > > > solvers could investigate it if they had the time and inclination? > > > > > > > Run with -ksp_view_binary (it produces a file called 'binaryoutput') > > > > Don't email large files to the list. You can send up to a few MB to > > petsc-maint. If you can't host larger files yourself, anonymous ftp to > > ftp.mcs.anl.gov, cd incoming, and upload the file (preferably with a > unique > > name), then tell us the file name. > > Once I have my 'binaryoutput' file, is there a petsc example that shows how > to read this file back into petsc and use it? I'm not finding online > documentation about this option. >

1 0

Re: [petsc-dev] How to dump matrix in petsc
by Dave Nystrom 15 Jun '12

15 Jun '12

Jed Brown writes: > On Sun, Jun 10, 2012 at 10:07 AM, Dave Nystrom <dnystrom1(a)comcast.net>wrote: > > > Is there an easy way to dump a matrix and rhs in petsc? I have a > > particular > > system that has been challenging to solve with petsc other than using > > direct > > solves. Also, if I could dump the linear system, is it acceptable to post > > it > > on this email list so that someone who knows more about petsc and linear > > solvers could investigate it if they had the time and inclination? > > > > Run with -ksp_view_binary (it produces a file called 'binaryoutput') > > Don't email large files to the list. You can send up to a few MB to > petsc-maint. If you can't host larger files yourself, anonymous ftp to > ftp.mcs.anl.gov, cd incoming, and upload the file (preferably with a unique > name), then tell us the file name. Once I have my 'binaryoutput' file, is there a petsc example that shows how to read this file back into petsc and use it? I'm not finding online documentation about this option.

1 0

Re: [petsc-dev] checking sanity of user evaluations
by Barry Smith 14 Jun '12

14 Jun '12

On Jun 14, 2012, at 3:05 PM, Jed Brown wrote: > In the case of a matrix, shouldn't these checks go the first place we encounter them (MatSetValues)? Could be. > > Running with -fp_trap is really good at finding these kind of mistakes. > > On Wed, Jun 13, 2012 at 8:50 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > On return from user FormFunction and FormJacobian in debug mode should we check if all user output is sane? That is numerical values in the matrix and vector are sane, no 1.e-307 or 1.e85 and stuff like that? > > Barry > >

1 0

Re: [petsc-dev] checking sanity of user evaluations
by Jed Brown 14 Jun '12

14 Jun '12

In the case of a matrix, shouldn't these checks go the first place we encounter them (MatSetValues)? Running with -fp_trap is really good at finding these kind of mistakes. On Wed, Jun 13, 2012 at 8:50 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > On return from user FormFunction and FormJacobian in debug mode should > we check if all user output is sane? That is numerical values in the matrix > and vector are sane, no 1.e-307 or 1.e85 and stuff like that? > > Barry > >

1 0

Re: [petsc-dev] [petsc-users] MatSetBlockSize no longer works after MatCreateSeqAIJ
by Matthew Knepley 14 Jun '12

14 Jun '12

On Thu, Jun 14, 2012 at 11:16 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > On Jun 13, 2012, at 10:12 PM, Jed Brown wrote: > > > Okay, I thought switching to MatCreateAIJ was a good time to add it, bit > it's kind of too late now. > > Good point. Do it, call it a bug when we didn't add the bs on that > change so this is worthy of a patch for 3.3 Please no. This will break a TON of code, vs. the 1-3 messages we will get now. Matt > > Barry > > > > > On Jun 13, 2012 10:06 PM, "Barry Smith" <bsmith(a)mcs.anl.gov> wrote: > > > > On Jun 13, 2012, at 8:03 PM, Jed Brown wrote: > > > > > What I do is > > > > > > MatCreate(comm,&A); > > > MatSetSizes(A,...); > > > MatSetBlockSize(A,bs); > > > MatSetOptionsPrefix(A,"yourchoice_"); > > > MatSetFromOptions(A); > > > MatXAIJSetPreallocation(A,...); > > > > > > This should work with any matrix type, parallel and sequential, and > you can specify it without interfering with any other matrices using > -yourchoice_mat_type aij {baij, sbaij}. > > > > > > > > > Devs, is there a reason that block size wasn't added to the > convenience constructor? > > > > To break less stuff and not make most people change their > MatCreateMPIAIJ call() > > > > > Wasn't there a discussion about adding it? > > > > Yes > > > > | What should we do? > > > > Get rid of convenience constructors? > > > > Barry > > > > > > > > > > On Wed, Jun 13, 2012 at 7:55 PM, Geoffrey Irving <irving(a)naml.us> > wrote: > > > Hello, > > > > > > The following code used to work, but breaks after upgrading to 3.3: > > > > > > .... > > > CHECK(MatCreateSeqAIJ(comm,3*n,3*n,0,scalar_view(nnz).data(),&mat)); > > > CHECK(MatSetBlockSize(mat,3)); > > > ... > > > > > > The error follows. Presumably MatSetBlockSize got more strict, and I > > > need to break the single MatCreateSeqAIJ into multiple lines (matrix > > > creation followed by preallocation) in order to insert MatSetBlockSize > > > in the middle. What are the correct functions to call? > > > > > > Thanks, > > > Geoffrey > > > > > > [0]PETSC ERROR: --------------------- Error Message > > > ------------------------------------ > > > [0]PETSC ERROR: Arguments are incompatible! > > > [0]PETSC ERROR: Cannot change block size 1 to 3! > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > > 14:20:42 CDT 2012 > > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > > [0]PETSC ERROR: See docs/index.html for manual pages. > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > > Wed Jun 13 17:51:34 2012 > > > [0]PETSC ERROR: Libraries linked from > > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > > --PETSC_ARCH=darwin > > > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > > --with-cc=/opt/local/bin/openmpicc > > > --with-cxx=/opt/local/bin/openmpicxx > > > --with-mpiexec=/opt/local/bin/openmpiexec > > > --with-lapack-lib=/usr/lib/liblapack.dylib > > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > > --download-ml --download-metis --download-parmetis --download-blacs > > > --download-scalapack --download-mumps --download-ptscotch > > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: PetscLayoutSetBlockSize() line 460 in > > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/vec/vec/impls/mpi/pmap.c > > > [0]PETSC ERROR: MatSetBlockSize() line 6691 in > > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/mat/interface/matrix.c > > > [0]PETSC ERROR: --------------------- Error Message > > > ------------------------------------ > > > [0]PETSC ERROR: Arguments are incompatible! > > > [0]PETSC ERROR: ! > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > > 14:20:42 CDT 2012 > > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > > [0]PETSC ERROR: See docs/index.html for manual pages. > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > > Wed Jun 13 17:51:34 2012 > > > [0]PETSC ERROR: Libraries linked from > > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > > --PETSC_ARCH=darwin > > > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > > --with-cc=/opt/local/bin/openmpicc > > > --with-cxx=/opt/local/bin/openmpicxx > > > --with-mpiexec=/opt/local/bin/openmpiexec > > > --with-lapack-lib=/usr/lib/liblapack.dylib > > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > > --download-ml --download-metis --download-parmetis --download-blacs > > > --download-scalapack --download-mumps --download-ptscotch > > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > > [0]PETSC ERROR: > > > > ------------------------------------------------------------------------ > > > [0]PETSC ERROR: PetscSolidMat() line 114 in petsc/ksp.cpp > > > > > > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] [petsc-users] MatSetBlockSize no longer works after MatCreateSeqAIJ
by Barry Smith 13 Jun '12

13 Jun '12

On Jun 13, 2012, at 10:12 PM, Jed Brown wrote: > Okay, I thought switching to MatCreateAIJ was a good time to add it, bit it's kind of too late now. Good point. Do it, call it a bug when we didn't add the bs on that change so this is worthy of a patch for 3.3 Barry > > On Jun 13, 2012 10:06 PM, "Barry Smith" <bsmith(a)mcs.anl.gov> wrote: > > On Jun 13, 2012, at 8:03 PM, Jed Brown wrote: > > > What I do is > > > > MatCreate(comm,&A); > > MatSetSizes(A,...); > > MatSetBlockSize(A,bs); > > MatSetOptionsPrefix(A,"yourchoice_"); > > MatSetFromOptions(A); > > MatXAIJSetPreallocation(A,...); > > > > This should work with any matrix type, parallel and sequential, and you can specify it without interfering with any other matrices using -yourchoice_mat_type aij {baij, sbaij}. > > > > > > Devs, is there a reason that block size wasn't added to the convenience constructor? > > To break less stuff and not make most people change their MatCreateMPIAIJ call() > > > Wasn't there a discussion about adding it? > > Yes > > | What should we do? > > Get rid of convenience constructors? > > Barry > > > > > > On Wed, Jun 13, 2012 at 7:55 PM, Geoffrey Irving <irving(a)naml.us> wrote: > > Hello, > > > > The following code used to work, but breaks after upgrading to 3.3: > > > > .... > > CHECK(MatCreateSeqAIJ(comm,3*n,3*n,0,scalar_view(nnz).data(),&mat)); > > CHECK(MatSetBlockSize(mat,3)); > > ... > > > > The error follows. Presumably MatSetBlockSize got more strict, and I > > need to break the single MatCreateSeqAIJ into multiple lines (matrix > > creation followed by preallocation) in order to insert MatSetBlockSize > > in the middle. What are the correct functions to call? > > > > Thanks, > > Geoffrey > > > > [0]PETSC ERROR: --------------------- Error Message > > ------------------------------------ > > [0]PETSC ERROR: Arguments are incompatible! > > [0]PETSC ERROR: Cannot change block size 1 to 3! > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > 14:20:42 CDT 2012 > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > [0]PETSC ERROR: See docs/index.html for manual pages. > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > Wed Jun 13 17:51:34 2012 > > [0]PETSC ERROR: Libraries linked from > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > --PETSC_ARCH=darwin > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > --with-cc=/opt/local/bin/openmpicc > > --with-cxx=/opt/local/bin/openmpicxx > > --with-mpiexec=/opt/local/bin/openmpiexec > > --with-lapack-lib=/usr/lib/liblapack.dylib > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > --download-ml --download-metis --download-parmetis --download-blacs > > --download-scalapack --download-mumps --download-ptscotch > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: PetscLayoutSetBlockSize() line 460 in > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/vec/vec/impls/mpi/pmap.c > > [0]PETSC ERROR: MatSetBlockSize() line 6691 in > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/mat/interface/matrix.c > > [0]PETSC ERROR: --------------------- Error Message > > ------------------------------------ > > [0]PETSC ERROR: Arguments are incompatible! > > [0]PETSC ERROR: ! > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > 14:20:42 CDT 2012 > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > [0]PETSC ERROR: See docs/index.html for manual pages. > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > Wed Jun 13 17:51:34 2012 > > [0]PETSC ERROR: Libraries linked from > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > --PETSC_ARCH=darwin > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > --with-cc=/opt/local/bin/openmpicc > > --with-cxx=/opt/local/bin/openmpicxx > > --with-mpiexec=/opt/local/bin/openmpiexec > > --with-lapack-lib=/usr/lib/liblapack.dylib > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > --download-ml --download-metis --download-parmetis --download-blacs > > --download-scalapack --download-mumps --download-ptscotch > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: PetscSolidMat() line 114 in petsc/ksp.cpp > > >

1 0

Re: [petsc-dev] [petsc-users] MatSetBlockSize no longer works after MatCreateSeqAIJ
by Jed Brown 13 Jun '12

13 Jun '12

Okay, I thought switching to MatCreateAIJ was a good time to add it, bit it's kind of too late now. On Jun 13, 2012 10:06 PM, "Barry Smith" <bsmith(a)mcs.anl.gov> wrote: > > On Jun 13, 2012, at 8:03 PM, Jed Brown wrote: > > > What I do is > > > > MatCreate(comm,&A); > > MatSetSizes(A,...); > > MatSetBlockSize(A,bs); > > MatSetOptionsPrefix(A,"yourchoice_"); > > MatSetFromOptions(A); > > MatXAIJSetPreallocation(A,...); > > > > This should work with any matrix type, parallel and sequential, and you > can specify it without interfering with any other matrices using > -yourchoice_mat_type aij {baij, sbaij}. > > > > > > Devs, is there a reason that block size wasn't added to the convenience > constructor? > > To break less stuff and not make most people change their > MatCreateMPIAIJ call() > > > Wasn't there a discussion about adding it? > > Yes > > | What should we do? > > Get rid of convenience constructors? > > Barry > > > > > > On Wed, Jun 13, 2012 at 7:55 PM, Geoffrey Irving <irving(a)naml.us> wrote: > > Hello, > > > > The following code used to work, but breaks after upgrading to 3.3: > > > > .... > > CHECK(MatCreateSeqAIJ(comm,3*n,3*n,0,scalar_view(nnz).data(),&mat)); > > CHECK(MatSetBlockSize(mat,3)); > > ... > > > > The error follows. Presumably MatSetBlockSize got more strict, and I > > need to break the single MatCreateSeqAIJ into multiple lines (matrix > > creation followed by preallocation) in order to insert MatSetBlockSize > > in the middle. What are the correct functions to call? > > > > Thanks, > > Geoffrey > > > > [0]PETSC ERROR: --------------------- Error Message > > ------------------------------------ > > [0]PETSC ERROR: Arguments are incompatible! > > [0]PETSC ERROR: Cannot change block size 1 to 3! > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > 14:20:42 CDT 2012 > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > [0]PETSC ERROR: See docs/index.html for manual pages. > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > Wed Jun 13 17:51:34 2012 > > [0]PETSC ERROR: Libraries linked from > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > --PETSC_ARCH=darwin > > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > --with-cc=/opt/local/bin/openmpicc > > --with-cxx=/opt/local/bin/openmpicxx > > --with-mpiexec=/opt/local/bin/openmpiexec > > --with-lapack-lib=/usr/lib/liblapack.dylib > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > --download-ml --download-metis --download-parmetis --download-blacs > > --download-scalapack --download-mumps --download-ptscotch > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: PetscLayoutSetBlockSize() line 460 in > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/vec/vec/impls/mpi/pmap.c > > [0]PETSC ERROR: MatSetBlockSize() line 6691 in > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/petsc-3.3-p0/src/mat/interface/matrix.c > > [0]PETSC ERROR: --------------------- Error Message > > ------------------------------------ > > [0]PETSC ERROR: Arguments are incompatible! > > [0]PETSC ERROR: ! > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Petsc Release Version 3.3.0, Patch 0, Tue Jun 5 > > 14:20:42 CDT 2012 > > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > > [0]PETSC ERROR: See docs/index.html for manual pages. > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: Unknown Name on a darwin named tile.local by irving > > Wed Jun 13 17:51:34 2012 > > [0]PETSC ERROR: Libraries linked from > > > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc/lib > > [0]PETSC ERROR: Configure run at Wed Jun 13 12:11:05 2012 > > [0]PETSC ERROR: Configure options --prefix=/opt/local --with-python > > --with-debugging=0 --with-c-support=1 --with-c++-support=1 > > --with-pic=fPIC --with-shared-libraries=0 --with-mpi=1 > > --PETSC_ARCH=darwin > > > --prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_petsc/petsc/work/destroot/opt/local/lib/petsc > > --with-cc=/opt/local/bin/openmpicc > > --with-cxx=/opt/local/bin/openmpicxx > > --with-mpiexec=/opt/local/bin/openmpiexec > > --with-lapack-lib=/usr/lib/liblapack.dylib > > --with-blas-lib=/usr/lib/libblas.dylib --download-umfpack=1 > > --download-ml --download-metis --download-parmetis --download-blacs > > --download-scalapack --download-mumps --download-ptscotch > > --with-fc=/opt/local/bin/openmpif90 --LIBS=-lstdc++ > > [0]PETSC ERROR: > > ------------------------------------------------------------------------ > > [0]PETSC ERROR: PetscSolidMat() line 114 in petsc/ksp.cpp > > > >

1 0