Opened 13 years ago
Closed 13 years ago
#1573 closed defect (done)
Nested Optimizers cannot be executed separately
| Reported by: | mkommend | Owned by: | gkronber |
|---|---|---|---|
| Priority: | high | Milestone: | HeuristicLab 3.3.6 |
| Component: | Optimizer | Version: | 3.3.6 |
| Keywords: | Cc: |
Description
In the current implementation it is impossible to execute the algorithm of a batchrun only once, because as soon as the algorithm is started the batchrun gets started and repeats the algorithm execution. The same also holds for nested optimzers in experiments.
Change History (12)
comment:1 Changed 13 years ago by mkommend
- Status changed from new to accepted
comment:2 Changed 13 years ago by mkommend
- Milestone changed from HeuristicLab 3.3.5 to HeuristicLab 3.3.6
comment:3 Changed 13 years ago by mkommend
- Status changed from accepted to assigned
- Summary changed from Nested Optimizers could not be executed separately to Nested Optimizers cannot be executed separately
comment:4 Changed 13 years ago by mkommend
comment:5 Changed 13 years ago by mkommend
- Status changed from assigned to accepted
r6767: Decoupled execution states of Experiment and BatchRun with the nested optimizers.
comment:6 Changed 13 years ago by mkommend
- Owner changed from mkommend to gkronber
- Status changed from accepted to reviewing
comment:7 Changed 13 years ago by gkronber
reviewed r6767
comment:8 Changed 13 years ago by gkronber
- Status changed from reviewing to readytorelease
comment:9 Changed 13 years ago by mkommend
r6816: BatchRuns prepared the included optimizer if they were resumed from pause state.
comment:10 Changed 13 years ago by gkronber
The readonly state of run collection view is not updated correctly. While executing optimizers the run collection view should be locked. However, if the view is displayed while an embedded optimizer stops, and is subsequently prepared the readonly state of the run collection view toggles to the enabled state.
comment:11 Changed 13 years ago by mkommend
r6818: Made RunView always readonly to prevent the manipulation of run results.
comment:12 Changed 13 years ago by swagner
- Resolution set to done
- Status changed from readytorelease to closed
- Version changed from 3.3.4 to 3.3.6
A connected issue is that already prepared optimizers in an experiment or batch run get again prepared when the enclosing optimizer gets prepared. Since the OnPrepared method synchronously triggers the object graph collection to initialize IStatefulItems this can have strong performance impacts.