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

Re: [petsc-dev] DM RefineLevel and CoarsenLevel
by Matthew Knepley 06 May '12

06 May '12

That sounds fine to me. Matt On Sun, May 6, 2012 at 3:44 PM, Jed Brown <jedbrown(a)mcs.anl.gov> wrote: > Should the refinement level be copied over by DMCoarsen (and the coarsen > level be copied by DMRefine)? > > It's useful for diagnostics to be able to define a universal level. If I > use PCMG and -snes_grid_sequence, there is effectively a sequence like > > DMCreate(,&dm0); // r=0,c=0 > DMRefine(dm0,&dmf); // r=1,c=0 > DMCoarsen(dmf,&dmc); // r=0,c=1 > > > I would like a way to identify dmc as being on the "same level" as dm0. > -- 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

DM RefineLevel and CoarsenLevel
by Jed Brown 06 May '12

06 May '12

Should the refinement level be copied over by DMCoarsen (and the coarsen level be copied by DMRefine)? It's useful for diagnostics to be able to define a universal level. If I use PCMG and -snes_grid_sequence, there is effectively a sequence like DMCreate(,&dm0); // r=0,c=0 DMRefine(dm0,&dmf); // r=1,c=0 DMCoarsen(dmf,&dmc); // r=0,c=1 I would like a way to identify dmc as being on the "same level" as dm0.

1 0

Re: [petsc-dev] Error in make test
by Shri 06 May '12

06 May '12

Stefano, Barry added additional guard to ensure that the thread code is not active. Please pull and retry. Sorry for the trouble, we are experimenting with the thread code so some things might get broken in the process. Shri On May 6, 2012, at 6:24 AM, Stefano Zampini wrote: > I've just pulled and make test is broken for me. There's something messed up with PetscThreadCommunicators. > Besides, I did not configure petsc-dev to use threads. > A revision which works for me is 23244. > I'm using openmpi.1.5.5. > > Here is the traceback of the error > > [0]PETSC ERROR: PetscCommDuplicate() line 200 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/tagm.c > [0]PETSC ERROR: PetscHeaderCreate_Private() line 51 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/inherit.c > [0]PETSC ERROR: SNESCreate() line 1293 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/snes/interface/snes.c > [0]PETSC ERROR: main() line 102 in src/snes/examples/tutorials/ex19.c > > > 2012/5/5 Stefano Zampini <stefano.zampini(a)gmail.com> > I reverted to 23244. > > 2012/5/5 Shri <abhyshr(a)mcs.anl.gov> > I've disabled the threadcomm code temporarily, so hopefully your code should run as before now. Please pull and retry. > > Thanks, > Shri > > Same error on make test. > > Moreover, I got some mpi errors running my fortran codes and PETSc doesn't show the traceback > I can only see that the problem occurs in PetscInitialize > Here is the cryptic output from MPI (openmpi.1.4.5) > > [neo155:25438] *** An error occurred in MPI_Attr_get > [neo155:25438] *** on communicator MPI COMMUNICATOR 3 DUP FROM 1 > [neo155:25438] *** MPI_ERR_OTHER: known error not in list > [neo155:25438] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort) > > > 2012/5/5 Shri <abhyshr(a)mcs.anl.gov> > I pushed some changes to fix these errors. Can you please pull and retry. > > > I had pulled some hours ago from http://petsc.cs.iit.edu/petsc/petsc-dev/rev/61898f35c333 and obtained the following error on make test > > [0]PETSC ERROR: PetscCommDuplicate() line 200 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/tagm.c > [0]PETSC ERROR: PetscHeaderCreate_Private() line 51 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/inherit.c > [0]PETSC ERROR: SNESCreate() line 1293 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/snes/interface/snes.c > [0]PETSC ERROR: main() line 102 in src/snes/examples/tutorials/ex19.c > > I've just pulled and got the following error after typing make test > > [0]PETSC ERROR: PetscCommDestroy() line 246 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/tagm.c > [0]PETSC ERROR: PetscThreadCommFinalizePackage() line 36 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/threadcomm/interface/dlregisthreadcomm.c > [0]PETSC ERROR: PetscRegisterFinalizeAll() line 313 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/destroy.c > [0]PETSC ERROR: PetscFinalize() line 1080 in /work/adz/zampini/MyWorkingCopyOfPetsc/petsc-dev/src/sys/objects/pinit. > > I did not configure for a threaded version of PETSc. > > -- > Stefano > > > > > -- > Stefano > > > > > -- > Stefano > > > > -- > Stefano

