Re: [petsc-dev] pnetcdf is a big problem

>>>>> > > > > 4. Reporting Installation or Usage Problems > > === > > > > Please send an email to parallel-net...@mcs.anl.gov > > > > <<<<<< > > > > We'll have to send in these bug reports. &g

[petsc-dev] Bitbucket vs Github

The RSS from Bitbucket is far superior. I cannot see anything that went on with Github, but Bitbucket shows it nicely. Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbe

Re: [petsc-dev] DM exodus viewer

On Fri, Dec 22, 2017 at 11:19 AM, Blaise A Bourdin wrote: > Hi, > > Now that all the low-level functions are in next, I’d like to add proper > support for an exodus viewer for Vector and DM, but I really don’t know > where to start from. > Can anybody point me to where I should start looking at i

Re: [petsc-dev] still relevant in ./configure help ? Should Matt remove them?

On Mon, Dec 25, 2017 at 10:19 PM, Smith, Barry F. wrote: > > > > On Dec 25, 2017, at 8:08 PM, Balay, Satish wrote: > > > > On Mon, 25 Dec 2017, Smith, Barry F. wrote: > > > >> > >> --with-autoreconf= > >> Specify autoreconf current: autoreconf > >> --with-libtoolize= > >> Specify l

Re: [petsc-dev] How to pass user data to a registered PC (PCRegister) ?

On Thu, Dec 28, 2017 at 11:34 AM, Franck Houssen wrote: > - Mail original - > > De: "Barry F. Smith" > > À: "Franck Houssen" > > Cc: "For users of the development version of PETSc" < > petsc-dev@mcs.anl.gov> > > Envoyé: Jeudi 28 Décembre 2017 16:43:16 > > Objet: Re: [petsc-dev] How to p

Re: [petsc-dev] IMPORTANT nightly builds are down do not add to next

On Fri, Dec 29, 2017 at 2:11 PM, Smith, Barry F. wrote: > >The nightly builds are down (out-dated data at the website) and Satish > is in India and cannot fix it. > > Please do not put anything into next until you are notified that the > nightly tests are working again. Cool. This shou

Re: [petsc-dev] IMPORTANT nightly builds are down do not add to next

On Fri, Dec 29, 2017 at 5:35 PM, Smith, Barry F. wrote: > > On Dec 29, 2017, at 3:52 PM, Matthew Knepley wrote: > > > > On Fri, Dec 29, 2017 at 2:11 PM, Smith, Barry F. > wrote: > > > >The nightly builds are down (out-dated data at the website) and >

Re: [petsc-dev] How to pass user data to a registered PC (PCRegister) ?

On Sun, Dec 31, 2017 at 9:40 AM, Franck Houssen wrote: > Seems finally, I got it to work. > To get the options to work I had to call PetscOptionsBegin/End > after/before PetscOptionsHead/Tail which is not what is done in the jacobi > example: is this the right way to go ? > No, you should not do

Re: [petsc-dev] How to pass user data to a registered PC (PCRegister) ?

On Sun, Dec 31, 2017 at 9:01 AM, Franck Houssen wrote: > Using PCSHELL means calling: > - PCShellSetSetUp, PCShellSetApply, PCShellSetDestroy to set callbacks. > - PCShellSetContext/PCShellGetContext to get/set context in callbacks. > > To go from PCSHELL to PCRegister, one need to: > - #inclu

Re: [petsc-dev] need c++ expert help

I would always try putting std:: on everything when this happened. Matt On Sun, Dec 31, 2017 at 11:59 AM, Smith, Barry F. wrote: > > ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2017/12/31/examples_next_arch-linux-gcc-ifc-cmplx_crank.log > > Yet seems to compile on other systems wi

Re: [petsc-dev] need c++ expert help

XX). Matt > Matthew Knepley writes: > > > I would always try putting std:: on everything when this happened. > > > >Matt > > > > On Sun, Dec 31, 2017 at 11:59 AM, Smith, Barry F. > > wrote: > > > >> > >> ftp://ftp.mcs.anl.gov/p

Re: [petsc-dev] need c++ expert help

On Sun, Dec 31, 2017 at 2:35 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Sun, Dec 31, 2017 at 1:55 PM, Jed Brown wrote: > > > >> These look like linker errors and that build uses > >> --with-cxxlib-autodetect=0. We either need a rule to *link*

Re: [petsc-dev] need c++ expert help

