Full operator-graphs are stored multiple times in the database even though most of it is static anyway

[gkronber]

added a table for operators in the CEDMA database with r416

[gkronber]

created a new type of operator library that is connected to the CEDMA db and a view for it with r417

[gkronber]

added class OperatorLink that allows to create CombinedOperators in the DatabaseOperatorLibrary which use other operators from the library (not via a copy but via a link) with r418

[gkronber]

worked on patching the operator-graph of an agent before execution with r419

[gkronber]

ticket was closed unintentionally in a hurry

[gkronber]

• Implemented downloading of linked operators from the database in AgentList (to allow view/edit of the whole operator graph)
• Implemented downloading and patching of linked operators in RunScheduler to prepare the operator-graph for execution (OperatorLink operator can't be executed)

with r420

(there is some code duplication because the patching is very similar in AgentList DatabaseOperatorLibrary and RunScheduler. This needs some more work)

[gkronber]

worked on this issue with r491:493

Patching of all operator links works correctly in test runs. However now all operator-links are patched on the first sweep. This means that sub-agents are already completely expanded (again fully expanded operator-graphs are stored multiple times in the DB unnecessarily). This issue needs to be fixed next.

[gkronber]

fixed the bug in the run scheduler that caused full expansion of all operator links with r497.

However this solution is just barely working for the test example. We probably need a better solution for this.

[gkronber]

There is still a bug where an operator-link is not patched before a view is created. Either make the operator-link patch itself or make sure all links are patched before the root operator is displayed.

[gkronber]

r513: Fixed the problem that sometimes an operator link was not patched before a view was created (which resulted in a NullException) by adding a property for the source database in OperatorLink! and updating this property recursively whenever an operator is loaded from the CEDMA DB.

The method for recursively setting the property is in static class OperatorLinkPatcher because the code is needed in Agent, DatabaseOperatorLibrary and OperatorLink.

Closing this ticket because with the help of OperatorLinks it's easy to define the static parts of operator-graphs separately in the server side operator library and link them into the algorithm.

[swagner]

Milestone 3.1 deleted

[swagner]

Milestone Iteration 0 deleted

[swagner]

Milestone Current deleted