[petsc-dev] do PETSC_VIEWER_{HDF5,BINARY}_ need to exist?

Matthew Knepley knepley at gmail.com
Wed May 8 07:02:07 CDT 2019

On Wed, May 8, 2019 at 7:41 AM Hapla Vaclav via petsc-dev <
petsc-dev at mcs.anl.gov> wrote:

> Hello
> I just encountered their manpages and it's a mess. I think in case of file
> I/O, a user should be deliberate about filename and other settings.
> Sometimes less is more and I think this is the case. Why anybody should use
> PETSC_VIEWER_BINARY_(comm) and then set the filename with environment
> variable? Better to use PetscObjectViewFromOptions for instance
> (PETSC_OPTIONS can be used if one wants to use env var).
> (And BTW in case of HDF5, the option -viewer_hdf5_filename is not
> processed anywhere.)
> Any objections about removing these?

I am fine with it. The new system is better.

Since these are user interface, we should deprecate them somehow. Will the
normal deprecation work?



> Vaclav

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.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190508/958ef740/attachment.html>

More information about the petsc-dev mailing list