[petsc-dev] JSON library

2011-03-14 Thread Jed Brown
tory and timing results for the purpose of plotting, e.g.: https://github.com/jedbrown/petscplot/wiki/PETSc-Plot). -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/0cc4a326/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Jed Brown
files, albeit easier to manipulate from other languages. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/cfd88a2a/attachment.html>

[petsc-dev] Help with configure and cmake

2011-03-14 Thread Jose E. Roman
El 11/03/2011, a las 16:41, Jed Brown escribi?: > On Fri, Mar 11, 2011 at 13:02, Jose E. Roman wrote: > I have been adding support for cmake in SLEPc. My simple approach is: > 1) generate a SLEPcConfig.cmake file > 2) generate CMakeLists.txt with a cmakegen module adapted from petsc-dev > 3) run

[petsc-dev] Lagging the numerical factorization for one of the fields of fieldsplit preconditioner

2011-03-14 Thread Barry Smith
On Mar 14, 2011, at 6:38 PM, Shri wrote: > > > - Original Message - >> Shri, >> >> In theory the flag for KSPSetOperators() (for example >> SAME_PRECONDITIONER) is propagated down through the PCFIELDSPLIT into >> the PC that is used on the A block. So in at least simple >> circumstance

[petsc-dev] Lagging the numerical factorization for one of the fields of fieldsplit preconditioner

2011-03-14 Thread Shri
- Original Message - > Shri, > > In theory the flag for KSPSetOperators() (for example > SAME_PRECONDITIONER) is propagated down through the PCFIELDSPLIT into > the PC that is used on the A block. So in at least simple > circumstances if you use -snes_lag_preconditioner it should "just >

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
--- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/affef305/attachment.html>

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
your plugin user to be able to build the plugin against a vendor-provided PETSc which of course wouldn't come with the src/ tree if they had modified anything. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attac

[petsc-dev] Lagging the numerical factorization for one of the fields of fieldsplit preconditioner

2011-03-14 Thread Barry Smith
Shri, In theory the flag for KSPSetOperators() (for example SAME_PRECONDITIONER) is propagated down through the PCFIELDSPLIT into the PC that is used on the A block. So in at least simple circumstances if you use -snes_lag_preconditioner it should "just work". I traced through the PCFIE

[petsc-dev] Lagging the numerical factorization for one of the fields of fieldsplit preconditioner

2011-03-14 Thread Shri
| A B | |dx| |fx| Jacobian == | C D | |dy| |fy| While solving this linear system with a fieldsplit precondioner,is there a way to lag the numerical factorization of the A matrix. The A matrix in my application is constant and is about 3-4 times

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
ypes are "open" in the sense that implementation inheritance is intended versus "closed" in the sense that it is not. This also affects using "static" for implementation functions. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/4d8d26be/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Sean Farley
ast a starting point. It would handle the features mentioned above. Sean -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/17804e74/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Blaise Bourdin
-- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/0748616a/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Barry Smith
yaml forbids tabs, that alone is a good enough reason to love it :-) Barry On Mar 14, 2011, at 4:04 PM, Jed Brown wrote: > I want to reiterate a statement I made a while back that any alternative > input format really needs to support references. This is a good reason to > prefer Yaml ov

[petsc-dev] DMDABoundaryType

2011-03-14 Thread Jed Brown
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/a1c000eb/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Barry Smith
Good think I brought this up. Let's get this synchronized. No reason to duplicate work. We can discuss the plan on petsc-dev Why not just have PetscOptionsInsert() and have it auto-detect the file format making life easier for user than remembering half-a-dozen function names? Barry

[petsc-dev] JSON library

2011-03-14 Thread Lisandro Dalcin
On 14 March 2011 15:31, Matthew Knepley wrote: > Does anyone have a favorite? Blaise is going to have a student add JSON > support > to PetscOptions. > ?? Matt > +1 -- Lisandro Dalcin --- CIMEC (INTEC/CONICET-UNL) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo 300

[petsc-dev] JSON library

2011-03-14 Thread Blaise Bourdin
Hi, No, I had no idea that Sean was bringing an LSU student to work on this. I have a sophomore CS student starting right now. The idea is to implement PetscOptionsInsertJSONFile(MPI_Comm comm,const char file[],const char section[],PetscBool require) where every child of section would be parse

[petsc-dev] DM interface versus implementation headers

2011-03-14 Thread Jed Brown
ted for recent changes. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/f975018e/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Barry Smith
Is this in any related to Sean's plan to have this done this summer with a student from LSU? I could assume, likely correctly, this is one and the same project, I just want to make sure. Barry On Mar 14, 2011, at 1:31 PM, Matthew Knepley wrote: > Does anyone have a favorite? Blaise i

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
nshared (and not intended to be derived from)? -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/73b84b88/attachment.html>

[petsc-dev] someone missed DMDA location?

2011-03-14 Thread Jed Brown
both fixed -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/1f9b76bb/attachment.html>

[petsc-dev] Using PCFieldSplitSetIS

2011-03-14 Thread Jed Brown
as with FETI-DP/BDDC). -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/1a9b0db6/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Matthew Knepley
--- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/a3979d82/attachment.html>

[petsc-dev] JSON library

2011-03-14 Thread Matthew Knepley
-- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/2797e77a/attachment.html>

[petsc-dev] Using PCFieldSplitSetIS

