Reported by michelpons, 14 years ago.

I am using the material of Ticket#28. When examining the log obtained with COLTT 1.08.4, I find the following sequence:

Unit <Anonymous> : Call to put_ComponentName Unit <Anonymous> : Return from put_ComponentName - Succeeded Unit <CO1> : Call to get_ports Unit <CO1> : Return from get_ports - Succeeded

My belief is that \"CO1\" is the name that is put on the UO by the call to put_ComponentName so it would be fitting to have it appearing within the log of put_ComponentName such as in:

Unit <Anonymous> : Call to put_ComponentName ComponentName: CO1 Unit <Anonymous> : Return from put_ComponentName - Succeeded

Reported by michelpons, 12 years ago.

I am starting from a case file out of PRO/II 9.2 in which three material streams have been drawn and two defined with flow, composition, pressure and temperature. The CPP Ideal Thermo PPM and its nC6nC8 PP are used. The scenario calls for inserting the CPP Mixer/Splitter Example in the flowsheet, access its CAPE-OPEN settings, change the heat input to 1, then connect the ports to material streams and run the simulation. It gives the log attached.

At the beginning of the Calculate method, the UO calls CopyFromMaterial onto a Material Object. The Material Object is mentioned as Anonymous. Within this call, it is logged that COLTT accesses the get_ComponentName method of the ICapeIdentification interface of an Anonymous MO: S1 is returned. Then the UO goes on by getting the present phases on a MO still mentioned as Anonymous. The CopyFromMaterial method has one argument, source. I think it would be wise somehow to mention the pointer value to the source MO. Further information could be displayed if indeed the get_ComponentName call succeeds like it is succeeding here.

Reported by michaelhalloran, 15 years ago.

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.