We should be planning to do a PETSc release around June 1.
Barry
Thanks, fixed in master
> On Apr 15, 2015, at 11:19 AM, Ed Bueler 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 zer
> On Apr 21, 2015, at 11:25 AM, Håkon Strandenes 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
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 bool
Matthew Knepley 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
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 gran
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 SNESSolv
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 w
