Re: [petsc-dev] fixing bugs in resolution of TSEvent's

Dear Ilya Thanks for your willing to contribute back to PETSc. Please submit a PR from the main branch. We do not allow API changes from minor patch versions. Thanks Stefano On Mon, Jul 17, 2023, 16:55 Ilya Fursov wrote: > Dear to whom is may concern, > > A while ago I tried to use TS events

Re: [petsc-dev] petsc4py doc problem

I have added a check to 79 characters lines in petsc4py docstrings. Just split the lines that are longer than that. On Wed, Jun 28, 2023, 04:07 Matthew Knepley wrote: > I do not understand those docs at all: > > Using PETSC inventory from >

Re: [petsc-dev] Swarm tag error

If ranks are uniquely listed in neighbour_procs, then you only need 1 fresh tag per communication round from PetscCommGetNewTag > On Nov 23, 2022, at 9:08 PM, Dave May wrote: > > > > On Wed, 23 Nov 2022 at 08:57, Junchao Zhang > wrote: > From my reading, the

Re: [petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen

PetscOptionsViewError(); > PetscErrorPrintfHilight(); > (*PetscErrorPrintf)("End of Error Message ---send > entire error message to petsc-ma...@mcs.anl.gov--\n"); > PetscErrorPrintfNormal(); > } > } > > Best regards, > >

[petsc-dev] Reached the main program with an out-of-range error code 1. This should never happen

What does the message imply? That PETSc error handler is misbehaving? or that the user code is wrong? I don't understand. This is the latest release with a faulty code that I use as an example for using valgrind and gdb. [0]PETSC ERROR: Memory corruption: https://petsc.org/release/faq/#valgrind

[petsc-dev] Python garbage collector broken?

Just reconfigured today with release and got this [szampini@localhost poisson]$ cat test.py from petsc4py import PETSc A = PETSc.Mat().create(comm=PETSc.COMM_WORLD) [szampini@localhost poisson]$ PETSC_ARCH=arch-test mpiexec -n 2 python test.py [0]PETSC ERROR: - Error Message

Re: [petsc-dev] Not a single person has approved the MR for allowing the use of clang-format on the repository

Just did it. I'm on vacation these days On Sat, Aug 6, 2022, 16:31 Barry Smith wrote: > > Note that this MR does not clang-format the repository nor require that > future MR satisfy the clang-format (yet). It merely fixes up everything > needed so that we can clang-format the repository. >

