[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

On my MacAir without elemental installed, I get clean 'make runex104' and anticipated message from 'make runex104_elemental' 0a1,28 > [0]PETSC ERROR: - Error Message > > [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing extern

[petsc-dev] PETSc goes Doxygen!?

geable as long as it's just typedefs, enums, or members of > structs. And function-like macros (some of which could be made inline functions). -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/112ffca6/attachment-0001.html>

[petsc-dev] PETSc goes Doxygen!?

Hi, > Oh, we use different definitions of 'documented'. I'm referring to > documentation right at the place of declaration/definition. > PetscScalar.html is generated from some comment block at some other > spot in the sources, hence Doxygen fails to associated it with the > co

[petsc-dev] PETSc goes Doxygen!?

achment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/044923d3/attachment.html>

[petsc-dev] PETSc goes Doxygen!?

Hi, > At least for PetscScalar and PetscReal this is unfortunately not the > case: > > include/petscmath.h" > > #if defined(PETSC_USE_COMPLEX) > typedef PetscComplex PetscScalar; > > #else /* PETSC_USE_COMPLEX */ > typedef PetscReal PetscScalar; > #defin

[petsc-dev] Add, Find, Register, Compose Query

gt; > > > Why have all these words? > > > > I propose Register, Compose and Add -> Register > > > > Find, Query -> Find > > > > Problems? > > > >Barry > > > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/68f5cb3b/attachment.html>

[petsc-dev] Add, Find, Register, Compose Query

What about at least moving the Add to Register? And why have both query and find? Barry On Jan 15, 2013, at 5:17 PM, Jed Brown wrote: > So we would have PetscObjectRegister(C,"Mat_Redundant",container)? Somehow I > find Compose more intuitive for this meaning and don't see a tangible

[petsc-dev] Compliant C89

-- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/268bffd4/attachment.html>

[petsc-dev] Add, Find, Register, Compose Query

part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/3c8e81dc/attachment.html>

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

eMatMult() */ > > ierr = > PetscObjectTypeCompare((PetscObject)A,MATELEMENTAL,&iselemental);CHKERRQ(ierr); > > if (!iselemental){ > > ierr = > MatTransposeMatMult(A,A,MAT_INITIAL_MATRIX,fill,&D);CHKERRQ(ierr); /* D = > A^T*A */ > > ierr = MatEqual(C,D,&equal);CHKERRQ(ierr); > > if (!equal) SETERRQ(PETSC_COMM_SELF,PETSC_ERR_ARG_WRONGSTATE,"C != > D"); > > ierr = MatDestroy(&D);CHKERRQ(ierr); > > > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/66168136/attachment-0001.html>

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

On Jan 15, 2013, at 5:03 PM, Jed Brown wrote: > On Tue, Jan 15, 2013 at 4:43 PM, Barry Smith wrote: > > It works for me. > >Cause you are running an install with Elemental, without elemental install > it goes bad. > > Isn't that why the elemental tests are in TESTEXAMPLES_ELEMENTAL? The

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

if (!equal) SETERRQ(PETSC_COMM_SELF,PETSC_ERR_ARG_WRONGSTATE,"C != D"); > ierr = MatDestroy(&D);CHKERRQ(ierr); > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/a225bbc3/attachment.html>

[petsc-dev] PETSc goes Doxygen!?

t; typedef PetscReal PetscScalar; > #define MPIU_SCALAR MPIU_REAL > They really are documented: http://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/Sys/PetscScalar.html -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermai

[petsc-dev] PETSc goes Doxygen!?

Hey, > I disabled the automatic documentation of undocumented entities, > that's why links got lost. > > > But all of those _are_ documented. At least for PetscScalar and PetscReal this is unfortunately not the case: include/petscmath.h" #if defined(PETSC_USE_COMPLEX) typedef PetscCompl

[petsc-dev] PETSc goes Doxygen!?

egards, > Karli > > -- 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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/287809e5/attachment.html>

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

On Jan 15, 2013, at 4:35 PM, Jed Brown wrote: > It works for me. Cause you are running an install with Elemental, without elemental install it goes bad. /* Test MatTransposeMatMult() */ ierr = PetscObjectTypeCompare((PetscObject)A,MATELEMENTAL,&iselemental);CHKERRQ(ierr); if (!isele

[petsc-dev] PETSc goes Doxygen!?

Hi Matt, > Right now, the search stinks. If I type in > >GetCone > > I get nothing found, whereas > >DMPlexGetCone > > has three things found, but does not find DMPlexSetCone. This is crappy, > and will > not replace seeing everything on one page, which I miss. Well, you can't expect the

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

- > > [0]PETSC ERROR: main() line 74 in src/mat/examples/tests/ex104.c > > application called MPI_Abort(MPI_COMM_WORLD, 73) - process 0 > > [cli_0]: aborting job: > > application called MPI_Abort(MPI_COMM_WORLD, 73) - pro

[petsc-dev] PETSc goes Doxygen!?

if we're going to provide a "developer" version, it should probably include everything (searching two places sucks). -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/18038365/attachment.html>

[petsc-dev] example broken for a while src/mat/examples/tests/ex104.c

This example has been broken for a while, did it ever work? = 0a1,25 > [0]PETSC ERROR: - Error Message > > [0]PETSC ERROR: Object is in wrong state! > [0]PETSC ERROR: C != D! > [0]PETSC ERROR: > -

[petsc-dev] PETSc goes Doxygen!?

Hi Jed, > The listing of > > http://krupp.iue.tuwien.ac.at/__petsc-doxygen/ksp_2ksp___2examples_2tutorials_2ex4_8c-__example.html > > > is now identical with the one Barry mentioned -

[petsc-dev] PETSc goes Doxygen!?

ame in the URL, similar to what sowing produces. >>>>> - Group examples: I haven't found a way to group examples, there's >>>>> only the list of all examples >>>>> - External Dependency rather than 'our own dependency'. >>>>> >>>>> >>>>> The most time consuming part was/is the migration of the manuals. This >>>>> is partly a technical thing (Doxygen does not parse all LaTeX stuff, so >>>>> this needs to be filtered), but also a semantic thing. For example, in a >>>>> PDF you naturally refer to another Chapter by something like 'as we know >>>>> from Chapter 1 ...', while in an HTML document it is preferable to have >>>>> something like 'as we know from the introductory discussion ...'. >>>>> >>>>> Doxygen allows to have commands for switching between different output >>>>> targets, so in principle it would be possible to transfer the current >>>>> manuals to a markup-time format, which can then be used with doxygen as >>>>> well as for dedicated standalone PDFs as we have it now. For that to >>>>> happen >>>>> it is essential to come to a conclusion on whether we want to use Doxygen >>>>> in the future, or whether we want to stick with the current tools. Barry? >>>>> ;-) >>>>> >>>>> Best regards, >>>>> Karli >>>>> >>>> >>>> >>> >> > -- 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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/7437ea50/attachment-0001.html>

[petsc-dev] Coding style and its violations...

Hi, >>> Some projects (e.g., moose) reject a noncompliant push. The >>> committer can then rewrite the patch locally before it is >>> published and resubmit. >>> >>> >>> IIRC, this is done server-side, but with a DVCS, that's too late (or >>> causes the "pusher" a

[petsc-dev] Coding style and its violations...

uld then have to explicitly disable it. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/213b6c1b/attachment.html>

[petsc-dev] Coding style and its violations...

On Jan 15, 2013, at 3:43 PM, Karl Rupp wrote: > Hi, > >>Some projects (e.g., moose) reject a noncompliant push. The >>committer can then rewrite the patch locally before it is >>published and resubmit. >> >> >>IIRC, this is done server-side, but with a DVCS, that'

[petsc-dev] PETSc goes Doxygen!?

://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/890e297d/attachment.html>

[petsc-dev] Coding style and its violations...

Hi, > Some projects (e.g., moose) reject a noncompliant push. The > committer can then rewrite the patch locally before it is > published and resubmit. > > > IIRC, this is done server-side, but with a DVCS, that's too late (or > causes the "pusher" a lot more troub

[petsc-dev] PETSc goes Doxygen!?

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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/7eeb92b1/attachment-0001.html>

[petsc-dev] Coding style and its violations...

tand the first sentence. I'm pretty sure it was just missing a negation. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/6df17a6b/attachment.html>

[petsc-dev] Coding style and its violations...

On 01/15/2013 02:51 PM, Jed Brown wrote: > On Tue, Jan 15, 2013 at 2:47 PM, Barry Smith > wrote: > > Yes. Jed is too in love with Git to ever do this so you have to. > > > What does this have to do with choice of VCS? They all support commit hooks. Oh, Jed, yo

[petsc-dev] Coding style and its violations...

Hi, >> (...) >> So we have a style guide that is partially respected, partially ignored. >> Some things are pretty hard to check automatically, while others are rather >> simple. So let's pick >> "No tabs are allowed in any of the source code." >> as an example and run >> >> $petsc-dev/src> fi

[petsc-dev] PETSc goes Doxygen!?

per level routines. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/9657b697/attachment.html>

[petsc-dev] PETSc goes Doxygen!?

ean I don't want documentation on it. Matt -- 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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/fdeb377f/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/1621ffc2/attachment.html>

[petsc-dev] Coding style and its violations...

L attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/20f97ecb/attachment-0001.html>

[petsc-dev] multiple dispatch code currently in PETSc

for Fortran pointers, but that class object could be used for multiple dispatch as well. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/e551523f/attachment.html>

[petsc-dev] Coding style and its violations...

on each committer to configure it locally. Dmitry. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/61d0331d/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

no longer be used, and which is typically set to 0 or -1 in calls to PetscHeaderCreate. So, barring some subtle backward-compatibility issue this can be reused to hold the typeid, which is computed or looked up on each PetscObjectChangeTypeName()? Dmitry. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/d372f427/attachment.html>

[petsc-dev] Coding style and its violations...

"pusher" a lot more trouble). Hg and Git both support client-side commit hooks. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/9ed1b90d/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/3dc21b2a/attachment.html>

[petsc-dev] Coding style and its violations...

xt part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/3cfccfcc/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

r = PetscStrallocpy(argType, argTypes+i);CHKERRQ(ierr); >> } >> va_end(ap); >> ierr = PetscOpFListFind(comm, MatOpList, function, op, numArgs, >> argTypes);CHKERRQ(ierr); >> for (i = 0; i < numArgs; ++i) { >> ierr = PetscFree(argTypes[i]);CHKERRQ(ierr); >> } >> ierr = PetscFree(argTypes);CHKERRQ(ierr); >> PetscFunctionReturn(0); >> } >> >> > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/bd8cce05/attachment-0001.html>

