Re: [petsc-dev] Should v->valid_GPU_array be a bitmask?

2019-10-01 Thread Karl Rupp via petsc-dev
Hi Junchao, I recall that Jed already suggested to make this a bitmask ~7 years ago ;-) On the other hand: If we touch valid_GPU_array, then we should also use a better name or refactor completely. Code like (V->valid_GPU_array & PETSC_OFFLOAD_GPU) simply isn't intuitive (nor does it make s

[petsc-dev] Should v->valid_GPU_array be a bitmask?

2019-10-01 Thread Zhang, Junchao via petsc-dev
Stafano recently modified the following code, PetscErrorCode VecCreate_SeqCUDA(Vec V) { PetscErrorCode ierr; PetscFunctionBegin; ierr = PetscLayoutSetUp(V->map);CHKERRQ(ierr); ierr = VecCUDAAllocateCheck(V);CHKERRQ(ierr); ierr = VecCreate_SeqCUDA_Private(V,((Vec_CUDA*)V->spptr)->GPUarr

Re: [petsc-dev] Better error message for missing components

2019-10-01 Thread Nathan Collier via petsc-dev
Personally, I would see the educational aspect as helpful. Most of what I learn about PETSc comes from '-help | grep XXX'. Nate On Tue, Oct 1, 2019 at 11:27 AM Jed Brown via petsc-dev < petsc-dev@mcs.anl.gov> wrote: > Matthew Knepley via petsc-dev writes: > > > Can anyone think of a way to get

[petsc-dev] Best Way to Assign Cell Number to VTK Plot in DMPlex

2019-10-01 Thread Faibussowitsch, Jacob via petsc-dev
Hello All, I am plotting an output value from a vecview, and want to show in a separate plot which cells correspond to which values in the vec. I plan to do this by making a field on the cells whose value is the global number of that cell. I have 2 issues with this: 1. How do I guarantee that

Re: [petsc-dev] Better error message for missing components

2019-10-01 Thread Jed Brown via petsc-dev
Matthew Knepley via petsc-dev writes: > Can anyone think of a way to get a better message from We could register all types and implement PetscViewerCreate_HDF5() to raise an error when not configured with HDF5. The "downside" is that -help would show implementations that aren't supported by the

Re: [petsc-dev] Makefile with latest PETSc

2019-10-01 Thread Tabrez Ali via petsc-dev
Thank you Satish. It works now. Tabrez On Tue, Oct 1, 2019 at 9:39 AM Balay, Satish wrote: > https://gitlab.com/petsc/petsc/issues/391 > > Can you try the branch balay/addback_F_o_compile_target/maint > [yet to test] > > Satish > > On Tue, 1 Oct 2019, Tabrez Ali via petsc-dev wrote: > > > Hello

Re: [petsc-dev] Makefile with latest PETSc

2019-10-01 Thread Balay, Satish via petsc-dev
https://gitlab.com/petsc/petsc/issues/391 Can you try the branch balay/addback_F_o_compile_target/maint [yet to test] Satish On Tue, 1 Oct 2019, Tabrez Ali via petsc-dev wrote: > Hello > > I am trying to compile a simple Fortran program and it works fine with > PETSc 3.10 but fails with the l

[petsc-dev] Fwd: Makefile with latest PETSc

2019-10-01 Thread Tabrez Ali via petsc-dev
Forgot to reply to all. --- Matt, No, that doesn't work either. Tabrez On Tue, Oct 1, 2019 at 6:54 AM Matthew Knepley wrote: > On Tue, Oct 1, 2019 at 6:38 AM Tabrez Ali via petsc-dev < > petsc-dev@mcs.anl.gov> wrote: > >> Hello >> >> I am trying to compile a simple Fortran program and it wor

[petsc-dev] Makefile with latest PETSc

2019-10-01 Thread Tabrez Ali via petsc-dev
Hello I am trying to compile a simple Fortran program and it works fine with PETSc 3.10 but fails with the latest version, e.g., see below: $ make clean; make exe PETSC_DIR=/opt/petsc-3.10.5_clang_uni flang -c -fPIC -Wall -Wno-unused-variable -g -O3 -I/opt/petsc-3.10.5_clang_uni/include -I/opt/p