View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002022 | CCdciel | General | public | 18-11-15 13:59 | 19-06-08 18:51 |
| Reporter | Cedric Raguenaud | Assigned To | Patrick Chevalley | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Target Version | 1.0 | ||||
| Summary | 0002022: Suggestion: keep track of targets in sequence | ||||
| Description | I think this is on the roadmap already, but I had a quick stab at the idea. It's the next big thing for me (and probably for anyone who uses filters, long sequences, or long exposure sequences): as tagets are visited, keep track of them in a file so that next time the sequence is run, targets that have already been visited aren't revisited. This needs to also record filters, number of exposures (compared to what the plan requires) and other possible variable parameters of a target. | ||||
| Steps To Reproduce | This will require a checkbox to say "ignore history" in the sequence start tab (e.g. near "run unattended") so that a sequence can be restarted from scratch (default not checked). My best guess looking at the code quickly: - in T_Targets.InitTarget, load the history file for the sequence (e.g. sequencename.history.xml). If the target/filter/# exposures have already been run, return not ok for this target. - if the plan is partially completed, set the last saved status. - in T_Plan.Start adjust the current step based on the history of the target. - in T_Plan.NextStep record each completed step to the history file. - in T_Targets.NextTargetAsync once the sequence is completed without error, record the fact in the history file. I wish I could implement that, but I don't have enough time to relearn Pascal. | ||||
| Tags | No tags attached. | ||||
|
|
Yes this is something very useful but I not want to do that before a complete rework of the scheduler. The actual code is a complete mess because at start I wanted something very simple but I added feature over feature until I get this big spaghetti plate. It work but it is very difficult to touch something without introducing new bug. I plan this change for version 2.0, and I attache this issue to 0001894 where there is already a few other. |
|
|
I finally find a way to implement that with the current scheduler. This will be in the next version 0.9.57 The documentation for this function: https://www.ap-i.net/ccdciel/en/documentation/sequence#restarting_a_sequence |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 18-11-15 13:59 | Cedric Raguenaud | New Issue | |
| 18-11-15 23:04 | Patrick Chevalley | Assigned To | => Patrick Chevalley |
| 18-11-15 23:04 | Patrick Chevalley | Status | new => confirmed |
| 18-11-15 23:04 | Patrick Chevalley | Target Version | => 2.0 |
| 18-11-15 23:04 | Patrick Chevalley | Note Added: 0005083 | |
| 18-11-15 23:04 | Patrick Chevalley | Relationship added | related to 0001894 |
| 19-06-08 18:39 | Patrick Chevalley | Status | confirmed => resolved |
| 19-06-08 18:39 | Patrick Chevalley | Resolution | open => fixed |
| 19-06-08 18:39 | Patrick Chevalley | Target Version | 2.0 => 1.0 |
| 19-06-08 18:39 | Patrick Chevalley | Note Added: 0005683 | |
| 19-06-08 18:51 | Patrick Chevalley | Relationship deleted | related to 0001894 |
