[petsc-dev] Scalar data

Nathan Collier nathaniel.collier at gmail.com
Sat Nov 7 13:18:39 CST 2015

Perhaps he means that you could set an API in PETSc where you could
register scalar numbers (like say a L2 norm of the solution at the end of
time or some other quantity of interest) that then would be written out in
the -log_summary in a special section for this kind of information. This
way, you could write a single parser of the -log_summary output instead of
some custom one to also read code-specific output.


On Sat, Nov 7, 2015 at 1:52 PM Barry Smith <bsmith at mcs.anl.gov> wrote:

>    I have no idea what you mean by "scalar data", please expand
> > On Nov 7, 2015, at 12:11 PM, Matthew Knepley <knepley at gmail.com> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20151107/539299b2/attachment.html>

More information about the petsc-dev mailing list