Re: [petsc-dev] fortran compilation error

There have been changes in the fortran stubs recently. Try regenerating the fortran stubs with "make deletefortranstubs" followed by "make allfortranstubs". If this does not work, try removing the $PETSC_ARCH directory and configure/make again.  ZjQcmQRYFpfptBannerStart

Re: [petsc-dev] Issue with -log_view

https://gitlab.com/petsc/petsc/-/merge_requests/6440 > El 9 may 2023, a las 15:31, Matthew Knepley escribió: > > On Tue, May 9, 2023 at 9:04 AM Jose E. Roman wrote: > I found the bug: the event MAT_MultHermitianTranspose is used but not > registered. > I will creat

Re: [petsc-dev] Issue with -log_view

I found the bug: the event MAT_MultHermitianTranspose is used but not registered. I will create a MR. Thanks Matt. > El 9 may 2023, a las 14:50, Matthew Knepley escribió: > > On Tue, May 9, 2023 at 8:41 AM Jose E. Roman wrote: > But MatCreateShell() calls MatInitializePa

Re: [petsc-dev] Issue with -log_view

y 9, 2023 at 7:17 AM Jose E. Roman wrote: > Hi. > > We are seeing a strange thing in the -log_view output with one of the SLEPc > solvers. It is probably an issue with SLEPc, but we don't know how to debug > it. > > It can be reproduced for instance with > > $ ./ex45 -

[petsc-dev] Issue with -log_view

Hi. We are seeing a strange thing in the -log_view output with one of the SLEPc solvers. It is probably an issue with SLEPc, but we don't know how to debug it. It can be reproduced for instance with $ ./ex45 -m 15 -n 20 -p 21 -svd_nsv 4 -svd_ncv 9 -log_view The log_view events are listed at

Re: [petsc-dev] Fortran-auto-interfaces

din escribió: > > Hi Jose, > > I have created the type tTAO and PETSC_NULL_TAO what I need to figure out is > how to get bfort to import tTAO in each auto interface, for instance > > Blaise > > > >> On Jan 10, 2023, at 12:23 PM, Jose E. Roman wrote: >

Re: [petsc-dev] Fortran-auto-interfaces

The files under ftn-auto-interfaces are generated with bfort when you run configure. You can also force its generation with 'make allfortranstubs'. In the case of Tao I think the problem is that the definition of tTao is missing. You should have something like this in

Re: [petsc-dev] Jacobi (smoothing) not staying on GPU

Add an implementation of MatGetDiagonal_SeqAIJCUSPARSE(), which is missing. Use for example this: https://stackoverflow.com/questions/60311408/how-to-get-the-diagonal-of-a-sparse-matrix-in-cusparse Jose > El 8 jun 2022, a las 3:21, Mark Adams escribió: > > I am looking at TS/SNES/KSP/GAMG

Re: [petsc-dev] odd log behavior

You have to add -log_view_gpu_time See https://gitlab.com/petsc/petsc/-/merge_requests/5056 Jose > El 26 abr 2022, a las 16:39, Mark Adams escribió: > > I'm seeing this on Perlmutter with Kokkos-CUDA. Nans in most log timing data > except the two 'Solve' lines. > Just cg/jacobi on snes/ex56.

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

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 las 13:15, Stefano Zampini > escribió: > > Just noticed this. Is it normal to have a ftn-auto directory generated by > bfort in

Re: [petsc-dev] Help tracking down unexpected Fortran behavior

PCSetType() has an interface in src/ksp/f90-mod/petscpc.h90 while PCFactorSetMatOrderingType() does not. I don't know if there is a clear criterion for when to add an interface in the corresponding h90 file. One criterion is that we need a F90 interface in case one of the arguments is allowed

Re: [petsc-dev] petsc4py build

./configure --with-petsc4py=1 and then run a test with export PYTHONPATH=$PETSC_DIR/$PETSC_ARCH/lib Jose > El 30 sept 2021, a las 14:05, Matthew Knepley escribió: > > If I add binding code as part of my MR, how do I check the build on my > machine? I have gotten confused since we merged the

Re: [petsc-dev] builds of PETSc based packages should not get their own secret files

