Ticket #144 (closed enhancement: fixed)

Opened 10 years ago

Last modified 10 years ago

Argument from CopyFromMaterial

Reported by: michelpons Owned by: Michael Halloran
Priority: minor Milestone: 2.2
Component: COLoggers Version: Development
Keywords: CopyFromMaterial Cc: michaelhalloran


I am starting from a case file out of PRO/II 9.2 in which three material streams have been drawn and two defined with flow, composition, pressure and temperature. The CPP Ideal Thermo PPM and its nC6nC8 PP are used. The scenario calls for inserting the CPP Mixer/Splitter Example in the flowsheet, access its CAPE-OPEN settings, change the heat input to 1, then connect the ports to material streams and run the simulation. It gives the log attached.

At the beginning of the Calculate method, the UO calls CopyFromMaterial onto a Material Object. The Material Object is mentioned as Anonymous. Within this call, it is logged that COLTT accesses the get_ComponentName method of the ICapeIdentification interface of an Anonymous MO: S1 is returned. Then the UO goes on by getting the present phases on a MO still mentioned as Anonymous. The CopyFromMaterial method has one argument, source. I think it would be wise somehow to mention the pointer value to the source MO. Further information could be displayed if indeed the get_ComponentName call succeeds like it is succeeding here.


Unconnected.prz (27.6 KB) - added by michelpons 10 years ago.
Case file in PRO/II 9.2
proii_082212_073508.log (173.8 KB) - added by michelpons 10 years ago.
Log file obtained with COLTT 2.1 build Aug 5, 2012

Change History

Changed 10 years ago by michelpons

Case file in PRO/II 9.2

Changed 10 years ago by michelpons

Log file obtained with COLTT 2.1 build Aug 5, 2012

comment:1 Changed 10 years ago by michaelhalloran

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

CopyFromMaterial now displays the name of the source material object as the input argument to the method. Fixed with commit 251 and available in builds after 16th September.

Note: See TracTickets for help on using tickets.