1 0

Re: [petsc-dev] Error during KSPDestroy
by Alexander Grayver 06 May '12

06 May '12

Barry, Are you able to reproduce the error? I've updated petsc-dev it is still there unfortunately. On 06.05.2012 20:00, Barry Smith wrote: > Alexander, > > Sorry, never mind. I found the code in the earlier email., > > barry > > On May 6, 2012, at 12:49 PM, Barry Smith wrote: > >> Alexander, >> >> No attached test program. (only valgrind log). >> >> Barry >> >> On May 6, 2012, at 8:21 AM, Alexander Grayver wrote: >> >>> On 06.05.2012 15:07, Matthew Knepley wrote: >>>>> Hello, >>>>> >>>>> I use KSP and random rhs to compute largest singular value: >>>>> >>>>> 1) Is this the whole program? If not, this can be caused by memory corruption somewhere else. This is what I suspect. >>>> Matt, >>>> >>>> I can reproduce error using attached test programm and this matrix (7 mb): >>>> http://dl.dropbox.com/u/60982984/A.dat >>>> >>>> I run it fine with the latest petsc-dev: >>>> >>>> 1.405802e+00 >>>> >>>> Can you valgrind it on your machine? >>>> >>> I did: >>> valgrind --tool=memcheck -q --num-callers=20 --log-file=valgrind.log.%p /solveTest -ksp_monitor_true_residual -log_summary -mat_type aij -ksp_rtol 1.0e-10 -malloc off >>> >>> The error is better constrained: >>> >>> ==20287== Invalid read of size 8 >>> ==20287== at 0x7874B4C: opal_os_path (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-pal.so.0.0.0) >>> ==20287== by 0x75F2E27: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >>> ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >>> ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >>> ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >>> ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) >>> ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) >>> ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) >>> ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) >>> ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) >>> ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) >>> ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) >>> ==20287== by 0x4509F8: main (solveTest.c:66) >>> ==20287== Address 0xbde4860 is 0 bytes inside a block of size 2 alloc'd >>> ==20287== at 0x4C26B9B: malloc (vg_replace_malloc.c:263) >>> ==20287== by 0x92876DF: vasprintf (in /lib64/libc-2.11.1.so) >>> ==20287== by 0x9266C67: asprintf (in /lib64/libc-2.11.1.so) >>> ==20287== by 0x75F1701: orte_util_convert_vpid_to_string (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >>> ==20287== by 0x75F2D4A: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >>> ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >>> ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >>> ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >>> ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) >>> ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) >>> ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) >>> ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) >>> ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) >>> ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) >>> ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) >>> ==20287== by 0x4509F8: main (solveTest.c:66) >>> >>> Full log is attached. >>> >>> Important. >>> If I comment this line: >>> KSPComputeExtremeSingularValues(ksp,&maxx,&minx); >>> >>> It works. >>> >>> -- >>> Regards, >>> Alexander >>> >>> <valgrind.zip> -- Regards, Alexander

1 0

Re: [petsc-dev] Error during KSPDestroy
by Barry Smith 06 May '12

06 May '12

