[petsc-dev] post 3.1 reorganization of PETSc DMMG code

Lisandro Dalcin dalcinl at gmail.com
Mon Apr 5 13:47:56 CDT 2010

On 3 April 2010 23:32, Matthew Knepley <knepley at gmail.com> wrote:
> Why would you attach an option instead of having an equiv API call?

Do PETSc have an equivalent API call for every option you can set
using options database?

> Strings
> are ALWAYS a bad interface.

But they are generic... I would love to to have a
{KSP|PC|SNES|TS}SetOptions() to pass name,value pairs of options...
Right now, every time I need it, I have to play with the GLOBAL
options database.

Think about MPI_Info ... Without it, the MPI API should be far more
complex for very little to gain... IMHO, your "ALWAYS" is  a bit
strong :-)

Lisandro Dalcin
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594

More information about the petsc-dev mailing list