Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 122)

Ticket Resolution Summary Owner Reporter
#57 fixed UO and PPM/PP logging not on same level in report MichaelHalloran michelpons

Reported by michelpons, 14 years ago.

Description

The attached log has been obtained while enabling simultaneously logging on a UO PMC and on a PPM PMC. The PPM and the PP appears to be logged at the same level in the log through the Viewer while the UO operation calls are below the level of the PP. Normally the UO and the PP should be on the same level at least for the first calls.

#2 fixed 09-020 CalcEquilibrium input arguments are logged after many intervening calls Michael Halloran michaelhalloran

Reported by michaelhalloran, 15 years ago.

Description

The scenario involves mostly a TP flash with accompanying property calculations. In the log file I have:

PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash:

MaterialObject <Anonymous> : Call to GetNumComponents

MaterialObject GetNumComponents returns 2

MaterialObject <Anonymous> : Return from GetNumComponents - No Error

To finally end with:

MaterialObject <Anonymous> : Call to SetProp :

Property Phase--- Basis--- Calc---- New value

volume Liquid mole Mixture 0.000022776

MaterialObject <Anonymous> : Return from SetProp - No Error

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

PropertyPackage <Anonymous> : Return from CalcEquilibrium - No Error

My point is that the lines:

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

Appear way too long after stating that a CalcEquilibrium is called. I would prefer, for the readibility of the log to have:

PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash:

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

And then

MaterialObject <Anonymous> : Call to GetNumComponents

MaterialObject GetNumComponents returns 2

MaterialObject <Anonymous> : Return from GetNumComponents - No Error

I have logged this issue as COLTT 09-020.

#3 worksforme 09-019 COLTT modifies error rmessage displayed in PROSIM when CalcEquilibrium fails Michael Halloran michaelhalloran

Reported by michaelhalloran, 15 years ago.

Description

I am logging a CAPE-OPEN VB6 UO in ProSim Plus 3.0.2.18. The Validate method is faced with a CalcEquilibrium that does not work, at least it is what I presume. When running the Validate without COLTT (1.07 and 1.08.02 have strictly the same behavior), I get an error message as in Screenshots_woCOLTT.doc, it says “la valeur de la propriété est inconnue”, something like the property value is unknown. With COLTT enabled on the UO, I get an error message as in Screenshots_withCOLTT.doc : “La méthode ~ de l’objet ~ a échoué” which may be translated as “the method of object ~ has failed”.

ProSim SA has told me that CalcEquilibrium is supposed to give an ECapeUnknown error code. The error is prompted by a GetProp made by the thermo server on the MO while the MO is not yet prepared to receive such calls since the MO is calculated once the UO represented the process feed has been calculated. The ECapeUnknown error code is consistent with the message displayed without COLTT “the value of the property is unknown”. So the point may be to investigate if and why ECapeUnknown does not appear as the error code displayed by CapeEquilibrium.

The message displayed by ProSIm Plus without COLTT is not that explicit for sure but it seems wrong to me for COLTT to somehow change the message displayed.

Note: See TracQuery for help on using queries.