Hi Roy, I just wanted to follow-up on this. The problem was on my side. I was incorrectly setting up the two-step solver options. The solver is behaving as expected now.
Thanks, Manav On Thu, Apr 4, 2013 at 7:06 PM, Manav Bhatia <[email protected]> wrote: > Thanks Roy. It is pretty high on my list, so I might take a stab at it in > the next couple of days. Will keep you posted about what I find. > > Manav > > On Apr 4, 2013, at 5:48 PM, Roy Stogner <[email protected]> wrote: > > > > > On Thu, 4 Apr 2013, Manav Bhatia wrote: > > > >> So, the TwoStepTimeSolver reduces the |F| to 10^-8 in about three > >> time steps, as opposed to about 100 that I would expect (with two > >> Newton iterations per time step). > > > >> The code modification that I mentioned in my previous email is all > >> that I changed for use of the TwostepTimeSolver class. > > > > I don't see anything wrong with that code modification... It's still > > certainly possible there's a bug in your application, but we don't > > have any test coverage on the TwostepTimeSolver right now and I > > personally haven't played with it in a long time; I'd give 50/50 odds > > on there being a library bug. > > > > I'll see if I can replicate the problem on some of my test > > applications here. I'm swamped right now though so ping me in a > > couple days if I don't get back to you before then. > > --- > > Roy > ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
