Mark,
MatMultTransposeAdd_SeqAIJCUSPARSE checks if the matrix is in compressed
row storage, MatMultTranspose_SeqAIJCUSPARSE does not. Probably is this the
issue? The CUSPARSE classes are kind of messy
Il giorno sab 28 set 2019 alle ore 07:55 Karl Rupp via petsc-dev <
petsc-dev@mcs.anl.gov> ha
mean first as a folder, than in the filename itself
Il giorno gio 26 set 2019 alle ore 09:38 Matthew Knepley
ha scritto:
> On Wed, Sep 25, 2019 at 8:52 PM Stefano Zampini via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> If we specify a PETSC_ARCH with a trailing slash
I'm receiving notifications for all activities originating from Merge
Requests since I'm listed as developer of PETSc.
The level of notification set in my GITLAB profile is "participate". Should
I push this down to "mentions"? Are "developers" always participating in
Merge Request discussions?
--
3.10 works fine
Il giorno lun 22 lug 2019 alle ore 15:28 Stefano Zampini <
stefano.zamp...@gmail.com> ha scritto:
> I just checked, and this is a bug also in maint.
>
> Il giorno lun 22 lug 2019 alle ore 13:23 Stefano Zampini via petsc-dev <
> petsc-dev@mcs.anl.gov>
I think snes reset should call ksp destroy. I don't see the case for which
this can lead to troubles
Il Gio 30 Mag 2019, 15:43 Matthew Knepley via petsc-dev <
petsc-dev@mcs.anl.gov> ha scritto:
> On Thu, May 30, 2019 at 6:08 AM Pierre Jolivet via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> H
> Eric
>
>
> Le 19-04-19 à 19:10, Stefano Zampini via petsc-dev a écrit :
>
> Can you please send a MWE to reproduce the errors so that I can provide a
> fix?
>
> Il Ven 19 Apr 2019, 17:00 Matthew Knepley via petsc-dev <
> petsc-dev@mcs.anl.gov> ha scri
Jed,
thanks. It fixed my issue too.
Il giorno mer 20 feb 2019 alle ore 09:33 Lisandro Dalcin
ha scritto:
> I tested your fix (on top of master) with my original PetIGA reproducer,
> and the issue seems to be fixed.
>
> On Wed, 20 Feb 2019 at 08:32, Jed Brown wrote:
>
>> Yuck, bad bug. I push
o make sure if the user
>>> requested a particular matrix type then it won't return a different type
>>> that is unexpected for the user (the AIJ checks are just to handle MATAIJ
>>> vs MATSEQAIJ, MATMPIAIJ).
>>>
>>> Barry
>
> On Feb 8, 2019, at 2:37 PM, Matthew Knepley wrote:
>
> On Fri, Feb 8, 2019 at 6:30 AM Stefano Zampini via petsc-dev
> mailto:petsc-dev@mcs.anl.gov>> wrote:
> I don’t understand the need of these checks (tacky and incomplete…, as per
> the comment)
>
> htt
Pierre,
The details of the inner solvers for PCFIELDSPLIT are not known if you don’t
call PCSetUp, so the cascade approach should be preferred.
After PCSetUp, you can access the inner solves, see e.g.
https://bitbucket.org/petsc/petsc/src/4ddd364d454d7bce974e92e0b5bd4f4516dbff02/src/ksp/pc/i
If I compile PETSc with complex support, all of the TAO methods are not
registered.
Fare enough? not really, I can imagine at least three valid reasons to use
those
1) I want to check that my code works for complex builds, even if I have
pure real function evaluations. I may need complex support i
Make reconfigure is equivalent to rerun the configure script
Il giorno Sab 1 Dic 2018, 18:09 Hapla Vaclav ha
scritto:
> ... but this is apparently not caused by your merge.
>
> Is it just normal behavior of make reconfigure?
> I didn't know about this, I always call the reconfigure script direct
12 matches
Mail list logo
