Thanks.
For what it is worth in regards to question (1), GNU Fortran (Homebrew
GCC 11.3.0_2) 11.3.0 seems to need .F90 (as opposed to just .F).
-sanjay
On 8/17/23 4:50 PM, Barry Smith wrote:
On Aug 17, 2023, at 7:44 PM, Sanjay Govindjee wrote:
Two questions about the PetscCall( ) etc.
> On Aug 17, 2023, at 7:44 PM, Sanjay Govindjee wrote:
>
> Two questions about the PetscCall( ) etc. functionality in fortran:
>
> (1) To use this functionality, is it required to use a .F90 naming
> convention? or should I be able to use .F?
This likely depends on the compiler.
>
>
Two questions about the PetscCall( ) etc. functionality in fortran:
(1) To use this functionality, is it required to use a .F90 naming
convention? or should I be able to use .F?
(2) Is it permitted to use line continuation within these calls? For
example something like
It appears there are currently no Python bindings for
> https://petsc.org/main/manualpages/Mat/MatSetPreallocationCOOLocal/
> https://petsc.org/main/manualpages/Mat/MatSetValuesCOO/
they should be fairly easy to add in a merge request.
Barry
> On Aug 17, 2023, at 5:57 PM, Matthew
On Fri, Aug 18, 2023 at 12:49 AM Erik Kneller via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Hi All,
>
> I need to fill non-zero values of a Petsc matrix via petsc4py for the
> domain defined by A.getOwnershipRange() using three Numpy arrays: (1)
> array containing row indices of non-zero
Hi All,
I need to fill non-zero values of a Petsc matrix via petsc4py for the domain
defined by A.getOwnershipRange() using three Numpy arrays: (1) array containing
row indices of non-zero value, (2) array containing column indices of non-zero
values and (3) array containing the non-zero matrix
