Re: [petsc-dev] WTF

On Thu, Jun 30, 2016 at 8:48 PM, Jeff Hammond wrote: > > The default settings often don’t work well for 3D problems. > > Are 2D (1D?) problems really the common case for PDE solvers? Aren't > interesting problems 3D? Shouldn't the defaults be set to optimize for 3D? >

Re: [petsc-dev] asm / gasm

Garth: we have something for you to try: branch barry/fix-gamg-asm-aggs add: -pc_gamg_use_agg_asm -mg_levels_sub_pc_type lu > > > > I added some code to add a block on each processor for any singletons, > because the MIS code strips these (so, yes, not a true MIS). I should do > this for users

Re: [petsc-dev] asm / gasm

Thanks Barry, ... we are still not communicating (see below). On Sun, Jun 26, 2016 at 11:56 PM, Barry Smith wrote: > > I have changed the GAMG aggs support to use PCASM and not PCGASM. I > don't see how it ever worked with PCGASM; very strange. Maybe it was > written and

Re: [petsc-dev] asm / gasm

GASM does assume the index set includes every equation in the matrix. It should probably check this as it has pmat. I guess I can add these BC vertices in. On Sun, Jun 26, 2016 at 11:20 AM, Mark Adams <mfad...@lbl.gov> wrote: > Fande, > > An alternative debug path that

Re: [petsc-dev] regression in master

OK, this comes from '--with-viewfromoptions=0' On Sun, Jun 26, 2016 at 2:15 PM, Mark Adams <mfad...@lbl.gov> wrote: > This is puzzling but this seems to be a problem from Feb 28. How could > this be broken for this long ... > > 14:10 (27b0f28...)|BISECTING ~/Codes/pet

Re: [petsc-dev] regression in master

