Reported by michelpons, 12 years ago.

Using COLTT 2.1 Build June 5, 2012 I noticed in the attached log that many warning messages are written to the log file, within SetProp and GetProp method calls: Warning - compIds argument is empty

I wonder if this is relevant since the compIds argument may be UNDEFINED. Does it mean that the way UNDEFINED is set is wrong wrt the argument type? Is this warning significant with respect to the PMC or is it related to COLTT?

Reported by michelpons, 12 years ago.

In the attached log filen within Calculate I know that the UO gets temperature, pressure, partial mass flowrates from the MO connected to the inlet Port and then sets the same properties on the MO connected to the outlet Port before flashing the MO on the outlet Port. But all SetProp/GetProp calls are mentioned as being made on an anonymous MO. Without the source code of the UO, it would be impossible to know on what the UO acts. Even if the MOs are not named by the PME, which is a pity, could COLTT discriminate between anonymous MOs and mention an Anonymous_1, Anonymous_2 so that one could better follow the sequence?

Reported by michelpons, 12 years ago.

I am using COLTT 2.1 Build June 16, 2012 enabled on Aspen Properties v7.2 in COFE. I start from the attached bkp file which, once launched in Aspen Plus, permits the creation of a CAPE-OPEN Property package. Then I launch COFE, selects Aspen Properties Thermo System and then the EtOHWater PP just created. Next I am using the \"calculator\" within the \"Flowsheet\" menu of COFE. I choose to calculate a property, density for phase \"overall\". I get a crash that I investigate with COLTT. What does not seem right to me with COLTT is the warning message appearing with the call to CalcEquilibrium. It says \"Warning - props argument is empty\". I don't see the purpose of such a warning since it is usual to have no property requested on a CalcEquilibrium call. This warning should not be there.