Re: [petsc-users] Multiple in-flight communications with PetscSFs

2015-02-07 Thread Lawrence Mitchell
On 6 Feb 2015, at 18:09, Jed Brown j...@jedbrown.org wrote: Lawrence Mitchell lawrence.mitch...@imperial.ac.uk writes: ... Or is this not something that is supposed to work at all and I'm just lucky. It's supposed to work, but I think not tested. Can you test the above (have the

Re: [petsc-users] Multiple in-flight communications with PetscSFs

2015-02-07 Thread Jed Brown
Lawrence Mitchell lawrence.mitch...@imperial.ac.uk writes: Thanks, patch (plus simple test) here https://bitbucket.org/petsc/petsc/pull-request/255/sf-fix-multiple-in-flight-comm-rounds-for/diff Thanks; I'll test here. Before this change the communication completion into A get's B's data and

[petsc-users] KSP with Nested Matrix and Vector

2015-02-07 Thread Ce Qin
Dear all, I'm trying to use the KSP solver with nested matrix and vector. If I do not call KSPSetup it goes just fine. When I call the KSPSetUp I am getting the following error [0]PETSC ERROR: Invalid argument [0]PETSC ERROR: Nest vector arguments 1 and 2 have different numbers of blocks.

Re: [petsc-users] MUMPS causing segmentation fault

2015-02-07 Thread Jed Brown
Barry Smith bsm...@mcs.anl.gov writes: Each version of external packages generally work with a very limited (often one) version of other external packages, hence using --download-xxx for everything is the way to go since we have tested them in this combination. Hoping that

Re: [petsc-users] MUMPS causing segmentation fault

2015-02-07 Thread Barry Smith
On Feb 6, 2015, at 11:35 PM, Manav Bhatia bhatiama...@gmail.com wrote: I am using metis and permetis from macports: versions 5.1.0_3 and 4.0.3_3, respectively. They both seem to be the latest versions. Do as Satish said use --download-metis --download-parmetis instead. Use this for all

Re: [petsc-users] Multiple in-flight communications with PetscSFs

2015-02-07 Thread Barry Smith
Lawrence, In general we do not want XXXSetFromOptions() to be randomly called deep within constructors or other places. Ideally we want them called either when I user calls them directly or from another YYYSetFromOptions() that the user called. We do violate this rule occasionally