Reported by michelpons, 12 years ago.

I am using PRO/II 9.2 alpha and I am starting from a case file where the CPP Ideal Thermo PPM and its PP nC6nC8 are plugged in. Then I am inserting the CPP MixerSplitter example UO, connected its two inlets and one outlet.

Then I am running the case, saving and exiting. This gives the attached log file. I am looking at the sequence of calls logged at the beginning of the Calculate call:

COLTT <Anonymous> : Call to GetOverallProp

GetOverallProp Takes Input arguments:

Property Basis pressure UNDEFINED

GetOverallProp Returns:

Property Basis ValueReturned pressure UNDEFINED 100000

COLTT <Anonymous> : Return from GetOverallProp - Succeeded COLTT <Anonymous> : Call to GetOverallProp

GetOverallProp Takes Input arguments:

Property Basis totalFlow mole

GetOverallProp Returns:

Property Basis ValueReturned totalFlow mole 1.25998

COLTT <Anonymous> : Return from GetOverallProp - Succeeded COLTT <Anonymous> : Call to GetOverallProp

GetOverallProp Takes Input arguments:

Property Basis fraction mole

GetOverallProp Returns:

Property Basis ValueReturned fraction mole 0.3

0.7

COLTT <Anonymous> : Return from GetOverallProp - Succeeded COLTT <Anonymous> : Call to CreateMaterial COLTT <Anonymous> : Return from CreateMaterial - Succeeded COLTT Reference count for MO logger is 2 MaterialObject <Anonymous> : Call to CopyFromMaterial

It says that COLTT retrieves pressure, totalflow and composition. Well my reading of the CPP MixerSplitter source code tells me it is the Unit Operation which does that.

00195 first let us make sure we are in a valid state 00196 if (valStatus==CAPE_INVALID) 00197 {SetError(L\"Unit is not valid\",L\"ICapeUnit\",L\"Calculate\"); 00198 return ECapeUnknownHR; 00199 } 00200 if (valStatus==CAPE_NOT_VALIDATED) 00201 {SetError(L\"Unit has not been validated\",L\"ICapeUnit\",L\"Calculate\"); 00202 return ECapeUnknownHR; 00203 } 00204 ATLASSERT(valStatus==CAPE_VALID); 00205 init variables 00206 componentFlows.resize(nCompounds); 00207 for (j=0;j<nCompounds;j++) componentFlows[j]=0; 00208 totalFlow=0; 00209 enthalpy=0; 00210 pressure=0; 00211 loop over the connected feed ports, get the minimum pressure and the total component and enthalpy flows 00212 for (i=0;i<2;i++) 00213 {port=(MaterialPortObject *)portCollection->items[i]; 00214 if (port->IsConnected()) 00215 {get the pressure 00216 material=port->GetMaterial(); 00217 if (!material.GetOverallProperty(L\"pressure\",NULL,value,error)) 00218 {SetError(error.c_str(),L\"ICapeUnit\",L\"Calculate\"); 00219 return ECapeUnknownHR; 00220 } 00221 check count 00222 if (value.GetCount()!=1) 00223 {SetError(L\"Invalid values for pressure from material object: scalar expected\",L\"ICapeUnit\",L\"Calculate\"); 00224 return ECapeUnknownHR; 00225 } 00226 use minimum pressure 00227 d=value.GetDoubleAt(0);

00229 get total flow 00230 if (!material.GetOverallProperty(L\"totalFlow\",L\"mole\",value,error)) 00231 {SetError(error.c_str(),L\"ICapeUnit\",L\"Calculate\"); 00232 return ECapeUnknownHR; 00233 }

Reported by michelpons, 13 years ago.

After getting the list of log files in the Controller (see attachment Access logs Part 1.doc), I select the last log file obtained. Then I get an error message \"File not found\". After clicking OK to this message, the Viewer opens up with a blank view (see attachment Access logs Part 3.doc). Now if I call the Viewer outside from the controller and select the very same log file, it can be displayed. I am noticing that the name of the log file created by the Controller and passed on to the Viewer is wrong.

This defect is obtained with COLTT v2.0 Build Sep 10, 2011.

Reported by michelpons, 10 years ago.

With a UO supplied to me, once COLTT is enabled on it, even if I untick the \"Enable\" box, after closing the controller, reopening it lets see the UO with COLTT enabled once more. Something must be wrong in the way the registry access works. The DLL with its registration exe will be supplied. The only way I have found to go around the issue is to open the registry (regedit), to search for the UO name (Tester Helper), to suppress the entry in the registry for it, and then to register the UO again. If something goes wrong when disabling COLTT on a UO, the end-user should be told about it. If there is a way to easily circumvent the issue, it should be arranged for.