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

Re: [petsc-dev] MatAXPY with DIFFERENT_NONZERO_PATTERN
by Alexander Grayver 23 Apr '12

23 Apr '12

On 23.04.2012 15:12, Jed Brown wrote: > My fault, now fixed: > > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/8a997a5a65d3 Jed, MatAXPY works fine, although during tests there was crash: Possible error running C/C++ src/snes/examples/tutorials/ex19 with 2 MPI processes See http://www.mcs.anl.gov/petsc/documentation/faq.html lid velocity = 0.0016, prandtl # = 1, grashof # = 1 [0]PETSC ERROR: PetscSplitReductionApply() line 328 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [0]PETSC ERROR: PetscSplitReductionEnd() line 247 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [0]PETSC ERROR: VecNormEnd() line 672 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [0]PETSC ERROR: SNESSolve_LS() line 172 in /home/lib/petsc-dev1/src/snes/impls/ls/ls.c [0]PETSC ERROR: SNESSolve() line 3458 in /home/lib/petsc-dev1/src/snes/interface/snes.c [0]PETSC ERROR: main() line 151 in src/snes/examples/tutorials/ex19.c [1]PETSC ERROR: PetscSplitReductionApply() line 328 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [1]PETSC ERROR: PetscSplitReductionEnd() line 247 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [1]PETSC ERROR: VecNormEnd() line 672 in /home/lib/petsc-dev1/src/vec/vec/utils/comb.c [1]PETSC ERROR: SNESSolve_LS() line 172 in /home/lib/petsc-dev1/src/snes/impls/ls/ls.c [1]PETSC ERROR: SNESSolve() line 3458 in /home/lib/petsc-dev1/src/snes/interface/snes.c [1]PETSC ERROR: main() line 151 in src/snes/examples/tutorials/ex19.c -- Regards, Alexander

1 0

Re: [petsc-dev] testing of nvcc incomplete?
by Matthew Knepley 23 Apr '12

23 Apr '12

On Sat, Oct 1, 2011 at 10:34 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > Matt, > > It looks like the tests of nvcc are incomplete? That is it checks that > the nvcc compiler works but does not check if the the resulting .o can be > linked successfully. That is it never checks linking of a nvcc compiled > thing??[see attached file: configure.log] > > I think this is wrong. See the attached configure.log it claims that > nvcc works but then conks out when checking the cuda version (because it > cannot link a nvcc program). This is the wrong place to conk out and > misleading message to user. It should conk when checking linking of nvcc > program with a useful error message about not being able to link. > http://petsc.cs.iit.edu/petsc/BuildSystem/annotate/7fc6b5eafc08/config/setC… Matt > Thanks > > Barry > > > -- 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] MatAXPY with DIFFERENT_NONZERO_PATTERN
by Jed Brown 23 Apr '12

23 Apr '12

