From: Andras V. <and...@ui...> - 2012-04-19 08:49:02
|
Dear Raimar, Actually, no, because the timestep displayed in the 2nd column is dtDid and not dtTry, while the timestep read in from the .sv file is dtTry. This was my confusion, too. I have pushed a new revision recently, with a bit clearer output in the case of trajectory continuation to remove this confusion. So, I still (or, again) have no idea why you get these infinites. Keep in touch, András On Thu, Apr 19, 2012 at 10:30 AM, Raimar Sandner <rai...@ui...>wrote: > Dear András, > > I want to look into this problem a little bit more. You closed the bug > about > the erroneous parsing of the timestep as invalid, but it seems to be a > valid > bug. The timestep is read in as 1 which is clearly wrong or am I mistaken? > > Best regards > Raimar > > On Friday 30 March 2012 00:03:46 Andras Vukics wrote: > > I could already detect the error at T=30 (after several continuations). > > There is also a hint of some bug, cf. > > > http://sourceforge.net/tracker/?func=detail&aid=3512988&group_id=187775&atid > > =922653 > > On Thu, Mar 29, 2012 at 9:16 PM, Andras Vukics > <and...@ui...>wrote: > > > Dear Raimar, > > > I've started to experiment, and try to reproduce your error. > > > Just a quick question: did you try in debug mode? > > > András > > > > > > > > > > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Cppqed-support mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cppqed-support > |