[Facets-devel] PETSC ERROR

Satish Balay balay at mcs.anl.gov
Thu Jun 4 16:51:05 CDT 2009

On Thu, 4 Jun 2009, Matthew Knepley wrote:

> > > Why would the user give an argument for optfile, but not intend it to be
> > > found?
> >
> > Normally command line options is the way to pass in optional flags to
> > a petsc binary. In this application - command line options are not
> > possible [due to python/other packages that control main] - hence an
> > PetscIntialize("petscopt") is used to pass in equivalent optional
> > flags.
> >
> >
> > Also In this code - PETSc [solver] usage is optional. I guess there
> > are 2 ways of implementing this.
> >
> > The first is to always call PetscInitialize()/Finalize() - but
> > optionally use PETSc solvers. [in this case optfile should be
> > optional]
> I have no idea what you mean here. Why does optfile have to be an
> optional argument?  That makes no sense at all. You provide an
> argument, but only want it used sometimes?  DONT PROVIDE IT if it
> should not be used.

Why is ~/.petscrc or PWD/.petscrc or commandline options optional?
Same issue here.

Perhaps I want to define a different name than the .file so that its
visisble - and give it a unique name - so that its used by only this
application [and not other petsc applications]

Just giving reasons for why..

In this case - perhaps pwd/.petscrc will suffice. I'll have to check.


More information about the petsc-dev mailing list