slepc4py source is not yet included in SLEPc source, but this will be done soon. Jose > El 5 ene 2021, a las 8:30, Barry Smith escribió: > > > Thanks. > >I'd like to move to also building the python bindings for both PETSc and > SLEPc by default in the future. Gives better testing

Re: [petsc-dev] checkbadSource issue

I am getting the same in some machines. I don't think this is due to a recent change. In the pipeline, it is run as $ make checkbadSource SHELL=bash which solves the issue. On the other hand, in the 'checksource' job in the pipelines, there are errors (probably not important):

Re: [petsc-dev] MATOP_MAT_MULT

Let me know if you need more customization (e.g. attach data to the product >> in a more systematic way) or if it can already fit your frameworks. >> >> Best >> Stefano >> >> Il giorno dom 10 mag 2020 alle ore 21:04 Stefano Zampini >> ha scri

Re: [petsc-dev] MATOP_MAT_MULT

r MATSHELL > Can SLEPc benefit from such a feature ? Some solvers yes. > >> On May 10, 2020, at 7:47 PM, Jose E. Roman wrote: >> >> Thanks for the hints. I have modified my branch. I was missing the >> MatShellSetVecType() call. Now everything works fine and all t

Re: [petsc-dev] MATOP_MAT_MULT

- > # Summary > # - > # success 48/48 tests (100.0%) > # failed 0/48 tests (0.0%) > # todo 0/48 tests (0.0%) > # skip 0/48 tests (0.0%) > # > # Wall clock time for tests: 58 sec > # Approximate CPU time (not incl. build time): 62.11 sec &g

Re: [petsc-dev] MATOP_MAT_MULT

> El 9 may 2020, a las 20:00, Stefano Zampini > escribió: > > > > 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 > > > >

Re: [petsc-dev] MATOP_MAT_MULT

enseReplaceArray() does not exist. So the interface is different in GPU vs CPU, but I guess it is necessary here. Thanks. Jose > > > Il giorno ven 8 mag 2020 alle ore 18:48 Jose E. Roman ha > scritto: > Attached. Run with -test 1 or -test 2 > > > El 8 may 2020, a las 17:14, Ste

Re: [petsc-dev] MATOP_MAT_MULT

Attached. 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 ex1.c Description: Binary data

Re: [petsc-dev] MATOP_MAT_MULT

t; MatProductSetType(C,...); > >>>> ... > >>>> MatProductSetFromOptions(); //if the product is not supported for the > >>>> given mat types, currently petsc crashes here, which we can replace with > >>>> an error output > >>>> > >

Re: [petsc-dev] MATOP_MAT_MULT

;>> >>> Question: how to call MatHasOperation(C,..) when MatProductSymbloc() is not >>> supported? >>> >>> My fix to this bug: >>> Resume MatSetType() in MatProductSetFromOptions(). Then user calls: >>> >>> MatProductCreate(A,B,NULL,); >>> MatProductSet

Re: [petsc-dev] MATOP_MAT_MULT

is ok? >> Hong >> >> From: Pierre Jolivet >> Sent: Wednesday, April 22, 2020 3:08 PM >> To: Zhang, Hong >> Cc: Jose E. Roman ; Stefano Zampini >> ; petsc-dev ; Smith, Barry >> F. >> Subject: Re: [petsc-dev] MATOP_MAT_MULT >> >> Hong,

Re: [petsc-dev] MATOP_MAT_MULT

