[TRNSYS-users] Problems using several types in a project

[Diego A. Arias]

Hi Johannes,

I think the problem is in line 264 of Type152.for. You do not need to 
reassign IUNIT and ITYPE every time that the Type is called.   If you 
delete these lines, IUNIT and ITYPE will be assigned at initialization 
call (INFO(7) = -1), and then the if statement in line 432 
(IF(INFO(1).NE.IUNIT)) will work.

The other alternative is to get rid of the IF statement in line 432. 
Force the type to re-read the parameters every time that it is called.
Please let me know if this works.

Best regards,

Diego

JOHANNES Kevyn wrote:
>
> Dear TRNSys users,
>
>  
>
> We developed a new TYPE to simulated PCMs behaviour coupled with TYPE 
> 56. Unfortunately, there are problems when more than 1 PCM TYPE is 
> introduced into the project. The TYPE is dynamically design (number of 
> nodes within the PCM layer, number of layer on both side of the PCMs 
> layer the STORAGE vector, etc.), the parameter, as well as the inputs 
> are read at each time step (the IUNIT is forced at each type read: 
> IUNIT=INFO(1)) and as well as the STORAGE vector.
>
>  
>
> No problems are identified using only one TYPE in a project but when 
> more than one TYPE is used (we just copy and paste the first type and 
> we change an input), the PCMs TYPES inputs seem to be mixed. The time 
> step used has also an influence on the results.
>
>  
>
> We might think that the state of the nodes at each time step from 
> several PCMs TYPES is mixed from one unit to another (e.g. within the 
> STORAGE vector). But we think we have followed the documentation on 
> the use of several TYPEs within the same project.
>
>  
>
> Does any one have an idea?
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & 
> computer viruses.
> ************************************************************************************
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at engr.wisc.edu
> https://www.cae.wisc.edu/mailman/listinfo/trnsys-users


-- 
Diego A. Arias
TRNSYS Coordinator
Solar Energy Laboratory
University of Wisconsin - Madison
1500 Engineering Drive
Madison, WI 53706