Reported by michelpons, 14 years ago.

I am using a UO built by IFP within COFE 1.15. The UO is a 3-phase separator. When the UO is not logged, the calculation goes to its end but COFE displays warnings about properties not set. So I enabled COLTT on the UO and reran the case. With COLTT enabled on the UO, I can drop the UO in the flowsheet, I can connect the inlet port and the three outlet ports to streams, but COFE aborts when I double-click on the icon representing the UO. The Edit method of the UO is not implemented and normally the generic UO interface from COFE should have appeared so that I may give values to the UO parameters.

The attached COLTT log shows that the logging stops in get_Reports. I attach also the COFE document from where I start. The installer for the UO is too large to be attached and will be delivered through a file server.

Reported by michelpons, 14 years ago.

I am using ChemSep Lite UO in COFE. The COFE flowsheet case will be provided as an attachment. I used this case to check how COLTT was behaving. My only minor concern is with the logging of Validate:

Unit <HPC> : Return from Validate - Succeeded, isValid=false

Message returned from Validate was: not all ports are connected Checking validation status after the call...

It seems to me that the message returned from Validate could be placed before :

Unit <HPC> : Return from Validate - Succeeded, isValid=false

Something like:

Validate returns : isValid : false Message : not all ports are connected Unit <HPC> : Return from Validate - Succeeded

I don't know from where:

Checking validation status after the call...

comes from. If it is an action taken by COLTT, there should be an appropriate way to mention that, oterwise there should be another way.

Reported by michelpons, 14 years ago.

I am using the GLCC UO in PRO/II 8.3 Patch 1. It relates to a case raised with SimSci-Esscor Support. I have a scenario that calls fro dropping the GLCC UO on the PRO/II flowsheet, to connect inlet and outlet ports, to edit the UO in order to choose the location for its output file, then to calculate the process model made of this UO. Examining the log made with COLTT, I see that get_Values calls on the integer parameters of the UO are at first looking good. Then, after the Edit call, the get_Values calls for integer parameters return a message \"An Invalid Argument\". What is not clear is who is sending this message and then what it means exactly. The only argument of such a call is the returned value. There is no error raised and no means for the call to pass a message. So my educated guess is that COLTT is posting the message but on what grounds. Plus, if it is indeed COLTT which is posting the message, it should be made obvious. Here, as it is posted, one may think that get_Value returns this message. Would it be possible to get more info on what is going on?