e, MatShell with > products inside) > If flg1 and flg2 are both true -> Specific implementation available. > >> if (V->vmm && flg) { >> MatProductSymbolic(Wmat); >> MatProductNumeric(Wmat); >> } else { >> MatDestroy(Wmat); >> ... &

Re: [petsc-dev] MATOP_MAT_MULT

> El 21 abr 2020, a las 17:53, Pierre Jolivet > escribió: > > > >> On 21 Apr 2020, at 5:22 PM, Zhang, Hong wrote: >> >> Pierre, >> MatMatMult_xxx() is removed from MatOps table. > > Shouldn’t there be a deprecation notice somewhere? > There is nothing about MATOP_MAT_MULT in the 3.13

Re: [petsc-dev] Broken MatMatMult_MPIAIJ_MPIDense

> El 22 sept 2019, a las 19:11, Smith, Barry F. escribió: > > Jose, > > Thanks for the pointer. > > Will this change dramatically affect the organization of SLEPc? As noted > in my previous email eventually we need to switch to a new API where the > REUSE with a different

Re: [petsc-dev] Broken MatMatMult_MPIAIJ_MPIDense

The man page of MatMatMult says: "In the special case where matrix B (and hence C) are dense you can create the correctly sized matrix C yourself and then call this routine with MAT_REUSE_MATRIX, rather than first having MatMatMult() create it for you." If you are going to change the usage,

Re: [petsc-dev] MAT_HERMITIAN

Not sure if I understand you. Do you mean that a complex SBAIJ Mat with MAT_HERMITIAN flag can be assumed to have zero imaginary part? I don't think so. This matrix should have real diagonal entries, but off-diagonal entries should be allowed to have nonzero imaginary part. This is what is done

Re: [petsc-dev] Configure issue, PETSC_USE_SOCKET_VIEWER not defined

My recent PR#1886 is also related to what Lisandro reports: https://bitbucket.org/petsc/petsc/pull-requests/1886/fix-compiler-warning/diff The corresponding configure.log is here:

Re: [petsc-dev] I just removed Fortran support from my development build

In my experience, ifort is much faster than gfortran building the Fortran bindings. Jose > El 22 oct 2018, a las 15:18, Matthew Knepley escribió: > > Jenkins will now catch bad Fortran bindings. However, this is a larger > problem. GFortran takes forever to build the bindings. Is it similar

Re: [petsc-dev] Remove legacy tests

in(os.path.dirname(__file__), 'config', 'configure.py')) > File "./config/configure.py", line 321, in >testruns = set(petsc.test_runs.split()) > AttributeError: PETSc instance has no attribute 'test_runs' > <<<< > > This issue comes up with xsdk@develop - bu

Re: [petsc-dev] Remove legacy tests

It works for us. Thanks. Jose > El 5 sept 2018, a las 15:15, Satish Balay escribió: > > I pushed the change to balay/remove-Regression.py > > Satish > > On Mon, 3 Sep 2018, Jose E. Roman wrote: > >> We are almost done with migrating SLEPc tests to the new test

[petsc-dev] Remove legacy tests

We are almost done with migrating SLEPc tests to the new test harness. If you want, you can remove Regression.py from PETSc, as well as any makefile rules that might remain for legacy tests. Jose

Re: [petsc-dev] Undefined symbols for _kspfgmresmodifypcksp_ and _kspfgmresmodifypcnochange_ when rebuilding

