Custom Query (122 matches)
Results (64 - 66 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#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. |
|||
#16 | fixed | GetCompoundConstant logging | michaelhalloran | michelpons |
Description |
While re-testing case 09-008 (also known as TRAC ticket #15), I have reviewed the log obtained (see attached). I am not satisfied with the logging of the GetCompoundConstant call: PropertyPackage <Anonymous> : Call to GetCompoundConstant
PropertyPackage <Anonymous> : Return from GetCompoundConstant - Succeeded I can't tell from the log if there is no property listed and/or no compound listed. May be there is nothing in both arguments but this is not obvious from the message. It should be more explicit. |