On Sun, Dec 31, 2017 at 3:14 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Sun, Dec 31, 2017 at 2:35 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > On Sun, Dec 31, 2017 at 1:55 PM, Jed Brown wrote: > >> &g

Re: [petsc-dev] How to pass user data to a registered PC (PCRegister) ?

On Tue, Jan 2, 2018 at 6:04 AM, Franck Houssen wrote: > - Mail original - > > De: "Barry F. Smith" > > À: "Franck Houssen" > > Cc: "For users of the development version of PETSc" < > petsc-dev@mcs.anl.gov> > > Envoyé: Dimanche 31 Décembre 2017 23:41:42 > > Objet: Re: [petsc-dev] How to

Re: [petsc-dev] How to pass user data to a registered PC (PCRegister) ?

On Tue, Jan 2, 2018 at 8:47 AM, Franck Houssen wrote: > I'll try to fetch/pull the git clone: maybe there is a reg on the code > level I am on. > > - Mail original - > > De: "Barry F. Smith" > > À: "Franck Houssen" > > Cc: "For users of the development version of PETSc" < > petsc-dev@mc

Re: [petsc-dev] PETSc.pc: missing rpath ?

On Tue, Jan 2, 2018 at 9:15 AM, Franck Houssen wrote: > - Mail original - > > De: "Jed Brown" > > À: "Franck Houssen" , "For users of the > development version of PETSc" > > > > Envoyé: Mardi 2 Janvier 2018 15:02:17 > > Objet: Re: [petsc-dev] PETSc.pc: missing rpath ? > > > > Some peopl

Re: [petsc-dev] How do I collect all the values from a sequential vector on the zeroth processor into a parallel PETSc vector ?

On Wed, Jan 3, 2018 at 11:47 AM, Franck Houssen wrote: > How do I collect all the values from a sequential vector on the zeroth > processor into a parallel PETSc vector ? > Shall I use VecScatterCreateToZero "backward", or, use VecScatterCreate > instead ? If yes, how ? (my understanding is that

Re: [petsc-dev] SETERRQ in fortran

On Thu, Jan 4, 2018 at 2:42 PM, Blaise A Bourdin wrote: > Hi, > > Is SETERRQ still available in fortran? I notice that it is not used in any > of the example, but the man page still mentions fortran. Using it in a > fortran code leads to compiler errors. > Am I doing something wrong? > I see it

Re: [petsc-dev] Our pull request work flow is terrible and horrible

On Thu, Jan 11, 2018 at 12:40 PM, Patrick Sanan wrote: > One idea is to impose a stricter guideline that things on the bitbucket PR > page are things that everyone is actively trying to merge. That way, > maintainers can just look at the bottom of the list to see what's lagging, > instead of havi

Re: [petsc-dev] triangle is filled with calls to random() no reproducibility here

On Tue, Jan 16, 2018 at 11:49 PM, Smith, Barry F. wrote: > > Sorry, I should have said ctetgen > Yes. Jon was careful in Triangle to use the robust predicates from David Bailey, and it should be reproducible. TetGen does not care at all about that. For tests, it would be nice to create a struc

Re: [petsc-dev] Plex XDMF/HDF5 I/O

On Wed, Jan 17, 2018 at 6:49 AM, Vaclav Hapla wrote: > For DMPlex and PETSCVIEWERHDF5, DMView produces a HDF5 file consisting > basically of these 3 parts: > 1) vertices (HDF5 group /geometry) > 2) "native" Plex topology as a serialization of the Plex graph > 3) traditional topology as connectivi

[petsc-dev] Fwd: PETSc with homebrew