2ba839557306 010eacea0d6a858466b21641de11a1ee3089763b M config :04 04 52698dd9a2c4e4a4ac740457407730108ed9a0b7 202bf4b8bba01b04e74da4db3f5abf6e23ef4662 M src On Sun, Jun 26, 2016 at 1:12 PM, Mark Adams <mfad...@lbl.gov> wrote: > I am finding ksp_[view|monitor|converged_re

Re: [petsc-dev] asm / gasm

Fande, An alternative debug path that may be simpler and direct, as it works with master: 'make runex56' in ksp/examples/tutorials in branch mark/gamg-agg-asm. This runs clean in valgrind (for me), I've added an ISView call to see the data that causes the error, it runs on one processor, uses a

Re: [petsc-dev] asm / gasm

Note, I just pushed a 1 processor example and I am using KSP ex56, not SNES.

Re: [petsc-dev] asm / gasm

On Fri, Jun 24, 2016 at 4:52 PM, Mark Adams <mfad...@lbl.gov> wrote: > OK, but how should I proceed? > > On Fri, Jun 24, 2016 at 4:47 PM, Barry Smith <bsm...@mcs.anl.gov> wrote: > >> >> > On Jun 24, 2016, at 9:35 AM, Mark Adams <mfad...@lbl.gov> wrote:

Re: [petsc-dev] asm / gasm

OK, but how should I proceed? On Fri, Jun 24, 2016 at 4:47 PM, Barry Smith <bsm...@mcs.anl.gov> wrote: > > > On Jun 24, 2016, at 9:35 AM, Mark Adams <mfad...@lbl.gov> wrote: > > > > Barry, > > > > ASM worked before GASM existed. I've never heard

Re: [petsc-dev] asm / gasm

Also, note that the problem, that I am running, has inactive processors (ie, empty processors) on non-coarsest (ie, grids with smoothers). I don't know if my old problems that (I recall) ASM worked had that. On Fri, Jun 24, 2016 at 4:37 PM, Mark Adams <mfad...@lbl.gov> wrote: > &

Re: [petsc-dev] asm / gasm

-COPTFLAGS="-no-ipo -g -O0" >> --CXXOPTFLAGS="-no-ipo -g -O0" --FOPTFLAGS="-fast -no-ipo -g -O0" >> --download-parmetis --download-metis --with-ssl=0 --with-cc=cc >> --with-clib-autodetect=0 --with-cxx=CC --with-cxxlib-autodetect=0 >> --wi

Re: [petsc-dev] asm / gasm

Barry, ASM worked before GASM existed. I've never heard of GASM until yesterday, other than seeing the directory in the source. It has been so long, I could probably hunt for a working version, but who cares, we are going to roll back 5 years? > > In branch mark/gamg-agg-asm in ksp ex56, 'make

Re: [petsc-dev] Problem with GAMG

have seen this before, but I forget what to do about it. That is getting the B matrix to have compressed row storage. Do you recall? Thanks, Mark On Thu, Jun 23, 2016 at 7:59 PM, Mark Adams <mfad...@lbl.gov> wrote: > > > On Wed, Jun 22, 2016 at 11:27 PM, Barry Smith <bsm...@

Re: [petsc-dev] asm / gasm

aij/mpi/mpiov.c [1]PETSC ERROR: - Error Message -- On Thu, Jun 23, 2016 at 8:05 PM, Barry Smith <bsm...@mcs.anl.gov> wrote: > > Where is the command line that generates the error? > > > > On Jun 23, 2016, at 12:08 A

Re: [petsc-dev] Problem with GAMG

On Wed, Jun 22, 2016 at 11:27 PM, Barry Smith wrote: > > Mark, > > If I use the hem coarsen type I get this error. Does this go away with mis? Don't bother testing, it probably does. > Note that I am setting the -pc_gamg_sym_graph true flag I the debugger I > do

Re: [petsc-dev] asm / gasm

/src/ksp/ksp/examples/tutorials/ex56.c On Thu, Jun 23, 2016 at 7:08 AM, Mark Adams <mfad...@lbl.gov> wrote: > [adding Garth] > > On Thu, Jun 23, 2016 at 12:52 AM, Barry Smith <bsm...@mcs.anl.gov> wrote: > >> >> Mark, >> >>I think there is

Re: [petsc-dev] asm / gasm

le=1 --with-hdf5-dir=/Users/markadams/Codes/hdf5 --with-x=0 --with-debugging=1 PETSC_ARCH=arch-macosx-gnu-g --download-chaco > [3]PETSC ERROR: #1 VecScatterCreate_PtoS() line 2348 in /Users/markadams/Codes/petsc/src/vec/vec/utils/vpscat.c > [3]PETSC ERROR: #2 VecScatterCreate() line 1552 i

Re: [petsc-dev] asm / gasm

> Oh wow. So no view with ASM, Garth, you will need to configure with '--with-viewfromoptions=0' > > -- Boyce > > > -- Boyce > > I guess we should have a flag or not iterate over the blocks in ASMView ... > > >> >> -- Boyce >> >> >> Bar

Re: [petsc-dev] asm / gasm

rs) accidentally using view and crashing the run with output. I guess we should have a flag or not iterate over the blocks in ASMView ... > > -- Boyce > > > Barry > > On Jun 22, 2016, at 7:51 AM, Mark Adams <mfad...@lbl.gov> wrote: > > I'm trying to get block smoothe

Re: [petsc-dev] asm / gasm

vector communication costs are not bad, it probably does not include (too many) new processors to communicate with. >Barry > > > On Jun 22, 2016, at 7:51 AM, Mark Adams <mfad...@lbl.gov> wrote: > > > > I'm trying to get block smoothers to work for gamg. We (Garth

Re: [petsc-dev] asm / gasm

On Wed, Jun 22, 2016 at 5:13 PM, Matthew Knepley <knep...@gmail.com> wrote: > On Wed, Jun 22, 2016 at 5:51 AM, Mark Adams <mfad...@lbl.gov> wrote: > >> I'm trying to get block smoothers to work for gamg. We (Garth) tried >> this and got this error: >

[petsc-dev] asm / gasm

I'm trying to get block smoothers to work for gamg. We (Garth) tried this and got this error: - Another option is use '-pc_gamg_use_agg_gasm true' and use > '-mg_levels_pc_type gasm'. > > Running in parallel, I get ** Max-trans not allowed because matrix is distributed First, what

[petsc-dev] Fortran strings