My fault, now fixed: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/8a997a5a65d3 On Mon, Apr 23, 2012 at 02:39, Alexander Grayver <agrayver(a)gfz-potsdam.de>wrote: > ** > Jed, > > Thanks. However: > > [ 19%] Building C object > CMakeFiles/petsc.dir/src/sys/ftn-custom/zstartf.c.o > [ 19%] Building C object CMakeFiles/petsc.dir/src/sys/ftn-custom/zsys.c.o > Building C object CMakeFiles/petsc.dir/src/sys/ftn-custom/zutils.c.o > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(117): > error: expected a type specifier > extern MPI_Op MPIU_SUM; > ^ > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(117): > error: "MPI_Op" has already been declared in the current scope > extern MPI_Op MPIU_SUM; > ^ > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(128): > error: function "MPI_Op" is not a type name > extern MPI_Op PetscMaxSum_Op; > ^ > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(220): > error: function "MPI_Op" is not a type name > extern MPI_Op PetscADMax_Op; > ^ > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(221): > error: function "MPI_Op" is not a type name > extern MPI_Op PetscADMin_Op; > ^ > /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(343): > error: expression must be an lvalue or a function designator > *ierr = MPI_Op_create(PetscSum_Local,1,&MPIU_SUM); > > > On 23.04.2012 03:23, Jed Brown wrote: > > Thanks for the test case. Fixed here: > > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/7ac7040f19d7 > > On Sun, Apr 22, 2012 at 08:11, Alexander Grayver <agrayver(a)gfz-potsdam.de>wrote: > >> Matt, >> >> Here are matrices (double complex, 3 MB each): >> http://dl.dropbox.com/u/60982984/X.dat >> http://dl.dropbox.com/u/60982984/Y.dat >> >> Code: >> >> static char help[] = ""; >> int main(int argc,char **args) >> { >> Mat A,B; >> PetscErrorCode ierr; >> PetscViewer viewer; >> PetscScalar cone; >> >> PetscInitialize(&argc,&args,(char *)0,help); >> >> ierr = >> PetscViewerBinaryOpen(PETSC_COMM_WORLD,"Y.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); >> ierr = MatCreate(PETSC_COMM_WORLD,&A);CHKERRQ(ierr); >> ierr = MatSetFromOptions(A);CHKERRQ(ierr); >> ierr = MatLoad(A,viewer);CHKERRQ(ierr); >> ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); >> >> ierr = >> PetscViewerBinaryOpen(PETSC_COMM_WORLD,"X.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); >> ierr = MatCreate(PETSC_COMM_WORLD,&B);CHKERRQ(ierr); >> ierr = MatSetFromOptions(B);CHKERRQ(ierr); >> ierr = MatLoad(B,viewer);CHKERRQ(ierr); >> ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); >> >> cone = 1.0; >> ierr = MatAYPX(A,cone,B,DIFFERENT_NONZERO_PATTERN); >> ierr = PetscFinalize(); >> return 0; >> } >> >> It works fine if you run it with: >> mpirun -n 10 solveTest -mat_type aij >> >> and crashes if n > 10 >> >> Thanks. >> >> >> On 22.04.2012 14:51, Matthew Knepley wrote: >> >> On Sun, Apr 22, 2012 at 8:41 AM, Alexander Grayver < >> agrayver(a)gfz-potsdam.de> wrote: >> >>> Sorry, I don't quite get. Is this something I can avoid by doing >>> preallocation properly or petsc issue that will be fixed? >>> >> >> This looks like a PETSc bug to me, but it would be nice to get input >> that triggers it. >> >> Thanks, >> >> Matt >> >> >>> On 20.04.2012 14:23, Jed Brown wrote: >>> >>> On Fri, Apr 20, 2012 at 05:18, Matthew Knepley <knepley(a)gmail.com>wrote: >>> >>>> Did someone intend to fix this, and then >>>> stop? MatAXPY_BasicWithPreallocation() is the same as MatAXPY_Basic(). >>>> >>> >>> Look how it's called. I don't know what's going on here. >>> >>> ierr = >>> MatAXPYGetPreallocation_SeqAIJ(yy->A,xx->A,nnz_d);CHKERRQ(ierr); >>> ierr = >>> MatAXPYGetPreallocation_SeqAIJ(yy->B,xx->B,nnz_o);CHKERRQ(ierr); >>> ierr = MatMPIAIJSetPreallocation(B,0,nnz_d,0,nnz_o);CHKERRQ(ierr); >>> ierr = MatAXPY_BasicWithPreallocation(B,Y,a,X,str);CHKERRQ(ierr); >>> >>> >>> >>> -- >>> Regards, >>> Alexander >>> >>> >> >> >> -- >> 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 >> >> >> >> -- >> Regards, >> Alexander >> >> > > > -- > Regards, > Alexander > >

1 0

Re: [petsc-dev] MatAXPY with DIFFERENT_NONZERO_PATTERN
by Alexander Grayver 23 Apr '12

23 Apr '12

