Thanks Barry. I will update my petsc.
By the way, I simply replaced the functions PetscFormatConvert() and
PetscVFPrintfDefault() with those in petsc-3.6 and it works for me.
Best,
Rongliang
On 04/17/2018 05:53 AM, Smith, Barry F. wrote:
Rongliang,
I have prepared a fix for this in t
Rongliang,
I have prepared a fix for this in the branch barry/bugfix-petscformatconvert
which comes from the master branch of PETSc.
Unfortunately it requires many changes so cannot be back ported to previous
releases.
Thanks for reporting the problem,
Barry
> On Apr 11, 201
Thanks Barry. I found petsc-3.6 and older versions did not have this
restriction.
Best,
Rongliang
On 04/12/2018 07:22 AM, Smith, Barry F. wrote:
Yes, PetscPrintf() and related functions have a maximum string length of
about 8000 characters.
Barry
On Apr 11, 2018, at 6:17 PM, Rongli
Yes, PetscPrintf() and related functions have a maximum string length of
about 8000 characters.
Barry
> On Apr 11, 2018, at 6:17 PM, Rongliang Chen wrote:
>
> Dear All,
>
>
> When I tried to print a long string using PetscPrintf() I found that it
> truncated the string. Attached is a
Dear All,
When I tried to print a long string using PetscPrintf() I found that it
truncated the string. Attached is a simple example for this (run with
single processor). I used PetscPrintf() and printf() to print the same
string and the printf() seems OK. I am using petsc-3.8.4.
Best,
Ro
> On Sep 24, 2015, at 9:24 PM, Gideon Simpson wrote:
>
> I saw that Barry posted something about this in the dev listserv last
> December, but there wasn’t any follow up. Right now, on an OS X based
> machine with gcc compilers, if I do a PetscPrintf with a __float128, with %g,
> it outputs
On Thu, Sep 24, 2015 at 9:24 PM, Gideon Simpson
wrote:
> I saw that Barry posted something about this in the dev listserv last
> December, but there wasn’t any follow up. Right now, on an OS X based
> machine with gcc compilers, if I do a PetscPrintf with a __float128, with
> %g, it outputs 0.
I saw that Barry posted something about this in the dev listserv last December,
but there wasn’t any follow up. Right now, on an OS X based machine with gcc
compilers, if I do a PetscPrintf with a __float128, with %g, it outputs 0. Is
there a way to get around this, other than using quadmath_s
On Tue, Dec 13, 2011 at 11:24 AM, Matthew Knepley wrote:
> On Tue, Dec 13, 2011 at 10:19 AM, Xiangdong Liang
> wrote:
>>
>> On Tue, Dec 13, 2011 at 11:14 AM, Matthew Knepley
>> wrote:
>> > On Tue, Dec 13, 2011 at 10:13 AM, Xiangdong Liang
>> > wrote:
>> >>
>> >> Hello everyone,
>> >>
>> >> I a
On Tue, Dec 13, 2011 at 11:14 AM, Matthew Knepley wrote:
> On Tue, Dec 13, 2011 at 10:13 AM, Xiangdong Liang
> wrote:
>>
>> Hello everyone,
>>
>> I am using PetscPrintf(PETSC_COMM_WORLD,.) to print out some
>> information. When I run the program on multiple processors, some of
>> these calls
Hello everyone,
I am using PetscPrintf(PETSC_COMM_WORLD,.) to print out some
information. When I run the program on multiple processors, some of
these calls are printed out multiple times, while other calls are
printed out once. Should it be printed only once if I use
PETSC_COMM_WORLD? Thanks.
On Tue, 13 Dec 2011, Xiangdong Liang wrote:
> > The print is executed only on rank 0 of the communicator provided.
>
> I agree. This implies that the message can be printed out at most
> once. Do you have any hints why I saw the message printed out multiple
> times?
Perhaps bug with usage of Pe
On Tue, Dec 13, 2011 at 10:19 AM, Xiangdong Liang wrote:
> On Tue, Dec 13, 2011 at 11:14 AM, Matthew Knepley
> wrote:
> > On Tue, Dec 13, 2011 at 10:13 AM, Xiangdong Liang
> wrote:
> >>
> >> Hello everyone,
> >>
> >> I am using PetscPrintf(PETSC_COMM_WORLD,.) to print out some
> >> informat
On Tue, Dec 13, 2011 at 10:13 AM, Xiangdong Liang wrote:
> Hello everyone,
>
> I am using PetscPrintf(PETSC_COMM_WORLD,.) to print out some
> information. When I run the program on multiple processors, some of
> these calls are printed out multiple times, while other calls are
> printed out o
14 matches
Mail list logo