> El 22 ago 2018, a las 12:52, Matthew Knepley escribió: > > On Wed, Aug 22, 2018 at 6:35 AM Lawrence Mitchell wrote: > > > On 22 Aug 2018, at 10:04, Patrick Sanan wrote: > > > > This happens fairly frequently when I try to switch/update branches of > > PETSc (here invoked by building my

Re: [petsc-dev] Remove legacy tests?

Well, if you want to remove it, I can just insert ${PETSC_DIR}/lib/petsc/conf/test in SLEPc's repository, so not a big problem. > El 6 jul 2018, a las 7:46, Jose E. Roman escribió: > > SLEPc still uses the legacy test system. I have not had time to move to the > new test har

Re: [petsc-dev] Remove legacy tests?

SLEPc still uses the legacy test system. I have not had time to move to the new test harness. Jose > El 6 jul 2018, a las 2:42, Smith, Barry F. escribió: > > > >> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote: >> >> When can we delete the legacy test system? Are we currently using it >>

Re: [petsc-dev] Missing typedef ?

MatSolverPackage has been renamed to MatSolverType in a recent commit in master. Jose > El 28 ene 2018, a las 17:50, Franck Houssen > escribió: > > Hello, > > In petscmat.h, the line "#define MatSolverPackage char*" shouldn't it be > replaced with "typedef char*

Re: [petsc-dev] new test harness in PETSc

Are you going to keep the old makefiles? (I mean ${PETSC_DIR}/lib/petsc/conf/test) In SLEPc we still use makefiles for the tests. I should move to the new system, but don't have time at the moment. Jose > El 25 ene 2018, a las 5:47, Smith, Barry F. escribió: > > >

Re: [petsc-dev] [SPAM *****] Re: Issue with Lapack names

> El 18 dic 2017, a las 22:34, Karl Rupp escribió: > > > >> > > This is related to a message I sent 2 years ago to petsc-maint >>"Inconsistent naming of one Lapack subroutine", where I advocated >>renaming LAPACKungqr_ --> LAPACKorgqr_. But that thread did

Re: [petsc-dev] Issue with Lapack names

> El 18 dic 2017, a las 18:58, Matthew Knepley <knep...@gmail.com> escribió: > > On Mon, Dec 18, 2017 at 12:30 PM, Jose E. Roman <jro...@dsic.upv.es> wrote: > I find the following definitions in petscconf.h, which are wrong because the > corresponding subroutine

[petsc-dev] Issue with Lapack names

I find the following definitions in petscconf.h, which are wrong because the corresponding subroutines are present. #define PETSC_MISSING_LAPACK_UNGQR 1 #define PETSC_MISSING_LAPACK_HETRS 1 #define PETSC_MISSING_LAPACK_HETRF 1 #define PETSC_MISSING_LAPACK_HETRI 1 This did not happen in 3.8, it

Re: [petsc-dev] SLEPc failure

Increasing -eps_max_it does not help. So, I guess this is the end of the road. > > Would you consider to expose (in future release) the tolerance of this check > ? Or is this something you really want to keep private ? (whatever B is or > not singular - I guess in my case, this wou

Re: [petsc-dev] SLEPc failure

indefinite, I added > -mat_mumps_icntl_33 1 to get the determinant). > > Anyway, I don't expect you spend too much time on this. My understanding is > that there is no way to relax this check ? Correct ? > > Franck > > - Mail original - >> De: "

Re: [petsc-dev] QR factorization of dense matrix

ke it work, I had to set a BV type: I chose BVMAT as > I use BVCreateFromMat. Is that the good type ? (BVVECS works too) > > Franck > > ----- Mail original - >> De: "Jose E. Roman" <jro...@dsic.upv.es> >> À: "Franck Houssen" <franck.hou

Re: [petsc-dev] SLEPc failure

t; > Binary data are attached. > > Franck > > PS : running debian with little endian. >>> python -c "import sys;print(0 if sys.byteorder=='big' else 1)" > 1 > > > - Mail original - >> De: "Jose E. Roman" <jro...@dsic.upv.es> &

Re: [petsc-dev] QR factorization of dense matrix

ails with : >> [0]PETSC ERROR: Nonconforming object sizes >> [0]PETSC ERROR: Mat argument is not square, it has 1 rows and 3 columns > > So, as I didn't get what's wrong, I was looking for another way to do this. > > Franck > > - Mail original - >> D

Re: [petsc-dev] QR factorization of dense matrix

Franck, SLEPc has some support for this, but it is intended only for tall-skinny matrices, that is, when the number of columns is much smaller than rows. For an almost square matrix you should not use it. Have a look at this

Re: [petsc-dev] SLEPc failure

; to relax that check ? > Data are attached. > > Franck > > ----- Mail original - >> De: "Jose E. Roman" <jro...@dsic.upv.es> >> À: "Franck Houssen" <franck.hous...@inria.fr> >> Cc: "For users of the development version of PETSc

Re: [petsc-dev] SLEPc failure

nck Houssen <franck.hous...@inria.fr> escribió: > > I use the development version (bitbucket clone). How to relax the check ? At > command line option ? > > Franck > > - Mail original - >> De: "Jose E. Roman" <jro...@dsic.upv.es> &g

Re: [petsc-dev] SLEPc failure

> El 26 oct 2017, a las 18:36, Franck Houssen > escribió: > > Here is a stack I end up with when trying to solve an eigen problem (real, > sym, generalized) with SLEPc. My understanding is that, during the Gram > Schmidt orthogonalisation, the projection of one basis

Re: [petsc-dev] What is the difference between shift and target in SLEPc ?

s A-sigma*I or > A-sigma*B singular, then the solve may break. If so, afterwards, it's > possible to change slightly the shift to avoid solve break down (but there is > no way to know that beforehand). > > Franck > > - Mail original - >> De: "Jose E. Roma

Re: [petsc-dev] What is the difference between shift and target in SLEPc ?

> El 25 sept 2017, a las 13:21, Franck Houssen > escribió: > > What is the difference between shift and target in SLEPc ? Shift (STSetShift) > is clear to me, but, target (EPSSetTarget) is not. > Can somebody give an example where one want/need to have a target which

Re: [petsc-dev] MatCreateRedundantMatrix() does not work for rectangular matrices

ow if you have any comments. > > Hong > > On Mon, Jul 24, 2017 at 9:02 AM, Hong <hzh...@mcs.anl.gov> wrote: > This example works well on maint-branch. > > There is a bug in master branch. > I'll fix it after I'm back from the vacation (Thursday). > > Hong > >

Re: [petsc-dev] GPU regression tests

Karl, We have detected another problem. Could you take care of it? MatDuplicate() does not work for MATSEQAIJCUSPARSE (probably also for MATMPIAIJCUSPARSE). The attached example creates a matrix and duplicates it. There are two cases: 1) With a diagonal matrix it fails on GPU because