Jed, Thanks. However: [ 19%] Building C object CMakeFiles/petsc.dir/src/sys/ftn-custom/zstartf.c.o [ 19%] Building C object CMakeFiles/petsc.dir/src/sys/ftn-custom/zsys.c.o Building C object CMakeFiles/petsc.dir/src/sys/ftn-custom/zutils.c.o /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(117): error: expected a type specifier extern MPI_Op MPIU_SUM; ^ /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(117): error: "MPI_Op" has already been declared in the current scope extern MPI_Op MPIU_SUM; ^ /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(128): error: function "MPI_Op" is not a type name extern MPI_Op PetscMaxSum_Op; ^ /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(220): error: function "MPI_Op" is not a type name extern MPI_Op PetscADMax_Op; ^ /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(221): error: function "MPI_Op" is not a type name extern MPI_Op PetscADMin_Op; ^ /panfs/panfs.gfz-hpcc.cluster/home/mt/agrayver/lib/petsc-dev1/src/sys/ftn-custom/zstart.c(343): error: expression must be an lvalue or a function designator *ierr = MPI_Op_create(PetscSum_Local,1,&MPIU_SUM); On 23.04.2012 03:23, Jed Brown wrote: > Thanks for the test case. Fixed here: > > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/7ac7040f19d7 > > On Sun, Apr 22, 2012 at 08:11, Alexander Grayver > <agrayver(a)gfz-potsdam.de <mailto:[email protected]>> wrote: > > Matt, > > Here are matrices (double complex, 3 MB each): > http://dl.dropbox.com/u/60982984/X.dat > http://dl.dropbox.com/u/60982984/Y.dat > > Code: > > static char help[] = ""; > int main(int argc,char **args) > { > Mat A,B; > PetscErrorCode ierr; > PetscViewer viewer; > PetscScalar cone; > > PetscInitialize(&argc,&args,(char *)0,help); > > ierr = > PetscViewerBinaryOpen(PETSC_COMM_WORLD,"Y.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); > ierr = MatCreate(PETSC_COMM_WORLD,&A);CHKERRQ(ierr); > ierr = MatSetFromOptions(A);CHKERRQ(ierr); > ierr = MatLoad(A,viewer);CHKERRQ(ierr); > ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); > > ierr = > PetscViewerBinaryOpen(PETSC_COMM_WORLD,"X.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); > ierr = MatCreate(PETSC_COMM_WORLD,&B);CHKERRQ(ierr); > ierr = MatSetFromOptions(B);CHKERRQ(ierr); > ierr = MatLoad(B,viewer);CHKERRQ(ierr); > ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); > > cone = 1.0; > ierr = MatAYPX(A,cone,B,DIFFERENT_NONZERO_PATTERN); > ierr = PetscFinalize(); > return 0; > } > > It works fine if you run it with: > mpirun -n 10 solveTest -mat_type aij > > and crashes if n > 10 > > Thanks. > > > On 22.04.2012 14:51, Matthew Knepley wrote: >> On Sun, Apr 22, 2012 at 8:41 AM, Alexander Grayver >> <agrayver(a)gfz-potsdam.de <mailto:[email protected]>> wrote: >> >> Sorry, I don't quite get. Is this something I can avoid by >> doing preallocation properly or petsc issue that will be fixed? >> >> >> This looks like a PETSc bug to me, but it would be nice to get >> input that triggers it. >> >> Thanks, >> >> Matt >> >> On 20.04.2012 14:23, Jed Brown wrote: >>> On Fri, Apr 20, 2012 at 05:18, Matthew Knepley >>> <knepley(a)gmail.com <mailto:[email protected]>> wrote: >>> >>> Did someone intend to fix this, and then >>> stop? MatAXPY_BasicWithPreallocation() is the same >>> as MatAXPY_Basic(). >>> >>> >>> Look how it's called. I don't know what's going on here. >>> >>> ierr = >>> MatAXPYGetPreallocation_SeqAIJ(yy->A,xx->A,nnz_d);CHKERRQ(ierr); >>> ierr = >>> MatAXPYGetPreallocation_SeqAIJ(yy->B,xx->B,nnz_o);CHKERRQ(ierr); >>> ierr = >>> MatMPIAIJSetPreallocation(B,0,nnz_d,0,nnz_o);CHKERRQ(ierr); >>> ierr = >>> MatAXPY_BasicWithPreallocation(B,Y,a,X,str);CHKERRQ(ierr); >>> >> >> >> -- >> Regards, >> Alexander >> >> >> >> >> -- >> 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 > > > -- > Regards, > Alexander > > -- Regards, Alexander

1 0

Re: [petsc-dev] MatAXPY with DIFFERENT_NONZERO_PATTERN
by Jed Brown 22 Apr '12

22 Apr '12

