On 2 May 2017 at 17:22, Jed Brown wrote:
>>
>> At the time I was building PISM, I believe that was a requirement,
>
> That hasn't been a suggestion in the PISM distribution since 2009, as
> far as I know (and checking the Git history).
Just checked,
my notes indicate that my first PISM build was
On 24 April 2017 at 15:21, Jed Brown wrote:
> There is no harm in including all external packages that you might need.
>
>> In terms of laying out PETSc, can (should ?) one use PETSC_DIR
>> and PETSC_ARCH: to combine everything PETSc-related under one,
>> top-level, say
>>
>> /path/to/PETSC/3.7.5
Kevin Buckley writes:
> On 24 April 2017 at 14:11, Matthew Knepley wrote:
>
>>> The original package has a requirement for
>>>
>>> --with-clanguage=cxx
>>
>> Also, this is almost never needed. Are you sure the package needs it, or
>> just uses it due to history.
>
> Apologies, was away for a w
On 24 April 2017 at 14:11, Matthew Knepley wrote:
>> The original package has a requirement for
>>
>> --with-clanguage=cxx
>
> Also, this is almost never needed. Are you sure the package needs it, or
> just uses it due to history.
Apologies, was away for a while.
At the time I was building PI
pushed to master..
Satish
On Mon, 1 May 2017, Barry Smith wrote:
>
>Ok, take them out of the C side also.
>
>
> > On May 1, 2017, at 6:39 PM, Satish Balay wrote:
> >
> > On Mon, 1 May 2017, Jose E. Roman wrote:
> >
> >>
> >>> El 1 may 2017, a las 22:27, Barry Smith escribió:
> >>>
>
Ok, take them out of the C side also.
> On May 1, 2017, at 6:39 PM, Satish Balay wrote:
>
> On Mon, 1 May 2017, Jose E. Roman wrote:
>
>>
>>> El 1 may 2017, a las 22:27, Barry Smith escribió:
>>>
>>> Is there are reason to have the same symbol in both library (note they come
>>> from t
On Mon, 1 May 2017, Jose E. Roman wrote:
>
> > El 1 may 2017, a las 22:27, Barry Smith escribió:
> >
> > Is there are reason to have the same symbol in both library (note they
> > come from the fortran versions)
> >
> > $ nm -o arch-uni-f2cblaslapack/lib/libf2cblas.a | grep xerbla | grep " T
> El 1 may 2017, a las 22:27, Barry Smith escribió:
>
> Is there are reason to have the same symbol in both library (note they come
> from the fortran versions)
>
> $ nm -o arch-uni-f2cblaslapack/lib/libf2cblas.a | grep xerbla | grep " T "
> arch-uni-f2cblaslapack/lib/libf2cblas.a:xerbla_arra
Is there are reason to have the same symbol in both library (note they come
from the fortran versions)
$ nm -o arch-uni-f2cblaslapack/lib/libf2cblas.a | grep xerbla | grep " T "
arch-uni-f2cblaslapack/lib/libf2cblas.a:xerbla_array.o: T
_xerbla_array_
arch-uni-f2cblaslapack/li
Lisandro Dalcin writes:
> On 30 April 2017 at 23:34, Jed Brown wrote:
>>
>> One reliable, if somewhat expensive, option would be to use
>> extrapolation similar to TSARKIMEX1BEE.
>
> Somewhat expensive :-) ?
Naively, it's a 50% cost increase, but you have a good initial guess
from the two steps
Initial implementation, still WIP, I'll fire the PR once I get
dalcinl/refactor-ts-adapt merged into master
https://bitbucket.org/petsc/petsc/commits/9d2aaf5d9cfa4509075a23b366eed8b8cf407a27?at=dalcinl/ts-adapt-default-type
On 30 April 2017 at 23:27, Barry Smith wrote:
>
>> On Apr 30, 2017, at 3
On 30 April 2017 at 23:34, Jed Brown wrote:
>
> One reliable, if somewhat expensive, option would be to use
> extrapolation similar to TSARKIMEX1BEE.
Somewhat expensive :-) ?
> If this feels like reinventing
> a wheel using stone tools, it is; we could just add a TSARKIMEX tableau
> for Theta w
On 1 May 2017 at 00:05, Jed Brown wrote:
> Why not PetscStrallocpy like in PetscObjectChangeTypeName. Seems easier
> to do that than to explain in the documentation that the string cannot
> be constructed dynamically.
Just because I think this is not really needed, but of course I might
be wrong
13 matches
Mail list logo
