Ticket #212 (new defect)

Opened 6 years ago

Last modified 5 years ago

ICapeCollection not implemented on energy stream object

Reported by: michelpons Owned by: michelpons
Priority: critical Milestone: 2.5
Component: COLoggers Version: 2.4
Keywords: Cc: michaelhalloran

Description

In the attached COFE document, a simple heater/cooler from COUSCOUS is defined as a flowsheet. One inlet material stream, one outlet material stream and an energy stream to carry the heat duty for the heating/cooling (as a result). COFE64 is used and COLTT 64-bit is used to log the Heater/Cooler. When the Material Object <5> is connected to Port <Heat>, there is a call made on ICapeCollection on the Material Object but the logger of the Material Object does not implement this interface. It should do according to section 2.1.7 of the CAPE-OPEN Unit Operation specification: "Energy Objects that connect to Energy Ports are expected to expose an ICapeCollection of
parameters, analogous to the Information Objects connected to an Information Ports described
above. The parameter “work”, of which the value is of type Real, and the dimensionality
corresponding to Watt (i.e. [m = 2, kg = 1, S = -3, A = 0, K = 0, mole = 0, …] representing kg
m2 s-3, see “Open Interface Specification: Parameter Common Interface”) is always part of an
Energy Object. In addition to that additional parameters can be present depending on the type of
energy that is being transported..."

Attachments

EnergyStream.fsd (30.2 KB) - added by michelpons 6 years ago.
COFE document
cofe64_042619_203206.log (90.5 KB) - added by michelpons 6 years ago.
Log file obtained with COLTT 2.4.0

Change History

Changed 6 years ago by michelpons

COFE document

Changed 6 years ago by michelpons

Log file obtained with COLTT 2.4.0

comment:1 Changed 6 years ago by jasper

Same for information streams. Note that in addition the port exposes an ICapeCollection of ICapeParameterSpec objects. All of these are to be logged.

comment:2 Changed 5 years ago by michelpons

  • Milestone set to 2.5
Note: See TracTickets for help on using tickets.