Thanks for the test case. Fixed here: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/7ac7040f19d7 On Sun, Apr 22, 2012 at 08:11, Alexander Grayver <agrayver(a)gfz-potsdam.de>wrote: > ** > Matt, > > Here are matrices (double complex, 3 MB each): > http://dl.dropbox.com/u/60982984/X.dat > http://dl.dropbox.com/u/60982984/Y.dat > > Code: > > static char help[] = ""; > int main(int argc,char **args) > { > Mat A,B; > PetscErrorCode ierr; > PetscViewer viewer; > PetscScalar cone; > > PetscInitialize(&argc,&args,(char *)0,help); > > ierr = > PetscViewerBinaryOpen(PETSC_COMM_WORLD,"Y.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); > ierr = MatCreate(PETSC_COMM_WORLD,&A);CHKERRQ(ierr); > ierr = MatSetFromOptions(A);CHKERRQ(ierr); > ierr = MatLoad(A,viewer);CHKERRQ(ierr); > ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); > > ierr = > PetscViewerBinaryOpen(PETSC_COMM_WORLD,"X.dat",FILE_MODE_READ,&viewer);CHKERRQ(ierr); > ierr = MatCreate(PETSC_COMM_WORLD,&B);CHKERRQ(ierr); > ierr = MatSetFromOptions(B);CHKERRQ(ierr); > ierr = MatLoad(B,viewer);CHKERRQ(ierr); > ierr = PetscViewerDestroy(&viewer);CHKERRQ(ierr); > > cone = 1.0; > ierr = MatAYPX(A,cone,B,DIFFERENT_NONZERO_PATTERN); > ierr = PetscFinalize(); > return 0; > } > > It works fine if you run it with: > mpirun -n 10 solveTest -mat_type aij > > and crashes if n > 10 > > Thanks. > > > On 22.04.2012 14:51, Matthew Knepley wrote: > > On Sun, Apr 22, 2012 at 8:41 AM, Alexander Grayver < > agrayver(a)gfz-potsdam.de> wrote: > >> Sorry, I don't quite get. Is this something I can avoid by doing >> preallocation properly or petsc issue that will be fixed? >> > > This looks like a PETSc bug to me, but it would be nice to get input > that triggers it. > > Thanks, > > Matt > > >> On 20.04.2012 14:23, Jed Brown wrote: >> >> On Fri, Apr 20, 2012 at 05:18, Matthew Knepley <knepley(a)gmail.com> wrote: >> >>> Did someone intend to fix this, and then >>> stop? MatAXPY_BasicWithPreallocation() is the same as MatAXPY_Basic(). >>> >> >> Look how it's called. I don't know what's going on here. >> >> ierr = >> MatAXPYGetPreallocation_SeqAIJ(yy->A,xx->A,nnz_d);CHKERRQ(ierr); >> ierr = >> MatAXPYGetPreallocation_SeqAIJ(yy->B,xx->B,nnz_o);CHKERRQ(ierr); >> ierr = MatMPIAIJSetPreallocation(B,0,nnz_d,0,nnz_o);CHKERRQ(ierr); >> ierr = MatAXPY_BasicWithPreallocation(B,Y,a,X,str);CHKERRQ(ierr); >> >> >> >> -- >> Regards, >> Alexander >> >> > > > -- > 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 > > > > -- > Regards, > Alexander > >

1 0

Re: [petsc-dev] Recommended Petsc Build Procedure
by Satish Balay 22 Apr '12

22 Apr '12

On Sun, 22 Apr 2012, Dave Nystrom wrote: > At the end of configure.log, there are two possible ways to build petsc-dev > that are specified. Which is the recommended way to build - using make or > using python? I have been using make. > > Also, one is labeled as legacy and one is labeled as experimental. That > gives the impression of having a choice between an old, archaic method or a > new, experimental approach. Should one just be labeled as production? Currently the first choice printed by configure is the recommended choice. [this is either cmake or legacy depending on what configure figured out]. Python is labled experimental as most of us [except Matt] haven't actively used it yet. As more folks use it actively - we can remove the 'experimental' tag off it. Satish

1 0

