Ticket #131 (closed defect: fixed)

Opened 2 months ago

Last modified 7 days ago

COM registration of COBIA PMCs: CapeVersion

Reported by: jasper Owned by: jasper
Priority: major Milestone: Maintenance of Phase II
Component: COMBIA Version: 1.2.0.10
Keywords: Cc:

Description

COM registration of COBIA PMCs takes its information from the registrar. This includes CapeVersion?, which is 1.2 for COBIA PMCs. COM registration should adapt this to 1.1.

Change History

comment:1 Changed 2 months ago by jasper

-It appears that Aspen HYSYS may be bothered by this in its interop.-

(unconfirmed, probably not)

Last edited 6 weeks ago by jasper (previous) (diff)

comment:2 follow-up: ↓ 4 Changed 2 months ago by jasper

... the correct version for a thermo providing PMC would be 1.1 - but in principle the unit spec (and others) are still at 1.0. A decision should be taken here.

comment:3 Changed 2 months ago by jasper

  • Version changed from 1.2.0.9 to 1.2.0.10
  • Component changed from Building distribution to COMBIA
  • Milestone set to Maintenance of Phase II

comment:4 in reply to: ↑ 2 Changed 6 weeks ago by jasper

Replying to jasper:

... the correct version for a thermo providing PMC would be 1.1 - but in principle the unit spec (and others) are still at 1.0. A decision should be taken here.

the decision is compounded by the fact that after 1.0, 1.1, 1.2, CapeVersion? is really going to be replaced by category IDs that indicate the supported CAPE-OPEN versions. Let's discuss.

comment:5 Changed 6 weeks ago by michelpons

My understanding of the discussion held during the M&T SIG meeting on October 18, 2022 is that "when COMBIA is registering a Property Package, a Physical Property Calculator or an Equilibrium Server in the Windows registry, it should store 1.1 as the CapeVersion? and for a Unit Operationn COMBIA should store 1.0 in the Windows registry for the CapeVersion? of that type of PMCs."

comment:6 Changed 6 weeks ago by jasper

... and in addition reporting of COM PMCs to COBIA should adjust CapeVersion? to 1.2

comment:7 Changed 6 weeks ago by jasper

Changing COM registration for COBIA interop, in case capeVersion is 1.2, it is changed to 1.1 for thermo components (identified by catIDs CAPEOPEN::categoryId_PropertyPackageManagerm CAPEOPEN::categoryId_StandAlonePropertyPackage, CAPEOPEN::categoryId_PhysicalPropertyCalculator, CAPEOPEN::categoryId_EquilibriumCalculator) or 1.0. COM components are exposed to COBIA as "1.2" in case capeVersion is "1.0" or "1.1". All example codes and default codes are changed to "1.2"

comment:8 Changed 6 weeks ago by jasper

  • Status changed from new to closed
  • Resolution set to fixed

In [300]:

Fix #131

comment:9 Changed 6 weeks ago by jasper

In [301]:

Fix #131

Note: See TracTickets for help on using tickets.