I did not know about -log_trace.
Good to know,
Thanks
On Fri, Apr 23, 2021 at 8:19 AM Stefano Zampini
wrote:
>
>
>
>> I'm not talking about timings, I am talking about seeing where a code
>> dies.
>>
>
> When codes die within the MPI implementation is basically impossible to
> provide a backtra
> I'm not talking about timings, I am talking about seeing where a code dies.
>
When codes die within the MPI implementation is basically impossible to
provide a backtrace from PETSc, but the MPI implementation may offer some
verbose messaging.
If this happens quite early in the code (and I presum
On Fri, Apr 23, 2021 at 2:57 AM Pierre Jolivet wrote:
>
>
> On 22 Apr 2021, at 7:45 PM, Barry Smith wrote:
>
>
> It would be straightforward to add an option to -info to output only
> from a particular MPI_COMM_WORLD global rank.
>
> Maybe an extra :rank at the end of the info options?
>
>
On Thu, Apr 22, 2021 at 1:45 PM Barry Smith wrote:
>
> It would be straightforward to add an option to -info to output only
> from a particular MPI_COMM_WORLD global rank.
>
> Maybe an extra :rank at the end of the info options?
>
> Open 128k files is nuts.
>
Yep, and Fugaku can't deal wit
> On 22 Apr 2021, at 7:45 PM, Barry Smith wrote:
>
>
> It would be straightforward to add an option to -info to output only from a
> particular MPI_COMM_WORLD global rank.
>
> Maybe an extra :rank at the end of the info options?
>
> Open 128k files is nuts.
It is what it is, I’ve mad
It would be straightforward to add an option to -info to output only from a
particular MPI_COMM_WORLD global rank.
Maybe an extra :rank at the end of the info options?
Open 128k files is nuts.
Barry
> On Apr 22, 2021, at 11:14 AM, Mark Adams wrote:
>
> OK, so -info out.%p would do w
OK, so -info out.%p would do what I asked. Alas, what I really need it to
reduce the output with 128K processes.
Thanks,
On Thu, Apr 22, 2021 at 11:54 AM Pierre Jolivet wrote:
>
>
> On 22 Apr 2021, at 5:33 PM, Jacob Faibussowitsch
> wrote:
>
> Not out of the box no. There is -info ::self which
> On 22 Apr 2021, at 5:33 PM, Jacob Faibussowitsch wrote:
>
> Not out of the box no. There is -info ::self which makes info only print from
> calls made on PETSC_COMM_SELF, but I don’t think that’s what you want. Best
> advice would be to print to a file and grep the file for any lines starti
Not out of the box no. There is -info ::self which makes info only print from
calls made on PETSC_COMM_SELF, but I don’t think that’s what you want. Best
advice would be to print to a file and grep the file for any lines starting
with the rank number you want.
Best regards,
Jacob Faibussowitsc
Can I make -info only print from one process?
Mark
10 matches
Mail list logo