with homebrew To: Matthew Knepley Matt, The homebrew organizers are having all kinds to trouble with scientific software (https://github.com/Homebrew/homebrew-science/issues/6365). Now there appears to be some effort to get PETSc back into homebrew ( https://github.com/Homebrew/homebrew-core/pull

Re: [petsc-dev] horrible lies about PETSc that need to be fixed

On Mon, Feb 5, 2018 at 1:13 PM, Smith, Barry F. wrote: > >How dare you defame us in such a way. PETSc never ever "needed" cmake > and certainly never will > > > http://mooseframework.org/wiki/BasicManualInstallation/OSX/#0-pre-reqs > http://mooseframework.org/wiki/BasicManualInstallation/Linu

[petsc-dev] WHO BROKE THE TRIANGLE BUILD

That has worked for a decade. 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 https://www.cse.buffalo.edu/~knepley/

Re: [petsc-dev] WHO BROKE THE TRIANGLE BUILD

next_arch-linux-opt-misc_el6.log Matt > > On Feb 7, 2018, at 8:48 AM, Matthew Knepley wrote: > > > > That has worked for a decade. > > > >Matt > > > > -- > > What most experimenters take for granted before they begin their > experiments is

Re: [petsc-dev] WHO BROKE THE TRIANGLE BUILD

nches right now? > Pulling and checking. I has not pulled from yesterday. Does that mean Triangle is broken for stdc99? One more thing to fix. Matt > > On Feb 7, 2018, at 8:52 AM, Matthew Knepley wrote: > > > > On Thu, Feb 8, 2018 at 1:49 AM, Smith, Barry F. > wrote: &

Re: [petsc-dev] WHO BROKE THE TRIANGLE BUILD

On Thu, Feb 8, 2018 at 3:06 AM, Jed Brown wrote: > Matthew Knepley writes: > > > On Thu, Feb 8, 2018 at 2:02 AM, Smith, Barry F. > wrote: > > > >> > >> That is yesterday's build. Today's next look ok. > >> > >>I had

Re: [petsc-dev] petsc/master: unable to link in C++ with last night PETSC_WITH_EXTERNAL_LIB variable changes

On Sat, Feb 10, 2018 at 9:42 AM, Éric Chamberland < eric.chamberl...@giref.ulaval.ca> wrote: > Hi, > > we used to link our c++ code with PETSc using PETSC_WITH_EXTERNAL_LIB > variable defined in $PETSC_DIR/lib/petsc/conf/petscvariables and > everything was fine until this night. > > It seems some

Re: [petsc-dev] petsc/master: unable to link in C++ with last night PETSC_WITH_EXTERNAL_LIB variable changes

e C++ compiler /opt/openmpi-1.10.2/bin/mpicxx does link using -lmpi_cxx, but your link must not be using it. That is why I wanted to see the whole link line. Thanks, Matt I could send you our whole line of link, but the error is into this small > change introduced yesterday into master... > &

Re: [petsc-dev] petsc/master: unable to link in C++ with last night PETSC_WITH_EXTERNAL_LIB variable changes

On Sat, Feb 10, 2018 at 1:44 PM, Jed Brown wrote: > Éric Chamberland writes: > > > Le 18-02-10 à 12:38, Jed Brown a écrit : > >> Éric Chamberland writes: > >> > >>> > >>> and into this block there was the "-lmpi_cxx" that we need... > >> The point is that if you are linking C++ code that calls

Re: [petsc-dev] petsc/master: unable to link in C++ with last night PETSC_WITH_EXTERNAL_LIB variable changes

On Sat, Feb 10, 2018 at 2:34 PM, Jed Brown wrote: > Matthew Knepley writes: > > >> Note that PETSc's own dependency management is messy because someone in > >> the early days of BuildSystem thought that concatenating strings was > >> sufficient, instead

Re: [petsc-dev] petsc/master: unable to link in C++ with last night PETSC_WITH_EXTERNAL_LIB variable changes

On Sat, Feb 10, 2018 at 9:56 PM, Jed Brown wrote: > Matthew Knepley writes: > > > If we were in charge of all dependencies, that would be true. However, > > packages can dump in things that need to link with. if we could > > require that all dependencies be specified thr

Re: [petsc-dev] DMPlex VecView to HDF5

On Mon, Feb 12, 2018 at 10:57 PM, Adrian Croucher wrote: > hi, > > I have a DMPlex which I pass in to DMCreateGlobalVector() to create a > vector, and then use VecView() to view the vector. > > If the DM happens to contain no points on one process, this still works > fine if I view the vector usi

Re: [petsc-dev] How to get the subsnes from a nonlinear problem

On Sun, Feb 18, 2018 at 1:59 AM, Lulu Liu wrote: > Hi, > > I am trying to use nonlinear elimination (NE) to solve a nonlinear > problem, and I have to solve a subproblem. How to get the subsnes from > the original global nonlinear problem? Is there any easy way to do it? > Are you doing NE usi

Re: [petsc-dev] DMPlex VecView to HDF5

_HDF5_Internal() line 214 in > /home/acro018/software/PETSc/code/src/dm/impls/plex/plexhdf5.c > [2]PETSC ERROR: #11 VecView_Plex() line 354 in > /home/acro018/software/PETSc/code/src/dm/impls/plex/plex.c > [2]PETSC ERROR: #12 VecView() line 586 in /home/acro018/software/PETSc/ >

Re: [petsc-dev] [Mike McQuaid] Re: [Homebrew/homebrew-core] PETSc: import from homebrew-science (#23598)

On Fri, Feb 23, 2018 at 3:19 PM, Jed Brown wrote: > What, if anything, really needs to be installed to $prefix/bin? > > From the Homebrew lead maintainer. > The maintainer of Homebrew calling anything a mess is pretty rich. Matt > > -- Forwarded message -- > From: Mike McQu

Re: [petsc-dev] [Mike McQuaid] Re: [Homebrew/homebrew-core] PETSc: import from homebrew-science (#23598)

On Sun, Feb 25, 2018 at 1:55 PM, Smith, Barry F. wrote: > > > > On Feb 25, 2018, at 12:16 PM, Jed Brown wrote: > > > > "Smith, Barry F." writes: > > > >> So fix the damn script instead of just bitching about it! Jeepers, > that is what open source is all about. > > > > Yes, my last email was l

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 12:58 PM, Jed Brown wrote: > Adrián Amor writes: > > > 1. I have compiled PETSC with these options: > > ./configure --with-cc=mpiicc --with-cxx=mpiicpc --with-fc=mpiifort > > --with-blas-lapack-dir=/opt/intel/mkl/lib/intel64/ --with-debugging=1 > > --with-scalar-type=compl

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 2:02 PM, Jed Brown wrote: > Matthew Knepley writes: > > > I guess my superficial response to this is > > > > a) I do not consider Buildsystem "mine" anymore. I may still have the > > most lines of code, but I am not even sure of

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 2:33 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On this note, I am saddened by the fact that no current options parsing > > implementations has even this features, let alone other things that we > do. > > Are our needs to differe

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 2:39 PM, Jed Brown wrote: > Matthew Knepley writes: > > > That is not the same as printing unused arguments. Michael's Pythia > > does this correctly, but it is even less simple. > > You want it to accept the unused arguments and just print

[petsc-dev] Webpage missing

I cannot find http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/UsingFortran.html in the dev docs. Thanks, Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 6:17 PM, Scott Kruger wrote: > On 3/2/18 12:44 PM, Matthew Knepley wrote: > >> On Fri, Mar 2, 2018 at 2:39 PM, Jed Brown > j...@jedbrown.org>> wrote: >> >> Matthew Knepley mailto:knep...@gmail.com>> >> writes: >>

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On Fri, Mar 2, 2018 at 11:55 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 2, 2018 at 6:17 PM, Scott Kruger wrote: > > > >> On 3/2/18 12:44 PM, Matthew Knepley wrote: > >> > >>> On Fri, Mar 2, 2018 at 2:39 PM, Jed Brown >&g

Re: [petsc-dev] plans for preconditioners for SeqSELL

On Sun, Mar 4, 2018 at 6:57 PM, Jed Brown wrote: > "Zhang, Hong" writes: > > > We have thought about subclassing long before. As Barry suggested, an > > ideal solution is to make a base class (XAIJ ?) for AIJ, BAIJ, SBAIJ, > > and SELL. The base class will have diagonal and off diagonal parts >

[petsc-dev] Fwd: In February, you had 444 users visit your website (Google Analytics)

-- Forwarded message -- From: Google Analytics Date: Tue, Mar 6, 2018 at 12:04 AM Subject: In February, you had 444 users visit your website (Google Analytics) To: knep...@gmail.com Your Snapshot for FebruaryWant to get a monthly snapshot for more views? Edit your email preferenc

Re: [petsc-dev] dm/interface directory files should NOT have DMPlex code in them. Shudder!

This stuff is in DM because two concepts need to be promoted to DM. They are already both in DA and Plex: 1) GlobalToNatural, which is in dmi.c 2) Coordinates, in particular periodic coordinates, which is in dm.c Removing these means adding 1 or 2 functions to dmimpl Matt On Mon, Mar 12, 2

