On Sat, Nov 7, 2015 at 4:09 PM, Barry Smith <[email protected]> wrote:
> > > On Nov 7, 2015, at 2:52 PM, Matthew Knepley <[email protected]> wrote: > > > > On Sat, Nov 7, 2015 at 2:47 PM, Barry Smith <[email protected]> wrote: > > > > > On Nov 7, 2015, at 1:47 PM, Matthew Knepley <[email protected]> wrote: > > > > > > On Sat, Nov 7, 2015 at 12:52 PM, Barry Smith <[email protected]> > wrote: > > > > > > I have no idea what you mean by "scalar data", please expand > > > > > > Lets just make it very specific. I want log_summary to also report > something like > > > > > > "L2 error": {0.000134256} > > > > Do you mean -log_summary which is just one very specific output of > logging data or do you mean tools like PetscLogView_Detailed[] etc. > > > > I don't think people should be parsing the output of -log_summary I > think they should be writing there own viewers that dump the information in > the way they want it (an example of this is PetscLogView_Detailed) > > > > I mean adding it to the Python module output (I think that is 'detailed') > > After raking the lawn I think this is a bad idea. The "detailed" Python > output is just a viewer for logged time, flops etc. If you want "parsable" > Python output from PETSc objects like KSP, TS, Mat etc then you should just > write viewers that print python output. If you want problem specific output > like actual computed error norms after calling a solver then your > example/application should just print that out to a viewer (outputting this > stuff should NOT be mixed up in the code with profile outputting). To help > this perhaps we need methods like PetscViewerASCIIPrintfPython() that > simplifies the printing of the python so people don't have to have things > like > > PetscViewerASCIISynchronizedPrintf(viewer,"Stages[\"%s\"][\"%s\"][%d] = > {\"count\" : %D, \"time\" : %g, \"numMessages\" : %g, \"messageLength\" : > %g, \"numReductions\" : %g, \"flops\" : %g}\n", > > Is that what you mean? > > Perhaps you mean some way of outputting information that is "delayed" > until the program ends and then it is printed right next to the -log_view > stuff? That sounds like a possible thing to add as well. Perhaps start > with an example that outputs some Python information like you want and then > we can think about how to do it with viewers and python formatted viewers. Yes, that would be fine. Matt > > > Barry > > > > > Matt > > > > > > Barry > > > > > > > > Matt > > > > > > > On Nov 7, 2015, at 12:11 PM, Matthew Knepley <[email protected]> > wrote: > > > > > > > > I had many requests from the class to put scalar data into the > log_summary. We were generating many summaries using a Python script, which > then read them back in as modules and processed the results. We could not > automatically get things like the error, which had to be parsed from the > output. > > > > > > > > I think allowing users to put scalar data in there would be a good > thing. Thoughts? > > > > > > > > Matt > > > > > > > > -- > > > > 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 > > > > > > > > > > > > > > > -- > > > 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 > > > > > > > > > > -- > > 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 > > -- 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
