[petsc-dev] VecSetFromOptions() being called from all over the place

[Matthew Knepley]

On Sun, Sep 1, 2013 at 7:53 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> Barry Smith <bsmith at mcs.anl.gov> writes:
>
> > If so then shouldn't DMSetVecType() be the function that determines
> > the type for DM in one fell swoop instead of separate calls to
> > VecSetFromOptions() for each create? Note in theory that
> > DMSetFromOptions() has the option -dm_vec_type allowing runtime
> > selection of all the DM vectors also rather than the separate calls to
> > VecSetFromOptions() for each create?
>
> Yes.
>
> >   Can all these VecSetFromOptions() be removed?
>
> Probably replaced with VecSetType(X,dm->vectype)?
>

Note that this removes the ability to easily monitor these internal vectors.

   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/20130901/f825e836/attachment.html>