Alexander, Sorry, never mind. I found the code in the earlier email., barry On May 6, 2012, at 12:49 PM, Barry Smith wrote: > > Alexander, > > No attached test program. (only valgrind log). > > Barry > > On May 6, 2012, at 8:21 AM, Alexander Grayver wrote: > >> On 06.05.2012 15:07, Matthew Knepley wrote: >>>> Hello, >>>> >>>> I use KSP and random rhs to compute largest singular value: >>>> >>>> 1) Is this the whole program? If not, this can be caused by memory corruption somewhere else. This is what I suspect. >>> >>> Matt, >>> >>> I can reproduce error using attached test programm and this matrix (7 mb): >>> http://dl.dropbox.com/u/60982984/A.dat >>> >>> I run it fine with the latest petsc-dev: >>> >>> 1.405802e+00 >>> >>> Can you valgrind it on your machine? >>> >> >> I did: >> valgrind --tool=memcheck -q --num-callers=20 --log-file=valgrind.log.%p /solveTest -ksp_monitor_true_residual -log_summary -mat_type aij -ksp_rtol 1.0e-10 -malloc off >> >> The error is better constrained: >> >> ==20287== Invalid read of size 8 >> ==20287== at 0x7874B4C: opal_os_path (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-pal.so.0.0.0) >> ==20287== by 0x75F2E27: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >> ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >> ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >> ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >> ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) >> ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) >> ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) >> ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) >> ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) >> ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) >> ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) >> ==20287== by 0x4509F8: main (solveTest.c:66) >> ==20287== Address 0xbde4860 is 0 bytes inside a block of size 2 alloc'd >> ==20287== at 0x4C26B9B: malloc (vg_replace_malloc.c:263) >> ==20287== by 0x92876DF: vasprintf (in /lib64/libc-2.11.1.so) >> ==20287== by 0x9266C67: asprintf (in /lib64/libc-2.11.1.so) >> ==20287== by 0x75F1701: orte_util_convert_vpid_to_string (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >> ==20287== by 0x75F2D4A: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >> ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) >> ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >> ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) >> ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) >> ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) >> ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) >> ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) >> ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) >> ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) >> ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) >> ==20287== by 0x4509F8: main (solveTest.c:66) >> >> Full log is attached. >> >> Important. >> If I comment this line: >> KSPComputeExtremeSingularValues(ksp, &maxx, &minx); >> >> It works. >> >> -- >> Regards, >> Alexander >> >> <valgrind.zip> >

1 0

Re: [petsc-dev] PC defaults when matrix is not available at PCSetFromOptions
by Jed Brown 06 May '12

06 May '12

On Sun, May 6, 2012 at 11:47 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > I see. So if the Mat is not known when PCSetFromOptions() is called then > PCSetFromOptions() generates a bad guess for the PC to use. > > Presumably this has always been true. > Sure, but with DMMG, the top level PC was always set to PCMG and the PCSetFromOptions() on levels was not called until later: #0 PCGetDefaultType_Private (pc=0xc295e0, type=0x7fffffff8c18) at /home/jed/petsc-3.2/src/ksp/pc/interface/precon.c:20 #1 0x00007ffff74d083e in PCSetFromOptions (pc=0xc295e0) at /home/jed/petsc-3.2/src/ksp/pc/interface/pcset.c:177 #2 0x00007ffff7554723 in KSPSetFromOptions (ksp=0xc27410) at /home/jed/petsc-3.2/src/ksp/ksp/interface/itcl.c:286 #3 0x00007ffff74a8765 in PCSetUp_MG (pc=0xaa6e20) at /home/jed/petsc-3.2/src/ksp/pc/impls/mg/mg.c:575 #4 0x00007ffff74c7946 in PCSetUp (pc=0xaa6e20) at /home/jed/petsc-3.2/src/ksp/pc/interface/precon.c:819 #5 0x00007ffff755a2ab in KSPSetUp (ksp=0xaa4c50) at /home/jed/petsc-3.2/src/ksp/ksp/interface/itfunc.c:260 #6 0x00007ffff755b549 in KSPSolve (ksp=0xaa4c50, b=0x8b1280, x=0xc86190) at /home/jed/petsc-3.2/src/ksp/ksp/interface/itfunc.c:379 #7 0x00007ffff7b7dc90 in SNES_KSPSolve (snes=0xaa2a10, ksp=0xaa4c50, b=0x8b1280, x=0xc86190) at /home/jed/petsc-3.2/src/snes/interface/snes.c:3396 #8 0x00007ffff7b93e23 in SNESSolve_LS (snes=0xaa2a10) at /home/jed/petsc-3.2/src/snes/impls/ls/ls.c:190 #9 0x00007ffff7b76b82 in SNESSolve (snes=0xaa2a10, b=0x0, x=0x8dce10) at /home/jed/petsc-3.2/src/snes/interface/snes.c:2676 #10 0x00007ffff7b56774 in DMMGSolveSNES (dmmg=0x874ff0, level=1) at /home/jed/petsc-3.2/src/snes/utils/damgsnes.c:540 #11 0x00007ffff7b4e712 in DMMGSolve (dmmg=0x874ff0) at /home/jed/petsc-3.2/src/snes/utils/damg.c:331 #12 0x0000000000415f06 in main (argc=14, argv=0x7fffffffd6f8) at ex48.c:1541 > > Presumably the PCSetFromOptions() has access to the DM? Can it inquire > of the DM what PC to default to if the Mat is not available? > Yeah, but PCGetDefaultType_Private() was trying not to switch on the matrix type, instead inquiring about functionality ierr = MatGetFactorAvailable(pc->pmat,"petsc",MAT_FACTOR_ICC,&flg1);CHKERRQ(ierr); ierr = MatGetFactorAvailable(pc->pmat,"petsc",MAT_FACTOR_ILU,&flg2);CHKERRQ(ierr); ierr = MatIsSymmetricKnown(pc->pmat,&set,&flg3);CHKERRQ(ierr); I suppose we could eagerly create pc->pmat here if a DM is available. Alternatively, we could check the refinement level of the DM and make PCMG the default, though I'm not sure we want ex5 to do MG by default.

