[petsc-dev] PetscIntialize docs

Matthew Knepley knepley at gmail.com
Thu Sep 5 10:25:46 CDT 2013


On Thu, Sep 5, 2013 at 9:44 AM, Mark F. Adams <mfadams at lbl.gov> wrote:

> >
> >  1) ~username/.petscrc
> >  2) cwd/.petscrc
> >  3) "code specific file", whose name is passed into PetscIntitialize()
> >
> > If you pass in NULL to PetscInitialize(), it will not check option 3).
> If you pass in a real name to PetscIntiialize(), and
> > in the "code specific file" you put -skpi_petscrc, then it will not
> check options 1) and 2).
> >
>
> You can't put -skip_petscrc in the code specific file.  The whole idea of
> -skip_petscrc is that it keeps the code from trying to open a file.  The
> code opens the code specific file first, then command line args, then
> checks for -skip_petscrc.  So you need to give NULL for the the "file" here
> and put -skip_petscrc on the command line, if I am reading the code
> correctly.
>

Mark, it works exactly as I said in my first message. You can give
-skip_petscrc in the "code specific file" to prevent
reading the default files. You can ALSO give it on the command line to
prevent it reading the default files.

   Matt


> >     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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130905/669e9c12/attachment.html>


More information about the petsc-dev mailing list