On 2 August 2017 at 03:29, Barry Smith wrote:
>
>> On Aug 1, 2017, at 7:26 PM, Emil Constantinescu wrote:
>>
>> Well, there are situations in which you want to do a certain number of fixed
>> steps.
>
>Really, I think users ALWAYS want to get to a particular time; it is only
> due to flaws
On 1 August 2017 at 20:50, Barry Smith wrote:
>
>Currently this would mean writing manual stubs for those functions as
> Lisandro pointed out. Kind of an annoying extra burden since before they were
> depreciated they likely did not require manual stubs :-(
>
Well, not really, for STATIC_IN
Jed, I totally understand your answer ! I was just wondering if a relevant
option (at the command line) could do the trick.
Barry, I'll try to give a try to your suggestion.
Thanks,
Franck
- Mail original -
> De: "Barry Smith"
> À: "Franck Houssen"
> Cc: "petsc-dev"
> Envoyé: Mardi 1
Satish, I answered your questions beneath. Barry, to answer your question: I
may (or not) get messages like "WARNING! There are options you set that were
not used!...Option left: name". These messages "pollute" the output. As I try
to run/compare lots of cases, I have lots of output logs. To pos
Is this intentional or just an oversight? Should it be fixed in maint?
--
Lisandro Dalcin
Research Scientist
Computer, Electrical and Mathematical Sciences & Engineering (CEMSE)
Extreme Computing Research Center (ECRC)
King Abdullah University of Science and Technology (KAUST)
http:
On Wed, 2 Aug 2017, Franck Houssen wrote:
> Satish, I answered your questions beneath. Barry, to answer your question: I
> may (or not) get messages like "WARNING! There are options you set that were
> not used!...Option left: name". These messages "pollute" the output. As I try
> to run/compa
On Wed, 2 Aug 2017, Lisandro Dalcin wrote:
> Is this intentional or just an oversight?
Probably an oversight..
> Should it be fixed in maint?
Sure - with the bug-fix branch off maint - with testing in next first..
Satish
Things work fine when I use clang, but I'd really like to be able to use
GCC as well.
I updated the ignored issue to reflect that the bug is still present when
using GCC 7.1.0.
I suppose I will give OpenMPI a try when I get a chance.
--Richard
On Tue, Aug 1, 2017 at 5:15 PM, Matthew Knepley wr
> On Aug 2, 2017, at 3:47 AM, Lisandro Dalcin wrote:
>
> On 2 August 2017 at 03:29, Barry Smith wrote:
>>
>>> On Aug 1, 2017, at 7:26 PM, Emil Constantinescu
>>> wrote:
>>>
>>> Well, there are situations in which you want to do a certain number of
>>> fixed steps.
>>
>> Really, I think
> On Aug 2, 2017, at 4:22 AM, Franck Houssen wrote:
>
> Satish, I answered your questions beneath. Barry, to answer your question: I
> may (or not) get messages like "WARNING! There are options you set that were
> not used!...Option left: name". These messages "pollute" the output. As I try
>
On Wed, 2 Aug 2017, Richard Tran Mills wrote:
> I suppose I will give OpenMPI a try when I get a chance.
This works fine.
Satish
> On Aug 2, 2017, at 12:54 PM, Satish Balay wrote:
>
> On Wed, 2 Aug 2017, Richard Tran Mills wrote:
>
>> I suppose I will give OpenMPI a try when I get a chance.
>
> This works fine.
This should be noted in the MPICH GitHub issues tracker.
>
> Satish
Franck Houssen writes:
> Jed, I totally understand your answer ! I was just wondering if a relevant
> option (at the command line) could do the trick.
> Barry, I'll try to give a try to your suggestion.
If you can use different prefix, you could write
-a_ksp_view ascii:a.log -b_ksp_view asci
GCC works great on Linux, but IMHO it is always problematic on Mac. I had a lot
of trouble when using GCC on Mac for netcdf, libmesh and some other stuff. And
it seems not easy to fix the problems on the library side. For example, the
netcdf problem I got has existed for several years, and there
I haven't tried this myself, but two of my colleagues are reporting
problems accessing DMLabel from Fortran, when using the latest 'next'
branch.
Previously, #include and then 'use petsc' would
give access to DMLabel.
But now it appears that doesn't work- you need to include petscdmlabel.h
On Wed, Aug 2, 2017 at 8:06 PM, Adrian Croucher
wrote:
> I haven't tried this myself, but two of my colleagues are reporting
> problems accessing DMLabel from Fortran, when using the latest 'next'
> branch.
>
> Previously, #include and then 'use petsc' would
> give access to DMLabel.
>
> But now
16 matches
Mail list logo
