|
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. ************************************************************************************ |
Attachment:
Trnsy_users.rar
Description: Binary data