1 0

Re: [petsc-dev] Error during KSPDestroy
by Barry Smith 06 May '12

06 May '12

Alexander, No attached test program. (only valgrind log). Barry On May 6, 2012, at 8:21 AM, Alexander Grayver wrote: > On 06.05.2012 15:07, Matthew Knepley wrote: >>> Hello, >>> >>> I use KSP and random rhs to compute largest singular value: >>> >>> 1) Is this the whole program? If not, this can be caused by memory corruption somewhere else. This is what I suspect. >> >> Matt, >> >> I can reproduce error using attached test programm and this matrix (7 mb): >> http://dl.dropbox.com/u/60982984/A.dat >> >> I run it fine with the latest petsc-dev: >> >> 1.405802e+00 >> >> Can you valgrind it on your machine? >> > > I did: > valgrind --tool=memcheck -q --num-callers=20 --log-file=valgrind.log.%p /solveTest -ksp_monitor_true_residual -log_summary -mat_type aij -ksp_rtol 1.0e-10 -malloc off > > The error is better constrained: > > ==20287== Invalid read of size 8 > ==20287== at 0x7874B4C: opal_os_path (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-pal.so.0.0.0) > ==20287== by 0x75F2E27: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) > ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) > ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) > ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) > ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) > ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) > ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) > ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) > ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) > ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) > ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) > ==20287== by 0x4509F8: main (solveTest.c:66) > ==20287== Address 0xbde4860 is 0 bytes inside a block of size 2 alloc'd > ==20287== at 0x4C26B9B: malloc (vg_replace_malloc.c:263) > ==20287== by 0x92876DF: vasprintf (in /lib64/libc-2.11.1.so) > ==20287== by 0x9266C67: asprintf (in /lib64/libc-2.11.1.so) > ==20287== by 0x75F1701: orte_util_convert_vpid_to_string (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) > ==20287== by 0x75F2D4A: orte_session_dir_finalize (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) > ==20287== by 0x76012E8: orte_errmgr_base_error_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libopen-rte.so.0.0.0) > ==20287== by 0x73396E9: ompi_mpi_abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) > ==20287== by 0x734F36E: PMPI_Abort (in /opt/mpi/intel/openmpi-1.4.2/lib/libmpi.so.0.0.2) > ==20287== by 0x7499AB: PetscDefaultSignalHandler (signal.c:169) > ==20287== by 0x749267: PetscSignalHandler_Private (signal.c:53) > ==20287== by 0x924B9DF: ??? (in /lib64/libc-2.11.1.so) > ==20287== by 0x535D9E: VecDestroyVecs (vector.c:653) > ==20287== by 0x68B61D: KSPReset_GMRES (gmres.c:258) > ==20287== by 0x6A9D39: KSPReset (itfunc.c:733) > ==20287== by 0x6AA839: KSPDestroy (itfunc.c:780) > ==20287== by 0x4509F8: main (solveTest.c:66) > > Full log is attached. > > Important. > If I comment this line: > KSPComputeExtremeSingularValues(ksp, &maxx, &minx); > > It works. > > -- > Regards, > Alexander > > <valgrind.zip>

