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. Matt > For now I have it working by swapping out PETSC_COMM_WORLD with my > sub-communicator before calling that function.... but that's less than > ideal ;-) > > Derek > -- 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-users/attachments/20130405/9866e76c/attachment.html>