2011-03-14 Thread Thomas Witkowski
Jed, I'm a little bit confused about your and Matt's answers. I played a little bit with PFCFieldSplit, and I think that I got some basic understanding of this concept. My code now creates two splits. One for the unknowns of all subdomain interior nodes, and one for all unknowns on the subdomai

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Barry Smith
On Mar 14, 2011, at 11:03 AM, Matthew Knepley wrote: > On Mon, Mar 14, 2011 at 11:00 AM, Barry Smith wrote: > > On Mar 14, 2011, at 10:33 AM, Jed Brown wrote: > > > I had resisted doing this but maybe it is the way to go. > > I had resisted suggesting this, but if we are going towards all

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Dmitry Karpeev
On Mon, Mar 14, 2011 at 11:00 AM, Barry Smith wrote: > > On Mar 14, 2011, at 10:33 AM, Jed Brown wrote: > >> On Mon, Mar 14, 2011 at 16:22, Barry Smith wrote: >> What bothers me about this one is that private has no hierarchy and will >> eventually become cluttered with all kinds of stuff from m

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Matthew Knepley
to the headers by full path Then 3) might break if we move things, but they are writing to private interfaces anyway. Matt > > 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 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/02b1f3f9/attachment.html>

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Barry Smith
On Mar 14, 2011, at 10:33 AM, Jed Brown wrote: > On Mon, Mar 14, 2011 at 16:22, Barry Smith wrote: > What bothers me about this one is that private has no hierarchy and will > eventually become cluttered with all kinds of stuff from many different > places in PETSc. > > How many shared header

[petsc-dev] DM interface versus implementation headers

2011-03-14 Thread Lisandro Dalcin
On 13 March 2011 17:40, Barry Smith wrote: > > ?Concur. And fix that petscmg.h name at the same time :-) > > ? Barry > > On Mar 13, 2011, at 1:54 PM, Jed Brown wrote: > >> The solvers all have DM members now, but they only depend on the generic DM >> interface. Currently all of DMDA and now DMMes

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Dmitry Karpeev
On Mon, Mar 14, 2011 at 10:33 AM, Jed Brown wrote: > On Mon, Mar 14, 2011 at 16:22, Barry Smith wrote: >> >> What bothers me about this one is that private has no hierarchy and will >> eventually become cluttered with all kinds of stuff from many different >> places in PETSc. > > How many shared

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Dmitry Karpeev
On Mon, Mar 14, 2011 at 10:22 AM, Barry Smith wrote: > > On Mar 14, 2011, at 8:44 AM, Jed Brown wrote: > >> On Mon, Mar 14, 2011 at 14:08, Barry Smith wrote: >> For files like aij.h if you use the localinclude.h paradigm then in aij.c >> you would have ?#include "aij.h" ?but in mpiaij.h you woul

[petsc-dev] DMDABoundaryType

2011-03-14 Thread Barry Smith
esc x tags-search enter the string to search for and then use esc , to find the next use. BUT etags is only as good as its database and sometimes the generation of the etags file doesn't traverse everywhere it should. Barry On Mar 14, 2011, at 9:43 AM, Ethan Coon wrote: > Ok, apparen

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Barry Smith
On Mar 14, 2011, at 8:44 AM, Jed Brown wrote: > On Mon, Mar 14, 2011 at 14:08, Barry Smith wrote: > For files like aij.h if you use the localinclude.h paradigm then in aij.c you > would have #include "aij.h" but in mpiaij.h you would have #include > <./src/mat/impls/aij/seq/aij.h> I don't li

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Dmitry Karpeev
On Mon, Mar 14, 2011 at 8:44 AM, Jed Brown wrote: > On Mon, Mar 14, 2011 at 14:08, Barry Smith wrote: >> >> For files like aij.h if you use the localinclude.h paradigm then in aij.c >> you would have ?#include "aij.h" ?but in mpiaij.h you would have #include >> <./src/mat/impls/aij/seq/aij.h> I d

[petsc-dev] DMDABoundaryType

2011-03-14 Thread Ethan Coon
Ok, apparently etags does more than I thought it did... off to RTFM. Thanks, Ethan On Mon, 2011-03-14 at 15:39 +0100, Jed Brown wrote: > On Mon, Mar 14, 2011 at 15:34, Ethan Coon wrote: > Related to this, do you guys have a standard way of finding > all such > instances?

[petsc-dev] DMDABoundaryType

2011-03-14 Thread Ethan Coon
Related to this, do you guys have a standard way of finding all such instances? I was using grep/find (and then checking the compilation output), but I'm sure my find was missing a few files. Ethan On Fri, 2011-03-11 at 19:14 -0600, Satish Balay wrote: > I just pushed this patch along with the

[petsc-dev] someone missed DMDA location?

2011-03-14 Thread Barry Smith
testexamples_C_X11 in: /Users/barrysmith/Src/petsc-dev/src/dm/examples/tests 3c3 < Vector Object: --- > Vector Object: 2 MPI processes Possible problem with ex2_1, diffs above WARNING! There are options you set that were not used! WARNING! could be spelling mistake, etc! Option left: name:-test_or

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Barry Smith
On Mar 13, 2011, at 11:34 PM, Jed Brown wrote: > On Mon, Mar 14, 2011 at 05:01, Dmitry Karpeev wrote: > So it is okay to include headers from the source tree other than from > under $PETSC_DIR/include? > I thought the subject of this thread expressly banned that. > > That is a style decision th

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
understanding of whether the compiler's $PWD affected header resolution (it doesn't) and recall some possible IDE issues but don't know if they were resolved. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/ece7f20b/attachment.html>

[petsc-dev] reminder never use #include "mylocalinclude.h" in PETSc source

2011-03-14 Thread Jed Brown
s has caused any problems. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/1dd72abd/attachment.html>