[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TRNSYS-users] How to trace non-convergence problems in large models
Jean,
There is a TRACE command that will print out the values of all the
parameters, inputs, and outputs of a given model at every iteration of
every timestep. It is easy to implement in the Studio: click on the icon
in the toolbar on the left that looks like some footprints then click on
the component(s) that you want to trace. The problem with this is that
in the Studio, you can either turn the trace on or off so you get VAST
amounts of difficult to digest data. If you open the *.dck directly
using TRNEdit and look for the TRACE keyword that you added in the
Studio then you can adjust the simulation time at which TRACE is turned
on and off. The statement that Studio adds is:
TRACE START STOP
but you can specify other times if you want:
TRACE 12 14
if, for example you know that there is a period of non-convergence
starting at noon on January 1.
The results are printed in the *.lst file.
Best,
David
On 11/22/2012 00:07, jeannieboef wrote:
Dear Group,
I wonder if you may have a tip as to finding the source of
non-convergence in large complex models. In my error report non of the
controllers report being stuck more than 0.0000000000%. of the time
(so that isn't it) and I don't have any pipes reporting to be too small.
Any tips?
Regards,
Jean
Sent from my iPhone
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@cae.wisc.edu
https://mailman.cae.wisc.edu/listinfo/trnsys-users
--
***************************
David BRADLEY
Principal
Thermal Energy Systems Specialists, LLC
22 North Carroll Street - suite 370
Madison, WI 53703 USA
P:+1.608.274.2577
F:+1.608.278.1475
d.bradley@tess-inc.com
http://www.tess-inc.com
http://www.trnsys.com