Re: [petsc-dev] dm/interface directory files should NOT have DMPlex code in them. Shudder!

(h = 0; h <= maxHeight; h++) { > ierr = DMPlexGetHeightStratum(cdm, h, &pStart[h], > &pEnd[h]);CHKERRQ(ierr); > newStart = PetscMin(newStart,pStart[h]); > newEnd = PetscMax(newEnd,pEnd[h]); > > > > > On Mar 11, 2018, at 4:21 PM, Matthew K

Re: [petsc-dev] dm/interface directory files should NOT have DMPlex code in them. Shudder!

On Mon, Mar 12, 2018 at 9:07 AM, Smith, Barry F. wrote: > > On Mar 11, 2018, at 6:49 PM, Matthew Knepley wrote: > > > > On Mon, Mar 12, 2018 at 8:33 AM, Smith, Barry F. > wrote: > > Please implement things properly with subclasses (subtypes) and get this > cr

[petsc-dev] Test parsers is parsing *.c~ files

This took me forever to find. The parser is parsing emacs backups and overwriting some tests. 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 https://www.cs

Re: [petsc-dev] Test parsers is parsing *.c~ files

5 PM, Smith, Barry F. wrote: > >> >> >>This drives me nuts also, obviously Scott does not use Emacs or he >> would have make sure long ago that the test harness would not trip over the >> crumbs of Emacs. >> >> Matt, You'll need to share the

Re: [petsc-dev] Is ./configure --help broken?

On Thu, Mar 15, 2018 at 9:30 AM, Satish Balay wrote: > On Thu, 15 Mar 2018, Stefano Zampini wrote: > > > it seems we can no longer print the available configure options in master > > > > [szampini@localhost petsc]$ ./configure --help > > ===

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 9:03 AM, Matthew Knepley wrote: > On Thu, Mar 15, 2018 at 9:30 AM, Satish Balay wrote: > >> On Thu, 15 Mar 2018, Stefano Zampini wrote: >> >> > it seems we can no longer print the available configure options in >> master >> > &g

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 9:13 AM, Satish Balay wrote: > On Fri, 16 Mar 2018, Matthew Knepley wrote: > > > On Thu, Mar 15, 2018 at 9:30 AM, Satish Balay wrote: > > > > > On Thu, 15 Mar 2018, Stefano Zampini wrote: > > > > > > > it seems we can no

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 9:26 AM, Satish Balay wrote: > On Fri, 16 Mar 2018, Matthew Knepley wrote: > > > This works for me. Do you want to put it in your branch, or should I > check > > it in? > > > >Matt > > > > diff --git a/config/Build

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 1:17 PM, Jed Brown wrote: > Matthew Knepley writes: > > > I agree. We should remove all code (about 2/3 of it) which does a > > hierarchy of communicating dicts (the original design). That would > > make everything simple. No threads, no paren

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 1:27 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 16, 2018 at 1:17 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > I agree. We should remove all code (about 2/3 of it) which doe

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 2:20 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 16, 2018 at 1:27 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > On Fri, Mar 16, 2018 at 1:17 PM, Jed Brown wrote: > >> >

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 6:25 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 16, 2018 at 2:20 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > On Fri, Mar 16, 2018 at 1:27 PM, Jed Brown wrote: > >> &g

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 9:23 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 16, 2018 at 6:25 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > On Fri, Mar 16, 2018 at 2:20 PM, Jed Brown wrote: > >> &g

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 9:33 PM, Jed Brown wrote: > Matthew Knepley writes: > > >> Cray and others have admitted to doing this for as long as I've used > >> PETSc. It's possible to discourage it without setting land mines. > > > > > > I guess

Re: [petsc-dev] Is ./configure --help broken?

On Fri, Mar 16, 2018 at 11:50 PM, Jed Brown wrote: > Matthew Knepley writes: > > > On Fri, Mar 16, 2018 at 9:33 PM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> >> Cray and others have admitted to doing this for as long as I&

[petsc-dev] Tests are not working for me in next

I get CC arch-next-opt/tests/dm/impls/plex/examples/tests/ex20.o CLINKER arch-next-opt/tests/dm/impls/plex/examples/tests/ex20 TEST arch-next-opt/tests/counts/dm_impls_plex_tests-ex20_2d.counts not ok dm_impls_plex_tests-ex20_2d # dyld: Library not loaded: arch-next-opt/lib/

[petsc-dev] We have SSL problems with some sites

I fail when retrieving GMP, and I get 4next $:/PETSc3/petsc/petsc-dev$ wget --secure-protocol=TLSv1 https://gmplib.org/download/gmp/gmp-6.0.0a.tar.bz2 . wget --secure-protocol=TLSv1 https://gmplib.org/download/gmp/gmp-6.0.0a.tar.bz2 . --2018-03-21 21:33:42-- https://gmplib.org/download/gmp/gmp-6

Re: [petsc-dev] We have SSL problems with some sites

On Wed, Mar 21, 2018 at 9:49 PM, Jed Brown wrote: > Matthew Knepley writes: > > > I fail when retrieving GMP, and I get > > > > 4next $:/PETSc3/petsc/petsc-dev$ wget --secure-protocol=TLSv1 > > https://gmplib.org/download/gmp/gmp-6.0.0a.tar.bz2 . > > wg

Re: [petsc-dev] We have SSL problems with some sites

Nope, I get failure with that as well. Matt On Wed, Mar 21, 2018 at 9:55 PM, Matthew Knepley wrote: > I get > > > *** > UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.lo

Re: [petsc-dev] We have SSL problems with some sites

==>] > 2.21M 423KB/sin 6.1s > > 2018-03-21 20:51:19 (372 KB/s) - ‘gmp-6.0.0a.tar.bz2.1’ saved > [2319400/2319400] > > [petsc@ipro ~]$ > > > On Thu, 22 Mar 2018, Matthew Knepley wrote: > >

