<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 21, 2013, at 10:07 PM, Jed Brown <<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@mcs.anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 3:31 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Why isn't this `PetscOptionsList()` so that it shows up in `-help`?<br>
<br>
My mistake, I cut and pasted the PetscOptionsGetInt() from the line above and figure that it mustn't be in a PetscOptionsBegin{} phase. You can fix it if you like.<br></blockquote></div><br>Hmm, problem is deeper than that. If the method has no sub-solver, wouldn't we rather not be checking this option, so that it shows up as an unused option? </div></div></blockquote><div><br></div><div>I thought the primary mission of options_left was to catch spelling mistakes.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">(This is also useful if a PC logically ought to pay attention to this option, but isn't.) What about making PCSetUseAmat() use PetscTryMethod() and move the check of "-pc_use_amat" into each implementation?</div>
<div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>I agree with Barry that it should be high level and make it there for any PC to use if they want.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">Do we really want to leave the confusing option in place for all the PCs that don't have inner solvers?</div>
</div>
</blockquote></div><br><div>It just doesn't seem that bad to me.</div></body></html>