Changes between Version 2 and Version 4 of Ticket #5721
- Timestamp:
- 2019-12-02T13:08:07Z (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5721 – Description
v2 v4 24 24 }}} 25 25 26 this function is generated for {{{sou_1}}} as you can see from the name. However, it seems the record type that is the input to the function is of type {{{ConstantEffectiveness.Medium.ThermodynamicState}}}. This type does not, strictly speaking, exist in the model since the partial Medium from which this type is picked up has been redeclared. It should have been {{{ConstantEffectiveness.sou_1.Medium. specificEnthalpy}}} from {{{sou_1}}}.26 this function is generated for {{{sou_1}}} as you can see from the name. However, it seems the record type that is the input to the function is of type {{{ConstantEffectiveness.Medium.ThermodynamicState}}}. This type does not, strictly speaking, exist in the model since the partial Medium from which this type is picked up has been redeclared. It should have been {{{ConstantEffectiveness.sou_1.Medium.ThermodynamicState}}} from {{{sou_1}}}. 27 27 28 28 I am still not entirely sure what causes this. If you use just one of the components, {{{sou_1}}} or {{{sou_2}}} **but not both** then everything works fine. This is because even though we pick the wrong name/type for the record we at least pick the one with correct elements in it. However, if you use both then the name is used for both and we have issues at codegen time.
