Custom Query (122 matches)
Results (58 - 60 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. |
|||
#58 | fixed | Handling of long list of methods in Viewer | michaelhalloran | michelpons |
Description |
In the attached log file, both a UO and a PPM are logged. The list of methods in the method list is very long and goes further down than the screen in which it is displayed, resulting in some methods not being reached for filtering/defiltering. Could the list be displayed in multiple columns or maybe in multiple pages, ten or fifteen methods per page and a page numbering permitting to go from one page of method list to another. |
|||
#126 | fixed | Incomplete information out of GetComponentConstant call | Michael Halloran | michelpons |
Description |
I am investigating an issue that appeared initially when using an Aspen Properties Property Package out of version 7.3.2 from Aspen Plus in HTRI Xchanger Suite 6.0. I have transformed the scenario so that I am using COFE instead of XChanger. COFE crashes (with or without COLTT enabled on Aspen Properties Thermo System) when accessing the info on a compound. The document expliciting the scenario will be emailed separately. I am puzzled by the lack of info showing from the GetComponentConstant calls. For example: PropertyPackage <Anonymous> : Call to GetComponentConstant requesting these constants :
MaterialObject <Anonymous> : Call to get_ComponentIds
MaterialObject <Anonymous> : Return from get_ComponentIds - Succeeded PropertyPackage <Anonymous> : GetComponentConstant returns It looks like there is no return but I can't tell what is actually returned. At some point, when the property \"acentric factor\" is requested, COFE crashes. Can't tell why. I would appreciate if COLTT would show more. Don't know if it is possible. |