Re: [petsc-users] MatNest error with null matrix blocks

2025-07-04 Thread Randall Mackie
Thanks Barry We were confused because the online manual says: PETSc objects are always automatically initialized when declared so you do not need to (and should not) do type(tXXX) x = PETSC_NULL_XXX XXX x = PETSC_NULL_XXX Randy > On Jul 4, 2025, at 6:56 PM, Barry Smith wrote: > > >You

Re: [petsc-users] MatNest error with null matrix blocks

2025-07-04 Thread Barry Smith
You need to pass PETSC_NULL_MAT in those locations, you cannot just pass a Mat that has never been created (that is a different kind of NULL matrix :-). I have added clearer error checking in https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/8526__;!!G_uCfscf7eWS!c7m

Re: [petsc-users] Suggestion: Support optional extras for Firedrake (or other python package) when installed via PETSc

2025-07-04 Thread Barry Smith
Yes, what specific ones are portable and fairly commonly needed? I would like a default installation to include everything a user would need. So let me know the list and I will add them. Barry > On Jul 3, 2025, at 8:07 PM, Zongze Yang wrote: > > Hi all, > > As PETSc can install Firedra

[petsc-users] MatNest error with null matrix blocks

2025-07-04 Thread Randall Mackie
In the process of upgrading our code to version 3.23, we have run into another issue, this time with nest matrices.In previous versions (well to at least 3.21) it was perfectly fine to pass in null matrix blocks to create a nest matrix. There are situations where we have, for example, only diagonal