Re: [petsc-dev] We have SSL problems with some sites

= > = > > > =========== > > Running make on GMP; this may take several > minutes > > ===

Re: [petsc-dev] MPI I/O tests failing in master after merging my branch

On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin wrote: > ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/03/21/examples_master_arch-linux-cxx-cmplx-pkgs-64idx_churn.log > > The thing is, PETSc does not currently have a way of mapping a plain C > `int` type to a PETSc datatype. I'm wi

Re: [petsc-dev] MPI I/O tests failing in master after merging my branch

On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin wrote: > On 22 March 2018 at 12:51, Matthew Knepley wrote: > > On Thu, Mar 22, 2018 at 3:44 AM, Lisandro Dalcin > wrote: > >> > >> > >> ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/03/21

Re: [petsc-dev] We have SSL problems with some sites

On Thu, Mar 22, 2018 at 6:09 AM, Lawrence Mitchell wrote: > > On 22 Mar 2018, at 09:47, Matthew Knepley wrote: > > > > On Wed, Mar 21, 2018 at 10:00 PM, Satish Balay > wrote: > > Works for me.. > > > > Well, I am not kidding when I say it fails for me.

Re: [petsc-dev] MPI I/O tests failing in master after merging my branch

On Thu, Mar 22, 2018 at 7:09 AM, Jed Brown wrote: > Matthew Knepley writes: > > > On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin > wrote: > > > >> On 22 March 2018 at 12:51, Matthew Knepley wrote: > >> > On Thu, Mar 22, 20

