Reported by michelpons, 15 years ago.

I am using the scenario used in Ticket#21.

When analyzing the log obtained with COLTT 1.08.4 (proii_110609_112126), I see the following for the logging of a get_ValStatus call:

Unit <CO1> : Call to get_ValStatus Unit <CO1> : Return from get_ValStatus - CAPE_NOT_VALIDATED

This is not consistent with the logging of for example a call to get_Value:

Parameter <Check> : Call to get_Value

get_Value returns: 1

Parameter <Check> : Return from get_Value - Succeeded

I think the log of get_ValStatus should look like:

Unit <CO1> : Call to get_ValStatus get_ValStatus returns CAPE_NOT_VALIDATED Unit <CO1> : Return from get_ValStatus - Succeeded

Reported by michelpons, 12 years ago.

I am using gPROMS to call an Aspen Properties Property Package. At some point gPROMS is requesting from Aspen Properties the calculation of vapor pressure for each pure compound. It gives the following sequence of calls:

PropertyPackage <Anonymous> : Call to CalcProp requesting: MaterialObject <Anonymous> : Call to get_ComponentIds

get_ComponentIds returns : WATER ETOH MEOH

MaterialObject <Anonymous> : Return from get_ComponentIds - Succeeded

Property Phase Calc Compounds vaporpressure liquid pure WATER

ETOH MEOH

MaterialObject <Anonymous> : Logging for ICOMaterialObject with GUID {3C860BB3-8AF4-4D93-A4BB-F9D068804365} is not supported by COLTT MaterialObject <Anonymous> : Call to GetNumComponents MaterialObject GetNumComponents returns 3 MaterialObject <Anonymous> : Return from GetNumComponents - Succeeded MaterialObject <Anonymous> : Call to get_ComponentIds

get_ComponentIds returns : WATER ETOH MEOH

MaterialObject <Anonymous> : Return from get_ComponentIds - Succeeded MaterialObject <Anonymous> : Call to GetProp

Warning - compIds argument is empty Property Phase Basis Calc Value returned temperature Overall (null) mixture 353.15

MaterialObject <Anonymous> : Return from GetProp - Succeeded MaterialObject <Anonymous> : Call to SetProp :

Warning - compIds argument is empty

COLTT <Anonymous> : Call to get_ComponentIds

get_ComponentIds returns : WATER ETOH MEOH

COLTT <Anonymous> : Return from get_ComponentIds - Succeeded

Property Phase Basis Calc Compounds New values vaporpressure Liquid (null) pure WATER 47368.360944

ETOH 108253.051078 MEOH 180667.040063

MaterialObject <Anonymous> : Return from SetProp - Succeeded PropertyPackage <Anonymous> : Return from CalcProp – Succeeded

One of the calls to get_ComponentIds is logged as made by COLTT but there are two other calls to get_ComponentIds in this sequence and they appear as made by the Property Package while there is only one made. So one call, while made by COLTT, is not flagged as made by COLTT.

Reported by michelpons, 11 years ago.

Build 263 is used: when opening up Controller and selecting a given component, the \"Enable Logging\" box is appearing as non-ticked. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out. Then I tick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box remain ticked and are now ungreyed. Next I untick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box have then greyed out and unticked. I close the COLTT controller and then enters it again. When going to the same component as before, the \"Enable Logging\" box is unticked while The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out.

I would think that ticking or unticking the \"Enable Logging\" box should not alter the two other boxes. Since by default these two boxes are ticked but greyed out, it means that they are partially independent from the \"Enable Logging\" box. Anyway they will be \"active\" only when a component is logged. Now I wonder if really the selection for these boxes is per component or rather is it for the entire set of components to be logged. I don't exactly how the implementation is done. If reference counting and error interface calls are not component dependent, the corresponding boxes should appear elsewhere than within a component detail.