> 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) 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
