The Thermo SIG met from 3 pm till 4:45 pm (Central European Time).


Custom Data interface specification


Jasper van BATEN (AmsterCHEM), Mark STIJNMAN (Shell Global Solutions), Michel PONS (CO-LaN)


Participants went through the additions proposed earlier by Mark STIJNMAN:

  • for requirement 12 (persistence common interface to be used as the mean for copying custom data container from one thread to another), it now reads “If transfer between threads or processes needs to be facilitated, Persistence Common Interface must be implemented on Custom Data Containers”. An extensive rationale is given for this requirement,
  • the note in Use Case UC-004 ‘Copy Material Object content” now reads “Implementations can apply optimization techniques like copy-on-write, where data isn’t copied, but is instead shared between the original and the copied Custom Data Containers, until the data on either of them is changed. Only then a real (deep) copy will be made. The author of the Custom Data Container is responsible for implementing such optimizations in a way that maintain the same thread-safety guarantees as two fully independent copies.”,
  • scenario example (chapter 4.1) on electrolyte model was revised to explain how such a model could be optimized using Custom Data: assumptions regarding the scenario are listed, then what needs to be implemented is listed and explained with finally a proposed calculation procedure.

Next conference call is scheduled for May 16, 2018.