No, we are running that function again in solve, so it appears redundant, assuming solve will always be run. This may not be the correct abstraction but it is better than getting "Invalid Object State" errors back from PETSc when performing the order of operations mentioned in the comment. If you have ideas for a better abstraction, let us know.
Cody Sent from my evil iPhone On Mar 15, 2011, at 11:53 AM, Roy Stogner <[email protected]> wrote: > > It looks as if, as soon as we upgrade to PETSc 3.1, that new #if test > is going to disable any -snes_whatever options get set on the command > line. Am I misreading r4264? > --- > Roy ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
