On Apr 4, 2013, at 7:42 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> > On Thu, Apr 4, 2013 at 7:10 PM, Matthew Knepley <knepley at gmail.com> wrote: > On Fri, Apr 5, 2013 at 9:53 AM, Derek Gaston <friedmud at gmail.com> wrote: > On Tue, Apr 2, 2013 at 12:09 PM, Barry Smith <bsmith at mcs.anl.gov> wrote: > You can use PetscGetArgs() followed by by PetscOptionsInsert(). Let us > know if you have any troubles with this. > > Hmmm... any chance of getting a version of that function that takes an > MPI_Comm? It is using PETSC_COMM_WORLD implicitly inside it.... and I need > to call it asynchronously on sub-communicators. > > I don't think we would put that in the interface since it would allow > inconsistencies among options. You can > call PetscOptionsInsertString() yourself to manage that. We don't technically forbid having different options on different communicators but unless you are careful it could be risky. > > Derek, what problem are you trying to solve by resetting the options like > this?