[petsc-dev] GPU regression tests

Hi. With pull request #719 we have finished a set of fixes to VECCUDA stuff. With these changes it is now possible to run many tests in SLEPc's testsuite on GPU (AIJCUSPARSE+VECCUDA). These tests will be included in the nightly tests from now on. However, PETSc nightly tests related to

[petsc-dev] MatCreateRedundantMatrix() does not work for rectangular matrices

Attached is an example that shows that MatCreateRedundantMatrix() fails if the matrix is rectangular. Is it a bug or an unsupported case? Jose ex207.c Description: Binary data

Re: [petsc-dev] DMCopyDMSNES

20:21, Barry Smith <bsm...@mcs.anl.gov> escribió: > > > It is developer level, so might not belong in the public headers. > > Do you need it in the public headers? > > >> On Jul 20, 2017, at 11:27 AM, Jose E. Roman <jro...@dsic.upv.es> wrote: &

[petsc-dev] DMCopyDMSNES

DMCopyDMSNES() is documented http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/DMCopyDMSNES.html but it is defined in the private header snesimpl.h. Shouldn't it be in the public header petscsnes.h? Jose

Re: [petsc-dev] [petsc-maint] problems compiling petsc on MAC

> El 1 may 2017, a las 22:27, Barry Smith escribió: > > Is there are reason to have the same symbol in both library (note they come > from the fortran versions) > > $ nm -o arch-uni-f2cblaslapack/lib/libf2cblas.a | grep xerbla | grep " T " >

[petsc-dev] Extending MatLRC

Hi. I need to work with low-rank matrices represented as the outer product of tall-skinny matrices. Specifically, I need to cover these cases: - Symmetric positive-definite: X*X' - Symmetric indefinite: X*C*X' - Non-symmetric: X*Y' (or maybe X*C*Y') This could be added by extending MATLRC

Re: [petsc-dev] unpleasantness in CUDA tests in master

> El 21 jun 2016, a las 9:18, Karl Rupp escribió: > > On 06/21/2016 04:16 AM, Barry Smith wrote: >> >> ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/06/20/master.html > > I'll fix this. > > Best regards, > Karli > > Probably some of these are fixed in PR

Re: [petsc-dev] PETSc "testing" infrastructure

> El 17 jun 2016, a las 0:18, Barry Smith escribió: > > > There is a lot going on currently to enhance the PETSc "testing" > infrastructure; in particular Lisandro has begun to set up stuff on both > github and bitbucket. > > I've update the PETSc "Dashboard" for

Re: [petsc-dev] Undefined symbol in SLEPc dylib (Haskell bindings, OSX)

I have no idea why this symbol is not resolved. I have never had a similar problem. Anyway, if it helps, I have pushed a commit to maint where all occurrences of this symbol are removed, since they are not necessary anyway. https://bitbucket.org/slepc/slepc/commits/b3c04e8 Jose > El 9 jun