Re: [petsc-dev] MPI I/O tests failing in master after merging my branch

On Thu, Mar 22, 2018 at 8:28 AM, Jed Brown wrote: > Matthew Knepley writes: > > > On Thu, Mar 22, 2018 at 7:09 AM, Jed Brown wrote: > > > >> Matthew Knepley writes: > >> > >> > On Thu, Mar 22, 2018 at 6:15 AM, Lisandro Dalcin > >>

Re: [petsc-dev] DMFOREST repartitioning in PETSc

On Thu, Mar 22, 2018 at 11:45 AM, Saurabh Chawdhary wrote: > Thank you Tobin. I was actually more interested in repartitioning after > the mesh has been dynamically changed (say, after refinement in certain > portions of mesh). > That kinds of repartitioning in p4est is handled by just splitting

Re: [petsc-dev] HDF5 read attribute from HDF5

This looks fine to me. I have put it in a branch https://bitbucket.org/petsc/petsc/branch/knepley/fix-hdf5-attribute and into next. It should promote to master in a week or so. Thanks, Matt On Mon, Mar 19, 2018 at 3:18 PM, Marek Pecha wrote: > Hello, > > I would like to request ne

Re: [petsc-dev] [mpich-discuss] Is mpich/master:a8a2b30fd21 tested with Petsc?

On Tue, Mar 27, 2018 at 4:59 PM, Min Si wrote: > Hi Eric, > > It will be great if you could give us a simple MPI program (not with > PETSc) to reproduce this issue. If this is a problem happens only when > PETSc is involved, the PETSc team can give you more suggestions. > Hi Min, It is really e

[petsc-dev] Fwd: [mpich-discuss] Is mpich/master:a8a2b30fd21 tested with Petsc?

