Re: [petsc-users] Petsc Section in DMPlex

Hi Thank you for your help with this barrage of questions. The AddField, while nice for visualization, isn't the critical path for my development. I've gotten the Filtered DM with its corresponding state vector sorted out. Now I'm moving on to the mesh distribution. From your 2nd email in this

[petsc-users] Modifying Entries Tied to Specific Points in Finite Element Stiffness Matrix using DMPlex

Hello! I'm trying to adapt a serial Finite Element code using PETSc. In this code it reads in special stiffness terms between the boundary DoFs from an input file, and add them to corresponding locations in the global Jacobian matrix. I currently use a DM Plex object to store the mesh information.

Re: [petsc-users] Fortran Interface NULL object / Casting

You would use PETSC_NULL_DMLABEL but Matt needs to customize the PETSc Fortran stub for DMAddField() for you to handle accepting the NULL from PETSc. Barry > On Dec 8, 2022, at 1:05 PM, Nicholas Arnold-Medabalimi > wrote: > > Hi Petsc Users > > I am trying to use DMAddField in a

Re: [petsc-users] prevent linking to multithreaded BLAS?

Barry Smith writes: >> We could test at runtime whether child threads exist/are created when >> calling BLAS and deliver a warning. > > How does one test for this? Some standard Unix API for checking this? I'm not sure, the ids of child threads are in /proc/$pid/task/ and (when opened by a

[petsc-users] Fortran Interface NULL object / Casting

Hi Petsc Users I am trying to use DMAddField in a Fortran code. I had some questions on casting/passing NULL. I follow how to pass NULL for standard types (INT, CHAR, etc). Is there a method/best practice for passing NULL for Petsc type arguments? (In this case DMAddLabel I'd want to pass NULL

Re: [petsc-users] Petsc Section in DMPlex

I think I've figured out the issue. In previous efforts, I used DMAddField, which I think was key for the output to work properly. On Thu, Dec 8, 2022 at 10:48 AM Nicholas Arnold-Medabalimi < narno...@umich.edu> wrote: > Hi Matt > > Thanks. Found the issue just messed up the Fortran to C

Re: [petsc-users] prevent linking to multithreaded BLAS?

> On Dec 7, 2022, at 11:56 PM, Jed Brown wrote: > > It isn't always wrong to link threaded BLAS. For example, a user might need > to call threaded BLAS on the side (but the application can only link one) or > a sparse direct solver might want threading for the supernode. Indeed, the user

Re: [petsc-users] Petsc Section in DMPlex

Hi Matt Thanks. Found the issue just messed up the Fortran to C indexing. Another question. I have been using the Petsc VTK output to view things. In some previous efforts, I used the PetscFVM object to set up my section data. When I output vectors using that method in ParaView, I could view the

Re: [petsc-users] [EXTERNAL] Re: Kokkos backend for Mat and Vec diverging when running on CUDA device.

Great! Thank you! Philip Fackler Research Software Engineer, Application Engineering Group Advanced Computing Systems Research Section Computer Science and Mathematics Division Oak Ridge National Laboratory From: Junchao Zhang Sent: Wednesday, December 7, 2022

Re: [petsc-users] Petsc Section in DMPlex

On Thu, Dec 8, 2022 at 3:04 AM Nicholas Arnold-Medabalimi < narno...@umich.edu> wrote: > Hi Matt > > I think I've gotten it just about there. I'm just having an issue with the > VecISCopy. I have an IS built that matches size correctly to map from the > full state to the filtered state. The core

Re: [petsc-users] Petsc Section in DMPlex

Hi Matt I think I've gotten it just about there. I'm just having an issue with the VecISCopy. I have an IS built that matches size correctly to map from the full state to the filtered state. The core issue I think, is should the expanded IS the ownership range of the vector subtracted out.