[petsc-dev] GPU regression tests

Hi. We recently noticed that MatMultTranspose_MPIAIJCUSPARSE does not work. We tried to debug it but it is difficult because we don't know the internal details of Mat. There might be other cases. It would be convenient to add nightly tests for VECCUDA and MATAIJCUSPARSE (in real and complex

Re: [petsc-dev] stability issue

> El 4 may 2016, a las 7:35, Vasiliy Kozyrev escribió: > > Hi > > I have an issue with solution stability(small variations in > my matrixes causes significant variations in the solution). > It looks like a feature of my eigen value problem, because > for other problems

[petsc-dev] Support for complex scalars in VECCUDA

Hi Karl, We would like to add support for complex scalars in VECCUDA and MATAIJCUSPARSE. This is almost finished and we plan to create a new pull request for this. Is PR #421 ready to merge? Jose

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-03-11

> El 11 mar 2016, a las 17:28, Satish Balay escribió: > > There is one more broken build due to cuda changes. > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/make_next_arch-linux-pkgs-dbg-ftn-interfaces_crank.log > >

Re: [petsc-dev] Not possible to do a VecPlaceArray for veccusp

> El 10 mar 2016, a las 11:21, Karl Rupp escribió: > > Great! I'm looking forward to reviewing your pull request. Let me know if you > need support with the Mat part. > > Best regards, > Karli The pull request: https://bitbucket.org/petsc/petsc/pull-requests/421/

Re: [petsc-dev] Not possible to do a VecPlaceArray for veccusp

> El 10 mar 2016, a las 10:10, Karl Rupp escribió: > > Hi Jose and Alejandro, > > how's your current progress/status? It looks like I'm able to spend some time > on this and can get this done by early next week. On the other hand, if > you've finished all the relevant

Re: [petsc-dev] Not possible to do a VecPlaceArray for veccusp

> El 28 feb 2016, a las 10:45, Karl Rupp escribió: > > Hi, > >> I like the idea of having separate VECCUDA and VECVIENNACL, because it is >> possible to implement VECCUDA without dependence on a C++ compiler (only the >> CUDA compiler). > > I don't understand this

Re: [petsc-dev] Not possible to do a VecPlaceArray for veccusp

> El 26 feb 2016, a las 18:31, Dominic Meiser escribió: > > On Fri, Feb 26, 2016 at 02:49:39PM +0100, Karl Rupp wrote: >> The alternative would be to use raw cuda pointers instead of cusp arrays for GPU memory in VecCUSP. That would be a fairly significant

Re: [petsc-dev] Not possible to do a VecPlaceArray for veccusp

> El 25 feb 2016, a las 17:19, Dominic Meiser <dmei...@txcorp.com> escribió: > > On Thu, Feb 25, 2016 at 01:13:01PM +0100, Jose E. Roman wrote: >> We are trying to do some GPU developments on the SLEPc side, and we would >> need a way of placing the array of a VECCUS

[petsc-dev] Not possible to do a VecPlaceArray for veccusp

We are trying to do some GPU developments on the SLEPc side, and we would need a way of placing the array of a VECCUSP vector, providing the GPU address. Specifically, what we want to do is have a large Vec on GPU and slice it in several smaller Vecs. For the GetArray/RestoreArray we have all

Re: [petsc-dev] [SLEPc] For users of PETSc master branch, API change

> I attach the logs. It looks like there is a definition that was not updated. > > Best, > > Massimiliano > > >> -Original Message- >> From: Jose E. Roman [mailto:jro...@dsic.upv.es] >> Sent: 09 November 2015 14:48 >> To: petsc-users >&g

Re: [petsc-dev] [SLEPc] For users of PETSc master branch, API change

looks like I chose the worst possible day to update :D >> >> Best, >> >> Massimiliano >> >>> -Original Message- >>> From: Jose E. Roman [mailto:jro...@dsic.upv.es] >>> Sent: 09 November 2015 14:26 >>> To: Leoni, Mass

Re: [petsc-dev] [SLEPc] For users of PETSc master branch, API change

Working on it. Be patient. Should be available on master tomorrow. Jose > El 9/11/2015, a las 15:23, Leoni, Massimiliano > escribió: > > Is there a branch in the SLEPc repo that supports this? > > Massimiliano > >> -Original Message- >> From:

