Reported by michelpons, 14 years ago.

The attached log file is obtained with the GLCC UO in Aspen Hysys 7.2. Using COLTT on the GLCC UO makes a number of error messages appear that do not exist without COLTT enabled on the GLCC UO (typically error setting cell color which is documented in a previous issue). When looking the log file with the Viewer, I can't locate the call to Calculate method which is in the log file.

Reported by michelpons, 14 years ago.

I am using the CO-LaN Property Package prototype in version 1.1 as a plug in Aspen Hysys 7.2. I am puzzled by the following: after a number of CheckEquilibrium calls, Aspen Hysys makes a number of GetCompoundConstant calls on the Property package. While in OATS, argument values of these calls are logged, in the COLTT log, no value of arguments is shown. Also, perhaps to deliver in the log the list of compounds, COLTT makes calls to GetCompoundList on top of what Aspen Hysys is requesting. These calls are returning an error. This run has been made with the version built on Aug 16, 2010. I attach the log obtained with COLTT as well as the one obtained with OATS.

Reported by michelpons, 14 years ago.

The issue raised in Ticket#68 makes me feel that there is a need to clear discreminate between calls made by COLTT to obtain additional info in order to display better info in the log and calls made by PME/PMC. COLTT is supposed to trace the interaction between PME and PMCs so this interaction should be clearly delineated. Any call on top of that should be marked differently. The attached log files obtained with COLTT and OATS exemplify that GetCompoundList calls are added by COLTT to the interaction between PME and PMC.