When I was having this issue, I was using Homebrew-based PETSc. After
switching to my using my own build, I no longer have the issues described
above.
Thanks again,
Austin
On Tue, Apr 4, 2017 at 1:30 PM, Gaetan Kenway wrote:
> There shouldn't be any additional issue with the
There shouldn't be any additional issue with the petsc4py wrapper. We do
this all the time. In fact, it's generally best to use the petsc4py to do
the initialization of petsc at the very top of your highest level python
script. You'll need to do this anyway if you want to use command line
Hello all,
Another question in a fairly long line of questions from me. Thank you to
this community for all the help I've gotten.
I have a Fortran/PETSc-based code that, with the help of f2py and some of
you, I have compiled into a python module (we'll call it pc_fort_mod). So I
can now