Reported by michelpons, 13 years ago.

When analyzing logs obtained with COLTT 1.08.5 with two different PMEs and the same PMC (the CPP Mixer Splitter example), I have noticed that within the Calculate method, the Duplicate method is called twice (because there are two feeds to the UO) and each time the pointer returned appears as the same. This is worrying me because in fact the previous MO is not released before a new duplicate is done according to the following excerpt of the CPP Mixer Splitter code:

bool Duplicate(Material &m,wstring &error) {ATLASSERT(materialObject); class should be instanciated properly create a new material object MaterialObjectWrapper *MO=materialObject->Duplicate(error); <------- NEW ONE IS OBTAINED if (!MO) return false ; fail clean up old MO in m if (m.materialObject) m.materialObject->Release(); <------- OLD ONE IS RELEASED set new m.materialObject=MO; ok return true ;

}

So while this has no consequence really for the CPP Mixer Splitter it is of interest to know if the pointer mentioned in the log is the real pointer or one pertaining to the CO logger. Could this be assessed?

Reported by michelpons, 15 years ago.

A defect had been raised a while ago with SimSci-Esscor about the fact that InitNew was not called by PRO/II on a a new CAPE-OPEN UO being inserted in a flowsheet. According to SimSci-Esscor secondary support, the bug LFPE#25122 (InitNew not called) got fixed and working fine. However the log I can make of a COUSCOUS UO in PRO/II 8.3 does not show InitNew being called (see proii_090909_194007.log). SimSci-Esscor thinks that COLLT is not reporting InitNew call when the persistence type is IPersistPropertyBag.

They have tested the behavior with their internal CAPE-OPEN test units (COSESPersistB100.dll, COSESPersistC100.dll and COSESPersistD100.dll in zipped archive). The COLTT log file (proiid_PKM.log) shows that InitNew is called for persistence types IPersistStreamInit and IPersistStorage (they made their run with COLTT 1.07). However, the COLTT log file does not show the call to InitNew when the persistence type is IPersistPropertyBag. SimSci-Esscor has debugged the code and noticed that InitNew is called for IPersistPropertyBag also. So there is a good chance that COLTT has not implemented IPersistPropertyBag and that leads to an improper report on InitNew being called.

Reported by michelpons, 14 years ago.

The attached log file is obtained with the GLCC UO in Aspen Hysys 7.2. Using COLTT on the GLCC UO makes a number of error messages appear that do not exist without COLTT enabled on the GLCC UO (typically error setting cell color which is documented in a previous issue). When looking the log file with the Viewer, I can't locate the call to Calculate method which is in the log file.