Ticket #129 (closed enhancement: fixed)
Discriminating between Anonymous
| Reported by: | michelpons | Owned by: | Michael Halloran |
|---|---|---|---|
| Priority: | major | Milestone: | 2.2 |
| Component: | COLoggers | Version: | Development |
| Keywords: | Anonymous | Cc: | michaelhalloran |
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?
Attachments
Change History
comment:1 Changed 12 years ago by michelpons
I had documented a request with PRO/II saying that MOs in PRO/II are not named and should. Development at Invensys has shown me using OATS/COULIS that MOs in PRO/II are indeed names while COLTT says they are Anonymous. This ought to be fixed because this issue does not reflect how PMEs behave and secondly it is often difficult to discreminate between MOs when all are Anonymous. I have attached one case in COFE where logging the Thermo System (TEA) and one UO (Compressor) let think that no MOs are named. Same issue in PRO/II where no MO appears with name.
Changed 12 years ago by michelpons
- Attachment cofe_090312_180902.zip added
Zipped log file obtained within COFE with COLTT 2.1.239
Changed 12 years ago by michelpons
- Attachment proii_090312_140526.log added
COLTT log file obtained with COLTT 2.1.239