We are pleased to announce the release of PETSc version 3.11 at
http://www.mcs.anl.gov/petsc
The major changes and updates can be found at
http://www.mcs.anl.gov/petsc/documentation/changes/311.html
We recommend upgrading to PETSc 3.11 soon. As always, please report problems to
ref: https://lists.mcs.anl.gov/pipermail/petsc-dev/2018-April/022748.html
I've deleted all development branches that are already merged into
maint (v3.11) from https://bitbucket.org/petsc/petsc
However if you wish to remove these branches from your clone - it has
to be done manually (in each
All (next users),
ref: https://lists.mcs.anl.gov/pipermail/petsc-dev/2017-September/021361.html
I've recreated 'next' branch - and have a backup for current 'next' at
'origin/next-mar-2019'.
[Note: this backup is from Mar 21. Subsequently next was used as a rewrite-able
branch]
So if you
This issue is fixed by Matt and the PR is already merged in.
https://bitbucket.org/petsc/petsc/pull-requests/1453/sys-extension-to-the-xml-logging-system/commits
Satish
On Fri, 29 Mar 2019, Bas van 't Hof via petsc-checkbuilds wrote:
> Dear PETSc development team,
>
> My apologies for
Dear PETSc development team,
My apologies for not noticing this mail before. I think the
problem only occured with the option --with-mpi=0.
Attached, please find the original patch and an additional patch that
should remedy the problem.
Regards,
Bas van 't Hof
On 20-03-19 13:28, PETSc
Hi all,
I would really appreciate it if all PETSc developers who are planning
on attending the user meeting would
- submit their proposed talks/posters soon on easychair
https://easychair.org/cfp/petsc19
- register on eventbrite