Re: [petsc-dev] [GPU - slepc] Hands-on exercise 4 (SVD) not working with GPU and default configurations

El 11/8/2015, a las 12:17, Leoni, Massimiliano massimiliano.le...@rolls-royce.com escribió: Jose, I have a doubt I made myself unclear earlier: when I said the GPU version was slower than the CPU version, I meant single GPU vs single CPU multithreaded [i.e. 12 threads]. The single

Re: [petsc-dev] [GPU - slepc] Hands-on exercise 4 (SVD) not working with GPU and default configurations

Massimiliano, You should not be getting slower times on the GPU. I tried with a hardware similar to what you mention, running SVD on a dense square matrix stored as aij, and also with sparse rectangular matrices. In all cases, executions on the GPU were roughly 2x faster than on the CPU. Are

Re: [petsc-dev] [GPU - slepc] Hands-on exercise 4 (SVD) not working with GPU and default configurations

Yes, there seems to be a problem with the default SVD solver (SVDCROSS). I will fix it in the master branch in the next days. Meanwhile, you can run the example with -svd_type trlanczos Thanks for reporting this. Jose El 7/8/2015, a las 16:31, Leoni, Massimiliano

Re: [petsc-dev] [SLEPc - GPU] Problems running SLEPc on GPUs

El 24/7/2015, a las 10:09, Leoni, Massimiliano massimiliano.le...@rolls-royce.com escribió: Hi everybody, I have recently being trying to run SLEPc on GPUs, but I am experiencing some trouble. I think I correctly installed PETSc to run on GPUs, as I can actually see an execution

[petsc-dev] PetscCheckSameType

Shouldn't PetscCheckSameType compare type_name instead of type? #define PetscCheckSameType(a,arga,b,argb) \ if (((PetscObject)a)-type != ((PetscObject)b)-type) SETERRQ2(PETSC_COMM_SELF,PETSC_ERR_ARG_NOTSAMETYPE,Objects not of same type: Argument # %d and %d,arga,argb);

Re: [petsc-dev] CUDA 7

experimenting if anyone is interested. Steve On Tue, Apr 14, 2015 at 10:09 AM, Jose E. Roman jro...@dsic.upv.es wrote: Has anyone updated to CUDA 7? With clanguage=c++ now I get lots of warnings with CUSP v0.4.0. These presumably will go away when updating to CUSP v0.5.0, but it turns out

[petsc-dev] CUDA 7

Has anyone updated to CUDA 7? With clanguage=c++ now I get lots of warnings with CUSP v0.4.0. These presumably will go away when updating to CUSP v0.5.0, but it turns out that PETSc build is broken with CUSP v0.5.0 (a header file was moved, and some other issues). Jose

Re: [petsc-dev] -ksp_view

Try -ksp_view_pre El 26/03/2015, a las 15:36, Matthew Knepley escribió: If the solve fails, we never see the output, so I think we need something like -ksp_preview which outputs the view before the solve is run. Am I wrong here? Thanks, Matt -- What most experimenters

Re: [petsc-dev] Symmetry acceleration of the Jacobi-Davidson method (in SLEPc)

El 13/02/2015, a las 15:06, Krzysztof Gawarecki escribió: Dear All, I'm calculating eigenvalues and eigenvectors of the matrix which has specific kind of symmetry. Due to this symmetry I obtain the eigenvalues which are doubly degenerated. So eg. eigeinvalue 'e1' has eigenvectors 'a1'

[petsc-dev] Force synchronization of CUSP vector

I would like to force the copy of a VECCUSP from/to the GPU. I need this in user code, in particular from within a shell matrix MatMult. Both VecCUSPCopyToGPU() and VecCUSPCopyToGPU_Public() are declared PETSC_INTERN in a private header. The only public function is

Re: [petsc-dev] Sean is going to love this

El 23/12/2014, a las 20:38, Sean Farley escribió: 4) Better coordination with dependent packages This item is hard to implement because it's out of the PETSc team's control. For example, packages like SLEPc depend on PETSc but don't have as good of a build system. SLEPc can't be built with

