Problems replace the operators collection after deserialization

[mkommend]

Most problems have a StorableHook.AfterDeserialization that calls the InitializeOperators method. This method replaces the already loaded operators list with a newly instantiated list and populates the new list. Therefore it is possible that the operators change when an old file is loaded. A more accurate handling of loading problems would be to let the persistence populate the operators and only wire them correctly.

[abeham]

We fixed this for the algorithms, but seems like we forgot it for the problems.

[abeham]

r4098

• Fixed initialization of operators and made operator list storable

Reassigning to mkommend for change review

[abeham]

mkommend suggested:

• Checking the base calls from the storable constructor, that they call the base storable constructor
• Separate AttachEventHandlers from the post serialization storable hook

[abeham]

r4118

• Fixed problem plugins reloading their operators on deserialization in following problems (forgot on them in the first commit)
  • SupportVectorRegressionProblem
  • SymbolicTimeSeriesPrognosisProblem
• Fixed a bug in the FeatureSelectionProblem introduced in r4098
• Fixed the issues mentioned in the code review of mkommend

Reassigning to mkommend for another review please

[gkronber]

Added a project dependency for the ExternalEvaluation plugin with r4134.

[mkommend]

Reviewed the changes by abeham and everything seems to work.

[swagner]

Milestone Iteration 4 deleted

[swagner]

Milestone Current deleted