Git commit c058b9e63563d8984dd5e9350ef910d45aa19163 by Yuri Chornoivan. Committed on 09/11/2024 at 07:40. Pushed by yurchor into branch 'master'.
Fix minor typos M +7 -7 doc/imagingplanner.docbook https://invent.kde.org/education/kstars/-/commit/c058b9e63563d8984dd5e9350ef910d45aa19163 diff --git a/doc/imagingplanner.docbook b/doc/imagingplanner.docbook index b9d97eee08..8b7cf917ff 100644 --- a/doc/imagingplanner.docbook +++ b/doc/imagingplanner.docbook @@ -55,7 +55,7 @@ The Imaging Planner tool calculates when during the night objects can be imaged. <itemizedlist> <listitem><para>The minimum altitude in degrees that an object can be imaged is given in the Min alt box. If you change this value, you should see the Hours column recalculated in the object table and the graph recalculated in the Object Info section. </para></listitem><listitem><para>Similar to altitude, you can change the minimum Moon-separation angle in degrees. -</para></listitem><listitem><para>If the artificial horizon checkbox is checked, then artificial horizon constraints are used to calculate the possible imaging times. The artificial horizon are the parts of the sky that are blocked from imaging by buidings or trees or the like at your telescope's location. The artificial horizon is set up elsewhere in KStars (see <link linkend="settingmenu">Setting Menu</link> and go down to <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Artificial Horizon</guimenuitem></menuchoice>) and at its simplest is a list of azimuth and altitude values. If you make use of this tool and image from an area where significant parts of the sky is blocked, it is recommended you set up and use the artificial horizon feature. Associated with the artificial horizon is the SkyMap's <link linkend="terrain">terrain feature</link>. If you set up your terrain image, then when the Imaging Planner tool displays the object, you will see when it is relative to your local environment. Of course, you'd need to set a realistic imaging time--that is, if you plan during the daytime and the tool is locating objects at the current time, then the object may be set or behind buildings or trees. +</para></listitem><listitem><para>If the artificial horizon checkbox is checked, then artificial horizon constraints are used to calculate the possible imaging times. The artificial horizon are the parts of the sky that are blocked from imaging by buildings or trees or the like at your telescope's location. The artificial horizon is set up elsewhere in KStars (see <link linkend="settingmenu">Setting Menu</link> and go down to <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Artificial Horizon</guimenuitem></menuchoice>) and at its simplest is a list of azimuth and altitude values. If you make use of this tool and image from an area where significant parts of the sky is blocked, it is recommended you set up and use the artificial horizon feature. Associated with the artificial horizon is the SkyMap's <link linkend="terrain">terrain feature</link>. If you set up your terrain image, then when the Imaging Planner tool displays the object, you will see when it is relative to your local environment. Of course, you'd need to set a realistic imaging time--that is, if you plan during the daytime and the tool is locating objects at the current time, then the object may be set or behind buildings or trees. </para></listitem><listitem><para> KStars/Ekos uses astronomical twilight times to constrain imaging times. Using the defaults will result in no imaging outside of astronomical twilight times. If you wish to adjust this please see the constraint in the Ekos Scheduler's Offset menu--change the Dusk Offset positive to start imaging later, and negative to start imaging earlier. Similarly change Dawn Offset positive to continue imaging longer, and negative to stop imaging sooner. These controls can be found by selecting <menuchoice><guimenu>Tools</guimenu> <guimenuitem>Ekos</guimenuitem></menuchoice> and then clicking on the Scheduler tab (2nd from the left), clicking the <guibutton>Options</guibutton> button on the bottom right, and the offset tab on the top-left. </para></listitem> @@ -132,9 +132,9 @@ The Imaging Planner tool calculates when during the night objects can be imaged. </para></listitem><listitem><para>You may also want to set the time in KStars to reflect when you'll be imaging. See the Time menu. </para></listitem><listitem><para>If you don't set the time, you may want to hide the terrain display (if you've set that up) and also not render the ground, as those may obscure the object. You show and hide the terrain display in the view menu, and the ground can be disabled in <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Guides</guimenuitem></menuchoice> with the Opaque Ground checkbox. </para></listitem><listitem><para>If you're using a HiPS-based skymap, you would likely want local copies of the DSS data to speed-up the rendering of the SkyMap. See <menuchoice><guimenu>View</guimenu> <guimenuitem>HiPS All Sky Survey</guimenuitem></menuchoice> and under there <menuchoice><guimenu>HiPS Settings...</guimenu> <guimenuitem>Cache</guimenuitem></menuchoice> and enable the cache and enter the location of your local copy of the data. To download the data, one resource is https://coochey.net/?p=699 -</para></listitem><listitem><para>It would be useful to create a custom SkyMap "FOV Symbol" which is the same as the field-of-view of your imager. See <menuchoice><guimenu>Settings</guimenu> <guimenuitem>FOV Symbols</guimenuitem></menuchoice>, and inside there select <menuchoice><guimenu>New</guimenu> <guimenuitem>Canera</guimenuitem></menuchoice>, and enter the focal length of your optics and the camera's spedifications. +</para></listitem><listitem><para>It would be useful to create a custom SkyMap "FOV Symbol" which is the same as the field-of-view of your imager. See <menuchoice><guimenu>Settings</guimenu> <guimenuitem>FOV Symbols</guimenuitem></menuchoice>, and inside there select <menuchoice><guimenu>New</guimenu> <guimenuitem>Camera</guimenuitem></menuchoice>, and enter the focal length of your optics and the camera's specifications. </para></listitem> -</itemizedlist> +</itemizedlist> </sect2> <sect2 id="imagingplanner-catalogs"> <title>Catalogs</title> @@ -142,7 +142,7 @@ The Imaging Planner tool calculates when during the night objects can be imaged. KStars currently provides a single imaging-planner catalog via the <menuchoice><guimenu>Data</guimenu> <guimenuitem>Download New Data...</guimenuitem></menuchoice> menu item. The hope is that there will be future specialized catalogs, and possibly user-generated catalogs too. Therefore the catalog is formatted in a human-readable way. </para> <sect3 id="imagingplanner-catalogs-format"> - <title>Catalog Format</title> + <title>Catalog Format</title> <para> The format is currently a comma-separated file with one object on a row. </para> @@ -152,7 +152,7 @@ The Imaging Planner tool calculates when during the night objects can be imaged. </para></listitem><listitem><para>The 3rd column is the name of the image's photographer. </para></listitem><listitem><para>The 4th is a link to a larger version of the image, </para></listitem><listitem><para>The 5th column is Creative Commons license permission for using the image (e.g. ACC is Attribution Creative Commons, ANCSACC is Attribution Non-Commercial ShareAlike Creative Commons, using the same conventions as the Astrobin.com website). -</para></listitem> +</para></listitem> </itemizedlist> <para> To add an object without an image, simply add the object ID with no following commas, or an object ID with 4 following commas, such as one of these lines (without quotes): "M 42", or "M 42,,,,". An example full line might be: "M 42,M_42.jpg,Hy Murveit,https://www.astrobin.com/x4dpey/,ACC";. @@ -162,11 +162,11 @@ There are a few other possible specialized rows: </para> <itemizedlist> <listitem><para>Rows that start with # are comments.</para></listitem> - <listitem><para>Rows that containt LoadCatalog RELATIVE_CATALOG_FILENAME mean that the contents of RELATIVE_CATALOG_FILENAME should be read in as if they were in this catalog file.</para></listitem> + <listitem><para>Rows that contain LoadCatalog RELATIVE_CATALOG_FILENAME mean that the contents of RELATIVE_CATALOG_FILENAME should be read in as if they were in this catalog file.</para></listitem> </itemizedlist> </sect3> <sect3 id="imagingplanner-catalogs-loading"> - <title>Loading Catalogs</title> + <title>Loading Catalogs</title> <itemizedlist> <listitem><para> Catalogs read in from <menuchoice><guimenu>Data</guimenu> <guimenuitem>Download New Data...</guimenuitem></menuchoice> are stored in the standard KStars data directory, but catalogs can be read in from anywhere.