[petsc-dev] Coding style and its violations...

-- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/850c7ff2/attachment.html>

[petsc-dev] Coding style and its violations...

On Jan 15, 2013, at 2:42 PM, Karl Rupp wrote: > Dear all, > > quoting a recent commit: > > > BarryFSmith committed 16 hours ago (raw commit) > > > > silly code formatting problems; some people still need to read the > > style guide > > So we have a style guide that is partially respected, par

[petsc-dev] multiple dispatch code currently in PETSc

r (i = 0; i < numArgs; ++i) { > > argType = va_arg(ap,const char*); > > ierr = PetscStrallocpy(argType, argTypes+i);CHKERRQ(ierr); > > } > > va_end(ap); > > ierr = PetscOpFListFind(comm, MatOpList, function, op, numArgs, > argTypes);CHKERRQ(ierr); > > for (i = 0; i < numArgs; ++i) { > > ierr = PetscFree(argTypes[i]);CHKERRQ(ierr); > > } > > ierr = PetscFree(argTypes);CHKERRQ(ierr); > > PetscFunctionReturn(0); > > } > > > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/1c7b96ed/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

va_end(ap); > > ierr = PetscOpFListFind(comm, MatOpList, function, op, numArgs, > argTypes);CHKERRQ(ierr); > > for (i = 0; i < numArgs; ++i) { > > ierr = PetscFree(argTypes[i]);CHKERRQ(ierr); > > } > > ierr = PetscFree(argTypes);CHKERRQ(ierr); > > PetscFunctionReturn(0); > > } > > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/a6fb94a8/attachment.html>

