I posted some information at the issue.
IMHO it is likely a bug in one or more of hypre's smoothers that use OpenMP.
We have never tested them before (and likely hypre has not tested all the
combinations) and so would not have seen the bug. Hopefully they can just fix
it.
Barry
On Mon, 15 Mar 2021, Lisandro Dalcin wrote:
> On Mon, 15 Mar 2021 at 18:26, Satish Balay wrote:
>
> >
> > But epydoc can be installed with python3.
>
>
> Maybe. Have you tried to actually run it after installation? :-)
I have not (yet).
>
>
> > So this is more of petsc4py code that uses
On Mon, 15 Mar 2021 at 18:26, Satish Balay wrote:
>
> But epydoc can be installed with python3.
Maybe. Have you tried to actually run it after installation? :-)
> So this is more of petsc4py code that uses epydoc - than epydoc code?
>
>
I did not understand your question. Epidoc is just an
I tried earlier but I don't know what I'm doing, so was hoping Lisandro would
help. If it's worth anything this is what I did:
# set PETSC_DIR and PETSC_ARCH for minimal docs build as used for Sphinx
(basically just c2html and sowing).
# had to remember to actually build the library or you get
Ok - I can look at updating builddist script to build PETSc and
PETSc4py [with python2 - and prerequistes installed] before attempting
to build python docs [and petsc4py tarball]
Satish
On Mon, 15 Mar 2021, Barry Smith wrote:
>
> Satish,
>
> I think some of the python documentation
Well someone tried importing epydoc for python3 and it did not generate an
error, did they try generating the petsc4py docs with it. That would tell you
if it works?
Yes, we do want to be able to build all the PETSc docs together in a
portable way.
> On Mar 15, 2021, at 10:56 AM,
Satish,
I think some of the python documentation tools used, epydoc, require that
the python package it is documenting exists and is run-able since it probably
uses the self-documenting features of Python. This makes perfect sense for
Python. A python package cannot provide help
> Am 15.03.2021 um 16:26 schrieb Satish Balay :
>
> On Mon, 15 Mar 2021, Lisandro Dalcin wrote:
>
>> On Mon, 15 Mar 2021 at 07:06, Satish Balay wrote:
>>
>>> Lisandro,
>>>
>>> For the upcoming release its best to update lib/petsc/bin/maint/builddist
>>> to also build petsc4py tarball in
On Mon, 15 Mar 2021, Satish Balay wrote:
>
> > and run "make sdist".
>
> Ah - ok. Will check this to see if I can generate the tarball in sync
> with petsc tarball. What source files need updating for
> release/version info?
Is it required to build PETSc library - to build petsc4py tarball?
Reported timeout bugs to SuperLU_dist too:
https://github.com/xiaoyeli/superlu_dist/issues/69
Eric
On 2021-03-14 2:18 p.m., Eric Chamberland wrote:
Done:
https://github.com/hypre-space/hypre/issues/303
Maybe I will need some help about PETSc to answer their questions...
Eric
On
On Mon, 15 Mar 2021, Lisandro Dalcin wrote:
> On Mon, 15 Mar 2021 at 07:06, Satish Balay wrote:
>
> > Lisandro,
> >
> > For the upcoming release its best to update lib/petsc/bin/maint/builddist
> > to also build petsc4py tarball in sync with petsc tarball.
> >
> > What is the current process to
On Mon, 15 Mar 2021 at 07:06, Satish Balay wrote:
> Lisandro,
>
> For the upcoming release its best to update lib/petsc/bin/maint/builddist
> to also build petsc4py tarball in sync with petsc tarball.
>
> What is the current process to generate petsc4py tarball?
>
>
>
> BTW: I stumbled into a
12 matches
Mail list logo