[petsc-dev] Can ViennaCL coexist with Cusp?

It seems ViennaCL and Cusp are exclusive. From vecimpl.h: #if defined(PETSC_HAVE_CUSP) PetscCUSPFlag valid_GPU_array;/* indicates where the most recently modified vector data is (GPU or CPU) */ void *spptr; /* if we're using CUSP, then this is the special

Re: [petsc-dev] unwind next branch

origin/jose/mumps-bugfix -- remove (those fixes have already been included in other commits by Hong.) Jose

Re: [petsc-dev] PetscSplitReduction

El 09/07/2014, a las 23:39, Jed Brown escribió: Satish Balay ba...@mcs.anl.gov writes: merged to maint now. Satish, we can't have this non-namespaced stuff in 'maint' (it really can break user code). The struct definition should really be private (so if Jose needs to access fields, we

Re: [petsc-dev] PetscSplitReduction

El 08/06/2014, a las 13:13, Jose E. Roman escribió: El 08/06/2014, a las 12:57, Jed Brown escribió: Jose E. Roman jro...@dsic.upv.es writes: Would it be too much asking that PetscSplitReduction be available in a public header? (together with the functions PetscSplitReductionGet

[petsc-dev] PetscSplitReduction

Would it be too much asking that PetscSplitReduction be available in a public header? (together with the functions PetscSplitReductionGet, PetscSplitReductionEnd, PetscSplitReductionExtend). I know this request comes too close to the release date. Jose

Re: [petsc-dev] PetscSplitReduction

El 08/06/2014, a las 12:57, Jed Brown escribió: Jose E. Roman jro...@dsic.upv.es writes: Would it be too much asking that PetscSplitReduction be available in a public header? (together with the functions PetscSplitReductionGet, PetscSplitReductionEnd, PetscSplitReductionExtend). Sounds

[petsc-dev] Problem with generateetags.py

I am getting an error when generating the tags, see error below. I have tracked the problem down to this offending commit: https://bitbucket.org/petsc/petsc/commits/326299b7 It started to appear when the TAO users guide was placed under src. A simple fix is to remove *.tex from generateetags.py

Re: [petsc-dev] Problem with generateetags.py

in generateetags.py nor does it crash for me.Is it crashing in a particular directory? Thanks Barry On Apr 4, 2014, at 4:17 AM, Jose E. Roman jro...@dsic.upv.es wrote: I am getting an error when generating the tags, see error below. I have tracked the problem down to this offending commit

Re: [petsc-dev] MatAXPY does not increase state

El 02/04/2014, a las 18:21, Jed Brown escribió: Jose E. Roman jro...@dsic.upv.es writes: Hi. We are having problems since the MatStructure flag was removed from KSPSetOperators. https://bitbucket.org/petsc/petsc/commits/b37f9b8 Tracking our problem leads to blame MatAXPY, which does

[petsc-dev] MatAXPY does not increase state

Hi. We are having problems since the MatStructure flag was removed from KSPSetOperators. https://bitbucket.org/petsc/petsc/commits/b37f9b8 Tracking our problem leads to blame MatAXPY, which does not increase the state of the first Mat argument. The attached patch fixes the problem for us. Is

[petsc-dev] options_left

Now in 'master' mistyped/unused options are not displayed unless -options_left is specified. Is this intentional? If so, this change should appear in the list of changes. Another question: I could use some of the additions to branch prbrune/removeunwrappedmathfunctions, but this branch has not

Re: [petsc-dev] Migrate SLEPc to bitbucket

El 09/07/2013, a las 03:01, Jed Brown escribió: Jose E. Roman jro...@dsic.upv.es writes: Now that slepc-3.4 is out, I would like to migrate the SLEPc repository to bitbucket. I think it is good to have a user experience and workflow as close to PETSc as possible. Great, would you prefer

[petsc-dev] Migrate SLEPc to bitbucket

Now that slepc-3.4 is out, I would like to migrate the SLEPc repository to bitbucket. I think it is good to have a user experience and workflow as close to PETSc as possible. To avoid sending lots of emails to the list, I would appreciate if anyone can volunteer to help me in the process

  1   2   >