Re: [petsc-dev] gitlab migration for pull request

2019-09-11 Thread Balay, Satish via petsc-dev
On Wed, 11 Sep 2019, Jed Brown via petsc-dev wrote: > Please fork the repository on GitLab > (https://gitlab.com/petsc/petsc/-/forks/new) and push your branch to the > fork, then make a merge request. If you become a regular contributor, > we can give you push privileges to the main repository.

Re: [petsc-dev] MAT_HERMITIAN

2019-09-11 Thread Smith, Barry F. via petsc-dev
The phrase Hermitian symmetric was originally an attempt to make the text clearer, but in fact it is confusing and wrong. The phrase Hermitian symmetric should be removed and just Hermitian used. Real matrices are either either both symmetric and Hermitian or not symmetric and not

Re: [petsc-dev] gitlab migration for pull request

2019-09-11 Thread Balay, Satish via petsc-dev
On Wed, 11 Sep 2019, Pierre Gosselet via petsc-dev wrote: > Dear all, > I am sorry, I have not understood how to migrate Push Request from > bitbucket to gitlab. > > I think I need the equivalent of > git remote set-url origin https://gitlab.com/petsc/petsc.git > applied to my development branch

Re: [petsc-dev] gitlab migration for pull request

2019-09-11 Thread Jed Brown via petsc-dev
Please fork the repository on GitLab (https://gitlab.com/petsc/petsc/-/forks/new) and push your branch to the fork, then make a merge request. If you become a regular contributor, we can give you push privileges to the main repository. Pierre Gosselet via petsc-dev writes: > Dear all, > I am

[petsc-dev] gitlab migration for pull request

2019-09-11 Thread Pierre Gosselet via petsc-dev
Dear all, I am sorry, I have not understood how to migrate Push Request from bitbucket to gitlab. I think I need the equivalent of git remote set-url origin https://gitlab.com/petsc/petsc.git applied to my development branch (I see that my branch's remote is incorrect in .git/config). Or am I

Re: [petsc-dev] MAT_HERMITIAN

2019-09-11 Thread Pierre Jolivet via petsc-dev
(Putting back petsc-dev on c/c) I don’t think you are the one that needs to do the changes. There should be clarifications from the PETSc side of things, first. From the man page your are quoting (https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MATSEQSBAIJ.html

Re: [petsc-dev] MAT_HERMITIAN

2019-09-11 Thread Jose E. Roman via petsc-dev
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] MAT_HERMITIAN

2019-09-11 Thread Pierre Jolivet via petsc-dev
Nevermind, this is the wrong fix. The proper fix is in PETSc. It should not error out if the matrix is also symmetric. Indeed, complex symmetric Hermitian => complex with no imaginary part. Thus all operations like MatMult, MatMultHermitianTranspose, Cholesky… will work for bs > 1, since all is