1 0

Re: [petsc-dev] PC defaults when matrix is not available at PCSetFromOptions
by Barry Smith 06 May '12

06 May '12

I see. So if the Mat is not known when PCSetFromOptions() is called then PCSetFromOptions() generates a bad guess for the PC to use. Presumably this has always been true. Presumably the PCSetFromOptions() has access to the DM? Can it inquire of the DM what PC to default to if the Mat is not available? Screw it, take out DM and we'll go back to the old model :-( Barry On May 6, 2012, at 12:42 PM, Jed Brown wrote: > On Sun, May 6, 2012 at 11:38 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > PetscErrorCode PCSetUp(PC pc) > { > PetscErrorCode ierr; > const char *def; > > PetscFunctionBegin; > PetscValidHeaderSpecific(pc,PC_CLASSID,1); > if (!pc->mat) SETERRQ(((PetscObject)pc)->comm,PETSC_ERR_ARG_WRONGSTATE,"Matrix must be set first"); > > How can it be in there without a Mat? The Mat must be set before PCSetUp(). > > PetscErrorCode PCSetFromOptions(PC pc) > { > PetscErrorCode ierr; > char type[256]; > const char *def; > PetscBool flg; > > PetscFunctionBegin; > PetscValidHeaderSpecific(pc,PC_CLASSID,1); > > if (!PCRegisterAllCalled) {ierr = PCRegisterAll(PETSC_NULL);CHKERRQ(ierr);} > ierr = PetscObjectOptionsBegin((PetscObject)pc);CHKERRQ(ierr); > if (!((PetscObject)pc)->type_name) { > ierr = PCGetDefaultType_Private(pc,&def);CHKERRQ(ierr); > > > > > PetscErrorCode PCGetDefaultType_Private(PC pc,const char* type[]) > { > PetscErrorCode ierr; > PetscMPIInt size; > PetscBool flg1,flg2,set,flg3; > > PetscFunctionBegin; > ierr = MPI_Comm_size(((PetscObject)pc)->comm,&size);CHKERRQ(ierr); > if (pc->pmat) { > PetscErrorCode (*f)(Mat,MatReuse,Mat*); > ierr = PetscObjectQueryFunction((PetscObject)pc->pmat,"MatGetDiagonalBlock_C",(void (**)(void))&f);CHKERRQ(ierr); >

1 0

Re: [petsc-dev] PC defaults when matrix is not available at PCSetFromOptions
by Jed Brown 06 May '12

06 May '12

