Re: [petsc-dev] CUDA 7
Hello Jose, I pushed a release candidate that should resolve your errors. Please try compiling using branch release/0.5.1 of the CUSP repo. Once I've verified compiling on VS2013 is fully operational I will bag and tag v0.5.1. Thanks, Steve On Tue, Apr 14, 2015 at 10:32 AM, Steven Dalton sdalt...@gmail.com wrote: Hello Jose, I'm hacking on version to integrate 0.5.0 changes and verify CUDA 7 support. I can make it available or send a pull request later this week to start experimenting if anyone is interested. Steve On Tue, Apr 14, 2015 at 10:09 AM, Jose E. Roman jro...@dsic.upv.es wrote: Has anyone updated to CUDA 7? With clanguage=c++ now I get lots of warnings with CUSP v0.4.0. These presumably will go away when updating to CUSP v0.5.0, but it turns out that PETSc build is broken with CUSP v0.5.0 (a header file was moved, and some other issues). Jose
Re: [petsc-dev] CUDA 7
Thanks. It works now. Jose El 21/04/2015, a las 08:51, Steven Dalton escribió: Hello Jose, I pushed a release candidate that should resolve your errors. Please try compiling using branch release/0.5.1 of the CUSP repo. Once I've verified compiling on VS2013 is fully operational I will bag and tag v0.5.1. Thanks, Steve On Tue, Apr 14, 2015 at 10:32 AM, Steven Dalton sdalt...@gmail.com wrote: Hello Jose, I'm hacking on version to integrate 0.5.0 changes and verify CUDA 7 support. I can make it available or send a pull request later this week to start experimenting if anyone is interested. Steve On Tue, Apr 14, 2015 at 10:09 AM, Jose E. Roman jro...@dsic.upv.es wrote: Has anyone updated to CUDA 7? With clanguage=c++ now I get lots of warnings with CUSP v0.4.0. These presumably will go away when updating to CUSP v0.5.0, but it turns out that PETSc build is broken with CUSP v0.5.0 (a header file was moved, and some other issues). Jose
[petsc-dev] Custom reductions
I understood from Jed that MPIU_MIN and friends are for floating point, but here https://bitbucket.org/petsc/petsc/src/da407576a5bf29881cba0f2df6c198aa8caa98f0/src/sys/logging/plog.c?at=master#cl-1346 we use MPI_MIN. Is this wrong? 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
[petsc-dev] PETSc release
We should be planning to do a PETSc release around June 1. Barry
Re: [petsc-dev] SNESCOMPOSITE with a VI underneath
Dear Barry et al, Thanks for that. I've started a pull request for supporting VIs in SNESCOMPOSITE: https://bitbucket.org/petsc/petsc/pull-request/306/make-snescomposite-support-vis/diff This is mainly to start the discussion. In particular, (a) Do you want me to add a check to every SNESSolve_* that doesn't support bounds that no bounds are present? (b) Is there a writeup of what additiveoptimal actually does? I looked in the manual and in the SIAM Review paper and couldn't see a description anywhere. I think the coefficients in the least-squares problem need to be modified in light of the VI, but I'm not sure how. Cheerio, Patrick
Re: [petsc-dev] Custom reductions
On Apr 21, 2015, at 11:25 AM, Håkon Strandenes haa...@hakostra.net wrote: The MPI_MIN, MPI_MAX and MPI_SUM only indicate that we want to have the smallest or largest value, or in case of MPI_SUM, the sum of all values participating in the reduction. It has nothing to do with floting point or integer types as such, they work with both. However as Jed notes MPI_MIN, MPI_MAX and MPI_SUM do not work with __float128, hence to have PETSc code that works for --with-precision=__float128 one must use MPIU_MIN, MPIU_MAX, and MPIU_SUM for PetscReal and PetscScalar (In addition there is some boolean operations like MPI_LAND, MPI_LOR, MPI_LXOR, MPI_BAND, MPI_BOR that work with boolean types, and some operations like MPI_SUM and MPI_PROD can also be used with complex types, but I don't know if PETSc use this at all.) Håkon On 21. april 2015 18:11, Matthew Knepley wrote: I understood from Jed that MPIU_MIN and friends are for floating point, but here https://bitbucket.org/petsc/petsc/src/da407576a5bf29881cba0f2df6c198aa8caa98f0/src/sys/logging/plog.c?at=master#cl-1346 we use MPI_MIN. Is this wrong? 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
Re: [petsc-dev] man page for VecChop
Thanks, fixed in master On Apr 15, 2015, at 11:19 AM, Ed Bueler elbue...@alaska.edu wrote: Dear Petsc -- That man page should say Set all values in the vector WITH ABSOLUTE VALUE less than the tolerance to zero instead of Set all values in the vector less than the tolerance to zero I was very confused til I looked at the source code! Of course, it would be nice to have a true VecChop() *and* a VecAbsChop(), but that would mean a loss of backward-compatibility ... wouldn't want that ... Also, shouldn't VecChop() be implemented in src/vec/vec/interface/rvector.c instead of orphaned in src/vec/vec/utils/vecio.c ? Thanks! Ed -- Ed Bueler Dept of Math and Stat and Geophysical Institute University of Alaska Fairbanks Fairbanks, AK 99775-6660 301C Chapman and 410D Elvey 907 474-7693 and 907 474-7199 (fax 907 474-5394)
Re: [petsc-dev] Custom reductions
The MPI_MIN, MPI_MAX and MPI_SUM only indicate that we want to have the smallest or largest value, or in case of MPI_SUM, the sum of all values participating in the reduction. It has nothing to do with floting point or integer types as such, they work with both. (In addition there is some boolean operations like MPI_LAND, MPI_LOR, MPI_LXOR, MPI_BAND, MPI_BOR that work with boolean types, and some operations like MPI_SUM and MPI_PROD can also be used with complex types, but I don't know if PETSc use this at all.) Håkon On 21. april 2015 18:11, Matthew Knepley wrote: I understood from Jed that MPIU_MIN and friends are for floating point, but here https://bitbucket.org/petsc/petsc/src/da407576a5bf29881cba0f2df6c198aa8caa98f0/src/sys/logging/plog.c?at=master#cl-1346 we use MPI_MIN. Is this wrong? 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
Re: [petsc-dev] Custom reductions
Matthew Knepley knep...@gmail.com writes: I understood from Jed that MPIU_MIN and friends are for floating point, but here https://bitbucket.org/petsc/petsc/src/da407576a5bf29881cba0f2df6c198aa8caa98f0/src/sys/logging/plog.c?at=master#cl-1346 we use MPI_MIN. Is this wrong? PetscLogDouble is always a basic MPI type; never something cool like __float128. signature.asc Description: PGP signature