address when sending messages, then contact the mailing list owner at discuss-ow...@lists.mpich.org. -- Forwarded message -- From: Matthew Knepley To: Min Si Cc: disc...@mpich.org, PETSc Bcc: Date: Tue, 27 Mar 2018 17:04:57 -0400 Subject: Re: [petsc-dev] [mpich-discuss] Is mpich

Re: [petsc-dev] upcoming release and testing

On Sun, Apr 1, 2018 at 5:12 PM, Satish Balay wrote: > > I've merged the following branches [tested in next-tmp] to master. > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/04/01/next-tmp.html > > origin/jed/fix-analyzer-bugs > origin/balay/update-hypre-v2.14.0 > origin/denera/tao-

Re: [petsc-dev] upcoming release and testing

On Mon, Apr 2, 2018 at 10:02 AM, Satish Balay wrote: > On Mon, 2 Apr 2018, Matthew Knepley wrote: > > > > > origin/knepley/fix-cylinder-mesh > > origin/knepley/fix-dm-gmg > > origin/knepley/fix-ex62-tests > > > > should all go clean. Can we try those

Re: [petsc-dev] [issue1595] Issues of limited number of MPI communicators when having many instances of hypre boomerAMG with Moose

On Tue, Apr 3, 2018 at 6:02 PM, Rob Falgout hypre Tracker < hypre-supp...@llnl.gov> wrote: > > Rob Falgout added the comment: > > In my opinion, if the user is doing something simultaneously with a hypre > solve (not the typical case, I think), then they should be responsible for > ensuring that

Re: [petsc-dev] [issue1595] Issues of limited number of MPI communicators when having many instances of hypre boomerAMG with Moose 49d13fee5f3a3720

I have to be registered. I believe there is also a suitcoat requirement for the Hypre list. Matt On Tue, Apr 3, 2018 at 6:03 PM, Matthew Knepley wrote: > On Tue, Apr 3, 2018 at 6:02 PM, Rob Falgout hypre Tracker < > hypre-supp...@llnl.gov> wrote: > >> >> Rob

[petsc-dev] FAS indentation

The recent indentation fix (I think) has broken the FAS solver indentation. 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 https://www.cse.buffalo.edu/~kne

Re: [petsc-dev] FAS indentation

> On April 3, 2018 at 6:11:12 PM, Smith, Barry F. (bsm...@mcs.anl.gov) > wrote: > > > Alp, > > Can you please take a look at this? > > Thanks > > Barry > > > > On Apr 3, 2018, at 4:46 PM, Matthew Knepley wrote: > > > > The recent indentation fix

[petsc-dev] Fwd: In March, you had 482 users visit your website (Google Analytics)

Good month. Matt -- Forwarded message -- From: Google Analytics Date: Wed, Apr 4, 2018 at 5:21 AM Subject: In March, you had 482 users visit your website (Google Analytics) To: knep...@gmail.com Your Snapshot for March Want to get a monthly snapshot for more views? Edit your

[petsc-dev] Nullspace with right preconditioning

This is broken. Did we know this was broken? Thanks, 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 https://www.cse.buffalo.edu/~knepley/

Re: [petsc-dev] Nullspace with right preconditioning

ght. Basically, I put in a constant for the pressure as the nullspace. If you run with gmres/left it gives back a pressure with integral 0. If you run with gmres/right, it gives back a pressure with a big integral. Matt > > Barry > > > > > > On Apr 4, 2018, at 1:13 PM

Re: [petsc-dev] getting on with the nested timers

On Thu, Apr 5, 2018 at 6:15 AM, Klaij, Christiaan wrote: > Barry, > > I'm still trying to use petsc's nested logging with our code. I > have it working for 3.8.3 with the command line option, for > example: > > mpirun -n 3 ./refresco -log_view :performance.xml:ascii_xml > > This gives the expecte

Re: [petsc-dev] getting on with the nested timers

semi-submersible yachts > <http://www.marin.nl/web/News/News-items/Comfort-draft-for-semisubmersible-yachts.htm> > > -- > *From:* Matthew Knepley > *Sent:* Thursday, April 05, 2018 12:50 PM > *To:* Klaij, Christiaan > *Cc:* Smith, Barry F.; pet

Re: [petsc-dev] getting on with the nested timers

- read Thanks, Matt > Chris > ---------- > *From:* Matthew Knepley > *Sent:* Thursday, April 05, 2018 1:35 PM > *To:* Klaij, Christiaan > *Cc:* Smith, Barry F.; petsc-dev@mcs.anl.gov; Koos Huijssen > *Subject:* Re: [petsc-dev] getting on wi

