Sure thing! Matt, just to give you a bit of detail, the Monitor() calls to ASCII viewers were changed to respect the tab levels for the parent objects instead of manually pushing and popping tabs on the printouts. The code also tries to preserve the existing tab levels of the viewer though — that is, we first save the existing tab level, then indent monitor printouts from the root (0 tab) using the object’s tab level, and then set the viewer back to whatever tab level it was at before the monitor is called. So in theory, it shouldn’t be changing the behavior of the viewer outside of the monitor. It is entirely possible I introduced a bug somewhere and that’s what I’m going to look for right now, but in the meantime please let me know if there’s a use-case or a test I can use for debugging as well.
Thanks, — Alp Dener On April 3, 2018 at 6:11:12 PM, Smith, Barry F. ([email protected]<mailto:[email protected]>) wrote: Alp, Can you please take a look at this? Thanks Barry > On Apr 3, 2018, at 4:46 PM, Matthew Knepley <[email protected]> wrote: > > The recent indentation fix (I think) has broken the FAS solver indentation. > > Matt > > -- > 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 > > https://www.cse.buffalo.edu/~knepley/
