??? In my original email I mention that page and state that the
command line option is working.


Were you expecting me to understand from your reply that the
option :ascii_xml somehow translates to
PetscViewerPushFormat(viewer,"PETSC_VIEWER_ASCII_XML")?


Chris

________________________________
From: Matthew Knepley <[email protected]>
Sent: Thursday, April 05, 2018 1:35 PM
To: Klaij, Christiaan
Cc: Smith, Barry F.; [email protected]; Koos Huijssen
Subject: Re: [petsc-dev] getting on with the nested timers

On Thu, Apr 5, 2018 at 7:31 AM, Klaij, Christiaan 
<[email protected]<mailto:[email protected]>> wrote:

Matt,

I guess you meant to send this link:

http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Viewer/PetscViewerPushFormat.html

No, I meant to send the link I sent. In the section Options Database Keys, it 
gives you the format.

  Matt

If so, it doesn't say anything on XML either. But after some
trial and error I found the format to
be "PETSC_VIEWER_ASCII_XML", so problem solved.

Summarizing the problem from a user perspective:

1) The manual page of PetscLogView mentions PetscViewerASCIIOpen,
which mentions PetscViewerPushFormat, I should have figured that
out by myself, sorry.

2) The manual page of PetscLogView mentions PetscLogNestedBegin,
which doesn't have a manual entry.

3) The manual page of PetscViewerPushFormat doesn't mention the
format PETSC_VIEWER_ASCII_XML, although it is available.

Chris

dr. ir. Christiaan Klaij | Senior Researcher | Research & Development
MARIN | T +31 317 49 33 44 | [email protected]<mailto:[email protected]> | 
www.marin.nl<http://www.marin.nl>

[LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] 
<http://www.youtube.com/marinmultimedia>  [Twitter] 
<https://twitter.com/MARIN_nieuws>  [Facebook] 
<https://www.facebook.com/marin.wageningen>
MARIN news: Comfort draft for semi-submersible 
yachts<http://www.marin.nl/web/News/News-items/Comfort-draft-for-semisubmersible-yachts.htm>

________________________________
From: Matthew Knepley <[email protected]<mailto:[email protected]>>
Sent: Thursday, April 05, 2018 12:50 PM
To: Klaij, Christiaan
Cc: Smith, Barry F.; [email protected]<mailto:[email protected]>; Koos 
Huijssen
Subject: Re: [petsc-dev] getting on with the nested timers

On Thu, Apr 5, 2018 at 6:15 AM, Klaij, Christiaan 
<[email protected]<mailto:[email protected]>> wrote:
Barry,

I'm still trying to use petsc's nested logging with our code. I
have it working for 3.8.3 with the command line option, for
example:

mpirun -n 3 ./refresco -log_view :performance.xml:ascii_xml

This gives the expected performance.xml file. How to get the same
without command line options? So far I have:

CALL PetscLogDefaultBegin(ierr)
...
CALL PetscViewerASCIIOpen(MPI_COMM_WORLD,'performance.xml',viewer,ierr)
CALL PetscLogView(viewer,ierr)

which gives the regular log in the performance.xml file.

I guess I should replace PetscLogDefaultBegin by
PetscLogNestedBegin as stated in the manual page of PetscLogView.

But there's no manual page for PetscLogNestedBegin and I didn't
find anything like PetscViewerASCIIOpenXML either.

http://www.mcs.anl.gov/petsc/petsc-master/docs/manualpages/Profiling/PetscLogView.html

You need to push the ASCII_XML format before viewing.

  Thanks,

     Matt

Chris


dr. ir. Christiaan Klaij  | Senior Researcher | Research & Development
MARIN | T +31 317 49 33 44 | mailto:[email protected]<mailto:[email protected]> | 
http://www.marin.nl

MARIN news: 
http://www.marin.nl/web/News/News-items/Kom-zaterdag-10-november-naar-de-open-dag-in-Wageningen.htm




--
What most experimenters take for granted before they begin their experiments is 
infinitely more interesting than any results to which their experiments lead.
-- Norbert Wiener

https://www.cse.buffalo.edu/~knepley/<http://www.caam.rice.edu/~mk51/>



--
What most experimenters take for granted before they begin their experiments is 
infinitely more interesting than any results to which their experiments lead.
-- Norbert Wiener

https://www.cse.buffalo.edu/~knepley/<http://www.caam.rice.edu/~mk51/>

Reply via email to