Re: [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6

Is your petsc configured with strumpack? I seem to recall some name clashing with MUMPS ordering routines. We found a similar issue with spack and mfem On Thu, Jul 14, 2022, 04:11 Barry Smith wrote: > > PETSc main > > $ ./ex69 > dyld[95838]: symbol not found in flat namespace >

Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs

The logic is wrong. It should check for MATSEQAIJCUSPARSE. On Thu, Jun 23, 2022, 21:36 Mark Adams wrote: > > > On Thu, Jun 23, 2022 at 3:02 PM Barry Smith wrote: > >> >> It looks like the current code copies the nonzero values to the CPU >> from the MPI matrix (with the calls >>

Re: [petsc-dev] MatMPIAIJGetLocalMat problem with GPUs

How do you use amgx->localA after it is created? On Thu, Jun 23, 2022, 20:25 Mark Adams wrote: > We have a bug in the AMGx test snes_tests-ex13_amgx in parallel. > Matt Martineau found that MatMPIAIJGetLocalMat worked in the first pass in > the code below, where the local matrix is created

Re: [petsc-dev] C++ and hypre long long int vs PETSc int64_t for 64 bit integer builds

This is what we currently have in PETSc, we check for sizeof and cast Il giorno mer 13 apr 2022 alle ore 17:13 Jed Brown ha scritto: > C/C++ integer hierarchy was a mistake, with the language-specified types > overlapping and the size-specific (int64_t) being typedefs. So long is > "different"

[petsc-dev] Current status of using streams within PETSc

Jacob what is the current status of the async support in PETSc? Can you summarize here? Is there any documentation available? Thanks -- Stefano

Re: [petsc-dev] [petsc-users] MatPreallocatorPreallocate segfault with PETSC 3.16

Il giorno mar 1 feb 2022 alle ore 18:34 Jed Brown ha scritto: > Patrick Sanan writes: > > > Am Di., 1. Feb. 2022 um 16:20 Uhr schrieb Jed Brown : > > > >> Patrick Sanan writes: > >> > >> > Sorry about the delay on this. I can reproduce. > >> > > >> > This regression appears to be a result of

Re: [petsc-dev] ftn-auto in $PETSC_DIR/include ?

This is a bug and it should be fixed Il giorno gio 27 gen 2022 alle ore 15:22 Jose E. Roman ha scritto: > That is because PetscLogFlops() has an auto fortran stub. This is a > PETSC_STATIC_INLINE function in include/petsclog.h > > Jose > > > > El 27 ene 2022, a la

[petsc-dev] ftn-auto in $PETSC_DIR/include ?

Just noticed this. Is it normal to have a ftn-auto directory generated by bfort in $PETSC_DIR/include? (ecrcml-user) [szampini@localhost petsc]$ ls include/ftn-auto makefile petscloghf.c -- Stefano

Re: [petsc-dev] HIP / hypre

I did the work last summer. It's already available in 3.16 Il Mer 10 Nov 2021, 20:44 Mark Adams ha scritto: > Hypre has released HIP support and Ulrike says: > > I just want to let you know that hypre can now be used through PETSc with > GPUs (both Nvidia and AMD). > > I am guessing we have

[petsc-dev] Running with CUDA and CUDA_VISIBLE_DEVICES=-1

Just found out that if we configure with cuda and then want to run on CPU only using CUDA_VISIBLE_DEVICES=-1 PETSc errors out. Is this intended behavior? I supposed it should work This is with main (ecrcml-cuda) zampins@qaysar:~/miniforge/Devel/petsc$ make check Running check examples to verify

Re: [petsc-dev] AMGx integration

Il giorno mar 19 ott 2021 alle ore 15:17 Mark Adams ha scritto: > We (Matt Martineau and I) are ready to work on the AMGx integration and I > want to start by getting the AMGx download working. > > I'm looking for advice on how to proceed. > > Should I look at a simple example and clone it? >

[petsc-dev] Big in MF hessian and BNK?

Alp I have found this problem, reproducible with release (see below using src/tao/unconstrained/tutorials/minsurf1) I was trying MFFD hessian with bntr. Using assembled hessian is fine (tf-oneapi) [szampini@localhost tutorials]$ ./minsurf1 -tao_smonitor -tao_type bntr -mx 10 -my 8

[petsc-dev] Why clanguage __str1__ appears before the summary?

at the end, configure dumps the summary. The c language used should appear in the PETSc: section of the summary, but it is actually printed before ... regex: Language used to compile PETSc: C PETSc: PETSC_ARCH: arch-wtf -- Stefano

Re: [petsc-dev] libpetsc.so: undefined references

ld/BUILD/petsc-3.16.0/petsc-3.16.0/lib/petsc/bin/win32fe/nvcc...not > found > Unable to find programs ['nvcc'] providing listing of the specific > search path > Warning accessing /usr/local/cuda/bin gives errors: can only > concatenate str (not "builtin_function_or_method&quo

Re: [petsc-dev] libpetsc.so: undefined references

I knew this was coming https://gitlab.com/petsc/petsc/-/issues/997 Il Sab 2 Ott 2021, 15:48 Antonio T. sagitter ha scritto: > Hi all. > > In PETSc-3.16.0, the linker is not working because of these undefined > references (see https://pastebin.com/izGTfmMp): > > /usr/bin/ld:

Re: [petsc-dev] Cannot locate file: share/petsc/datafiles/matrices/small

01 2146435072 ok vec_is_sf_tutorials-ex1_4+sf_window_sync-lock_sf_window_flavor-allocate ok diff-vec_is_sf_tutorials-ex1_4+sf_window_sync-lock_sf_window_flavor-allocate Il giorno mar 14 set 2021 alle ore 07:44 Stefano Zampini < stefano.zamp...@gmail.com> ha scritto: > I'll see if I can re

Re: [petsc-dev] Cannot locate file: share/petsc/datafiles/matrices/small

I'll see if I can reproduce Il Mar 14 Set 2021, 06:58 Junchao Zhang ha scritto: > Hi, Stefano, >Ping you again to see if you want to resolve this problem before > petsc-3.16 > > --Junchao Zhang > > > On Sun, Sep 12, 2021 at 3:06 PM Antonio T. sagitter < > sagit...@fedoraproject.org> wrote:

[petsc-dev] Remove PetscDevice initialization from main before 3.16 is released

Jacob Just got a report about the error below PetscDevice code is still experimental and I believe it should not be active (in any way) in the next release. It can also conflict with the current way we initialize devices. Can we comment out these two extra lines in PetscInitialize in main and

[petsc-dev] Is this a bug in test generation?

Scott This test is specified as testset: suffix: expl nsize: {{1 2}} filter: grep -v "MPI processes" | grep -v " type:" | grep -v "Mat Object" args: -ksp_converged_reason -view_explicit_mat -pc_type none -ksp_type {{cg gmres}} test: args: -mat_type aij

Re: [petsc-dev] Broken snes_tutorials-ex20_2d_p1_gmg_vcycle_cr and CRSetup_Private()

Matt, I’m fine flagging the test as broken for now Actually, this test has always been broken…. As Pierre said, if we make these matrices inherit from MatShell, we get shift and scale for free > On Aug 4, 2021, at 10:13 AM, Pierre Jolivet wrote: > > Hello, > Up until very recently,

Re: [petsc-dev] Kokkos make error on Spock

This is probably kokkos pulling in the dependencies where compiling kokkos source within PETSc. Il Dom 18 Lug 2021, 16:29 Mark Adams ha scritto: > Whoops, this error was just from not telling gfortran to allow long lines. > > Anway, I did find that the when fortran bindings are enabled this OMP

Re: [petsc-dev] [petsc-users] CUDA MatSetValues test

t block at the top of ex5cu.cu > > * I ended up with two declarations of PetscSplitCSRDataStructure > * I added some includes to fix errors like this: > /ccs/home/adams/petsc/include/../src/mat/impls/aij/seq/seqcusparse/cusparsematimpl.h(263): > error: incomplete type is not allowed > * I en

Re: [petsc-dev] Mat test ex238

+1 The help says for timing tests, but it makes no sense to me for them being part of the entire CI We should probably have a dedicated runner for performance regressions (running only performance runs, something like requires: performance) Not sure why the sizes are so large, probably Barry wants

Re: [petsc-dev] Listing failed tests

This was changed recently, I still don’t know why. I also find very convenient to have the list of failing tests printed at the end, instead of having to manually scroll up the output. For now, you can edit gmakefile.test and fix showreport variable showreport = "-s" Which is now set only if

Re: [petsc-dev] Strange issue with testsuite

catching tests are tricker to debug than the normal tests. > > Scott > > On 2021-05-12 16:48, Stefano Zampini did write: > > I'm currently trying to build PETSc on a NEC-SX. Apart from other issues, > > I'm facing the following issue with the testsuite. > > > > [

[petsc-dev] Strange issue with testsuite

I'm currently trying to build PETSc on a NEC-SX. Apart from other issues, I'm facing the following issue with the testsuite. [zampins@stork petsc]$ make test s='sys*ex54*1a*' V=1 Using MAKEFLAGS: -- V=1 s=sys*ex54*1a* arch-debug-uni/tests/sys/tests/runex54_1_options_file-ex54options_1a_wrong.sh

Re: [petsc-dev] -info from just one process?

> I'm not talking about timings, I am talking about seeing where a code dies. > When codes die within the MPI implementation is basically impossible to provide a backtrace from PETSc, but the MPI implementation may offer some verbose messaging. If this happens quite early in the code (and I

Re: [petsc-dev] Compilation errors with kokkos and --with-scalar-type complex

no cuda Il giorno mer 21 apr 2021 alle ore 18:11 Junchao Zhang < junchao.zh...@gmail.com> ha scritto: > > > > On Wed, Apr 21, 2021 at 5:23 AM Stefano Zampini > wrote: > >> Incidentally, I found PETSc does not compile when configured using >> >> --

[petsc-dev] Compilation errors with kokkos and --with-scalar-type complex

Incidentally, I found PETSc does not compile when configured using --with-scalar-type=complex --with-kokkos-dir= --with-kokkos_kernels-dir=... Some fixes are trivial, others require some more thought. Thanks -- Stefano

Re: [petsc-dev] configureLibrary fails for c++11 projects

he latest Kokkos and ran into >>> an even hairier version of this problem trying to use CUDA - the Kokkos >>> headers now apparently check that you're using nvcc. He has some workaround >>> which I'll review and hopefully be able to submit. >>> >>> &g

Re: [petsc-dev] configureLibrary fails for c++11 projects

(CXXLINKER) $(CXX_FLAGS) $(CXXFLAGS) $(CXXCPPFLAGS) $(LDFLAGS) > > Satish > > > On Tue, 23 Mar 2021, Junchao Zhang wrote: > > > I would rather directly change the project to use CXXFLAGS instead of > > CXXPPFLAGS. > > > > --Junchao Zhang > > > >

[petsc-dev] configureLibrary fails for c++11 projects

Just tried out of main, and and the include tests of a c++11 project fail Below my fix, if we agree on, I'll make a MR diff --git a/config/BuildSystem/config/compilers.py b/config/BuildSystem/config/compilers.py index c96967e..44e4657 100644 --- a/config/BuildSystem/config/compilers.py +++

Re: [petsc-dev] Petsc "make test" have more failures for --with-openmp=1

Eric You should report these HYPRE issues upstream https://github.com/hypre-space/hypre/issues > On Mar 14, 2021, at 3:44 AM, Eric Chamberland > wrote: > > For us it clearly creates problems in real computations... > > I understand the need to

Re: [petsc-dev] Argonne GPU Virtual Hackathon - Accepted

The COO assembly is entirely based on thrust primitives, I don’t have much experience to say we will get a serious speedup by writing our own kernels, but it is definitely worth a try if we will end up adopting COO as entry point for GPU irregular assembly. Jed, you mentioned BDDC deluxe, what

Re: [petsc-dev] valgrind now a point of failure?

Valgrind does not play well with optimization flags. It's either 03 or march=native. Il Mar 23 Feb 2021, 06:38 Barry Smith ha scritto: > > I knew they hate Macs but now Linux? Any trustworthy machines to run > valgrind? > > > $ petscmpiexec -valgrind -n 1 ./ex238 -mat_block_size 12 >

Re: [petsc-dev] Understanding Vecscatter with Kokkos Vecs

I dont understand the issue. I assume your vecscatter is not a throw away object but you will reuse it many times. Once the setup is done, the indices used internally by the implementation should be on gpu , or not? Il Ven 19 Feb 2021, 13:33 Patrick Sanan ha scritto: > Thanks! That helps a

Re: [petsc-dev] TSSetConvergedReason(ts,TS_CONVERGED_USER);

Mark monitors are not supposed to change the TS. You can think at monitors being 'const' methods of the TS. Also, TSMonitor is called at the beginning of each step , see here https://gitlab.com/petsc/petsc/-/blob/master/src/ts/interface/ts.c#L4169 Il giorno gio 18 feb 2021 alle ore 15:16 Mark

Re: [petsc-dev] obscure changes in TSGetStages_Theta

ages associated with these methods. The endpoint > variant actually has two stages. This will be changed in a separate > forthcoming MR, where TSRestoreStages() will be added and TSGetStages will > return an array of vectors for the endpoint variant. > > Hong > > On Jan 21, 2021,

Re: [petsc-dev] Memory problem with OpenMP and Fieldsplit sub solvers

I like NVIDIA docs, here is the message I got from what you posted: multiple threads can call cublas with the same handle but I would not do it if I were you…. In other words, everything is doable until you encounter an error. Very clear. > On Jan 22, 2021, at 4:51 PM, Mark Adams wrote: > >

[petsc-dev] obscure changes in TSGetStages_Theta

Hong, I do not understand why you changed the behavior of TSGetStages_Theta https://gitlab.com/petsc/petsc/-/merge_requests/3500/diffs#a582bbaec75f4ae14bbf97d1d0404073ca89ff09_1194_1209 with this MR https://gitlab.com/petsc/petsc/-/merge_requests/3500 Now, the non-endpoint variant does no longer

Re: [petsc-dev] bin/sh error while running tests

ent still holds true). > > Thanks, > Pierre > > On 20 Jan 2021, at 1:59 PM, Pierre Jolivet wrote: > > > > On 20 Jan 2021, at 12:11 PM, Stefano Zampini > wrote: > > This is an issue with the default shell used by the makefile. Below is my > fix.

Re: [petsc-dev] bin/sh error while running tests

mer 20 gen 2021 alle ore 14:11 Stefano Zampini < stefano.zamp...@gmail.com> ha scritto: > This is an issue with the default shell used by the makefile. Below is my > fix. We should probably have a CI machine that checks for these > shell-related errors. > > diff --g

Re: [petsc-dev] bin/sh error while running tests

; +endif Il giorno mar 19 gen 2021 alle ore 20:41 Scott Kruger ha scritto: > > > I can't reproduce this with the latest master: > > hip 1261: git pull > Already up to date. > hip 1262: make -f gmakefile.test test search='notatest' > Using MAKEFLAGS: -- search=notatest >

[petsc-dev] bin/sh error while running tests

Just rebased over latest master and got this zampins@vulture:~/Devel/petsc$ make -f gmakefile.test test search='notatest' Using MAKEFLAGS: -- search=notatest /bin/sh: 1: test: false: unexpected operator -- Stefano

Re: [petsc-dev] ASM for each field solve on GPUs

You should swap fieldsplit and ASM -pc_type fieldsplit -fieldsplit_0_pc_type asm …. > On Dec 31, 2020, at 10:19 PM, Mark Adams wrote: > > PCFieldSplitSetDefaults is called from PCSetUpOnBlocks and there is only one > block. So it is called from a subpc, which does not have a DM and it's too

[petsc-dev] checkbadSource issue

Just rebased my MR over master zampins@vulture:~/Devel/petsc$ make checkbadSource /bin/sh: 1: let: not found /bin/sh: 2: [: -gt: unexpected operator /bin/sh: 6: test: Illegal number: ! /home/zampins/Devel/petsc/lib/petsc/conf/rules:660: recipe for target 'checkbadSource' failed make[1]: ***

Re: [petsc-dev] Can't find test matrix

We have been using this repo for a while now, the ftp server is no longer up to date with the new datafiles Il Ven 18 Dic 2020, 20:02 Matthew Knepley ha scritto: > I need this one > > /PETSc3/petsc/petsc-dev/../datafiles/matrices/hpddm/GCRODR/A_400.dat > > but I cannot find it on the FTP site.

Re: [petsc-dev] Building PETSc on LLNL Lassen

While we are discussing this dialect stuff, do we still want to test for gnu++{11|14} extensions before testing for c++{11|14} ? We get warnings when using KOKKOS since it replaces gnu++14 with c++14. What is the added value of using gnu++{11|14}? Il giorno lun 14 dic 2020 alle ore 08:21 Barry

Re: [petsc-dev] Scaling test with ex13 (snes)

> On Oct 3, 2020, at 9:12 PM, Matthew Knepley wrote: > > On Sat, Oct 3, 2020 at 1:49 PM Stefano Zampini <mailto:stefano.zamp...@gmail.com>> wrote: > > There is a MATPARTITIONINGHIERARCH (man page) that Fande provided that > helped scaling up problems he w

Re: [petsc-dev] Scaling test with ex13 (snes)

node, migrate the PLEX data, then partition on each node separately, and migrate the data again. > > On Oct 3, 2020, at 10:04 AM, Matthew Knepley wrote: > > On Sat, Oct 3, 2020 at 10:51 AM Stefano Zampini > wrote: > >> >> >> >>> Secondly, I'd

Re: [petsc-dev] Scaling test with ex13 (snes)

> Secondly, I'd like to add a multilevel "simple" partitioning in DMPlex to > optimize communication. I am thinking that I can create a mesh with > 'nnodes' cells and distribute that to 'nnodes*procs_node' processes with a > "spread" distribution. (the default seems to be "compact"). Then refine >

Re: [petsc-dev] sm_70

I have added the configure option --with-cuda-gencodearch=XX to pass down such information to the external packages build. We are not currently using it in the library itself. Il Sab 26 Set 2020, 06:08 Barry Smith ha scritto: > > > On Sep 25, 2020, at 8:36 PM, Jacob Faibussowitsch > wrote: > >

Re: [petsc-dev] PETSc issue I cannot post combine WaitForCUDA(); inside PetscLogGpuTimeEnd();

> On Aug 28, 2020, at 5:18 PM, Barry Smith wrote: > > > >> On Aug 28, 2020, at 5:35 AM, Karl Rupp wrote: >> >> Hi, >> >>> Since we cannot post issues (reported here >>>

Re: [petsc-dev] Pause-for-approval Pipelines?

+1 for the new infrastructure > On Aug 27, 2020, at 6:59 PM, Satish Balay via petsc-dev > wrote: > > BTW: here are some reasons for using the MR pipeline instead of the web > interface pipeline. > > - it tests branch+master (more useful?) - instead of branch [web pipeline]. > - you can

Re: [petsc-dev] GitLab: Resolve this thread in a new issue

very useful, thanks https://gitlab.com/petsc/petsc/-/issues/676 Il giorno ven 3 lug 2020 alle ore 13:32 Hapla Vaclav < vaclav.ha...@erdw.ethz.ch> ha scritto: > I just used for the first time the feature of GitLab called "Resolve this > thread in a new issue". It's the button next to Resolve

Re: [petsc-dev] question on MatGolubKahanComputeExplicitOperator()

We usually try to avoid these expensive checks in PETSc (unless they are really needed they are run in debug mode only); > On Jun 24, 2020, at 8:23 AM, Barry Smith wrote: > > > MatGolubKahanComputeExplicitOperator() first verifies that C is the transpose > of B, it then computes the

Re: [petsc-dev] Meaning of PETSc matrices with zero rows but nonzero columns?

ork to handle these cases > properly. (Sure wish that MKL could just do it, though!) > > --Richard > > On 5/30/20 4:09 PM, Stefano Zampini wrote: >>> On May 31, 2020, at 1:03 AM, Jed Brown >>> <mailto:j...@jedbrown.org> wrote: >>> >>&

Re: [petsc-dev] Meaning of PETSc matrices with zero rows but nonzero columns?

> On May 31, 2020, at 1:03 AM, Jed Brown wrote: > > Stefano Zampini writes: > >> If A is 0x8 and B is 8x5 then C is correct to be of size 0x5. The rows and >> columns of the resulting matrix have to follow the rules. > > Right, I think if you said C is 0

Re: [petsc-dev] Meaning of PETSc matrices with zero rows but nonzero columns?

And MKL has the same issues for dense , see for example here https://gitlab.com/petsc/petsc/-/blob/master/src/mat/impls/dense/seq/dense.c#L2186 If A is 0x8 and B is 8x5 then C is correct to be of size 0x5. The

Re: [petsc-dev] Are we suppressing stderr when comparing outputs of tests?

PETSc. Sadly, they do exist. > Also, I’m using PetscFunction[Begin|End]User, don’t know if switching to > PetscFunction[Begin|End] would change something here, though I’m guessing it > wouldn't. > > I’ll keep you posted, thanks for reporting this, > Pierre > >> On

Re: [petsc-dev] Are we suppressing stderr when comparing outputs of tests?

The error is raised from HPDDM , that does not stop and I think does not return error codes. Pierre? Il giorno mer 13 mag 2020 alle ore 16:01 Matthew Knepley ha scritto: > I see my stderr with tests. I am running it right now. > >Matt > > On Wed, May 13, 2020 at 8:55 AM

[petsc-dev] Are we suppressing stderr when comparing outputs of tests?

I have a test that fails, but it only prints a small amount of information [szampini@localhost petsc]$ make -f gmakefile.test test search='ksp%' searchin='ex75_2_icc' PETSC_ARCH=arch-opt Using MAKEFLAGS: -- PETSC_ARCH=arch-opt searchin=ex75_2_icc search=ksp% TEST

Re: [petsc-dev] MATOP_MAT_MULT

Zampini < stefano.zamp...@gmail.com> ha scritto: > > > On May 10, 2020, at 8:56 PM, Jose E. Roman wrote: > > > > El 10 may 2020, a las 19:42, Stefano Zampini > escribió: > > Glad to hear it works. Anyway, without the MatShellVecSetType call the > code was error

Re: [petsc-dev] MATOP_MAT_MULT

> On May 10, 2020, at 8:56 PM, Jose E. Roman wrote: > > > >> El 10 may 2020, a las 19:42, Stefano Zampini >> escribió: >> >> Glad to hear it works. Anyway, without the MatShellVecSetType call the code >> was erroring for me, not leaking memory.

Re: [petsc-dev] MATOP_MAT_MULT

s. I have modified my branch. I was missing the > MatShellSetVecType() call. Now everything works fine and all tests are clean. > > Jose > > >> El 9 may 2020, a las 21:32, Stefano Zampini >> escribió: >> >> Jose >> >> I have just pushed an upd

Re: [petsc-dev] MATOP_MAT_MULT

(actual test time / total CPU time): # mat_tests-ex69_1: 2.30 sec / 62.11 sec > On May 9, 2020, at 9:28 PM, Jose E. Roman wrote: > > > >> El 9 may 2020, a las 20:00, Stefano Zampini >> escribió: >> >> >> >> Il giorno sab 9 mag 2

Re: [petsc-dev] MATOP_MAT_MULT

Il giorno sab 9 mag 2020 alle ore 19:43 Jose E. Roman ha scritto: > > > > El 9 may 2020, a las 12:45, Stefano Zampini > escribió: > > > > Jose > > > > I have just pushed a test > https://gitlab.com/petsc/petsc/-/blob/d64c2bc63c8d5d1a8c689f1abc7

Re: [petsc-dev] MATOP_MAT_MULT

ore 13:45 Stefano Zampini < stefano.zamp...@gmail.com> ha scritto: > Jose > > I have just pushed a test > https://gitlab.com/petsc/petsc/-/blob/d64c2bc63c8d5d1a8c689f1abc762ae2722bba26/src/mat/tests/ex69.c > See if it fits your framework, and feel free to modify the test

Re: [petsc-dev] MATOP_MAT_MULT

hed. Run with -test 1 or -test 2 > > > El 8 may 2020, a las 17:14, Stefano Zampini > escribió: > > > > Jose > > > > Just send me a MWE and I’ll fix the case for you > > > > Thanks > > Stefano > -- Stefano

Re: [petsc-dev] MATOP_MAT_MULT

[0]PETSC ERROR: #10 main() line 167 in ex19.c > [0]PETSC ERROR: PETSc Option Table entries: > [0]PETSC ERROR: -check_pointer_intensity 0 > [0]PETSC ERROR: -eps_type lobpcg > [0]PETSC ERROR: -error_output_stdout > [0]PETSC ERROR: -malloc > [0]PETSC ERROR: -malloc_debug > [0]

Re: [petsc-dev] MATOP_MAT_MULT

added a test for sbaij in parallel and it works nicely (automatically doing the loop over dense columns). Let me know if it works for you now Thanks Il giorno gio 7 mag 2020 alle ore 00:17 Stefano Zampini < stefano.zamp...@gmail.com> ha scritto: > > > > > > >> El 6

Re: [petsc-dev] MATOP_MAT_MULT

lagging behind maint, so maybe I’m missing some other >> fixes, take this with a grain of salt). >> Thanks, >> Pierre >> >>> On 6 May 2020, at 4:52 PM, Stefano Zampini >>> wrote: >>> >>> I have working support for MATSHELL here

Re: [petsc-dev] MATOP_MAT_MULT

’m missing some other >> fixes, take this with a grain of salt). >> Thanks, >> Pierre >> >>> On 6 May 2020, at 4:52 PM, Stefano Zampini >>> wrote: >>> >>> I have working support for MATSHELL here >>> https://gitlab.com/petsc/pets

Re: [petsc-dev] MATOP_MAT_MULT

Il giorno mer 6 mag 2020 alle ore 17:50 Zhang, Hong ha scritto: > Stefano, > How about you work on this issue? > here you have https://gitlab.com/petsc/petsc/-/commit/1c88b2e1d7c133c480fe45577b7a34a84969dc11 -- > *From:* Stefano Zampini > *Sent:* W

Re: [petsc-dev] MATOP_MAT_MULT

it yet Can you tell me if this fixes the issues for you to not have to loop over the columns of the dense matrix yourself? Il giorno mer 6 mag 2020 alle ore 10:09 Stefano Zampini < stefano.zamp...@gmail.com> ha scritto: > Hong > > If the product is not supported, the type of C wi

Re: [petsc-dev] MATOP_MAT_MULT

Either you take care of this bug report, or let me know your thoughts about > how to fix this bug. > Hong > From: Zhang, Hong > Sent: Saturday, April 25, 2020 2:40 PM > To: Pierre Jolivet > Cc: Jose E. Roman ; Stefano Zampini > ; petsc-dev ; Smith, Barry > F. > Subjec

Re: [petsc-dev] DMPlexInterpolate after DMPlexDistribute

I think the slowdown in the second test (interpolate 0) is coming from the fact that Plex has to compute the dual graph on the fly, see here https://gitlab.com/petsc/petsc/-/blob/master/src/dm/impls/plex/plexpartition.c#L469 . Are you having a performance regression with DMPLEX on this second

Re: [petsc-dev] Modify 3rd party lib

e-04 >>>> >>>> *dDestroy_LU: GPU free Llu->Lnzval_bc_ptr[0/134] = 0x4ff9b000, CPU free >>>> Llu->Lrowind_bc_ptr = 0x4ff9a000*ex112d: cudahook.cc:762: CUresult >>>> host_free_callback(void*): Assertion `cacheNode != __null' failed. >>>> >>

Re: [petsc-dev] MATOP_MAT_MULT

> > MatProductCreateWithMat(A,Vmat,NULL,Wmat); > MatProductSetType(Wmat,MATPRODUCT_AB); > MatHasOperation(Wmat,MATOP_MATPRODUCT,); //new support, it calls > MatProductSetFromOptions(Wmat) Hong, this would go in the direction I was outlining here https://gitlab.com/petsc/petsc/-/issues/608

Re: [petsc-dev] Modify 3rd party lib

>Lnzval_bc_ptr[0/134] = 0x4ff9b000, CPU free > Llu->Lrowind_bc_ptr = 0x4ff9a000 > ex112d: cudahook.cc:762: CUresult host_free_callback(void*): Assertion > `cacheNode != __null' failed. > > THis looks like Lnzval_bc_ptr is on the CPU so I removed the GPU_ACC stuff > and it works now.

Re: [petsc-dev] Modify 3rd party lib

You should still use —download-superlu_dist along with the option I have sent you > On Apr 20, 2020, at 1:29 AM, Mark Adams wrote: > > > > On Sun, Apr 19, 2020 at 5:52 PM Stefano Zampini <mailto:stefano.zamp...@gmail.com>> wrote: > First, commit your changes

Re: [petsc-dev] Modify 3rd party lib

First, commit your changes to the superlu_dist branch, then rerun configure with —download-superlu_dist-commit=HEAD > On Apr 20, 2020, at 12:50 AM, Mark Adams wrote: > > I would like to modify SuperLU_dist but if I change the source and configure > it says no need to reconfigure, use

Re: [petsc-dev] MATSBAIJ MatChop MAT_GETROW_UPPERTRIANGULAR

Other basic operations (i.e. MatAXPY_Basic) handles this programmatically. You should open an MR fixing it. > On Apr 15, 2020, at 1:22 AM, Jed Brown wrote: > > Jacob Faibussowitsch mailto:jacob@gmail.com>> > writes: > >> Hello All, >> >> When using MATSBAIJ and MatChop you get the

[petsc-dev] Issue with make test and globsearch

[szampini@localhost petsc]$ make -f gmakefile.test test globsearch='mat_*' Using MAKEFLAGS: -- globsearch=mat_* make: *** No rule to make target 'mat_tests-ex1_1', needed by 'report_tests'. Stop. -- Stefano

Re: [petsc-dev] Globsearch fails for me when running tests

> > > What do you have for > > getconf ARG_MAX > > [szampini@localhost petsc]$ getconf ARG_MAX 2097152 > make -f gmakefile.test test search=dm% > > works. This is on Fedora 30 > > make: execvp: /usr/bin/sh: Argument list too long > > Using MAKEFLAGS: -- globsearch=dm* > > # No tests run >

[petsc-dev] Globsearch fails for me when running tests

This was working before.. [szampini@localhost petsc]$ make -f gmakefile.test test globsearch='dm*' make: execvp: /usr/bin/sh: Argument list too long Using MAKEFLAGS: -- globsearch=dm* # No tests run # No tests run # No tests run [szampini@localhost petsc]$ git branch *

Re: [petsc-dev] [petsc-users] Matrix-free method in PETSc

Barry Lisandro already said most of it. We are all adults and we make mistakes, and we listen without getting offended. We listen and, if we are smart, we listen carefully. I value sincerity more than inclusiveness. With that said, I think your very last email was the real mistake. Thanks

[petsc-dev] How to replace floating point numbers in test outputs?

I would like to overwrite floating point numbers in tests outputs. I remember in the past we could just pass REPLACE=1; it seems it is not possible with the current master. I tried the command below (this is a test which produces different floating point values) with no success. Any suggestion

Re: [petsc-dev] error with karlrupp/fix-cuda-streams

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

Re: [petsc-dev] TAP file and testing error

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

[petsc-dev] Gitlab notifications

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?

Re: [petsc-dev] (no subject)

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>

Re: [petsc-dev] SNESSetKSP and SNESDestroy

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: > >>

  1   2   3   4   >