Custom Query (122 matches)
Results (1 - 3 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #49 | worksforme | Error 1303 occurs when installing on Windows 7 or Vista | Michael Halloran | lich10hr |
| Description |
When attempting to install the 1.08 version of COLTT on a computer running Windows 7 or Vista, an error 1303 dialog occurs when attempting to install common controls to the WinSxS directory. You must then cancel the installation as it provides no option to get past the problem. Logging in as Adminstrator and/or setting compatibily mode to previous versions of Windows doesn't help. See the attached to view the error dialog. |
|||
| #1 | fixed | 09-021 COLTT 1.08.2 fails with Aspen Hysys and PPDS | michaelhalloran | michaelhalloran |
| Description |
This morning I had a remote session organized with Andy Johns of TUV NEL Ltd about a test of their PPDS Thermo server implementing Thermo 1.1 in Aspen Hysys v7.1.
During a run based on a case provided by one of TUV NEL clients (ABB I guess), I observed error messages sent by PPDS to Aspen Hysys about stream composition appearing as null. PPDS is equipped with its own logging facility but it is far from complete: the SetPresentPhases is not logged for example. So I moved to COLTT.
With COLTT 1.07 I was able to give evidence to Andy that PPDS was at fault while setting present phases for both vapor and liquid when the phase fraction for liquid was something like 10 to the minus 16 and while the liquid phase composition was set by PPDS to zero for all compounds. Then Aspen Hysys had the right to request the calculation of liquid phase properties that PPDS was unable to provide since it raises an exception when finding that the composition was null in the MO.
That proves that COLTT is working well.
The only problem I got was that Aspen Hysys is crashing when exiting (see ScreenshotsCOLTTv107.doc). No big deal except it means the PPDS license is not released.
So I moved to COLTT v1.08.02 with the hope of having it doing better on that. Well it is a complete failure: Aspen Hysys simply crashes when opening the case.
I will send you the logs obtained with 1.07 (hysys_090409_115121_v107.log) and 1.08.02 (hysys_090409_114804_v10802.log) as accompanying material in a zipped archive. The issue is numbered 09-021. |
|||
| #2 | fixed | 09-020 CalcEquilibrium input arguments are logged after many intervening calls | Michael Halloran | michaelhalloran |
| Description |
The scenario involves mostly a TP flash with accompanying property calculations. In the log file I have:
PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash: MaterialObject <Anonymous> : Call to GetNumComponents MaterialObject GetNumComponents returns 2 MaterialObject <Anonymous> : Return from GetNumComponents - No Error
To finally end with:
MaterialObject <Anonymous> : Call to SetProp :
MaterialObject <Anonymous> : Return from SetProp - No Error PropertyPackage Flashtype: TP PropertyPackage Properties: enthalpy, volume PropertyPackage <Anonymous> : Return from CalcEquilibrium - No Error
My point is that the lines:
PropertyPackage Flashtype: TP PropertyPackage Properties: enthalpy, volume
Appear way too long after stating that a CalcEquilibrium is called. I would prefer, for the readibility of the log to have:
PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash: PropertyPackage Flashtype: TP PropertyPackage Properties: enthalpy, volume
And then
MaterialObject <Anonymous> : Call to GetNumComponents MaterialObject GetNumComponents returns 2 MaterialObject <Anonymous> : Return from GetNumComponents - No Error
I have logged this issue as COLTT 09-020. |
|||