"Balay, Satish via petsc-dev" writes:
> Hm for CXXFLAGS - I think you have to do:
>
> self.pushLanguage('Cxx')
> CXXFLAGS = self.getCompilerFlags()
> self.popLanguage()
These days, it's better to write this using the context manager:
with self.Language('Cxx'):
CXXFLAGS =
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
https://bitbucket.org/petsc/petsc/commits/ea2d7708fa6
we could have files that look like the following, and thus were easy to
navigate in Paraview and
module load mkl
use petsc options:
--with-blas-lapack-dir=${MKLROOT}
--with-cc=${MPICH_HOME}/mpicc --with-cxx=${MPICH_HOME}/mpicxx
--with-fc=${MPICH_HOME}/mpif90
Sorry about the extraneous crap. I was cutting/pasting from my own much longer
script.
V.
On Mar 27, 2019, at 8:47 AM, Mark Adams
Myriam,
- PETSc 3.6.4 (reference)
- PETSc 3.10.4 without specific options
- PETSc 3.10.4 with the three scalability options you mentionned
What are the 'three scalability options' here?
What is "MaxMemRSS", the max memory used by a single core? How many cores do
you start with?
Do you have
https://bitbucket.org/petsc/petsc/pull-requests/1475/
Satish
On Wed, 27 Mar 2019, Lisandro Dalcin via petsc-dev wrote:
> DMLabel is now a PetscObject, but the struct name does not match the usual
> conventions, it should be _p_DMLabel, but instead:
>
>
So is this the instructions that I should give him? This grad student is a
quick study but he has not computing background. So we don't care what we
use, we just want to work (easily).
Thanks
Do not use "--download-fblaslapack=1". Set it to 0. Same for
"--download-mpich=1".
Now do:
> module
On Mar 27, 2019, at 7:29 AM, Mark Adams
mailto:mfad...@lbl.gov>> wrote:
How should he configure to this? remove "--download-fblaslapack=1" and add
1. If using gcc
module load mkl
with either compiler:
export BLAS_LAPACK_LOAD=--with-blas-lapack-dir=${MKLROOT}
2. We define MPICH_HOME
On Wed, Mar 27, 2019 at 12:06 AM Victor Eijkhout
wrote:
>
>
> On Mar 26, 2019, at 6:25 PM, Mark Adams via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
> /home1/04906/bonnheim/olympus-keaveny/Olympus/olympus.petsc-3.9.3.skx-cxx-O
> on a skx-cxx-O named c478-062.stampede2.tacc.utexas.edu with
DMLabel is now a PetscObject, but the struct name does not match the usual
conventions, it should be _p_DMLabel, but instead:
include/petsc/private/dmlabelimpl.h:struct _n_DMLabel {
include/petscdmlabel.h:typedef struct _n_DMLabel *DMLabel;
--
Lisandro Dalcin
Research Scientist
