Custom Query (122 matches)
Results (43 - 45 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #73 | fixed | Crash on get_MaterialTemplate | michelpons | michelpons |
| Description |
I am using ChemSep Lite in Aspen Hysys 7.2 while relying on 1.1 Thermo (a COMThermo PP here). I am logging just ChemSep UO when configuring the case. As shown in the attachment, just at the beginning of the Edit method, there seems to be a call to get_MaterialTemplate. With COLTT enabled on ChemSep UO, Aspen Hysys crashes. Without cOLTT enabled on ChemSep UO, there is no crash. |
|||
| #69 | worksforme | Discreminating between calls made by COLTT itself and by PME/PMC | michaelhalloran | michelpons |
| Description |
The issue raised in Ticket#68 makes me feel that there is a need to clear discreminate between calls made by COLTT to obtain additional info in order to display better info in the log and calls made by PME/PMC. COLTT is supposed to trace the interaction between PME and PMCs so this interaction should be clearly delineated. Any call on top of that should be marked differently. The attached log files obtained with COLTT and OATS exemplify that GetCompoundList calls are added by COLTT to the interaction between PME and PMC. |
|||
| #129 | fixed | Discriminating between Anonymous | Michael Halloran | michelpons |
| Description |
In the attached log filen within Calculate I know that the UO gets temperature, pressure, partial mass flowrates from the MO connected to the inlet Port and then sets the same properties on the MO connected to the outlet Port before flashing the MO on the outlet Port. But all SetProp/GetProp calls are mentioned as being made on an anonymous MO. Without the source code of the UO, it would be impossible to know on what the UO acts. Even if the MOs are not named by the PME, which is a pity, could COLTT discriminate between anonymous MOs and mention an Anonymous_1, Anonymous_2 so that one could better follow the sequence? |
|||