The is revising the Custom Data interface specification which has been developed as a side project of the rewriting of the . During that rewriting, it appeared that letting a Property Package or a Chemical Reaction Package store intermediate results on a Material Object could be beneficial in terms of performance, especially when a Property Package is operating on a true composition and the PME on an apparent composition.
The current revision of the Custom Data interface specification introduces the concepts of a Custom Data Source and of a Custom Data Container. Obviously a Custom Data Source may be a Property Package or a Chemical Reaction Package. A Custom Data Container is a secondary CAPE-OPEN object on a Material Object. The Material Object has no way to write/read specific data from the Custom Data Container. Since Custom Data is private to a Custom Data Source, only the Custom Data Source who asked for that Custom Data Container to be created,is capable to access it in write or read. However it is the Material Object which creates and deletes the Custom Data Container. These concepts of Custom Data Source and Custom Data Container are new to this version of the Custom Data interface specification and are meant to clarify the interactions taking place around Custom Data.
is still expecting to release the Custom Data interface specification for review later this year.Statistics: Posted by colancto — 30 May 2018, 12:22
]]>