Dissolve2 has the opportunity to make all data local to Nodes rather than storing everything deemed important in a GenericList. While the GenericList model (giving us Dissolve::processingModuleData_) does provide an easy means to read/write all important data at once with minimal effort, it does have its drawbacks.
If we move to a system where each Node has a serialiseData() and deserialiseData() function responsible for handling its own important data we can completely remove GenericList and all of the associated GenericItems. However, this raises important questions over what the stored data "looks like". Is it still one monolithic restart file, or a directory containing one file for each Nodes data, or something else?
Dissolve2 has the opportunity to make all data local to
Nodes rather than storing everything deemed important in aGenericList. While theGenericListmodel (giving usDissolve::processingModuleData_) does provide an easy means to read/write all important data at once with minimal effort, it does have its drawbacks.If we move to a system where each
Nodehas aserialiseData()anddeserialiseData()function responsible for handling its own important data we can completely removeGenericListand all of the associatedGenericItems. However, this raises important questions over what the stored data "looks like". Is it still one monolithic restart file, or a directory containing one file for eachNodes data, or something else?