[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Matthew Knepley
hat lasts more than an hour. 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/20120831/933dc9b1/attachment.html>

[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Jed Brown
next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/0ef83751/attachment.html>

[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Barry Smith
On Aug 31, 2012, at 10:02 PM, Matthew Knepley wrote: > On Fri, Aug 31, 2012 at 10:00 PM, Barry Smith wrote: > > I put a couple patches in petsc-3.3 can a skilled person (Satish?) > please push them up to petsc-dev ? > > We are in deep shit if this takes skill. What is wrong with > >

[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Satish Balay
pushed now satish On Fri, 31 Aug 2012, Barry Smith wrote: > > I put a couple patches in petsc-3.3 can a skilled person (Satish?) > please push them up to petsc-dev ? > > Thanks > > Barry >

[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Matthew Knepley
attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/3b4b36c9/attachment.html>

[petsc-dev] managing moving patches in pets 3.3. to petsc-dev?

2012-08-31 Thread Barry Smith
I put a couple patches in petsc-3.3 can a skilled person (Satish?) please push them up to petsc-dev ? Thanks Barry

[petsc-dev] clique

2012-08-31 Thread Jed Brown
his patented innovation, then sue them for billions. American Innovation at work. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/173a32c0/attachment-0001.html>

[petsc-dev] clique

2012-08-31 Thread Matthew Knepley
t;> > [I'm having to add the flag BUILD_PARMETIS=0.] But now I get: >>>>>> > >>>>>> > cd >>>>>> /home/balay/spetsc/externalpackages/clique/arch-clique/src/parmetis && >>>>>> /usr/lib64/ccache/gcc -Wall -Wwrite-strings -Wno-strict-aliasing >>>>>> -Wno-unknown-pragmas -g3 -fno-inline -O0 >>>>>> -I/home/balay/spetsc/externalpackages/clique/arch-clique/external/elemental/include >>>>>> -I/home/balay/soft/linux64/mpich2-1.1/include >>>>>> -I/home/balay/spetsc/arch-clique/include >>>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/include >>>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/libparmetis >>>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/GKlib >>>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/include >>>>>>-o CMakeFiles/parmetis-addons.dir/ParallelBisect.c.o -c >>>>>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >>>>>> > >>>>>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >>>>>> fatal error: parmetislib.h: No such file or directory >>>>>> > >>>>>> > Looks like this code needs parmetis private includes. So the current >>>>>> > stratergy [of splitting into -lparmetis-addons] isn't working. >>>>>> > >>>>>> > Perhaps we'll have to use a single patched metis/parmetis tarball >>>>>> for >>>>>> > both petsc and clique afterall.. >>>>>> > >>>>>> > Satish >>>>>> > >>>>>> >>>>>> >>>> >>> >> > -- 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/20120831/1f11c8f8/attachment.html>

[petsc-dev] clique

2012-08-31 Thread Jed Brown
t;>>>> > cd >>>>> /home/balay/spetsc/externalpackages/clique/arch-clique/src/parmetis && >>>>> /usr/lib64/ccache/gcc -Wall -Wwrite-strings -Wno-strict-aliasing >>>>> -Wno-unknown-pragmas -g3 -fno-inline -O0 >>>>> -I/home/balay/spetsc/externalpackages/clique/arch-clique/external/elemental/include >>>>> -I/home/balay/soft/linux64/mpich2-1.1/include >>>>> -I/home/balay/spetsc/arch-clique/include >>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/include >>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/libparmetis >>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/GKlib >>>>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/include >>>>>-o CMakeFiles/parmetis-addons.dir/ParallelBisect.c.o -c >>>>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >>>>> > >>>>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >>>>> fatal error: parmetislib.h: No such file or directory >>>>> > >>>>> > Looks like this code needs parmetis private includes. So the current >>>>> > stratergy [of splitting into -lparmetis-addons] isn't working. >>>>> > >>>>> > Perhaps we'll have to use a single patched metis/parmetis tarball for >>>>> > both petsc and clique afterall.. >>>>> > >>>>> > Satish >>>>> > >>>>> >>>>> >>> >> > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/4b72b777/attachment.html>

[petsc-dev] clique

2012-08-31 Thread Jack Poulson
> /usr/lib64/ccache/gcc -Wall -Wwrite-strings -Wno-strict-aliasing >>>> -Wno-unknown-pragmas -g3 -fno-inline -O0 >>>> -I/home/balay/spetsc/externalpackages/clique/arch-clique/external/elemental/include >>>> -I/home/balay/soft/linux64/mpich2-1.1/include >>

[petsc-dev] clique

2012-08-31 Thread Jed Brown
es/clique/external/parmetis/libparmetis >>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/GKlib >>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/include >>>-o CMakeFiles/parmetis-addons.dir/ParallelBisect.c.o -c >>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >>> > >>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >>> fatal error: parmetislib.h: No such file or directory >>> > >>> > Looks like this code needs parmetis private includes. So the current >>> > stratergy [of splitting into -lparmetis-addons] isn't working. >>> > >>> > Perhaps we'll have to use a single patched metis/parmetis tarball for >>> > both petsc and clique afterall.. >>> > >>> > Satish >>> > >>> >>> > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/9f83f41b/attachment.html>

[petsc-dev] components in PetscSection

2012-08-31 Thread Matthew Knepley
ing than any results to which their > experiments > > lead. > > -- Norbert Wiener > > > > -- > Chris Eldred > DOE Computational Science Graduate Fellow > Graduate Student, Atmospheric Science, Colorado State University > B.S. Applied Computational Physics, Carnegie Mellon University, 2009 > chris.eldred at gmail.com > -- 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/20120831/e6d0c74a/attachment.html>

[petsc-dev] components in PetscSection

2012-08-31 Thread Matthew Knepley
- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/8728c154/attachment.html>

[petsc-dev] clique

2012-08-31 Thread Jack Poulson
alpackages/clique/external/parmetis/metis/include >>-o CMakeFiles/parmetis-addons.dir/ParallelBisect.c.o -c >> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >> > >> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >> fatal error: parmetislib.h: No such file or directory >> > >> > Looks like this code needs parmetis private includes. So the current >> > stratergy [of splitting into -lparmetis-addons] isn't working. >> > >> > Perhaps we'll have to use a single patched metis/parmetis tarball for >> > both petsc and clique afterall.. >> > >> > Satish >> > >> >> -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/50fe9f07/attachment.html>

[petsc-dev] clique

2012-08-31 Thread Jack Poulson
-I/home/balay/spetsc/externalpackages/clique/external/parmetis/include >>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/libparmetis >>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/GKlib >>> -I/home/balay/spetsc/externalpackages/clique/external/parmetis/metis/include >>>-o CMakeFiles/parmetis-addons.dir/ParallelBisect.c.o -c >>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >>> > >>> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >>> fatal error: parmetislib.h: No such file or directory >>> > >>> > Looks like this code needs parmetis private includes. So the current >>> > stratergy [of splitting into -lparmetis-addons] isn't working. >>> > >>> > Perhaps we'll have to use a single patched metis/parmetis tarball for >>> > both petsc and clique afterall.. >>> > >>> > Satish >>> > >>> >>> > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/21acbee6/attachment.html>

[petsc-dev] components in PetscSection

2012-08-31 Thread Chris Eldred
Ok- so if I have a multicomponent field, I should define the number of dofs at a point for that field to be the total number of dofs I want for that field. Ex a 2 component field with 2 dofs per component should have 4 dofs defined, not 2. Num components just serves to give additional info about th

[petsc-dev] clique

2012-08-31 Thread Jack Poulson
ir/ParallelBisect.c.o -c >> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c >> > >> /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: >> fatal error: parmetislib.h: No such file or directory >> > >> > Looks like this code needs parmetis private includes. So the current >> > stratergy [of splitting into -lparmetis-addons] isn't working. >> > >> > Perhaps we'll have to use a single patched metis/parmetis tarball for >> > both petsc and clique afterall.. >> > >> > Satish >> > >> >> -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/529dfc9f/attachment-0001.html>

[petsc-dev] clique

2012-08-31 Thread Satish Balay
The fix I'm hoping for is: the bundled software defaults to using internal pckage - but the build tools also support --with-package-include,--with-package-lib options for externally build version of the internal packages. this is partly done for metis/parmetis within clique but there is this other

[petsc-dev] clique

2012-08-31 Thread Jed Brown
arallelBisect.c > > > /home/balay/spetsc/externalpackages/clique/src/parmetis/ParallelBisect.c:5:25: > fatal error: parmetislib.h: No such file or directory > > > > Looks like this code needs parmetis private includes. So the current > > stratergy [of splitting into -lparmetis-addons] isn't working. > > > > Perhaps we'll have to use a single patched metis/parmetis tarball for > > both petsc and clique afterall.. > > > > Satish > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120831/d77c352b/attachment.html>

[petsc-dev] clique

2012-08-31 Thread Satish Balay
Should have cc:d to petsc-dev context: clique packages metis,parmetis,elemental sources in a single bundle. So we were attempting to build them separately [from petsc configure]. Jack has extensions to metis and parmetis functionality - thats used in clique. We tried to split this out into separ

[petsc-dev] Fwd: [petsc-users] pctype hmpi

2012-08-31 Thread Barry Smith
HMPI usage in PETSc relies on sending function pointer addresses between MPI processes; this use to be fine since you start up several copies of the same executable on a machine each has the same virtual addresses for instructions. Yes, this a bit hacky but it worked great. With ASLR t

[petsc-dev] components in PetscSection

2012-08-31 Thread Chris Eldred
I was wondering how components were treated in PetscSection- my understanding is that a field with multiple components and multiple dofs would have those dofs duplicated for each component, but that does not appear to be the case. For example, let's say I have a field with 2 components and 2 dofs t