> On 6 Apr 2021, at 5:03 PM, Satish Balay <[email protected]> wrote: > > > https://www.mcs.anl.gov/petsc/petsc-current/ is from petsc-3.15.0 - > and is normally gets updated with the next patch release - i.e > petsc-3.15.1. [ok - I'll update now with current release snapshot]
Ah, of course, I don’t know why I checked there instead of the dev version, my bad. Well, thank you for updating the 3.15.0 pages as well I guess. Thanks, Pierre > Also dev pages should get updated daily [there is a bug here > that I should fix] > > With the latest snapshots - both the pages appear to list MatGetRow_MPIDense > > https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MatGetRow.html > https://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/Mat/MatGetRow.html > > Satish > > On Tue, 6 Apr 2021, Pierre Jolivet wrote: > >> Thanks for the recent MR. >> This sadly only partially addresses the issue. >> https://www.mcs.anl.gov/petsc/petsc-3.14.6/docs/manualpages/Mat/MatGetRow.html >> >> <https://www.mcs.anl.gov/petsc/petsc-3.14.6/docs/manualpages/Mat/MatGetRow.html> >> correctly has MatGetRow_MPIDense while >> https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MatGetRow.html >> >> <https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MatGetRow.html> >> hasn’t. >> >> Thanks, >> Pierre >> >>> On 3 Apr 2021, at 1:24 PM, Patrick Sanan <[email protected]> wrote: >>> >>> I think this was likely a non-portable regex that was being used to match >>> the function signatures, >>> causing it to miss anything with an internal "s" in the function name. >>> Here's a quick fix for the release branch: >>> >>> https://gitlab.com/petsc/petsc/-/merge_requests/3813 >>> <https://gitlab.com/petsc/petsc/-/merge_requests/3813> >>> >>> (This sort of thing will become easier to work with, soon, as we'll have an >>> automated doc build which can be examined for each MR.) >>> >>> P.S. nice email address! >>> >>>> Am 03.04.2021 um 11:19 schrieb Patrick Sanan <[email protected] >>>> <mailto:[email protected]>>: >>>> >>>> That isn't expected - thanks for pointing this out! I can reproduce >>>> locally so will take a look. >>>> >>>>> Am 03.04.2021 um 11:10 schrieb Pierre Jolivet <[email protected] >>>>> <mailto:[email protected]>>: >>>>> >>>>> Hello, >>>>> https://www.mcs.anl.gov/petsc/petsc-3.14/docs/manualpages/Mat/MatTranspose.html >>>>> >>>>> <https://www.mcs.anl.gov/petsc/petsc-3.14/docs/manualpages/Mat/MatTranspose.html> >>>>> lists available implementations while >>>>> https://www.mcs.anl.gov/petsc/petsc-3.15/docs/manualpages/Mat/MatTranspose.html >>>>> >>>>> <https://www.mcs.anl.gov/petsc/petsc-3.15/docs/manualpages/Mat/MatTranspose.html> >>>>> doesn’t. >>>>> Is this expected? >>>>> >>>>> Thanks, >>>>> Pierre >>>> >>> >> >>