Re: [petsc-dev] upcoming release and testing [v2]

On Thu, Apr 5, 2018 at 8:58 AM, Satish Balay wrote: > All, > > master builds have been clean for the past 2 days [except for some > timeouts] > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/04/04/master.html > > However next is still not clean [slightly better than previous build

Re: [petsc-dev] upcoming release and testing [v2]

On Thu, Apr 5, 2018 at 9:28 AM, Satish Balay wrote: > On Thu, 5 Apr 2018, Matthew Knepley wrote: > > > > > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/04/05/next.html > > > > I think I know all the fixes. I cannot do it until ton

[petsc-dev] CMake

Can we remove all packages that use CMake before the next release? See also "/PETSc3/petsc/petsc-pylith/arch-next-debug/externalpackages/hg.eigen/build/CMakeFiles/CMakeOutput.log".CMake Error at /PETSc3/petsc/petsc-pylith/arch-pylith-debug/share/cmake-3.0/Modules/Platform/Darwin.cmake:211 (message

Re: [petsc-dev] upcoming release and testing [v2]

On Thu, Apr 5, 2018 at 9:05 AM, Matthew Knepley wrote: > On Thu, Apr 5, 2018 at 8:58 AM, Satish Balay wrote: > >> All, >> >> master builds have been clean for the past 2 days [except for some >> timeouts] >> >> http://ftp.mcs.anl.gov/pub/petsc/nigh

Re: [petsc-dev] upcoming release and testing [v2]

On Thu, Apr 5, 2018 at 10:34 PM, Satish Balay wrote: > On Fri, 6 Apr 2018, Matthew Knepley wrote: > > > Okay, I pushed fixes for everything I saw except: > > > > > 1) The weird ex56_1 bug. This is only due to feature-dmfield, and > > its very strange that this

[petsc-dev] More CMake hatred

Error configuring EIGEN with cmake Could not execute "cd /projects/academic/knepley/PETSc3/petsc/arch-master-debug/externalpackages/eigen-eigen-5a0156e40feb/build && /projects/academic/knepley/PETSc3/petsc/arch-master-debug/bin/cmake .. -DCMAKE_INSTALL_PREFIX=/projects/academic/knepley/PETSc3/petsc

Re: [petsc-dev] More CMake hatred

On Thu, Apr 5, 2018 at 11:44 PM, Jed Brown wrote: > Matthew Knepley writes: > > > Error configuring EIGEN with cmake Could not execute "cd > > /projects/academic/knepley/PETSc3/petsc/arch-master- > debug/externalpackages/eigen-eigen-5a0156e40feb/build > > &

Re: [petsc-dev] plexexodusii.c incompatible with complex - not covered?

On Thu, Apr 12, 2018 at 12:26 PM, Vaclav Hapla wrote: > At master, configured with > --download-exodusii --download-hdf5 --download-netcdf --download-pnetcdf > --with-scalar-type=complex > I get bunch of compiler warnings > warning: passing argument 2 of ‘VecGetArrayRead’ from incompatible >

Re: [petsc-dev] Default dimension of a DM

I am fine with this change. Matt On Mon, Apr 16, 2018 at 9:19 AM, Stefano Zampini wrote: > Maybe this is silly, but why the default dimenson of a DM is 0; why not -1? > A DM of dimension 0 is a point, while a DM of dimension -1 is a DM in a > not yet complete setup state. > -- > Stefano >

Re: [petsc-dev] Vec set a block of values

On Fri, Apr 20, 2018 at 4:10 PM, Junchao Zhang wrote: > To pad a vector, i.e., copy a vector to a new one, I have to call > VecSetValue(newb,1,&idx,...) for each element. But to be efficient, what I > really needs is to set a block of values in one call. It looks PETSc does > not have a routine f

Re: [petsc-dev] Vec set a block of values

On Fri, Apr 20, 2018 at 4:33 PM, Junchao Zhang wrote: > > On Fri, Apr 20, 2018 at 3:18 PM, Matthew Knepley > wrote: > >> On Fri, Apr 20, 2018 at 4:10 PM, Junchao Zhang >> wrote: >> >>> To pad a vector, i.e., copy a vector to a new one, I have to call &g

<    2   3   4   5   6   7   8   9   10   11   >