On Sun, May 6, 2012 at 11:38 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > PetscErrorCode PCSetUp(PC pc) > { > PetscErrorCode ierr; > const char *def; > > PetscFunctionBegin; > PetscValidHeaderSpecific(pc,PC_CLASSID,1); > if (!pc->mat) > SETERRQ(((PetscObject)pc)->comm,PETSC_ERR_ARG_WRONGSTATE,"Matrix must be > set first"); > > How can it be in there without a Mat? The Mat must be set before PCSetUp(). > PetscErrorCode PCSetFromOptions(PC pc) { PetscErrorCode ierr; char type[256]; const char *def; PetscBool flg; PetscFunctionBegin; PetscValidHeaderSpecific(pc,PC_CLASSID,1); if (!PCRegisterAllCalled) {ierr = PCRegisterAll(PETSC_NULL);CHKERRQ(ierr);} ierr = PetscObjectOptionsBegin((PetscObject)pc);CHKERRQ(ierr); if (!((PetscObject)pc)->type_name) { ierr = PCGetDefaultType_Private(pc,&def);CHKERRQ(ierr); PetscErrorCode PCGetDefaultType_Private(PC pc,const char* type[]) { PetscErrorCode ierr; PetscMPIInt size; PetscBool flg1,flg2,set,flg3; PetscFunctionBegin; ierr = MPI_Comm_size(((PetscObject)pc)->comm,&size);CHKERRQ(ierr); if (pc->pmat) { PetscErrorCode (*f)(Mat,MatReuse,Mat*); ierr = PetscObjectQueryFunction((PetscObject)pc->pmat,"MatGetDiagonalBlock_C",(void (**)(void))&f);CHKERRQ(ierr);

1 0

Re: [petsc-dev] PC defaults when matrix is not available at PCSetFromOptions
by Barry Smith 06 May '12

06 May '12

PetscErrorCode PCSetUp(PC pc) { PetscErrorCode ierr; const char *def; PetscFunctionBegin; PetscValidHeaderSpecific(pc,PC_CLASSID,1); if (!pc->mat) SETERRQ(((PetscObject)pc)->comm,PETSC_ERR_ARG_WRONGSTATE,"Matrix must be set first"); How can it be in there without a Mat? The Mat must be set before PCSetUp(). Barry On May 6, 2012, at 12:29 PM, Jed Brown wrote: > With the now-recommended approach of SNESSetDM(), a matrix is no longer available for PCGetDefaultType_Private(), so stuff like this fails: > > ~/petsc/src/snes/examples/tutorials$ ./ex5 -dm_mat_type sbaij > [0]PETSC ERROR: --------------------- Error Message ------------------------------------ > [0]PETSC ERROR: No support for this operation for this object type! > [0]PETSC ERROR: Factor type not supported! > [0]PETSC ERROR: ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Development HG revision: fb0b659c7d3475598a50a3736d056cce163b2de9 HG Date: Sun Apr 15 00:02:43 2012 +0000 > [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: ./ex5 on a mpich named batura by jed Sun May 6 11:25:55 2012 > [0]PETSC ERROR: Libraries linked from /home/jed/petsc/mpich/lib > [0]PETSC ERROR: Configure run at Tue Apr 17 15:54:40 2012 > [0]PETSC ERROR: Configure options --download-ams --download-blacs --download-chaco --download-hypre --download-metis --download-ml --download-parmetis --download-spai --download-spooles --download-sundials --download-superlu --download-superlu_dist --download-triangle --with-blas-lapack=/usr --with-c2html --with-cholmod-dir=/usr --with-lgrind --with-mpi-dir=/opt/mpich2 --with-pcbddc --with-pthreadclasses --with-shared-libraries --with-single-library=0 --with-sowing --with-umfpack-dir=/usr --with-x -PETSC_ARCH=mpich > [0]PETSC ERROR: ------------------------------------------------------------------------ > [0]PETSC ERROR: MatGetFactor_seqsbaij_petsc() line 1817 in /home/jed/petsc/src/mat/impls/sbaij/seq/sbaij.c > [0]PETSC ERROR: MatGetFactor() line 3990 in /home/jed/petsc/src/mat/interface/matrix.c > [0]PETSC ERROR: PCSetUp_ILU() line 214 in /home/jed/petsc/src/ksp/pc/impls/factor/ilu/ilu.c > [0]PETSC ERROR: PCSetUp() line 832 in /home/jed/petsc/src/ksp/pc/interface/precon.c > [0]PETSC ERROR: KSPSetUp() line 278 in /home/jed/petsc/src/ksp/ksp/interface/itfunc.c > [0]PETSC ERROR: KSPSolve() line 402 in /home/jed/petsc/src/ksp/ksp/interface/itfunc.c > [0]PETSC ERROR: SNES_KSPSolve() line 4224 in /home/jed/petsc/src/snes/interface/snes.c > [0]PETSC ERROR: SNESSolve_LS() line 200 in /home/jed/petsc/src/snes/impls/ls/ls.c > [0]PETSC ERROR: SNESSolve() line 3442 in /home/jed/petsc/src/snes/interface/snes.c > [0]PETSC ERROR: main() line 152 in src/snes/examples/tutorials/ex5.c > application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0 > > What are the alternatives to moving matrix creation (via DM) all the way up here?

1 0