Re: [TRNSYS-users] Debugging own type with Microsoft Visual Studio 2010

[David Bradley <d.bradley@tess-inc.com>]

Florian,
Sorry, I should have specified. TRNSYS itself will generate a standard *.lst/*.log file error if there is a problem caught. The reason that debug mode isn't always active is that the checks are slow and reduce simulation speed.

Sent from my iPhone

On Aug 9, 2013, at 7:14, "Schreiner, Florian" <florian.schreiner2@student.kit.edu> wrote:

> Dear David,
> 
> thanks for your hint.
> I've activated the "debug mode" in the control cards. But the only change I
> can recognize is that  the "NAN_CHECK-entry" and the 
> "OVERWRITE_CHECK-entry" are set to "1" instead of "0" in the list-file.
> 
> How exactly should I recognize such an error now?
> If my type causes such an error (NAN or OVERWRITE)
> and  "debug mode" is activated, should the debugger stop now
> immediately at the causal code line?
> Because actually nothing changed.
> Debugging in Visual Studio, the simulation still proceeds to a certain Time and then gets stuck
> without some additional warnings before.
> 
> Kind regards,
> Florian
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users@cae.wisc.edu
> https://mailman.cae.wisc.edu/listinfo/trnsys-users