Git commit 47e7a0a6f8872f4fb0dfb120d45608c98f4e08df by Hy Murveit.
Committed on 15/01/2024 at 22:29.
Pushed by murveit into branch 'master'.
Added handbook section on editing the scheduler queue while running, and on...
Added handbook section on editing the scheduler queue while running, and on the
Capture Sequence Editor.
M +5-0doc/ekos-capture.docbook
M +40 -2doc/ekos-scheduler.docbook
A +---doc/ekos_capture_sequence_editor.png
https://invent.kde.org/education/kstars/-/commit/47e7a0a6f8872f4fb0dfb120d45608c98f4e08df
diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 6d6a5edcea..565a63e974 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -343,6 +343,11 @@
To edit a job, double click it. You will notice the add button
now changed to check mark
button . Make your changes on the
left-hand side of the CCD module and once done, click on the check mark button.
To cancel a job edit, click anywhere on the empty space within the sequence
queue table.
+
+
+ Editing running jobs: When
Capture is running, or when the Scheduler is running, you cannot edit the
sequence queue or a .esq file on disk using the Capture tab. However, the
scheduler tab does have a Capture Sequence Editor tool that can be used to edit
.esl files on disk, or create new ones.
+
+
If your camera supports live video feed, then you can click the
Live Video button to start streaming. The video stream
window enables recording and subframing of the video stream. For more
information, check the video below:
diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook
index 61103b5cc0..2b287aa70e 100644
--- a/doc/ekos-scheduler.docbook
+++ b/doc/ekos-scheduler.docbook
@@ -80,9 +80,9 @@
-Scheduler Files (.esq)
+Scheduler Files (.esl)
- The scheduler table with its list of jobs and attributes can be
saved onto disk and read back in. It writes an .esq file. Controls for writing
the current Scheduler table to disk, and reading back other .esq files are
located above the table to the right.
+ The scheduler table with its list of jobs and attributes can be
saved onto disk and read back in. It writes an .esl file. Controls for writing
the current Scheduler table to disk, and reading back other .esl files are
located above the table to the right.
@@ -189,6 +189,44 @@ There is a checkbox and number input right below the
Scheduler jobs table that a
+
+Editing running jobs
+
+ It is possible to edit the scheduler's job table, and attributes of
individual jobs, while the scheduler is running. As always, you double click on
a job, change the desired attributes, and click the checkbox to finalize the
change. If you edit the running job it will be restarted (i.e. the startup
steps (slew, focus, align, guide) will be re-done. You can also move jobs up
and down in priority, add new jobs, or deleted existing ones. You cannot delete
the running job.
+
+
+ One important attribute of scheduler jobs is their sequence file
(.esq) which controls the capture module while the job is running. For example,
it sets number of captures, filters used, gain/ISO, etc. The .esq is normally
created and edited in the capture tab, but that cannot be done while the
scheduler is running. If you desire to make changes to a .esq file while the
scheduler is running, or create a new one, the scheduler provides a tool called
the Capture Sequence Editor.
+
+
+Capture Sequence Editor
+
+ The Capture Sequence Editor is a tool to create and edit capture
sequence files (.esq) which can be started by clicking the edit (pencil) icon
just above the scheduler table. A screenshot is shown below.
+
+
+
+Capture Sequence Editor
+
+
+
+
+
+
+Capture Sequence Editor
+
+
+
+
+ The editor is very similar in use and layout to the capture
tab--though it is missing all the controls to actually capture image. You edit
jobs the same way you do in capture, and load or save sequence queues the same
way too (though there are additional Load and Save-To buttons provided in the
editor).
+
+
+It is important to understand that capture sequences rely to
some extent on the filterwheel and camera being used (e.g. the filter names,
the possible ISO values, ...). The Capture Sequence Editor, which is not
connected to the device drivers, does not have direct access to this
information. Instead, the editor uses the values from the last time the capture
tab