Custom Query (122 matches)
Results (19 - 21 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#144 | fixed | Argument from CopyFromMaterial | Michael Halloran | michelpons |
Description |
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. |
|||
#39 | fixed | Argument of put_ComponentName call not displayed | Michael Halloran | michelpons |
Description |
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 |
|||
#75 | worksforme | Aspen Hysys crashes when using logged Aspen Properties PP | michaelhalloran | michelpons |
Description |
I am using a simple Aspen Properties PP in Aspen Hysys. Without COLTT enabled on Aspen Properties Therrmo System, I see no problem. When enabling COLTT on Aspen Properties Thermo System, I have a crash just after selecting the PP from Aspen Properties Thermo System. In the attached log, I see: MaterialObject <Anonymous> : Call to SetProp :
which may be wrong but does not cause a crash without COLTT. |