[petsc-dev] Coding style and its violations...

Dear all, quoting a recent commit: > BarryFSmith committed 16 hours ago (raw commit) > > silly code formatting problems; some people still need to read the > style guide So we have a style guide that is partially respected, partially ignored. Some things are pretty hard to check automatical

[petsc-dev] PETSc goes Doxygen!?

("plex"). -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/c58fd1cb/attachment-0001.html>

[petsc-dev] multiple dispatch code currently in PETSc

So who wrote the PetscOpFList() code and who will refactor it? Is this a high priority or just something to be listed on that website and then ignored for years? Barry On Jan 15, 2013, at 2:14 PM, Jed Brown wrote: > On Tue, Jan 15, 2013 at 1:50 PM, Barry Smith wrote: > > Do we

[petsc-dev] PETSc goes Doxygen!?

Hi again, some more improvements to the doxygen generation process have been applied: - Examples are finally filtered now as I specified everything correctly (not a Doxygen shortcoming, bug report closed). > You can also take out the PetscErrorCode ierr; since ierr is never used. >

[petsc-dev] multiple dispatch code currently in PETSc

numArgs; ++i) { > ierr = PetscFree(argTypes[i]);CHKERRQ(ierr); > } > ierr = PetscFree(argTypes);CHKERRQ(ierr); > PetscFunctionReturn(0); > } > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/050944dc/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

enters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/f1ee543e/attachment.html>

[petsc-dev] multiple dispatch code currently in PETSc

Do we really want mallocs for EVERY single multiple-dispatch function call in PETSc? I suggest not having MatQueryOp() but calling directly PetscOpFListFind() (with the MatOpFList argument) and changing PetscOpFListAdd/Find() to use variable args directly. Finally do we really want string

[petsc-dev] Barry doesn't like typedefs for function pointers

On Tue, Jan 15, 2013 at 12:49 PM, Lisandro Dalcin wrote: > On Mon, Jan 14, 2013 at 1:00 AM, Barry Smith wrote: >> >> ... please don't introduce new ones in the future. >> > > Can you provide your rationale for this? > Forget about it, I've found the answer in another thread. -- Lisandro Dalc

[petsc-dev] Barry doesn't like typedefs for function pointers

On Mon, Jan 14, 2013 at 1:00 AM, Barry Smith wrote: > > ... please don't introduce new ones in the future. > Can you provide your rationale for this? -- Lisandro Dalcin --- CIMEC (INTEC/CONICET-UNL) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo 3000 Santa Fe, Arg

[petsc-dev] Barry doesn't like typedefs for function pointers

-- 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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130115/f15eb719/attachment.html>