[petsc-dev] Stop breaking my build
libfast in: /PETSc3/petsc/petsc-dev/src/snes/impls/lsvi lsvi.c: In function 'PetscErrorCode SNESLSVIComputeMeritFunction(_p_Vec*, PetscScalar*)': lsvi.c:137: error: no matching function for call to 'VecNormBegin(_p_Vec*&, NormType, PetscScalar*)' /PETSc3/petsc/petsc-dev/include/petscvec.h:468: note: candidates are: PetscErrorCode VecNormBegin(_p_Vec*, NormType, PetscReal*) /PETSc3/petsc/petsc-dev/include/petscvec.h:469: note: PetscErrorCode VecNormBegin(_p_Vec*, NormType) /PETSc3/petsc/petsc-dev/include/petscvec.h:470: note: PetscErrorCode VecNormBegin(_p_Vec*) lsvi.c:138: error: no matching function for call to 'VecNormEnd(_p_Vec*&, NormType, PetscScalar*)' /PETSc3/petsc/petsc-dev/include/petscvec.h:471: note: candidates are: PetscErrorCode VecNormEnd(_p_Vec*, NormType, PetscReal*) /PETSc3/petsc/petsc-dev/include/petscvec.h:472: note: PetscReal VecNormEnd(_p_Vec*, NormType) /PETSc3/petsc/petsc-dev/include/petscvec.h:473: note: PetscReal VecNormEnd(_p_Vec*) lsvi.c: In function 'PetscErrorCode SNESLSVIComputeSSFunction(_p_SNES*, _p_Vec*, _p_Vec*)': lsvi.c:207: error: no match for 'operator<=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + l) <= -1.0e+20' lsvi.c:207: error: no match for 'operator>=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + u) >= 1.0e+20' lsvi.c:210: error: no match for 'operator<=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + l) <= -1.0e+20' lsvi.c:215: error: no match for 'operator>=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + u) >= 1.0e+20' lsvi.c: In function 'PetscErrorCode SNESLSVIComputeBsubdifferential(_p_SNES*, _p_Vec*, _p_Vec*, _p_Mat*, _p_Mat*, MatStructure*)': lsvi.c:279: error: no match for 'operator<=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + l) <= -1.0e+20' lsvi.c:279: error: no match for 'operator>=' in '*(((PetscScalar*)(((long unsigned int)i) * 16ul)) + u) >= 1.0e+20' lsvi.c: In function 'PetscErrorCode SNESLSVICheckDescentDirection(_p_SNES*, _p_Vec*, _p_Vec*, PetscTruth*)': lsvi.c:360: error: no matching function for call to 'VecNormBegin(_p_Vec*&, NormType, PetscScalar*)' /PETSc3/petsc/petsc-dev/include/petscvec.h:468: note: candidates are: PetscErrorCode VecNormBegin(_p_Vec*, NormType, PetscReal*) /PETSc3/petsc/petsc-dev/include/petscvec.h:469: note: PetscErrorCode VecNormBegin(_p_Vec*, NormType) /PETSc3/petsc/petsc-dev/include/petscvec.h:470: note: PetscErrorCode VecNormBegin(_p_Vec*) lsvi.c:361: error: no matching function for call to 'VecNormEnd(_p_Vec*&, NormType, PetscScalar*)' /PETSc3/petsc/petsc-dev/include/petscvec.h:471: note: candidates are: PetscErrorCode VecNormEnd(_p_Vec*, NormType, PetscReal*) /PETSc3/petsc/petsc-dev/include/petscvec.h:472: note: PetscReal VecNormEnd(_p_Vec*, NormType) /PETSc3/petsc/petsc-dev/include/petscvec.h:473: note: PetscReal VecNormEnd(_p_Vec*) lsvi.c:365: error: no match for 'operator>' in 'dpsidotY > rhs' lsvi.c: In function 'PetscErrorCode SNESSolve_LSVI(_p_SNES*)': lsvi.c:469: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment lsvi.c:471: error: cannot convert 'PetscScalar' to 'double' in assignment lsvi.c:472: error: cannot convert 'PetscScalar' to 'PetscReal' in argument passing lsvi.c:475: error: cannot convert 'std::complex' to 'PetscReal' in assignment lsvi.c:477: error: cannot convert 'PetscScalar' to 'PetscReal' in argument passing lsvi.c:521: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment lsvi.c:522: error: cannot convert 'PetscScalar' to 'PetscReal' in argument passing lsvi.c:523: warning: cannot pass objects of non-POD type 'struct PetscScalar' through '...'; call will abort at runtime lsvi.c:545: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment lsvi.c:551: error: cannot convert 'PetscScalar' to 'PetscReal' in argument passing ar: lsvi.o: No such file or directory Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/0a599e9b/attachment.html>
[petsc-dev] Stop breaking my build
Matt, Nobody knows how you build stuff. Atleast mention the configure command used so it can be reproduced and fixed.. Satish On Thu, 19 Aug 2010, Matthew Knepley wrote: > libfast in: /PETSc3/petsc/petsc-dev/src/snes/impls/lsvi > lsvi.c: In function 'PetscErrorCode SNESLSVIComputeMeritFunction(_p_Vec*, > PetscScalar*)': > lsvi.c:137: error: no matching function for call to 'VecNormBegin(_p_Vec*&, > NormType, PetscScalar*)' > /PETSc3/petsc/petsc-dev/include/petscvec.h:468: note: candidates are: > PetscErrorCode VecNormBegin(_p_Vec*, NormType, PetscReal*) > /PETSc3/petsc/petsc-dev/include/petscvec.h:469: note: > PetscErrorCode VecNormBegin(_p_Vec*, NormType) > /PETSc3/petsc/petsc-dev/include/petscvec.h:470: note: > PetscErrorCode VecNormBegin(_p_Vec*) > lsvi.c:138: error: no matching function for call to 'VecNormEnd(_p_Vec*&, > NormType, PetscScalar*)' > /PETSc3/petsc/petsc-dev/include/petscvec.h:471: note: candidates are: > PetscErrorCode VecNormEnd(_p_Vec*, NormType, PetscReal*) > /PETSc3/petsc/petsc-dev/include/petscvec.h:472: note: > PetscReal VecNormEnd(_p_Vec*, NormType) > /PETSc3/petsc/petsc-dev/include/petscvec.h:473: note: > PetscReal VecNormEnd(_p_Vec*) > lsvi.c: In function 'PetscErrorCode SNESLSVIComputeSSFunction(_p_SNES*, > _p_Vec*, _p_Vec*)': > lsvi.c:207: error: no match for 'operator<=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + l) <= -1.0e+20' > lsvi.c:207: error: no match for 'operator>=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + u) >= 1.0e+20' > lsvi.c:210: error: no match for 'operator<=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + l) <= -1.0e+20' > lsvi.c:215: error: no match for 'operator>=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + u) >= 1.0e+20' > lsvi.c: In function 'PetscErrorCode > SNESLSVIComputeBsubdifferential(_p_SNES*, _p_Vec*, _p_Vec*, _p_Mat*, > _p_Mat*, MatStructure*)': > lsvi.c:279: error: no match for 'operator<=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + l) <= -1.0e+20' > lsvi.c:279: error: no match for 'operator>=' in '*(((PetscScalar*)(((long > unsigned int)i) * 16ul)) + u) >= 1.0e+20' > lsvi.c: In function 'PetscErrorCode SNESLSVICheckDescentDirection(_p_SNES*, > _p_Vec*, _p_Vec*, PetscTruth*)': > lsvi.c:360: error: no matching function for call to 'VecNormBegin(_p_Vec*&, > NormType, PetscScalar*)' > /PETSc3/petsc/petsc-dev/include/petscvec.h:468: note: candidates are: > PetscErrorCode VecNormBegin(_p_Vec*, NormType, PetscReal*) > /PETSc3/petsc/petsc-dev/include/petscvec.h:469: note: > PetscErrorCode VecNormBegin(_p_Vec*, NormType) > /PETSc3/petsc/petsc-dev/include/petscvec.h:470: note: > PetscErrorCode VecNormBegin(_p_Vec*) > lsvi.c:361: error: no matching function for call to 'VecNormEnd(_p_Vec*&, > NormType, PetscScalar*)' > /PETSc3/petsc/petsc-dev/include/petscvec.h:471: note: candidates are: > PetscErrorCode VecNormEnd(_p_Vec*, NormType, PetscReal*) > /PETSc3/petsc/petsc-dev/include/petscvec.h:472: note: > PetscReal VecNormEnd(_p_Vec*, NormType) > /PETSc3/petsc/petsc-dev/include/petscvec.h:473: note: > PetscReal VecNormEnd(_p_Vec*) > lsvi.c:365: error: no match for 'operator>' in 'dpsidotY > rhs' > lsvi.c: In function 'PetscErrorCode SNESSolve_LSVI(_p_SNES*)': > lsvi.c:469: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment > lsvi.c:471: error: cannot convert 'PetscScalar' to 'double' in assignment > lsvi.c:472: error: cannot convert 'PetscScalar' to 'PetscReal' in argument > passing > lsvi.c:475: error: cannot convert 'std::complex' to 'PetscReal' in > assignment > lsvi.c:477: error: cannot convert 'PetscScalar' to 'PetscReal' in argument > passing > lsvi.c:521: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment > lsvi.c:522: error: cannot convert 'PetscScalar' to 'PetscReal' in argument > passing > lsvi.c:523: warning: cannot pass objects of non-POD type 'struct > PetscScalar' through '...'; call will abort at runtime > lsvi.c:545: error: cannot convert 'PetscScalar' to 'PetscReal' in assignment > lsvi.c:551: error: cannot convert 'PetscScalar' to 'PetscReal' in argument > passing > ar: lsvi.o: No such file or directory > >Matt > >
[petsc-dev] Stop breaking my build
On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay wrote: > Matt, > > Nobody knows how you build stuff. Atleast mention the configure > command used so it can be reproduced and fixed.. Complex: http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/build_arch-linux-complex-gcov_steamroller.log Jed
[petsc-dev] Stop breaking my build
On Thu, 19 Aug 2010, Jed Brown wrote: > On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay > wrote: > > Matt, > > > > Nobody knows how you build stuff. Atleast mention the configure > > command used so it can be reproduced and fixed.. > > Complex: > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/build_arch-linux-complex-gcov_steamroller.log yeah - I guess I should search and find it - but its more of a general comment to Matt. We expect all our users to send complete logs - whenreporting problems. we as developers should be able to include atleat minimal realvent info in such e-mails - which is the configure command used. Satish
[petsc-dev] Stop breaking my build
> > We expect all our users to send complete logs - whenreporting > problems. we as developers should be able to include atleat minimal > realvent info in such e-mails - which is the configure command used. I really need to start the twitter account for Satish: SatishSmackDown Sean -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/c4ada6f8/attachment.html>
[petsc-dev] Stop breaking my build
On Thu, Aug 19, 2010 at 5:37 PM, Satish Balay wrote: > On Thu, 19 Aug 2010, Jed Brown wrote: > > > On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay < > balay at mcs.anl.gov> wrote: > > > Matt, > > > > > > Nobody knows how you build stuff. Atleast mention the configure > > > command used so it can be reproduced and fixed.. > > > > Complex: > > > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/build_arch-linux-complex-gcov_steamroller.log > > yeah - I guess I should search and find it - but its more of a general > comment to Matt. > > We expect all our users to send complete logs - whenreporting > problems. we as developers should be able to include atleat minimal > realvent info in such e-mails - which is the configure command used. I did not see the point here since we are all developers and know that 'complex' is broken from the error message. And I fixed the breakage twice before this. Matt > > Satish > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/580916d9/attachment.html>
[petsc-dev] Stop breaking my build
On Thu, 19 Aug 2010, Matthew Knepley wrote: > On Thu, Aug 19, 2010 at 5:37 PM, Satish Balay wrote: > > We expect all our users to send complete logs - whenreporting > > problems. we as developers should be able to include atleat minimal > > realvent info in such e-mails - which is the configure command used. > > > I did not see the point here since we are all developers and know > that 'complex' is broken from the error message. And I fixed the > breakage twice before this. I guess I should have read error messages properly.. Shri - looks like merit should be PetscReal - not PetscComplex [pusing a fix for this. If this is incorrect - you can revert my change] Satish
[petsc-dev] using consistant username for commits
Currently some of us let hg choose the 'username' automatically in our commits. Some of us use 'username=value' in our ~/.hgrc - which is consistant - but each of us have a different format here.. petsc:/homes/balay>cat ~/.hgrc [ui] verbose=true username=balay at mcs.anl.gov editor=emacs -nw Should we adopt a consistant naming convention for commits? Perhaps the following notation? [which would imply - I should change mine as well] user:Jed Brown thanks, Satish --- asterix:/home/balay/tmp/petsc-dev>hg log | grep 'user:' | head -100 | sort | uniq user:balay at mcs.anl.gov user:Barry Smith bsmith at mcs.anl.gov user:Dmitry Karpeev user:hong at hmacair2010.local user:hong at hzhangmac.mcs.anl.gov user:hong at vis-v410v166.mcs.anl-external.org user:hzhang user:hzhang at mcs.anl.gov user:Jed Brown user:Matt Knepley user:Shri at dhcp147.swwn2.iit.edu user:Shri at mcswl134.mcs.anl.gov user:Shri at mcswl156.mcs.anl.gov user:Shri at mcswl165.mcs.anl.gov user:Shri at mcswl173.mcs.anl.gov user:Shri at shris-macbook-pro.local user:Victor Minden victorminden at gmail.com asterix:/home/balay/tmp/petsc-dev> --
[petsc-dev] using consistant username for commits
I am going to vote for consistent formatting the way Jed and I have it now. Is that alright? Matt On Thu, Aug 19, 2010 at 6:56 PM, Satish Balay wrote: > > Currently some of us let hg choose the 'username' automatically in our > commits. Some of us use 'username=value' in our ~/.hgrc - which is > consistant - but each of us have a different format here.. > > petsc:/homes/balay>cat ~/.hgrc > [ui] > verbose=true > username=balay at mcs.anl.gov > editor=emacs -nw > > > Should we adopt a consistant naming convention for commits? Perhaps > the following notation? [which would imply - I should change mine as > well] > > user:Jed Brown > > thanks, > Satish > > --- > asterix:/home/balay/tmp/petsc-dev>hg log | grep 'user:' | head -100 | sort > | uniq > user:balay at mcs.anl.gov > user:Barry Smith bsmith at mcs.anl.gov > user:Dmitry Karpeev > user:hong at hmacair2010.local > user:hong at hzhangmac.mcs.anl.gov > user:hong at vis-v410v166.mcs.anl-external.org > user:hzhang > user:hzhang at mcs.anl.gov > user:Jed Brown > user:Matt Knepley > user:Shri at dhcp147.swwn2.iit.edu > user:Shri at mcswl134.mcs.anl.gov > user:Shri at mcswl156.mcs.anl.gov > user:Shri at mcswl165.mcs.anl.gov > user:Shri at mcswl173.mcs.anl.gov > user:Shri at shris-macbook-pro.local > user:Victor Minden victorminden at gmail.com > asterix:/home/balay/tmp/petsc-dev> > -- > > > > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/d0d286cf/attachment.html>
[petsc-dev] Stop breaking my build
> Shri - looks like merit should be PetscReal - not PetscComplex [pusing > a fix for this. If this is incorrect - you can revert my change] > That's correct...thanks.I am building petsc with complex right now to see if there are any other changes needed. > Satish
[petsc-dev] using consistant username for commits
Ok - I'm changing mine.. [ui] username=Satish Balay satish On Thu, 19 Aug 2010, Matthew Knepley wrote: > I am going to vote for consistent formatting the way Jed and I have it now. > Is that > alright? > >Matt > > On Thu, Aug 19, 2010 at 6:56 PM, Satish Balay wrote: > > > > > Currently some of us let hg choose the 'username' automatically in our > > commits. Some of us use 'username=value' in our ~/.hgrc - which is > > consistant - but each of us have a different format here.. > > > > petsc:/homes/balay>cat ~/.hgrc > > [ui] > > verbose=true > > username=balay at mcs.anl.gov > > editor=emacs -nw > > > > > > Should we adopt a consistant naming convention for commits? Perhaps > > the following notation? [which would imply - I should change mine as > > well] > > > > user:Jed Brown > > > > thanks, > > Satish > > > > --- > > asterix:/home/balay/tmp/petsc-dev>hg log | grep 'user:' | head -100 | sort > > | uniq > > user:balay at mcs.anl.gov > > user:Barry Smith bsmith at mcs.anl.gov > > user:Dmitry Karpeev > > user:hong at hmacair2010.local > > user:hong at hzhangmac.mcs.anl.gov > > user:hong at vis-v410v166.mcs.anl-external.org > > user:hzhang > > user:hzhang at mcs.anl.gov > > user:Jed Brown > > user:Matt Knepley > > user:Shri at dhcp147.swwn2.iit.edu > > user:Shri at mcswl134.mcs.anl.gov > > user:Shri at mcswl156.mcs.anl.gov > > user:Shri at mcswl165.mcs.anl.gov > > user:Shri at mcswl173.mcs.anl.gov > > user:Shri at shris-macbook-pro.local > > user:Victor Minden victorminden at gmail.com > > asterix:/home/balay/tmp/petsc-dev> > > -- > > > > > > > > > > > > >
[petsc-dev] using consistant username for commits
Satish, Just tell Hong, Satish and Shri to add their ~/.hg properly but I won't make a big deal about it since inconsistencies will sometimes pop up on new machines etc. Barry On Aug 19, 2010, at 2:01 PM, Matthew Knepley wrote: > I am going to vote for consistent formatting the way Jed and I have it now. > Is that > alright? > >Matt > > On Thu, Aug 19, 2010 at 6:56 PM, Satish Balay wrote: > > Currently some of us let hg choose the 'username' automatically in our > commits. Some of us use 'username=value' in our ~/.hgrc - which is > consistant - but each of us have a different format here.. > > petsc:/homes/balay>cat ~/.hgrc > [ui] > verbose=true > username=balay at mcs.anl.gov > editor=emacs -nw > > > Should we adopt a consistant naming convention for commits? Perhaps > the following notation? [which would imply - I should change mine as > well] > > user:Jed Brown > > thanks, > Satish > > --- > asterix:/home/balay/tmp/petsc-dev>hg log | grep 'user:' | head -100 | sort | > uniq > user:balay at mcs.anl.gov > user:Barry Smith bsmith at mcs.anl.gov > user:Dmitry Karpeev > user:hong at hmacair2010.local > user:hong at hzhangmac.mcs.anl.gov > user:hong at vis-v410v166.mcs.anl-external.org > user:hzhang > user:hzhang at mcs.anl.gov > user:Jed Brown > user:Matt Knepley > user:Shri at dhcp147.swwn2.iit.edu > user:Shri at mcswl134.mcs.anl.gov > user:Shri at mcswl156.mcs.anl.gov > user:Shri at mcswl165.mcs.anl.gov > user:Shri at mcswl173.mcs.anl.gov > user:Shri at shris-macbook-pro.local > user:Victor Minden victorminden at gmail.com > asterix:/home/balay/tmp/petsc-dev> > -- > > > > > > > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/21c7be36/attachment.html>
[petsc-dev] Stop breaking my build
Shri, Since this is development code that only you are working on you can "protect" its use by putting a #requirespackage 'PETSC_USE_DVI' in the makefile in that directory and if you register the method in SNESRegisterAll() then protect it with #if defined(PETSC_USE_DVI) then define PETSC_USE_DVI in $PETSC_ARCH/include/petscconf.h this way you can "be sloppy" but other people will still have access to your new stuff if they want it in the repository. Then later when the code is ready for general builds take out the ifdefs Barry On Aug 19, 2010, at 2:02 PM, Shri wrote: > > >> Shri - looks like merit should be PetscReal - not PetscComplex [pusing >> a fix for this. If this is incorrect - you can revert my change] >> > That's correct...thanks.I am building petsc with complex right now to see if > there are any other changes needed. > >> Satish >
[petsc-dev] proceedings on preliminary work on PETSc with GPUs
Folks, Please find attached an easy proceedings paper on the preliminary work Victor did this summer on "getting PETSc to run on GPUs". We would appreciate any comments or corrections to Barry, Victor and Matt at the cc list above. Thanks! Barry
[petsc-dev] Old Patches
Hey folks. I'm trying to find out what the effect of patch 12 to petsc-3.0.0-p9. Where can I look that up? I thought I'd be able to find that info here: http://www.mcs.anl.gov/petsc/petsc-as/download/petsc-patches.html but that stopped saying what the patches did back at petsc-2.2.1. Thanks -Mike
[petsc-dev] proceedings on preliminary work on PETSc with GPUs
I spoke to Scott MacLachlan today (Victor's advisor at Tufts). He would like a little blurb saying how good Victor was this summer. He wants to give it to the Dean and get him to give Victor money for this semester instead of grading. I can write something to start, or feel free if you have time. Matt On Thu, Aug 19, 2010 at 9:14 PM, Barry Smith wrote: > > Folks, > >Please find attached an easy proceedings paper on the preliminary work > Victor did this summer on "getting PETSc to run on GPUs". > >We would appreciate any comments or corrections to Barry, Victor and > Matt at the cc list above. > >Thanks! > > Barry > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/a333055d/attachment.html>
[petsc-dev] Old Patches
you don't apply p12 patches to petsc-3.0.0-p9. You just download p12 tarball and use it. http://www.mcs.anl.gov/petsc/petsc-as/download/index.html Satish On Thu, 19 Aug 2010, Mike McCourt wrote: > Hey folks. I'm trying to find out what the effect of patch 12 to > petsc-3.0.0-p9. Where can I look that up? > > I thought I'd be able to find that info here: > http://www.mcs.anl.gov/petsc/petsc-as/download/petsc-patches.html > but that stopped saying what the patches did back at petsc-2.2.1. > > Thanks > -Mike >
[petsc-dev] Old Patches
Sorry, I phrased that poorly. I guess I meant: what are the practical changes of p9 to p12? -Mike - Original Message - From: "Satish Balay" To: "For users of the development version of PETSc" Cc: "For users of the development version of PETSc" Sent: Thursday, August 19, 2010 3:24:06 PM GMT -07:00 US/Canada Mountain Subject: Re: [petsc-dev] Old Patches you don't apply p12 patches to petsc-3.0.0-p9. You just download p12 tarball and use it. http://www.mcs.anl.gov/petsc/petsc-as/download/index.html Satish On Thu, 19 Aug 2010, Mike McCourt wrote: > Hey folks. I'm trying to find out what the effect of patch 12 to > petsc-3.0.0-p9. Where can I look that up? > > I thought I'd be able to find that info here: > http://www.mcs.anl.gov/petsc/petsc-as/download/petsc-patches.html > but that stopped saying what the patches did back at petsc-2.2.1. > > Thanks > -Mike >
[petsc-dev] Old Patches
BTW: - if you are looking for the list of changes between p9 and p12 - you'll have to check the repos http://petsc.cs.iit.edu/petsc/releases/petsc-3.0.0/shortlog http://petsc.cs.iit.edu/petsc/releases/BuildSystem-3.0.0/shortlog Satish On Thu, 19 Aug 2010, Satish Balay wrote: > you don't apply p12 patches to petsc-3.0.0-p9. You just > download p12 tarball and use it. > > http://www.mcs.anl.gov/petsc/petsc-as/download/index.html > > Satish > > > On Thu, 19 Aug 2010, Mike McCourt wrote: > > > Hey folks. I'm trying to find out what the effect of patch 12 to > > petsc-3.0.0-p9. Where can I look that up? > > > > I thought I'd be able to find that info here: > > http://www.mcs.anl.gov/petsc/petsc-as/download/petsc-patches.html > > but that stopped saying what the patches did back at petsc-2.2.1. > > > > Thanks > > -Mike > > > >
[petsc-dev] proceedings on preliminary work on PETSc with GPUs
I don't see an attached paper. <>Srinath On Thu, Aug 19, 2010 at 3:14 PM, Barry Smith wrote: > > Folks, > >Please find attached an easy proceedings paper on the preliminary work > Victor did this summer on "getting PETSc to run on GPUs". > >We would appreciate any comments or corrections to Barry, Victor and > Matt at the cc list above. > >Thanks! > > Barry > > > -- = Srinath Vadlamani, PhD. Tech-X Corp. Research Scientist 5621 Arapahoe Ave. Suite A Boulder, CO 80303 303-996-2034 = -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/7a32960b/attachment.html>
[petsc-dev] Old Patches
Thanks Satish, that's closer to what I was looking for. -Mike - Original Message - From: "Satish Balay" To: "For users of the development version of PETSc" Sent: Thursday, August 19, 2010 3:30:29 PM GMT -07:00 US/Canada Mountain Subject: Re: [petsc-dev] Old Patches BTW: - if you are looking for the list of changes between p9 and p12 - you'll have to check the repos http://petsc.cs.iit.edu/petsc/releases/petsc-3.0.0/shortlog http://petsc.cs.iit.edu/petsc/releases/BuildSystem-3.0.0/shortlog Satish On Thu, 19 Aug 2010, Satish Balay wrote: > you don't apply p12 patches to petsc-3.0.0-p9. You just > download p12 tarball and use it. > > http://www.mcs.anl.gov/petsc/petsc-as/download/index.html > > Satish > > > On Thu, 19 Aug 2010, Mike McCourt wrote: > > > Hey folks. I'm trying to find out what the effect of patch 12 to > > petsc-3.0.0-p9. Where can I look that up? > > > > I thought I'd be able to find that info here: > > http://www.mcs.anl.gov/petsc/petsc-as/download/petsc-patches.html > > but that stopped saying what the patches did back at petsc-2.2.1. > > > > Thanks > > -Mike > > > >
[petsc-dev] proceedings on preliminary work on PETSc with GPUs
Here is the paper. Barry On Aug 19, 2010, at 4:14 PM, Barry Smith wrote: > > Folks, > >Please find attached an easy proceedings paper on the preliminary work > Victor did this summer on "getting PETSc to run on GPUs". > >We would appreciate any comments or corrections to Barry, Victor and Matt > at the cc list above. > >Thanks! > > Barry > -- next part -- A non-text attachment was scrubbed... Name: paper.pdf Type: application/pdf Size: 122754 bytes Desc: not available URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100819/cd41a4b0/attachment.pdf>
[petsc-dev] Stop breaking my build
I'm not sure whether DVI should have support for complex type since complex variables with real upper and lower bounds don't make sense to me and i don't know of any actual problems which have or need complex bounds. - Barry Smith wrote: > > Shri, > > Since this is development code that only you are working on you can > "protect" its use by putting a > #requirespackage 'PETSC_USE_DVI' > in the makefile in that directory and if you register the method in > SNESRegisterAll() then protect it with > #if defined(PETSC_USE_DVI) > then define PETSC_USE_DVI in $PETSC_ARCH/include/petscconf.h > this way you can "be sloppy" but other people will still have access to your > new stuff if they want it in the repository. Then later when the code is > ready for general builds take out the ifdefs Ok. I've done this. > > >Barry > > > On Aug 19, 2010, at 2:02 PM, Shri wrote: > > > > > > >> Shri - looks like merit should be PetscReal - not PetscComplex [pusing > >> a fix for this. If this is incorrect - you can revert my change] > >> > > That's correct...thanks.I am building petsc with complex right now to see > > if there are any other changes needed. > > > >> Satish > > >
[petsc-dev] Stop breaking my build
Then you can just require in that directory real numbers (and when you register the method) so that make won't automatically try to build that stuff. Barry On Aug 19, 2010, at 6:12 PM, Shri wrote: > > > I'm not sure whether DVI should have support for complex type since complex > variables with real upper and lower bounds don't make sense to me and i don't > know of any actual problems which have or need complex bounds. > > > - Barry Smith wrote: >> >> Shri, >> >>Since this is development code that only you are working on you can >> "protect" its use by putting a >> #requirespackage 'PETSC_USE_DVI' >> in the makefile in that directory and if you register the method in >> SNESRegisterAll() then protect it with >> #if defined(PETSC_USE_DVI) >> then define PETSC_USE_DVI in $PETSC_ARCH/include/petscconf.h >> this way you can "be sloppy" but other people will still have access to your >> new stuff if they want it in the repository. Then later when the code is >> ready for general builds take out the ifdefs > > Ok. I've done this. >> >> >> Barry >> >> >> On Aug 19, 2010, at 2:02 PM, Shri wrote: >> >>> >>> Shri - looks like merit should be PetscReal - not PetscComplex [pusing a fix for this. If this is incorrect - you can revert my change] >>> That's correct...thanks.I am building petsc with complex right now to see >>> if there are any other changes needed. >>> Satish >>> >> >
[petsc-dev] Stop breaking my build
There is probably an equivalent version of DVI for complex numbers, but I think you can safely ignore it for now and only deal with reals. Cheers, Todd. On Aug 19, 2010, at 6:12 PM, Shri wrote: > > > I'm not sure whether DVI should have support for complex type since complex > variables with real upper and lower bounds don't make sense to me and i don't > know of any actual problems which have or need complex bounds. > > > - Barry Smith wrote: >> >> Shri, >> >>Since this is development code that only you are working on you can >> "protect" its use by putting a >> #requirespackage 'PETSC_USE_DVI' >> in the makefile in that directory and if you register the method in >> SNESRegisterAll() then protect it with >> #if defined(PETSC_USE_DVI) >> then define PETSC_USE_DVI in $PETSC_ARCH/include/petscconf.h >> this way you can "be sloppy" but other people will still have access to your >> new stuff if they want it in the repository. Then later when the code is >> ready for general builds take out the ifdefs > > Ok. I've done this. >> >> >> Barry >> >> >> On Aug 19, 2010, at 2:02 PM, Shri wrote: >> >>> >>> Shri - looks like merit should be PetscReal - not PetscComplex [pusing a fix for this. If this is incorrect - you can revert my change] >>> That's correct...thanks.I am building petsc with complex right now to see >>> if there are any other changes needed. >>> Satish >>> >> >
[petsc-dev] a few issues with current CUDA code for Mat.
I bet all involved people is aware of most of this issues, but just in case. * MatAssemblyEnd_SeqAIJCUDA: What about mode=MAT_FLUSH_ASSEMBLY? What's the point of coping to the GPU? * MatAssemblyEnd_SeqAIJCUDA: the 'tempvec' cusp array is always allocated, but not used for MatMult when no commpressed row. Of course, this issue is very low priority. * MatAssemblyEnd_SeqAIJCUDA: Perhaps memory allocation on the GPU is cheap, but if nonzeros do not change, we could avoid re-creating the GPU mat from scratch. * There are some calls that operate on assembled matrices (MatScale, MatZeroRows, MatDiagonalScale, etc.). These operations need GPU syncing. Am I missing something? * MatShift: seqaij does not implement MatShift, then MatSetValues is used in a loop, next the matrix is re-assembled. This will cause an extra copy to the GPU (take into account that used code already assembled the matrix before the MatShift call). Other calls will suffer from this issue: MatDiagonalSet * MatGetArray: if the user updates values, we are in trouble. All that being said, I'm still unsure why the GPU coping was implemented at MatAssemblyEnd_SeqAIJ. What about using a valid_GPU_data flag for Mat, set it to false in MatAssembly_Begin, and make the GPU coping at the time MatMult_SeqAIJ is called? Of course, such appoach would not solve all the previous issues... I'm just asking the rationale for the current approach. -- Lisandro Dalcin --- CIMEC (INTEC/CONICET-UNL) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo Tel: +54-342-4511594 (ext 1011) Tel/Fax: +54-342-4511169
[petsc-dev] using consistant username for commits
I changed mine to: username=Hong Zhang Hong On Thu, Aug 19, 2010 at 2:10 PM, Barry Smith wrote: > > ?? Satish, > ?? Just tell Hong, Satish and Shri to add their ~/.hg properly but I won't > make a big deal about it since inconsistencies will sometimes pop up on new > machines etc. > ?? Barry > On Aug 19, 2010, at 2:01 PM, Matthew Knepley wrote: > > I am going to vote for consistent formatting the way Jed and I have it now. > Is that > alright? > ?? Matt > > On Thu, Aug 19, 2010 at 6:56 PM, Satish Balay wrote: >> >> Currently some of us let hg choose the 'username' automatically in our >> commits. Some of us use 'username=value' in our ~/.hgrc - which is >> consistant - but each of us have a different format here.. >> >> petsc:/homes/balay>cat ~/.hgrc >> [ui] >> verbose=true >> username=balay at mcs.anl.gov >> editor=emacs -nw >> >> >> Should we adopt a consistant naming convention for commits? Perhaps >> the following notation? [which would imply - I should change mine as >> well] >> >> user: ? ? ? ?Jed Brown >> >> thanks, >> Satish >> >> --- >> asterix:/home/balay/tmp/petsc-dev>hg log | grep 'user:' | head -100 | sort >> | uniq >> user: ? ? ? ?balay at mcs.anl.gov >> user: ? ? ? ?Barry Smith bsmith at mcs.anl.gov >> user: ? ? ? ?Dmitry Karpeev >> user: ? ? ? ?hong at hmacair2010.local >> user: ? ? ? ?hong at hzhangmac.mcs.anl.gov >> user: ? ? ? ?hong at vis-v410v166.mcs.anl-external.org >> user: ? ? ? ?hzhang >> user: ? ? ? ?hzhang at mcs.anl.gov >> user: ? ? ? ?Jed Brown >> user: ? ? ? ?Matt Knepley >> user: ? ? ? ?Shri at dhcp147.swwn2.iit.edu >> user: ? ? ? ?Shri at mcswl134.mcs.anl.gov >> user: ? ? ? ?Shri at mcswl156.mcs.anl.gov >> user: ? ? ? ?Shri at mcswl165.mcs.anl.gov >> user: ? ? ? ?Shri at mcswl173.mcs.anl.gov >> user: ? ? ? ?Shri at shris-macbook-pro.local >> user: ? ? ? ?Victor Minden victorminden at gmail.com >> asterix:/home/balay/tmp/petsc-dev> >> -- >> >> >> >> > > > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener > >
