[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TRNSYS-users] How to skip timesteps if they don't reach convergence?



Javier,

  This sounds like TRNSYS is getting in to an infinite calculation loop inside one of its routines. The problem could be occurring in the kernel, in one of the standard Types or in a custom component. It is only possible to find out where the problem occurs by running the simulation from a Fortran compiler that allows you to step through the code. In our discussions yesterday, you mentioned that you were developing your own component. May I ask what compiler you are using and whether you are able to run your simulation in debug mode from the compiler so that you can step one line at a time through the code?

kind regards,

 David



On 06/08/2017 08:11, Javier Vega via TRNSYS-users wrote:
Jeff,

When I say TRNEXE gets "stuck" I mean it stops calculating at a certain timestep but TRNEXE doesn't close nor prints any message in the list file. It just stops and I can't use any of the display options of the TRNEXE window. When I check windows task administrator, TRNEXE is Non-Responding but using somewhat 17% of my CPU. Also, my mouse cursor changes in the TRNEXE window to the classical "loading" symbol.

I assume this is due to non convergence of a certain timestep? I was thinking that because right now, if I start my simulation from Time=0, TRNEXE turns "Non-Responding" at the same timestep.

I'm attaching a couple of images to illustrate the situation.

Kind regards,
Javier Vega






From: Jeff Thornton via TRNSYS-users <trnsys-users@lists.onebuilding.org>
To: trnsys-users@lists.onebuilding.org
Cc: 
Bcc: 
Date: Wed, 07 Jun 2017 16:09:54 -0500
Subject: Re: [TRNSYS-users] How to skip timesteps if they don't reach convergence?

TRNSYS will iterate until the iteration limit is reached, write a warning message to the list file, and then continue on to the next timestep.  When you say TRNEXE gets "stuck" what do you mean?

 

Jeff

 

---
Jeff Thornton
President - TESS LLC
22 N. Carroll Street, Madison WI USA 53703

On 06/07/2017 3:30 pm, Javier Vega via TRNSYS-users wrote:

Hello TRNSYS users,
 
I've noticed that some simulations finish with  messages that say that a certain component (or components) doesn't reach convergence at certain timesteps. The message is the following:
 
" The inputs to the listed units have not converged at this timestep. The values at the last iteration will be used and the simulation will proceed."
 
Right now I'm doing a simulation with 5 min timestep that works well but gets stuck at  hour 150, for example. If I change the simulation start time everytime this happens so the simulation can continue, it keeps calculating until  it gets stuck again 200 hours later.

I assume the TRNEXE gets stuck because of non convergence. Since the non converged timesteps are neglectable, how can I set TRNSYS to automatically ignore this timesteps and set the input/ouputs of the problematic units to the previous ones?
 
Is there a chapter in the TRNSYS Documentation that I should check?
 
Thanks in advance,
Javier Vega

_______________________________________________
TRNSYS-users mailing list
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@lists.onebuilding.org
http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
-- 
***************************
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