Wrapper code like this does is not working for Robert: subroutine my_PetscOptionsClearValue(value,ierr) use petscsys implicit none character(len=250), intent(in) :: value PetscErrorCode, intent(inout) :: ierr #if PETSC_VERSION_LT(3,7,0) call PetscOptionsClearValue(value,ierr) #else

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

OK, I squashed, fixed the push line (and also did --global pull.ff only), and pushed. On Fri, May 27, 2016 at 9:07 AM, Jed Brown <j...@jedbrown.org> wrote: > Mark Adams <mfad...@lbl.gov> writes: > > >> > >> Satish, please don't use this syntax for force pushes

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > Satish, please don't use this syntax for force pushes. Prefer > > git push origin +mark/snes-ex65c > 08:13 mark/snes-ex56c<> ~/Codes/petsc$ git push origin +mark/snes-ex65c error: src refspec mark/snes-ex65c does not match any. error: failed to push some refs to

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > Mark, > > I ran 'alltest' for master - and 'mark/snes-ex56c' reverted some > output file changes that shouldn't have been made [and some makefile > changes] - and added one additional one that shows diffs. > > thanks. > ./configure --download-metis --download-parmetis --download-ml >

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 1:01 PM, Satish Balay <ba...@mcs.anl.gov> wrote: > On Wed, 25 May 2016, Mark Adams wrote: > > > I'm doing an all test right now, what should I do after that? > > You have a PR on this branch. It gets automatically updated with all > the cha

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

use 'cheby' - but still you have to modify this file? > > Yea, I don't why I seem to have changed that one in the update. I think it just looked like a small change that was not meaningful. Mark > Satish > > $ git log --stat master..mark/snes-ex56c |cat > commit b4c92c7bf05a5d7c

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

