[education/kstars] /: sub-exposure calculator documentation updates
Jasem Mutlaq
null at kde.org
Wed Jan 10 10:40:51 GMT 2024
Git commit 1599677064d794e6fa66e108f9ef8445365f2a9f by Jasem Mutlaq, on behalf of Joseph McGee.
Committed on 10/01/2024 at 11:40.
Pushed by mutlaqja into branch 'master'.
sub-exposure calculator documentation updates
M +4 -4 doc/ekos-capture.docbook
M +- -- doc/exposure-calculator.png
M +1 -1 kstars/ekos/capture/capture.ui
M +1 -1 kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp
M +14 -2 kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui
https://invent.kde.org/education/kstars/-/commit/1599677064d794e6fa66e108f9ef8445365f2a9f
diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 597cd5bf25..6d8ee36371 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -545,8 +545,8 @@ Approaches to imaging can vary greatly in the selection of exposure times, and n
<listitem>
<para>
<guilabel>Sky Quality</guilabel>: The <guimenu>Sky Quality selector</guimenu> sets the measurement of the magnitude per square arc-second of the background sky.</para>
- <para>The range for Sky Quality is from 22 for the darkest skies, to 16 for the brightest (most light-polluted) skies. The magnitude scale is non-linear; it is a logarithmic scale based on the 5th root of 100. So 5 steps on the scale represent a change in brightness by a factor of 100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each full integer step on the scale is a change by a factor of approximately 2.512.). <ulink url="https://en.wikipedia.org/wiki/Light_pollution">Wikipedia Sky Brightness</ulink>
-<ulink url="https://en.wikipedia.org/wiki/Light_pollution">Wikipedia Light Pollution</ulink></para>
+ <para>The range for Sky Quality is from 22 for the darkest skies, to 16 for the brightest (most light-polluted) skies. The magnitude scale is non-linear; it is a logarithmic scale based on the 5th root of 100. So 5 steps on the scale represent a change in brightness by a factor of 100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each full integer step on the scale is a change by a factor of approximately 2.512.). <ulink url= "https://en.wikipedia.org/wiki/Sky_brightness">Wikipedia Sky Brightness</ulink>
+<ulink url= "https://en.wikipedia.org/wiki/Light_pollution">Wikipedia Light Pollution</ulink></para>
<para>
All light scattered in the background sky is considered to be light pollution regardless of its source, so the effects of moonlight should be considered as "natural" light pollution. But weather conditions can also impact Sky Quality, as humidity or cloud cover can reflect and scatter any source of light through the atmosphere</para>
<para>
@@ -558,7 +558,7 @@ Approaches to imaging can vary greatly in the selection of exposure times, and n
</listitem>
<listitem>
<para>
- <guilabel>Focal Ratio</guilabel>: The selector for <guimenu>Focal Ratio</guimenu> set the value from the optical train, which is needed for the evaluation of light gathering capability.</para>
+ <guilabel>Focal Ratio</guilabel>: The selector for <guimenu>Focal Ratio</guimenu> sets the value from the optical train, which is needed for the evaluation of light gathering capability.</para>
<para>
The value of the focal ratio of the optic has a direct effect on the exposure calculation. A lower focal ratio is considered to be a "faster optic" as it has a greater light gathering capability than an optic with a longer focal ratio. So the exposure calculation will be reduced when a lower focal ratio is used, and increased when a higher focal ratio is used.</para>
<para>
@@ -691,7 +691,7 @@ For a strong target, (example, Orion Nebula with magnitude 4), would provide a r
</para>
<para>
-Depending on the various inputs and imaging conditions, the potential quality of a sub-exposure can vary greatly. In poor sky quality with little or no filtering, the computed sub-exposure time will naturally be short to avoid an overwhelming noise from light pollution, and the exposure time relative to the computed noise will be low (a low time/noise ratio). To achieve a high quality integrated image from low time/noise ratio sub-exposures may require thousands sub-exposures. If the user is concerned about imaging and processing time or storage capacity; then a higher time/noise ratio would needed to reduce the quantity of sub-exposures. Conversely, when input conditions result in a sub-exposure with a long exposure time relative to the computed noise (as with narrow-band imaging), the result is a sub-exposure with a very high time/noise ratio. In such cases the default value of 80, might result in very few sub-exposures for the integration. But the delta value will be quite high, indicating that raising the time-noise ratio will greatly improve the potential quality of the integrated image.
+Depending on the various inputs and imaging conditions, the potential quality of a sub-exposure can vary greatly. In poor sky quality with little or no filtering, the computed sub-exposure time will naturally be short to avoid an overwhelming noise from light pollution, and the exposure time relative to the computed noise will be low (a low time/noise ratio). To achieve a high quality integrated image from low time/noise ratio sub-exposures may require thousands sub-exposures. If the user is concerned about imaging and processing time or storage capacity; then a higher time/noise ratio would needed to reduce the quantity of sub-exposures. Conversely, when input conditions result in a sub-exposure with a long exposure time relative to the computed noise (as with narrow-band imaging), the result may be a sub-exposure with a very high time/noise ratio. In such cases the default value of 80, might result in very few sub-exposures for the integration. But the delta value will be quite high, indicating that raising the time-noise ratio will greatly improve the potential quality of the integrated image.
</para>
<para>
diff --git a/doc/exposure-calculator.png b/doc/exposure-calculator.png
index cda0ebca9f..6ffbbf4e1c 100644
Binary files a/doc/exposure-calculator.png and b/doc/exposure-calculator.png differ
diff --git a/kstars/ekos/capture/capture.ui b/kstars/ekos/capture/capture.ui
index 0826deb059..51d7cd8ce9 100644
--- a/kstars/ekos/capture/capture.ui
+++ b/kstars/ekos/capture/capture.ui
@@ -782,7 +782,7 @@
</size>
</property>
<property name="toolTip">
- <string><html><head/><body><p>Optimal sub-exposure calculator</p></body></html></string>
+ <string><html><head/><body><p>Exposure calculator</p></body></html></string>
</property>
<property name="text">
<string/>
diff --git a/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp b/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp
index 3fedcaf60b..2df80d7504 100644
--- a/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp
+++ b/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp
@@ -94,7 +94,7 @@ ExposureCalculatorDialog::ExposureCalculatorDialog(QWidget *parent,
ui->userSkyQuality->setValue(aPreferredSkyQualityValue);
ui->noiseTolerance->setMinimum(0.02);
- ui->noiseTolerance->setMaximum(200.00);
+ ui->noiseTolerance->setMaximum(500.00);
ui->noiseTolerance->setSingleStep(0.25);
ui->noiseTolerance->setValue(5.0);
diff --git a/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui b/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui
index 3f43d678dd..b41be380a5 100644
--- a/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui
+++ b/kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui
@@ -29,7 +29,7 @@
</size>
</property>
<property name="windowTitle">
- <string>Sub-Exposure Calculator</string>
+ <string>Exposure Calculator</string>
</property>
<property name="toolTip">
<string/>
@@ -136,6 +136,18 @@
<property name="toolTip">
<string>Alter the bias of the noise sources</string>
</property>
+ <property name="minimum">
+ <double>0.250000000000000</double>
+ </property>
+ <property name="maximum">
+ <double>500.000000000000000</double>
+ </property>
+ <property name="singleStep">
+ <double>1.000000000000000</double>
+ </property>
+ <property name="value">
+ <double>5.000000000000000</double>
+ </property>
</widget>
</item>
<item row="6" column="3" colspan="2">
@@ -969,7 +981,7 @@
<string>Integration time to noise ratio (potential quality)</string>
</property>
<property name="decimals">
- <number>1</number>
+ <number>2</number>
</property>
<property name="maximum">
<double>2000.000000000000000</double>
More information about the kde-doc-english
mailing list