Re: [TRNSYS-users] Iterations in TRNSYS - Type101

["keilholz, werner" <werner.keilholz@cstb.fr>]

Hi Lesh, 

If by "two iterations" you mean that the type is called twice for the same value of TIME, I think that is perfectly normal, even if there is no change whatsoever: 
The first call is the "initialization call", the second the "post convergence call". 

When I implemented such couplings I used the info array to avoid unnecessary calls (its explained in .\Trnsys17\Documentation\07-ProgrammersGuide.pdf , page 7-57.

For example, if you want only one call per step, you can check info(13) against 1.
Or, if you want to avoid the initialization step, check info(7) for 0. Etc...

Hope this helps,

Werner

-----Message d'origine-----
De : trnsys-users-bounces@cae.wisc.edu [mailto:trnsys-users-bounces@cae.wisc.edu] De la part de Baboo Gowreesunker
Envoyé : jeudi 30 juin 2011 08:12
À : trnsys-users@cae.wisc.edu
Objet : [TRNSYS-users] Iterations in TRNSYS - Type101

Hi

I'm trying to couple Type 101 (TRNSYS 17) with FLUENT for a simultaneous dynamic simulation in both softwares.

The problem is that for each timestep in TRNSYS, there are two iterations, even though the inputs do not change. Can anybody tell me why the two iterations, as opposed to only one ?

Regards
Lesh
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@cae.wisc.edu
https://mailman.cae.wisc.edu/listinfo/trnsys-users