I'm doing an all test right now, what should I do after that? On Wednesday, May 25, 2016, Satish Balay <ba...@mcs.anl.gov> wrote: > On Wed, 25 May 2016, Mark Adams wrote: > > > On Wed, May 25, 2016 at 12:14 PM, Satish Balay <ba...@mcs.anl.gov > <javascript:;>> wr

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 12:14 PM, Satish Balay wrote: > Yeah - Sorry - bad copy/paste gave the wrong commit-id. > > Here this the process you would normally follow [without gitk] > gitk works but it opens Wish. Can I squash in Wish? Anyway, your rebase below worked, I got

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 12:08 PM, Satish Balay wrote: > On Wed, 25 May 2016, Satish Balay wrote: > > > sorry - copy/paste error. > > > > git rebase -i f303cd651cc9f18b5b8505d3b571425f3b3e5c1a > > > > [f303cd651cc9f18b5b8505d3b571425f3b3e5c1a is commit in master - from > where

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

etis commit 5de3a4cbdf1af535fdc82d14bd6ac1ae9d542b9e Author: Mark Adams <cal2prince...@yahoo.com> Date: Sun May 22 16:48:56 2016 -0400 fixed test for new cheby commit c8451888fd20ba830f186674f6df6761f650015e Author: Mark Adams <cal2prince...@yahoo.com> Date: Fri May 20 13:05:06 2016 -0400 up

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > Ok - I've done a 'rebase master' and 'push -f' on mark/snes-ex56c > > You might want to do: > > git checkout mark/snes-ex56c > git rebase -i 7216b81e99debbb3a0e1c5dd0b26b0d24a8a5ac0 > > done, but there was nothing in the rebase ("noop"). This is what I see: noop # Rebase 7216b81..7216b81

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

git branch -D mark/snes-ex56c jed/mark/snes-ex56c > done > > - Then I'll push to 'mark/snes-ex56c' [delete jed/mark/snes-ex56c on > server] > > - After I do my changes - you can start using mark/snes-ex56c > > Satish > > On Wed, 25 May 2016, Mark Adams wrote: &g

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > If thats the case - when you have a merge conflict during 'merge' or > 'rebase' - then you should be able to do 'git mergetool' and easily > resolve the conflict using kdiff3 > > OK, well this looks promising (kdiff3 seems to work, I think we set this up long ago): ... nothing added to

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

k c34fc5a remove spaces > pick 0008a30 fix complex build > pick e78b637 updated test for new cheby > pick 4acf97d fixed test for new cheby > pick fdcaa90 merge makefile changed for ex56 and parmetis > pick f2cb842 fixed bug in makefile > > Satish > > > On Wed, 25 May 201

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > > I have no idea how Mac users use git effectively without a working > 'gitk' [to verify commit diffs] or 'git gui' [to selectively commit > some changes] or 'kdiff3' which I use via 'git mergetool' [for 3-way > merges].. > Yes, I have a lot of things that I would like to be able to do,

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

is this morning and there were about 8 of these conflicts that I had to fix manually. I wanted to check before I proceed. They were straightforward fixes. Mark On Wed, May 25, 2016 at 10:40 AM, Mark Adams <mfad...@lbl.gov> wrote: > > > On Wed, May 25, 2016 at 10:18 AM, Satish Bal

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 10:18 AM, Satish Balay <ba...@mcs.anl.gov> wrote: > On Wed, 25 May 2016, Mark Adams wrote: > > > > > 10:09 mark/snes-ex56c= ~/Codes/petsc/src/snes/examples/tutorials$ git > reset > > --hard f2cb8422898d35ef96e146caa3a95b2f879b25f1 >

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 10:18 AM, Satish Balay <ba...@mcs.anl.gov> wrote: > On Wed, 25 May 2016, Mark Adams wrote: > > > > > 10:09 mark/snes-ex56c= ~/Codes/petsc/src/snes/examples/tutorials$ git > reset > > --hard f2cb8422898d35ef96e146caa3a95b2f879b25f1 >

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > >> 10:09 mark/snes-ex56c= ~/Codes/petsc/src/snes/examples/tutorials$ git > reset --hard f2cb8422898d35ef96e146caa3a95b2f879b25f1 > HEAD is now at f2cb842 fixed bug in makefile > > OK, now what? > > I guess there is not much choice. Pushed. 10:16 1 mark/snes-ex56c<>

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 9:44 AM, Satish Balay <ba...@mcs.anl.gov> wrote: > On Wed, 25 May 2016, Mark Adams wrote: > > > I did 'git rebase -i master', in jed's branch and need to fix about 1/2 > > dozen failures to apply patch. I fixed them, but this does not seem like &g

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

I did 'git rebase -i master', in jed's branch and need to fix about 1/2 dozen failures to apply patch. I fixed them, but this does not seem like what I should be doing. I also had many commits that were not mine, I guess because I pulled from master. I squashed about 8 of mine and kept 2 of

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

revision. So I was pulling from master all the time, by mistake. If I do a rebase -i with /jed/mark/snes-ex56c, will it give me all of the branch to squash? On Wed, May 25, 2016 at 8:16 AM, Mark Adams <mfad...@lbl.gov> wrote: > > > On Wed, May 25, 2016 at 8:00 AM, Jed Brown <

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, May 25, 2016 at 8:00 AM, Jed Brown <j...@jedbrown.org> wrote: > Mark Adams <mfad...@lbl.gov> writes: > > FYI, I get this error from rebasing. I will look into what they suggest. > > What command did you use to rebase? > git rebase master > > I r

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > Firstly - we should not be cherry-picking commits to next. Its an > 'integration branch' i.e any required fixes go into the feature branch > that might have triggered the issue. > So I should just (re)merge my branch with my local next, as I fix it, pull from next, push to next. I am

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

t? Looks like next is way > corrupted - and I should just rewind it to latest master.. > > Satish > > On Tue, 24 May 2016, Satish Balay wrote: > > > On Tue, 24 May 2016, Mark Adams wrote: > > > > > Do I now wait for my pull request to be approved? > > &g

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Tue, May 24, 2016 at 2:53 PM, Satish Balay <ba...@mcs.anl.gov> wrote: > On Tue, 24 May 2016, Mark Adams wrote: > > > Do I now wait for my pull request to be approved? > > Mark, > > Currently there is a bit of mess in regards to your branches. > Yes. This

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

thanks, On Tue, May 24, 2016 at 2:56 PM, Satish Balay wrote: > On Tue, 24 May 2016, Barry Smith wrote: > > > > > After you put something in next you need go to > ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/index.html follow the next > link and click on the all button in the

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

r' tests on dashboard - fix in > feature branch - and merge to master. > Thanks, > > Satish > > On Tue, 24 May 2016, Mark Adams wrote: > > > OK, so you just trust that working in next is proof that it will work in > > master and just 'git merge branch' in master with

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

wrote: > Mark Adams <mfad...@lbl.gov> writes: > > I am merging master more than I need to, just to be up to date. I guess > it > > pollutes the history with all these merges. And I should squash them... > > You shouldn't merge from 'master' unless you need something

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

> > > > Firstly - if you need Matt's stuff (requiring a merge) - that implies > the feature is not yet complete. So it should not be merged to next > [until the feature is complete] > It was in next, but not in master. It is all in master now. > > But if 'Matt does and it is not in master' -

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Fri, May 20, 2016 at 1:17 PM, Satish Balay wrote: > Mark, > > $ git log --merges origin/mark/snes-ex56c --oneline |grep mark/snes-ex56c > 27d400f Merge branch 'master' of bitbucket.org:petsc/petsc into > mark/snes-ex56c > f3dabe8 Merge branch 'master' of

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Tue, May 17, 2016 at 10:55 PM, Barry Smith wrote: > > Mark, > >So it sounds like the right fix is to change the "random" option name > to "noisy" and replace the use of the random number generator with Jed's > hash and make it the default. (Where if you turn off the

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

OK, I thought you were suggesting that: unsigned int hash(unsigned int x) { x = ((x >> 16) ^ x) * 0x45d9f3b; x = ((x >> 16) ^ x) * 0x45d9f3b; x = ((x >> 16) ^ x); return x;} But, Barry is vetoing this. On Tue, May 17, 2016 at 4:18 PM, Jed Brown <j...@jedbrow

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

Why not just set each index with hash(i) = (i >> 32)^i and forget VecSetRandom in here? This does not have to be perfectly decorrelated. Just not perfectly correlated. { PetscErrorCode ierr; PetscInt n = xin->map->n,i; PetscScalar*xx; PetscFunctionBegin; ierr =

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

Other than set userandom = PETSC_TRUE, should I do anything else? I see: ierr = VecSetRandom(B,cheb->random);CHKERRQ(ierr); Should I use a special one or change this default to the special one? On Tue, May 17, 2016 at 3:19 PM, Matthew Knepley wrote: > On Tue, May 17, 2016

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Sat, Aug 22, 2015 at 10:39 PM, Barry Smith <bsm...@mcs.anl.gov> wrote: > > > On Aug 22, 2015, at 9:26 PM, Mark Adams <mfad...@lbl.gov> wrote: > > > > I would vote for (1). > > > > Also, I hope cheb->random is the default. > >Well then

Re: [petsc-dev] KSPsolve

o > zero, the accurate one is TOUGH. Also, if we deal with multiphase flow, > flow is certainly compressible. e.g., for oil-water phase, ct(total fluid > compressibility)=Soco+Swcw, sum of each saturation times compressibility. > (That is, depending on the EOS, the fluid could be

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2015-09-02

Whoops, It looks like I missed this. I think we are all straight now. Mark On Wed, Sep 2, 2015 at 3:25 PM, Satish Balay wrote: > Mark, > > I've attempted to fix this [and pushed my fix to mark/eigen-rand] > >

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

What global idea? Even with something simple like DMDA the global idea of a variable depends on the number of processes, similarly if one is doing any kind of partitioner on the unknowns the ordering changes with the number of processors. The point is that it is possible to have a

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

Is there a good way to get a deterministic rand wrt number of processors? Seeding rand for each entry, with its global ID would work I assume. If drand48 is just one line then why not just copy it tweak it as desired? Cheby is otherwise deterministic, with a deterministic PC, and we have

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

What should I do if the DIVERGE_ITS test fails? I assume abort. And I assume I can put these two items (Cheby solve test and put petsc rand vectors back in GAMG and Cheby) in one branch. On Thu, Aug 27, 2015 at 5:50 PM, Jed Brown j...@jedbrown.org wrote: Mark Adams mfad...@lbl.gov writes

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

at 12:48 PM, Jed Brown j...@jedbrown.org wrote: Mark Adams mfad...@lbl.gov writes: My hash function is: PetscScalar v = ((PetscScalar)((PETSC_HASH_FACT*idx)%100) - 49.5)/50.0; ierr = VecSetValues(bb, 1, idx, v, INSERT_VALUES);CHKERRQ(ierr); include

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

OK, I can put PetscRandom back into GAMG and add a check for DIVERGE_ITS in the Cheby solve. Is that necessary and sufficient? Mark On Thu, Aug 27, 2015 at 4:25 PM, Matthew Knepley knep...@gmail.com wrote: On Thu, Aug 27, 2015 at 2:17 PM, Barry Smith bsm...@mcs.anl.gov wrote: On Aug 27,

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Wed, Aug 26, 2015 at 3:30 PM, Jed Brown j...@jedbrown.org wrote: Mark Adams mfad...@lbl.gov writes: I really think that it does not matter. Just as long as it is noisy. IMO, but we have no data, and I'm not sure how we could study it. What is the chance that your generator

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

My hash function is: PetscScalar v = ((PetscScalar)((PETSC_HASH_FACT*idx)%100) - 49.5)/50.0; ierr = VecSetValues(bb, 1, idx, v, INSERT_VALUES);CHKERRQ(ierr); include/petscctable.h:#define PETSC_HASH_FACT 79943 On Thu, Aug 27, 2015 at 7:53 AM, Mark Adams mfad...@lbl.gov

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

I agree that we should be using a random starting vector for spectral estimates. I'm not overly concerned whether it's a hash of the global ID or a deterministic seed, but let's use something that has been studied. I really think that it does not matter. Just as long as it is noisy.

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

On Sat, Aug 22, 2015 at 10:39 PM, Barry Smith bsm...@mcs.anl.gov wrote: On Aug 22, 2015, at 9:26 PM, Mark Adams mfad...@lbl.gov wrote: Good point. I can not see any reason to use the initial guess for the eigen estimate. Why not, won't it better select for the eigen space actually

Re: [petsc-dev] strangness in Chebyshev estimate of eigenvalues

Good point. I can not see any reason to use the initial guess for the eigen estimate. I would vote for (1). Also, I hope cheb-random is the default. One of my apps uses a zero RHS for the first solve, just because they did not care about adding some logic like: if (.not. first_solve) solve()

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (master) 2015-08-11

Whoops, I did it just now and put it un my branch, that I will merge this week. On Tue, Aug 11, 2015 at 11:18 PM, Satish Balay ba...@mcs.anl.gov wrote: pushed a fix for this issue. satish On Tue, 11 Aug 2015, PETSc checkBuilds wrote: Dear PETSc developer, This email contains

[petsc-dev] web page needs attention ...

http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/PetscOptionsBool.html#PetscOptionsBool has PetscOptionsBool_Private in the body. Mark

Re: [petsc-dev] use of random numbers in GAMG

We have three problems here (at least). 1) I use PETSc's random vectors to compute an eigen estimate. 2) I use srand() to mix up the graph ordering for the MIS. I could write a hash function like thing that takes the global ID and generates a (bad) random number. These random number do not

Re: [petsc-dev] config fail on OSX with master

On Fri, 19 Jun 2015, Mark Adams wrote:

Re: [petsc-dev] did Matt break next?

never mind, working now. On Fri, Jun 19, 2015 at 11:57 AM, Mark Adams mfad...@lbl.gov wrote:

Re: [petsc-dev] gamg regression

if works, without your fix? 'git fetch; git checkout mark/gamg-crs', Mark On Wed, Jun 17, 2015 at 1:03 PM, Stephan Kramer s.kra...@imperial.ac.uk wrote: On 17/06/15 17:37, Mark Adams wrote: Second question (less important): I didn't manage to change this at the command line. I

Re: [petsc-dev] gamg regression

Second question (less important): I didn't manage to change this at the command line. I would have thought -mg_coarse_ksp_type preonly should have done the trick but seemed to be ignored. Instead I had to do it with some calls in the code: Humm, this seems to work for me (I just cut

Re: [petsc-dev] gamg regression

On Tue, Jun 16, 2015 at 12:21 PM, Stephan Kramer s.kra...@imperial.ac.uk wrote: Dear petsc-devs I spent quite some time chasing a regression using gamg. This is solving a 2D Stokes problem for velocity only in a cylindrical domain with free slip and large viscosity contrasts - for which we

Re: [petsc-dev] ML via --download-ml

FYI, ML has some different defaults (eg, its threshold is 0 and GAMG is finite as I recall). I have verified GAMG against ML a year or so ago, but I had to set: -pc_gamg_threshold 0. Mark On Fri, Jun 12, 2015 at 7:38 AM, Matthew Knepley knep...@gmail.com wrote: On Fri, Jun 12, 2015 at 6:24 AM,

Re: [petsc-dev] printing matlab vectors

? I want Vec_0xc409_0 to be 'vec_name' Mark On Thu, Jun 11, 2015 at 8:06 PM, Jed Brown j...@jedbrown.org wrote: Mark Adams mfad...@lbl.gov writes: I am printing matlab vectors and I have a matlab script to read these files, take differences, etc. PETSc name the vectors (eg

Re: [petsc-dev] printing matlab vectors

Oh, duh, I put the name on the viewer and not the vector. On Fri, Jun 12, 2015 at 8:54 AM, Mark Adams mfad...@lbl.gov wrote: I do this: call VecCreateSeqWithArray(PETSC_COMM_SELF,ione,n64,phi,vec,ierr);CHKERRQ(ierr) call PetscViewerASCIIOpen(PETSC_COMM_SELF, file_name, viewer,ierr

[petsc-dev] printing matlab vectors

I am printing matlab vectors and I have a matlab script to read these files, take differences, etc. PETSc name the vectors (eg, Vec_0xc409_0) in a non-deterministic way as far as I can tell. Can I specify a name to make my workflow more automatic? Mark

Re: [petsc-dev] Titan error

BTW, it looks like you can configure PETSc from a home directory now on Titan. I still get this same permissions error when I try the installation with the prefix. Mark On Fri, Jun 5, 2015 at 4:24 PM, Mark Adams mfad...@lbl.gov wrote: This works without prefix. I tried prefixing

Re: [petsc-dev] Titan error

to test for write access by creating the directory; first in the shell and then from python? Did it work? Barry On Jun 8, 2015, at 5:32 PM, Mark Adams mfad...@lbl.gov wrote: BTW, it looks like you can configure PETSc from a home directory now on Titan. I still get this same permissions

Re: [petsc-dev] Titan error

:56 AM, Mark Adams mfad...@lbl.gov wrote: On Thu, Jun 4, 2015 at 10:53 PM, Barry Smith bsm...@mcs.anl.gov wrote: Hmm, You do not have write permissions to the --prefix directory /autofs/na3_home1/adams/petsc_master_opt64idx_pgi You will be prompted for the sudo

Re: [petsc-dev] Titan error

with a prefix, just to see if that is the only problem. Barry On Jun 4, 2015, at 9:43 PM, Mark Adams mfad...@lbl.gov wrote: Yet again, this one does have a slightly amusing and slightly baffling error message though. Mark configure.log

Re: [petsc-dev] Titan error

. So try: make PETSC_DIR=/autofs/nccs-svm1_home1/adams/petsc_treb PETSC_ARCH=arch-titan-opt64idx-pgi Mark On Fri, Jun 5, 2015 at 9:56 AM, Mark Adams mfad...@lbl.gov wrote: On Thu, Jun 4, 2015 at 10:53 PM, Barry Smith bsm...@mcs.anl.gov wrote: Hmm, You do not have write permissions

Re: [petsc-dev] memory leak

at 1:46 PM, Satish Balay ba...@mcs.anl.gov wrote: On Mon, 1 Jun 2015, Mark Adams wrote: Also 'git-prompt.sh' helps in tracking changes to any giving 'branch' wrt 'origin/branch'.. [assuming you do a 'git fetch' to sync changes from remote repo] I use (a) git-prompt.sh

Re: [petsc-dev] memory leak

. # nothing to commit (working directory clean) 19:11 edison03 master ~/petsc$ On Sun, May 31, 2015 at 10:02 PM, Mark Adams mfad...@lbl.gov wrote: This is coming from this line (last): #undef __FUNCT__ #define __FUNCT__ PCFieldSplitGetSubKSP_FieldSplit_Schur static PetscErrorCode

Re: [petsc-dev] memory leak

On Mon, Jun 1, 2015 at 8:05 AM, Matthew Knepley knep...@gmail.com wrote: On Sun, May 31, 2015 at 9:20 PM, Mark Adams mfad...@lbl.gov wrote: I have asked this question before but I still do not understand what git is doing here. I pulled, made a fix, did a git status, and I see that I am 7

Re: [petsc-dev] memory leak

status # On branch master # Your branch is ahead of 'origin/master' by 8 commits. # nothing to commit (working directory clean) 19:11 edison03 master ~/petsc$ On Sun, May 31, 2015 at 10:02 PM, Mark Adams mfad...@lbl.gov wrote: This is coming from this line (last): #undef __FUNCT__ #define

Re: [petsc-dev] memory leak

On Mon, Jun 1, 2015 at 10:59 AM, Satish Balay ba...@mcs.anl.gov wrote: On Mon, 1 Jun 2015, Mark Adams wrote: Let me summarize what I did (and showed the raw output in my original email) on a branch named master that is from a relatively new clone: git pull origin master If you

Re: [petsc-dev] memory leak

On Mon, Jun 1, 2015 at 9:23 AM, Matthew Knepley knep...@gmail.com wrote: On Mon, Jun 1, 2015 at 8:08 AM, Mark Adams mfad...@lbl.gov wrote: Send the command that you used to create the branch. Matt, I just cloned PETSc/master. I did not create any branches. 1) Cloning just creates

Re: [petsc-dev] memory leak

Thanks, On Mon, Jun 1, 2015 at 11:15 AM, Satish Balay ba...@mcs.anl.gov wrote: On Mon, 1 Jun 2015, Mark Adams wrote: To see what the local commits are - You would do: git fetch # this way origin/master is the latest git log origin/master..master or gitk origin/master..master

Re: [petsc-dev] memory leak

Also 'git-prompt.sh' helps in tracking changes to any giving 'branch' wrt 'origin/branch'.. [assuming you do a 'git fetch' to sync changes from remote repo] I use (a) git-prompt.sh. It shows the branch in the prompt. How does it help? Does it do the .. stuff? Satish

Re: [petsc-dev] memory leak

On Sat, May 30, 2015 at 10:51 PM, Barry Smith bsm...@mcs.anl.gov wrote: Need more details. How can we reproduce this? I was hoping this would be obvious. a missed free. What tests use Schur solvers? I could see if they have the same problem. Barry On May 30, 2015, at 7:10 PM, Mark

Re: [petsc-dev] VecGetArrayReadF90 ???

Got it, its working. Thanks. On Sun, May 31, 2015 at 1:14 PM, Barry Smith bsm...@mcs.anl.gov wrote: I've added the manual pages for master On May 30, 2015, at 2:01 PM, Mark Adams mfad...@lbl.gov wrote: Its not here: http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages

Re: [petsc-dev] memory leak

a PetscFree(tksp) here? On Sun, May 31, 2015 at 7:24 PM, Mark Adams mfad...@lbl.gov wrote: On Sat, May 30, 2015 at 10:51 PM, Barry Smith bsm...@mcs.anl.gov wrote: Need more details. How can we reproduce this? I was hoping this would be obvious. a missed free. What tests use Schur solvers

Re: [petsc-dev] memory leak

) 19:11 edison03 master ~/petsc$ On Sun, May 31, 2015 at 10:02 PM, Mark Adams mfad...@lbl.gov wrote: This is coming from this line (last): #undef __FUNCT__ #define __FUNCT__ PCFieldSplitGetSubKSP_FieldSplit_Schur static PetscErrorCode PCFieldSplitGetSubKSP_FieldSplit_Schur(PC pc,PetscInt

<    4   5   6   7   8   9   10   11   >