Ticket #27 (closed defect: wontfix)

Opened 11 years ago

Last modified 9 years ago

Log enabled automatically on both Thermo System and PPM

Reported by: michelpons Owned by: Michael Halloran
Priority: minor Milestone: Refactoring
Component: COLoggingController Version: 1.08.3
Keywords: Cc: michaelhalloran

Description

I am using COLTT 1.08.3 Build Oct 27, 2009. The combination involves Simulis Thermodynamics Thermo System as PMC and UniSim Design R390.1 as PME. I enable logging on Simulis Thermodynamics Thermo System through COLTT controller. I run the simulation in UniSim Design R390.1 and get a log file (attached). When reopening COLTT controller to disable COLTT on Simulis Thermodynamics Thermo System, I observe that COLTT is also indicated as enabled on Simulis Thermodynamics Property Package Manager. I find this awkward even if we know that Simulis Thermodynamics is designed a bit differently from other thermo servers providing support for both 1.0 and 1.1.

Attachments

unisimdesign_103109_150608.log (62.9 KB) - added by michelpons 11 years ago.
Log file obtained with COLTT 1.08.3 Build Oct 27, 2009
Registry_entries.zip (2.4 KB) - added by michelpons 11 years ago.
Zipped file containing registry entries of Simulis and TEA

Change History

Changed 11 years ago by michelpons

Log file obtained with COLTT 1.08.3 Build Oct 27, 2009

comment:1 Changed 11 years ago by michaelhalloran

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

This is not a problem that COLTT can solve: it requires the standard to define how a PMC that implements more than one set of interfaces should be described in the registry. I imagine that Simulis has one registry entry but records against it the categories for 1.0 Thermo System and 1.1 PPM. Because there is only one entry, both appear to be logged in COLTT's display, and in fact they are - a log would be created if either the 1.0 ThermoSystem or the 1.1 PPM was used. Contrast this with TEA. It is a single DLL that implements 1.0 and 1.1 but it has two registry entries, one for each set of interfaces but both entries point to the same DLL - COCOTEA.dll. When COLTT is applied to either one, the other is not affected even though they share the same dll. If Simulis were registered in the same way, this problem would not occur.

comment:2 Changed 11 years ago by michelpons

Since the CAPE-OPEN standards does not say how a PMC that implements more than one set of interfaces should be described in the registry, I guess it is up to COLTT to adapt itself slightly.

The end-user makes a decision, to enable either the Thermo System or the PPM. This decision could be enforced by the display, keeping track of what the end-user has clicked.

I have looked into the registry (see attached zipped file registry_entries.zip and indeed where TEA has two different CLSIDs one for a Thermo System the other one for a PPM, Simuls Thermodynamics has only one. It does not seem to me that paragraph 5.10 of the Thermodynamic and Physical Properties v1.1 interface specification tells what is right between the Simulis and the TEA registry entries. So till some modification is made to the spec, is there really no way to keep things clear in the controller?

Changed 11 years ago by michelpons

Zipped file containing registry entries of Simulis and TEA

comment:3 Changed 9 years ago by michelpons

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