All,
Th current master is in a good shape for a release. I'll look at
spinning the release after 'master' test today evening.
Please do not push any code changes to master [but please do check for
any needed doc fixes]
Thanks,
Satish
On Tue, 26 Mar 2019, Balay, Satish via petsc-maint wrote:
I'd advocate flattening everything as a scalar field. Why?
1) the xml vtk formats for vector only work if ncomponents = 3, so for a 2d
field you have to insert a dummy set of zero values for the z component
2) its simple to build vector fields which paraview can render if the
scalar fields are
On Thu, 28 Mar 2019 at 15:42, Jed Brown via petsc-dev
wrote:
> Matthew Knepley writes:
>
> > On Wed, Mar 27, 2019 at 10:56 PM Jed Brown via petsc-dev <
> > petsc-dev@mcs.anl.gov> wrote:
> >
> >> Prior to this PR, which was merged for 3.10
> >>
> >>
> >>
>
On Mar 27, 2019, at 8:30 AM, Matthew Knepley
mailto:knep...@gmail.com>> wrote:
I think Satish now prefers
--with-cc=${MPICH_HOME}/mpicc --with-cxx=${MPICH_HOME}/mpicxx
--with-fc=${MPICH_HOME}/mpif90
That still requires with-mpi:
Matthew Knepley writes:
> On Wed, Mar 27, 2019 at 10:56 PM Jed Brown via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> Prior to this PR, which was merged for 3.10
>>
>>
>> https://bitbucket.org/petsc/petsc/pull-requests/1029/dmda-vtk-viewing-output-multiple-dof/diff
>>
