Ahh, not a real Unix user :-)
> On Apr 14, 2015, at 10:04 PM, Aron Ahmadia wrote:
>
>
> On Tue, Apr 14, 2015 at 10:58 PM, Mark Adams wrote:
>
> I repeat, do we have any data on the number of user that use ~/.petscrc ?
>
> FWIW: I'm not using it, and I'd forgotten it existed until now
On Tue, Apr 14, 2015 at 9:59 PM, Mark Adams wrote:
> I am trying to see why MatConvert is failing for MatNest to MPIAIJ and
> added print statements in to see what it is checking for.
>
> Where is the function list created for MatNest? I am grepping on
> MatConvert_[n/N] and not finding anything
On Tue, Apr 14, 2015 at 10:58 PM, Mark Adams wrote:
>
> I repeat, do we have any data on the number of user that use ~/.petscrc ?
>
FWIW: I'm not using it, and I'd forgotten it existed until now
> On Apr 14, 2015, at 9:58 PM, Mark Adams wrote:
>
>
>
> I disagree that nobody uses it, but if we get rid of ~/.petscrc and
> recommend that they use PETSC_OPTIONS for that, what will they do?
>
> I repeat, do we have any data on the number of user that use ~/.petscrc ?
>
> I never have. T
I am trying to see why MatConvert is failing for MatNest to MPIAIJ and
added print statements in to see what it is checking for.
Where is the function list created for MatNest? I am grepping on
MatConvert_[n/N] and not finding anything other than:
21:54 next ~/Codes/petsc$ git grep MatConvert_N
>
> I disagree that nobody uses it, but if we get rid of ~/.petscrc and
> recommend that they use PETSC_OPTIONS for that, what will they do?
>
I repeat, do we have any data on the number of user that use ~/.petscrc ?
I never have. That is not data; that is an anecdote. Data?
If everyone is usi
Mark Adams writes:
>> You have not addressed the issue of people have a stale PETSC_OPTIONS.
>> Why is that any less likely then a stale .petscrc?
>>
>
> I think I said this: people use their home directories as *scratch space*.
> You download an email of a petscrc file, untar something, scp s
Barry Smith writes:
> Shame about your recent climbing accident when you lost all your fingers.
Touché
signature.asc
Description: PGP signature
On Tue, Apr 14, 2015 at 8:17 PM, Barry Smith wrote:
>
> Mark,
>
> You have not addressed the issue of people have a stale PETSC_OPTIONS.
> Why is that any less likely then a stale .petscrc?
>
I think I said this: people use their home directories as *scratch space*.
You download an email o
Matthew Knepley writes:
> I am arguing for uniformity. With the current system, all internal PETSc
> mallocs (we are supposed to use PetscMallocK everywhere)
> will return NULL for 0 size argument. On the other hand, if you just
> forward the request to malloc, the standard says it can return
> a
On Tue, Apr 14, 2015 at 7:12 PM, Barry Smith wrote:
>
> > On Apr 14, 2015, at 6:13 PM, Matthew Knepley wrote:
> >
> > On Tue, Apr 14, 2015 at 6:00 PM, Barry Smith wrote:
> >
> > > On Apr 14, 2015, at 5:40 PM, Jed Brown wrote:
> > >
> > > Matthew Knepley writes:
> > >> I really do not want tha
Mark,
You have not addressed the issue of people have a stale PETSC_OPTIONS. Why
is that any less likely then a stale .petscrc?
Barry
Note that based on our experiences with ./configure people generally have
lots and lots of stale environmental variables set in their .bashrc that
> On Apr 14, 2015, at 6:13 PM, Matthew Knepley wrote:
>
> On Tue, Apr 14, 2015 at 6:00 PM, Barry Smith wrote:
>
> > On Apr 14, 2015, at 5:40 PM, Jed Brown wrote:
> >
> > Matthew Knepley writes:
> >> I really do not want that. I am especially unwilling to do that just to
> >> appease static a
On Tue, Apr 14, 2015 at 5:51 PM, Barry Smith wrote:
>
> > On Apr 14, 2015, at 4:45 PM, Mark Adams wrote:
> >
> >
> > >
> > > This has never been a problem.
> >
> >I suspect this is because almost no one knows about PETSC_OPTIONS and
> uses it.
> >
> >
> > This could be a migration path for p
OK, I use:
call
MatConvert(a_ts%FJacobian,MATAIJ,MAT_INITIAL_MATRIX,a_ts%FJacobian2,ierr);CHKERRQ(ierr)
I added code to src/snes/examples/tutorials/ex73f90t.F90 that reproduces
this error, in next.
I'll look at it.
Mark
On Tue, Apr 14, 2015 at 6:33 PM, Matthew Knepley wrote:
> On Tue,
On Tue, Apr 14, 2015 at 6:00 PM, Barry Smith wrote:
>
> > On Apr 14, 2015, at 5:40 PM, Jed Brown wrote:
> >
> > Matthew Knepley writes:
> >> I really do not want that. I am especially unwilling to do that just to
> >> appease static analysis.
> >
> > I think it's actually better for debuggabili
> On Apr 14, 2015, at 5:40 PM, Jed Brown wrote:
>
> Matthew Knepley writes:
>> I really do not want that. I am especially unwilling to do that just to
>> appease static analysis.
>
> I think it's actually better for debuggability and
> strictness/normalization within the code, but we had this
> On Apr 14, 2015, at 3:33 AM, Lisandro Dalcin wrote:
>
> On 14 April 2015 at 02:46, Matthew Knepley wrote:
>> On Mon, Apr 13, 2015 at 5:48 PM, Barry Smith wrote:
>>>
>>>
>>> When I run clang --analyze on PETSc on getting warnings of the type below,
>>> any idea how to deal with them? Clearl
> On Apr 14, 2015, at 5:13 PM, Matthew Knepley wrote:
>
> On Tue, Apr 14, 2015 at 5:11 PM, Barry Smith wrote:
>
> Jed suggested just passing requests for zero length malloc to malloc() and
> free() (claim is standards require them to behave properly now a days) and
> remove all zero lengt
Matthew Knepley writes:
> I really do not want that. I am especially unwilling to do that just to
> appease static analysis.
I think it's actually better for debuggability and
strictness/normalization within the code, but we had this argument a
year ago and if you still insist, I'm not going to d
On Tue, Apr 14, 2015 at 5:19 PM, Mark Adams wrote:
> Matt, in looking at MatConvert_Nest_AIJ, the code looks like it is 2 years
> old.
>
> I need a MatConvert_Nest_MPIAIJ, should I write this or does it exist
> someplace?
>
This is MPIAIJ. Look at the code.
Matt
>
> Mark
>
>
>
> On Tue, Apr
Matt, in looking at MatConvert_Nest_AIJ, the code looks like it is 2 years
old.
I need a MatConvert_Nest_MPIAIJ, should I write this or does it exist
someplace?
Mark
On Tue, Apr 14, 2015 at 2:54 PM, Mark Adams wrote:
> Also, this is with MPI so I need MPIAIJ. Is that supposed to work?
>
> O
On Tue, Apr 14, 2015 at 5:11 PM, Barry Smith wrote:
>
> Jed suggested just passing requests for zero length malloc to malloc()
> and free() (claim is standards require them to behave properly now a days)
> and remove all zero length checking from the macros. Will this resolve
> everything? Not
Jed suggested just passing requests for zero length malloc to malloc() and
free() (claim is standards require them to behave properly now a days) and
remove all zero length checking from the macros. Will this resolve everything?
Note that we need to pass a flag to --analyze telling it that z
> On Apr 14, 2015, at 4:45 PM, Mark Adams wrote:
>
>
> >
> > This has never been a problem.
>
>I suspect this is because almost no one knows about PETSC_OPTIONS and uses
> it.
>
>
> This could be a migration path for people using ~/.petscrc ...
So people start using PETSC_OPTIONS. T
On Tue, 14 Apr 2015, Mark Adams wrote:
> > >
> > > This has never been a problem.
> >
> >I suspect this is because almost no one knows about PETSC_OPTIONS and
> > uses it.
> >
> >
> This could be a migration path for people using ~/.petscrc ...
The point is - once users migrate from .petscrc
> >
> > This has never been a problem.
>
>I suspect this is because almost no one knows about PETSC_OPTIONS and
> uses it.
>
>
This could be a migration path for people using ~/.petscrc ...
> On Apr 14, 2015, at 3:31 PM, Satish Balay wrote:
>
> Hm - for one - we rely on ~/.petscrc for our nightly builds.
Good point.
Now .xxrc and environmental variables are classic Unix techniques that
"real" Unix users are cognizant of and take into account when running and
debugging is
> On Apr 14, 2015, at 4:30 PM, Mark Adams wrote:
>
>
>
> How about when they copy their .bashrc file - which might include
> PETSC_OPTIONS env variable? [or LD_LIBRARY_PATH to wrong version of
> libraries]
>
>
> This has never been a problem.
I suspect this is because almost no one know
>
> How about when they copy their .bashrc file - which might include
> PETSC_OPTIONS env variable? [or LD_LIBRARY_PATH to wrong version of
> libraries]
>
>
This has never been a problem. Perhaps everyone know about .bashrc and
must deal with it, but .petscrc falls of the radar and they/we forget
> On Apr 14, 2015, at 3:47 PM, Matthew Knepley wrote:
>
> On Tue, Apr 14, 2015 at 3:31 PM, Satish Balay wrote:
> Hm - for one - we rely on ~/.petscrc for our nightly builds.
>
> petsc@petsc:~$ cat ~/.petscrc
> -malloc_dump
> -display 140.221.10.20:0.0
> #-nox
> #-nox_warning
> petsc@petsc:~$
>
> On Apr 14, 2015, at 8:50 AM, Patrick Farrell
> wrote:
>
> Dear PETSc developers,
>
> I have a nice algorithm for solving a variational inequality that arises in
> fracture mechanics --- first do some iterations of nonlinear
> Gauss-Seidel-Newton
> with the nonlinear fieldsplit I've implemen
On Tue, 14 Apr 2015, Mark Adams wrote:
> > using "-pc_type_hypre" in ~/.petscrc is a bad practice. [it makes
> > sense only for global options that are useful for multiple petsc
> > applications - like -malloc_dump]
> >
> >
> The problem is that users pass rc files around, scp, mail, whatever, and
> using "-pc_type_hypre" in ~/.petscrc is a bad practice. [it makes
> sense only for global options that are useful for multiple petsc
> applications - like -malloc_dump]
>
>
The problem is that users pass rc files around, scp, mail, whatever, and
they put it their home directory temporarily and le
On Tue, Apr 14, 2015 at 3:31 PM, Satish Balay wrote:
> Hm - for one - we rely on ~/.petscrc for our nightly builds.
>
> petsc@petsc:~$ cat ~/.petscrc
> -malloc_dump
> -display 140.221.10.20:0.0
> #-nox
> #-nox_warning
> petsc@petsc:~$
>
We can move these to the environment variable. I did this f
Hm - for one - we rely on ~/.petscrc for our nightly builds.
petsc@petsc:~$ cat ~/.petscrc
-malloc_dump
-display 140.221.10.20:0.0
#-nox
#-nox_warning
petsc@petsc:~$
And secondly we have an option -skip_petscrc that would skip it.
using "-pc_type_hypre" in ~/.petscrc is a bad practice. [it make
> On Apr 14, 2015, at 3:24 PM, Jed Brown wrote:
>
> Barry Smith writes:
>> Theoretically it is a great feature but no one uses it and those who do
>> use it forget that they used it.
>
> It would also be useful for -log_summary to state where each option was
> found (e.g., PETSC_OPTIONS, .p
Barry Smith writes:
>Theoretically it is a great feature but no one uses it and those who do
> use it forget that they used it.
It would also be useful for -log_summary to state where each option was
found (e.g., PETSC_OPTIONS, .petscrc, command line). People forget this
stuff all the time.
Mark,
Ok, you convinced me.
Satish,
Can you please rip out all the checking for .petscrc in the home directory.
Thanks
Barry
Theoretically it is a great feature but no one uses it and those who do use
it forget that they used it.
> On Apr 14, 2015, at 7:41 AM, Mark A
Related to that same commit: Should runex19adj and runex19opt_ic be
added to tests in TESTEXAMPLES_C in makefile?
Cheers,
Dominic
On 04/14/2015 12:49 PM, Satish Balay wrote:
Perhaps Hong didn't include these files in the commit. cc:ing Hong.
I see the commit was merged via branch barry/petsc-
Perhaps Hong didn't include these files in the commit. cc:ing Hong.
I see the commit was merged via branch barry/petsc-sa-refactor-rebase
$ git log --ancestry-path --reverse --merges
e468013211bb8e2e81ded0f6b4ec8e550e081d7e..master
commit 3188f603bf47e22bf58a6ef813d382ac5f05ad97
Merge: 9d414b0 3
Also, this is with MPI so I need MPIAIJ. Is that supposed to work?
On Tue, Apr 14, 2015 at 2:53 PM, Mark Adams wrote:
> It looks like MatConvert is looking for "MatConvert_nest_aij_C"
>
> but I see:
>
> > git grep MatConvert_Nest
> impls/nest/matnest.c:#define __FUNCT__ "MatConvert_Nest_AIJ"
>
It looks like MatConvert is looking for "MatConvert_nest_aij_C"
but I see:
> git grep MatConvert_Nest
impls/nest/matnest.c:#define __FUNCT__ "MatConvert_Nest_AIJ"
impls/nest/matnest.c:PETSC_EXTERN PetscErrorCode MatConvert_Nest_AIJ(Mat
A,MatType newtype,MatReuse reuse,Mat *newmat)
Is there a pro
I have tried
call
MatConvert(a_ts%FJacobian,MATMPIAIJ,MAT_INITIAL_MATRIX,a_ts%FJacobian2,ierr);CHKERRQ(ierr)
and
call
MatConvert(a_ts%FJacobian,MATAIJ,MAT_INITIAL_MATRIX,a_ts%FJacobian2,ierr);CHKERRQ(ierr)
in 'next' and it is not finding the specialized routine.
I will look into it.
Mark
On 04/14/2015 12:11 PM, Satish Balay wrote:
Hm - I don't see this file in the commit mentioned..
That's correct, they're not being added in that commit. However, the
files are needed by targets added to the makefile in this commit. That's
why I was thinking that perhaps they should have been ad
Hm - I don't see this file in the commit mentioned..
Satish
-
balay@asterix /home/balay/petsc (master=)
$ git show --stat e468013211
commit e468013211bb8e2e81ded0f6b4ec8e550e081d7e
Author: Hong Zhang
Date: Sun Nov 23 08:19:16 2014 -0600
change names for the quadrature term in the cost
Hi,
Is it possible that src/ts/examples/tutorials/ex19adj.c and
src/ts/examples/tutorials/ex19opt_ic.c are missing from the repo? I
believe these should have been added in commit e468013211.
Cheers,
Dominic
--
Dominic Meiser
Tech-X Corporation
5621 Arapahoe Avenue
Boulder, CO 80303
USA
Telep
Hello Jose,
I'm hacking on version to integrate 0.5.0 changes and verify CUDA 7
support. I can make it available or send a pull request later this week to
start experimenting if anyone is interested.
Steve
On Tue, Apr 14, 2015 at 10:09 AM, Jose E. Roman wrote:
> Has anyone updated to 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
Dear PETSc developers,
I have a nice algorithm for solving a variational inequality that arises in
fracture mechanics --- first do some iterations of nonlinear Gauss-Seidel-Newton
with the nonlinear fieldsplit I've implemented to acquire a good initial guess,
and then switch to VINEWTONRSLS for i
PETSc's design of looking for RC files in the users home directory really
sucks. I've complained about this before a few years ago and am going to
again.
A perfectly reasonable apps person had a .petscrc file in his home
directory with at "%-pc_type_hypre" in it. This gave an error but he could
On 14 April 2015 at 02:46, Matthew Knepley wrote:
> On Mon, Apr 13, 2015 at 5:48 PM, Barry Smith wrote:
>>
>>
>> When I run clang --analyze on PETSc on getting warnings of the type below,
>> any idea how to deal with them? Clearly these things are usually not null
>> pointers or PETSc would crash
52 matches
Mail list logo
