#220 closed enhancement (invalid)
Create a non-editable snapshot of operators from the database operator library
| Reported by: | gkronber | Owned by: | gkronber |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.0 |
| Component: | CEDMA.Core | Version: | 3.2 |
| Keywords: | Cc: |
Description
To make sure that the exact algorithm can be reconstructed for each run and result.
Change History (6)
comment:1 Changed 16 years ago by gkronber
comment:2 Changed 16 years ago by gkronber
- Milestone changed from 3.1 to 3.2
- Version changed from 3.1 to 3.2
comment:3 Changed 16 years ago by swagner
- Milestone changed from 3.2 to Iteration 0
Milestone 3.2 deleted
comment:4 Changed 15 years ago by gkronber
- Resolution set to invalid
- Status changed from new to closed
This issue is non-existent after refactoring of all CEDMA plugins (see #419). Operators and algorithms/agents are not stored in the CEDMA database anymore. This means that a server side operator library is not needed anymore.
comment:5 Changed 14 years ago by swagner
- Milestone changed from Iteration 1 to Current
Milestone Iteration 1 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
Note: See
TracTickets for help on using
tickets.
We could automatically store a copy of the previous version of an operator in the database when it is edited. However we have to be careful about operator-links linking to the previous version of the operator. If the root of the link is the server side operator library the link should point to the new version however if the root of the link is either in a result or in an agent then the link should point to the old version (for transparency).