Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (25 - 27 of 122)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#139 Not Reproducible COLTT log file created for a case with failed initialisation of Aspen Properties won't load into the Viewer michaelhalloran michaelhalloran

Reported by michaelhalloran, 8 years ago.

Description

This one is a mistake caused by using the Viewer when the log file was still being written to.

#137 fixed Logging of in argument for put_selectedReport Michael Halloran michelpons

Reported by michelpons, 8 years ago.

Description

I am starting from an Aspen Hysys case file where only three streams are declared, two of them being defined. I add a SciLab UO as a CAPE-OPEN Unit Operation. I don't go very far, just declaring two inlet ports and one outlet port in the SciLab UO before closing the \"Scilab CAPE-OPEN UO\" view. It means Edit is called only once. I am observing what takes place before the Edit call. It appears Aspen Hysys makes use of the methods of the ICapeUnitReport interface. Aspen Hysys asks the UO for its list of reports (call to get_Reports) and the list, made of a single report, is provided by the UO. Then Aspen Hysys makes a call to put_SelectedReport. COLTT checks by getting once more the list of reports, that the selected report is among the available reports. But there is no printing of a line like: put_selectedReport input argument: Scilab Output

which would be similar to what happens with put_ComponentName. For the sake of being consistent in the appearance of the logging, I think put_SelectedReport output should be modified.

#136 fixed Calculate call not flagged as in error while Michael Halloran michelpons

Reported by michelpons, 8 years ago.

Description

I am using a COUSCOUS Mixer within an Aspen Plus v7.3.2 flowsheet. On the first Calculate call on the Mixer UO, there is an error returned from Calculate with error code 0x80040501.

However, within COLTT Viewer, this call to Calculate is not flagged as being in error which is making more difficult the analysis. I think the Calculate call should be flagged as in error.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Note: See TracQuery for help on using queries.