Custom Query (122 matches)
Results (31 - 33 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #130 | duplicate | Repeated calls by COLTT on persistence interfaces | Michael Halloran | michelpons |
| Description |
I am using COLTT 2.1 Build June 16, 2012 enabled on a TEA Thermo System and a COUSCOUS Mixer in PRO/II 9.1. I start from a case file where the TEA Thermo System and one of its PP has already been declared and two material streams have been defined. Then I drop the COUCOUS Mixer on the flowsheet, connect inlet ports and the outlet ports and then I run the simulation which ends up with no error. Parsing through the log file obtained, I am puzzled by the following sequence: COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface
COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to IPersistStream.Save COLTT <CO1> : Return from IPersistStream.Save - Succeeded It seems there are repeated calls on the same interface by COLTT and that the failure to find this or that interface on the UO is not accounted for by COLTT which repeats on and on the same calls. This sequence seems to occur several times and since the overall logging takes quite longer than the simulation wothout any log, I was wondering if unnecessary calls were made by COLTT and if so could be discarded. |
|||
| #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? |
|||
| #127 | fixed | Warning message - compIds argument is empty | Michael Halloran | michelpons |
| Description |
Using COLTT 2.1 Build June 5, 2012 I noticed in the attached log that many warning messages are written to the log file, within SetProp and GetProp method calls: Warning - compIds argument is empty I wonder if this is relevant since the compIds argument may be UNDEFINED. Does it mean that the way UNDEFINED is set is wrong wrt the argument type? Is this warning significant with respect to the PMC or is it related to COLTT? |
|||