Custom Query (122 matches)
Results (55 - 57 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#68 | fixed | GetCompoundConstant logs without values | michaelhalloran | michelpons |
Description |
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. |
|||
#69 | worksforme | Discreminating between calls made by COLTT itself and by PME/PMC | michaelhalloran | michelpons |
Description |
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. |
|||
#70 | worksforme | Multiple log entries about connecting a Port | michaelhalloran | michelpons |
Description |
I am using a Scilab UO from AmsterCHEM in Aspen Hysys 7.2. In the attached log file obtained with COLTT built of Aug 16, 2010, I see only once: Port <Feed 1> : Call to Connect Port <Feed 1> : Return from Connect - Succeeded while in the attached screenshot obtaiend with COLTT Viewer, I see this entry repeated a number of times. |