Fwd: [petsc-maint #113654] Configure Problem
by Barry Smith 22 Apr '12

22 Apr '12

I guess this means this is on the petsc-dev to do list Begin forwarded message: > From: Sean Farley <sean(a)mcs.anl.gov> > Date: April 22, 2012 11:04:03 AM CDT > To: petsc-maint(a)mcs.anl.gov, Barry Smith <bsmith(a)mcs.anl.gov> > Cc: Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> > Subject: Re: [petsc-maint #113654] Configure Problem > >> The good folks at kitware apparently STILL don't know how to compile cuda code. Hence if you ./configure with cuda stuff it will not allow the use of cmake since cmake cannot handle building the cuda part of PETSc. Thus the cmake build option was automatically turned off. > > That's not true, Barry. cmake >1.8 can compile cuda ... we just > haven't written it yet.

1 0

Re: [petsc-dev] Recommended Petsc Build Procedure
by Dave Nystrom 22 Apr '12

22 Apr '12

Thanks. So far, I have been using make. Barry Smith writes: > The recommend usage is make > > If cmake was found with ./configure it will use it automatically if you do > make, if it was not found it will use the legacy make > > Barry > > On Apr 22, 2012, at 10:19 AM, Dave Nystrom wrote: > > > OK. I'll mail the configure.log to petsc-maint. But this did not start out > > as a configure problem - I was just asking for a recommendation on usage. > > And the response you cite below was to Aron before I received your response. > > > > Matthew Knepley writes: > >> On Sun, Apr 22, 2012 at 10:57 AM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: > >> > >>> I have cmake on my system but configure.log does not document that > >>> approach. > >>> > >> > >> We did not find it. This is a configure question, and should be mailed to > >> petsc-maint, not the dev list. > >> > >> > >>> What is your build command to build petsc with cmake? > >>> > >> > >> make > >> > >> Matt > >> > >> > >>> Thanks, > >>> > >>> Dave > >>> > >>> Aron Ahmadia writes: > >>>> I use the CMake build because it's the fastest, though it requires you > >>> to > >>>> have CMake installed on your system. > >>>> > >>>> A > >>>> > >>>> On Sun, Apr 22, 2012 at 5:42 PM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: > >>>> > >>>>> At the end of configure.log, there are two possible ways to build > >>> petsc-dev > >>>>> that are specified. Which is the recommended way to build - using > >>> make or > >>>>> using python? I have been using make. > >>>>> > >>>>> Also, one is labeled as legacy and one is labeled as experimental. > >>> That > >>>>> gives the impression of having a choice between an old, archaic > >>> method or a > >>>>> new, experimental approach. Should one just be labeled as production? > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Dave > >>>>> > >>> > >> > >> > >> > >> -- > >> 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] Recommended Petsc Build Procedure
by Barry Smith 22 Apr '12

22 Apr '12

The recommend usage is make If cmake was found with ./configure it will use it automatically if you do make, if it was not found it will use the legacy make Barry On Apr 22, 2012, at 10:19 AM, Dave Nystrom wrote: > OK. I'll mail the configure.log to petsc-maint. But this did not start out > as a configure problem - I was just asking for a recommendation on usage. > And the response you cite below was to Aron before I received your response. > > Matthew Knepley writes: >> On Sun, Apr 22, 2012 at 10:57 AM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: >> >>> I have cmake on my system but configure.log does not document that >>> approach. >>> >> >> We did not find it. This is a configure question, and should be mailed to >> petsc-maint, not the dev list. >> >> >>> What is your build command to build petsc with cmake? >>> >> >> make >> >> Matt >> >> >>> Thanks, >>> >>> Dave >>> >>> Aron Ahmadia writes: >>>> I use the CMake build because it's the fastest, though it requires you >>> to >>>> have CMake installed on your system. >>>> >>>> A >>>> >>>> On Sun, Apr 22, 2012 at 5:42 PM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: >>>> >>>>> At the end of configure.log, there are two possible ways to build >>> petsc-dev >>>>> that are specified. Which is the recommended way to build - using >>> make or >>>>> using python? I have been using make. >>>>> >>>>> Also, one is labeled as legacy and one is labeled as experimental. >>> That >>>>> gives the impression of having a choice between an old, archaic >>> method or a >>>>> new, experimental approach. Should one just be labeled as production? >>>>> >>>>> Thanks, >>>>> >>>>> Dave >>>>> >>> >> >> >> >> -- >> 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] Recommended Petsc Build Procedure
by Dave Nystrom 22 Apr '12

22 Apr '12

OK. I'll mail the configure.log to petsc-maint. But this did not start out as a configure problem - I was just asking for a recommendation on usage. And the response you cite below was to Aron before I received your response. Matthew Knepley writes: > On Sun, Apr 22, 2012 at 10:57 AM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: > > > I have cmake on my system but configure.log does not document that > > approach. > > > > We did not find it. This is a configure question, and should be mailed to > petsc-maint, not the dev list. > > > > What is your build command to build petsc with cmake? > > > > make > > Matt > > > > Thanks, > > > > Dave > > > > Aron Ahmadia writes: > > > I use the CMake build because it's the fastest, though it requires you > > to > > > have CMake installed on your system. > > > > > > A > > > > > > On Sun, Apr 22, 2012 at 5:42 PM, Dave Nystrom <Dave.Nystrom(a)tachyonlogic.com> wrote: > > > > > > > At the end of configure.log, there are two possible ways to build > > petsc-dev > > > > that are specified. Which is the recommended way to build - using > > make or > > > > using python? I have been using make. > > > > > > > > Also, one is labeled as legacy and one is labeled as experimental. > > That > > > > gives the impression of having a choice between an old, archaic > > method or a > > > > new, experimental approach. Should one just be labeled as production? > > > > > > > > Thanks, > > > > > > > > Dave > > > > > > > > > > -- > 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