<chapter id="config">
<title>Configuring &kstars;</title>

<sect1 id="setgeo">
<title>Setting the Geographic Location</title>

<para>
Here is a screenshot of the <guilabel>Set Geographic Location</guilabel>
window:
<screenshot>
<screeninfo>Changing the Geographic Location</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="geolocator.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Set Location Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
</para>

<para>
There is a list of over 3400 predefined cities available to choose from.
You set your location by highlighting a city from this list.  Each
city is represented in the world map as a small dot, and when a city
is highlighted in the list, a red crosshairs appears on its location
in the map.
</para>

<para>
<indexterm><primary>Geographic Location Tool</primary>
<secondary>Filtering</secondary></indexterm>
It is not practical to scroll through the full list of 3400 locations,
looking for a specific city. To make searches easier, the list can be
filtered by entering text in the boxes below the map. For example, in
the screenshot, the text <userinput>A</userinput> appears in the
<guilabel>City filter:</guilabel> box, while <userinput>Te</userinput> has been
entered in the <guilabel>Province filter:</guilabel> box, and
<userinput>USA</userinput> is in the <guilabel>Country filter:</guilabel>
box. Note that all of the cities displayed in the list have city,
province, and country names that begin with the entered filter
strings, and that the message below the filter boxes indicates that 6
cities are matched by the filters.  Also notice that the dots
representing these six cities in the map have been colored white,
while the unmatched cities remain gray.
</para><para>
The list can also be filtered by location in the map.  Clicking anywhere
in the world map will show only those cities within two degrees of the
clicked location.  At this time, you can search by name, or by location,
but not both at once.  In other words, when you click on the map, the
name filters are ignored, and vice versa.
</para><para>
<indexterm><primary>Geographic Location Tool</primary>
<secondary>Custom locations</secondary></indexterm>
The <link linkend="ai-geocoords">longitude, latitude</link> and
<link linkend="ai-timezones">time zone</link> information for the
currently-selected location are displayed in the boxes at the bottom of
the window.  If you feel that any of these values are inaccurate, you
can modify them and press the <guibutton>+</guibutton> (Add City) button
to record your custom version of the location.  You can also define a
completely new location by pressing the
<guibutton>Clear Fields</guibutton> button, and entering the data for
the new location.  Note that all fields except the optional
<guilabel>Province:</guilabel>/<guilabel>Country:</guilabel> must be filled before the new
location can be added to the list.  &kstars; will automatically load
your custom locations for all future sessions.  Please note, at this
point, the only way to remove a custom location is to remove the
appropriate line from the file <filename>kstars/mycities.dat</filename>
in your folder <userinput><command>qtpaths</command> <option>--paths GenericDataLocation</option></userinput>&nbsp;.
</para><para>
If you add custom locations (or modify existing ones), please send us
your <filename>mycities.dat</filename> file so that we can add your
locations to the master list.
</para>
</sect1>

<sect1 id="settime">
<title>Setting the Time</title>
<para>
<indexterm><primary>Date and Time</primary>
<secondary>The simulation clock</secondary></indexterm>
When &kstars; starts up, the time is set to your computer's system
clock, and the &kstars; clock is running to keep up with the real time.
If you want to stop the clock, select the <menuchoice><guimenu>Time</guimenu>
<guimenuitem>Stop Clock</guimenuitem></menuchoice> menu item, or simply
click on the <guiicon>Stop Clock</guiicon> icon in the toolbar.  You can
make the clock run slower or faster than normal, or even make it run
backward, using the time-step spinbox in the toolbar.  This spinbox
has two sets of up/down buttons.  The first one will step through all
83 available time steps, one by one.  The second one will skip to the
next higher (or lower) unit of time, which allows you to make large
timestep changes more quickly.
</para>
<para>
<indexterm><primary>Date and Time</primary>
<secondary>Setting</secondary></indexterm>
You can set the  time and date by selecting the <menuchoice><guimenu>Time</guimenu>
<guimenuitem>Set Time...</guimenuitem></menuchoice> menu item, or by
pressing the <guiicon>Time</guiicon> icon in the toolbar.  The
<guilabel>Set Time</guilabel> window uses a standard &kde; Date Picker
widget, coupled with a spinbox for setting the hours and minutes.
If you want to re-synchronize the simulation clock back to the
current CPU time, just select the <menuchoice><guimenu>Time</guimenu> <guimenuitem>Set
Time to Now</guimenuitem></menuchoice> menu item.</para>

<note><para>
<indexterm><primary>Date and Time</primary>
<secondary>Extended range of dates</secondary></indexterm>
&kstars; can accept very remote dates beyond the usual limits imposed by
QDate.  Currently, you can set the date between the years -100000 and +100000.
We may extend this range even further in future releases.  However, please
be aware that the accuracy of the simulation becomes more and more degraded
as more remote dates are examined.  This is especially true for the positions
of solar system bodies.
</para></note>
</sect1>

<sect1 id="viewops">
<title>The Configure &kstars; Window</title>
<para>
<indexterm><primary>Configure &kstars; window</primary></indexterm>
The <guilabel>Configure - &kstars;</guilabel> window allows you to modify
a wide range of display options.  You can access the window with the
<guiicon>Configure</guiicon> toolbar icon, or by selecting the
<menuchoice><guimenu>Settings</guimenu> <guimenuitem>Configure 
&kstars;...</guimenuitem></menuchoice> menu item.
The window is depicted below:

<screenshot>
<screeninfo>Configure - &kstars; Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="viewops.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Configure - &kstars; Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
</para>

<para>
The <guilabel>Configure - &kstars;</guilabel> window is divided into fourteen pages:
<guilabel>Catalogs</guilabel>, <guilabel>Solar System</guilabel>, <guilabel>Satellites</guilabel>,
<guilabel>Supernovae</guilabel>, <guilabel>Guides</guilabel>, <guilabel>Terrain</guilabel>,
<guilabel>Image Overlays</guilabel>, <guilabel>Colors</guilabel>, <guilabel>FITS</guilabel>,
<guilabel>INDI</guilabel>, <guilabel>Ekos</guilabel>, <guilabel>Xplanet</guilabel>,
<guilabel>Advanced</guilabel> and <guilabel>Developer</guilabel>.
</para>

<!-- Catalogs page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Catalogs page</secondary></indexterm> In
the <guilabel>Catalogs</guilabel> page, you determine several
properties concerning the display of the star and deep sky object catalogs.
</para>

<!-- Solar System page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Solar System page</secondary></indexterm>
In the <guilabel>Solar System</guilabel> page, you can specify whether
the Sun, Moon, planets, comets and asteroids are displayed.
</para>

<!-- Satellites page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Satellites page</secondary></indexterm>
The <guilabel>Satellites</guilabel> page allows you to set the satellites view options.
</para>

<!-- Supernovae page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Supernovae page</secondary></indexterm>
The <guilabel>Supernovae</guilabel> page allows you to manage how supernovae are displayed by &kstars;.
</para>

<!-- Guides page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Guides page</secondary></indexterm>
The <guilabel>Guides</guilabel> page lets you toggle whether non-objects
are displayed (&ie;, constellation lines, constellation names, the
Milky Way contour).
</para>

<variablelist>
  <varlistentry>
    <term></term><listitem><para><indexterm><primary>Sky culture</primary></indexterm>
    It is possible to choose a <guilabel>Sky culture:</guilabel> for the constellation lines and names on this page. The current version of &kstars; includes data for more than a dozen sky cultures.
    </para></listitem>
  </varlistentry>
</variablelist>

<!-- Terrain page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Terrain page</secondary></indexterm>
<indexterm><primary>Terrain image</primary>
<secondary>Customizing</secondary></indexterm>
The <guilabel>Terrain</guilabel> page allows you to set the terrain or landscape image
and configure its speedup options.
</para>

<!-- Image Overlays page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Image Overlays page</secondary></indexterm>
<indexterm><primary>Image Overlays</primary>
<secondary>Customizing</secondary></indexterm>
The <guilabel>Image Overlays</guilabel> page allows you to add and manage your own images
that will be displayed in the skymap.
</para>

<!-- Colors page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Colors page</secondary></indexterm>
<indexterm><primary>Color Schemes</primary>
<secondary>Customizing</secondary></indexterm>
The <guilabel>Colors</guilabel> page allows you to set the color scheme,
and to define new custom color schemes.
</para>

<!-- FITS page: -->
<para>For detailed explanation of the options on the <guilabel>FITS</guilabel>
page see the <link linkend="fits-configure">Configure FITS</link> section.
</para>

<!-- INDI page: -->
<para>For detailed explanation of the options on the <guilabel>INDI</guilabel>
page see the <link linkend="indi-configure">Configure INDI</link> section.
</para>

<!-- Ekos page: -->
<para>For detailed explanation of <guilabel>Ekos</guilabel> astrophotography suite,
see the <link linkend="ekos">Ekos section of this manual</link>.
</para>

<!-- Xplanet page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Xplanet page</secondary></indexterm>
The <guilabel>Xplanet</guilabel> page provides fine-grained control
over <ulink url="http://xplanet.sourceforge.net/">Solar system planet surface renderer Xplanet</ulink> (should be installed separately).
</para>

<!-- Advanced page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Advanced page</secondary></indexterm>
The <guilabel>Advanced</guilabel> page provides fine-grained control
over the more subtle behaviors of &kstars;.
</para>

<!-- Developer page: -->
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Advanced page</secondary></indexterm>
The <guilabel>Developer</guilabel> page allows you to enable or disable a few options mostly useful for developers or for folks looking to
help debug issues. Currently these are enabling the saving of images during Ekos's autofocus, guiding and alignment.
</para>
</sect1>

<sect1 id="catalogs">
<title>Catalogs</title>
<para>
  <indexterm><primary>Catalogs</primary></indexterm>
<screenshot>
<screeninfo>Catalogs Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="viewops.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Catalogs Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
</para>

<para>
<indexterm><primary>Catalogs page</primary>
<secondary>Short overview</secondary></indexterm> In the
<guilabel>Catalogs</guilabel> page, you can configure which object
catalogs are displayed by &kstars;, as well as how much information
you would like to be included on the Sky Map. By default, &kstars;
includes ~300,000 named and unnamed stars up to magnitude 8. For Deep
Sky Objects, the included catalog is the New General Catalog
(<quote>NGC</quote>) including the Index Catalog (<quote>IC</quote>)
and the Messier Catalog.
</para>

<para>
The New General Catalog of Nebulae and Clusters of Stars
(abbreviated as NGC) is a catalog of ca 7,840 deep-sky objects.
</para>

<para>
The Index Catalog of Nebulae and Clusters of Stars (abbreviated as
IC) serves as a supplement to the NGC, and contains an additional
5,386 objects, collectively known as the IC objects.
</para>

<para>
You can install new catalogs using &kstars; <quote>Add-On Installer</quote>. You can open it
via the <menuchoice><guimenu>Data</guimenu> <guimenuitem>Download New Data...</guimenuitem></menuchoice> menu item.
You can choose from a list of catalogs, including (but not limited to):
<itemizedlist>

<listitem><para>
Steinicke NGC/IC Catalog: is a more complete NGC/IC catalog.
</para></listitem>

<listitem><para>
Abell Planetary Nebulae Catalog: is a catalog of 86 planetary nebulae. The
maximum magnitude is represented by Abell 47's value of 19.5.
</para></listitem>

<listitem><para>
Sharpless HII region Catalog: is the Sharpless (Sh2) catalog of HII regions (diffuse nebulae).
</para></listitem>

<listitem><para>
Hickson Compact Groups: is a catalog consisting of 99 compact groups of galaxies.
</para></listitem>

<listitem><para>
Tycho-2 Star Catalog: is a catalog of more than 2.5 million of the brightest stars. It contains
stars with a magnitude value from 8.0 to 12.5.
</para></listitem>

<listitem><para>
USNO NOMAD Catalog: is a catalog of about 100 million stars with magnitude from 12.5 to 16.5.
Note that is requires Tycho-2 to be installed.
</para></listitem>

</itemizedlist>
</para>

<para>
The following is a summary of catalogs in &kstars;:

<table frame="top"><title>Stars Catalogs</title>
<tgroup cols="4" colsep="1" rowsep="1">
<thead>
<row>
<entry>Name</entry>
<entry>Abbreviation</entry>
<entry>Number of objects</entry>
<entry>Magnitude</entry>
<entry>Add-On</entry>
<entry>Default</entry>
</row>
</thead>
<tbody>
<row>
<entry>Default Catalog</entry>
<entry>Default</entry>
<entry>~300,000</entry>
<entry>Up to 8 magnitude</entry>
<entry>No</entry>
<entry>Yes</entry>
</row>
<row>
<entry>Tycho-2</entry>
<entry>Tycho2</entry>
<entry>more than 2.5 million</entry>
<entry>8.0-12.5 </entry>
<entry>Yes</entry>
<entry>No</entry>
</row>
<row>
<entry>Naval Observatory Merged Astronomic Dataset</entry>
<entry>USNO NOMAD</entry>
<entry>100 million</entry>
<entry>12.5-16.5</entry>
<entry>Yes</entry>
<entry>No</entry>
</row>
</tbody>
</tgroup>
</table>

<table frame="top"><title>Deep-sky objects Catalogs</title>
<tgroup cols="4" colsep="1" rowsep="1">
<thead>
<row>
<entry>Name</entry>
<entry>Abbreviation</entry>
<entry>Number of objects</entry>
<entry>Magnitude</entry>
<entry>Add-On</entry>
<entry>Default</entry>
</row>
</thead>
<tbody>
<row>
<entry>New General Catalog of Nebulae and Clusters of Stars (OpenNGC)</entry>
<entry>NGC</entry>
<entry>7,840</entry>
<entry>-</entry>
<entry>No</entry>
<entry>Yes</entry>
</row>
<row>

<entry>Steinicke NGC/IC</entry>
<entry>-</entry>
<entry>-</entry>
<entry>-</entry>
<entry>Yes</entry>
<entry>No</entry>
</row>

<row>
<entry>Abell Planetary Nebulae Catalog</entry>
<entry>-</entry>
<entry>86</entry>
<entry>Up to 19.5 magnitude</entry>
<entry>Yes</entry>
<entry>No</entry>
</row>

<row>
<entry>Sharpless HII region Catalog</entry>
<entry>Sh2</entry>
<entry>-</entry>
<entry>-</entry>
<entry>Yes</entry>
<entry>No</entry>
</row>

<row>
<entry>Hickson Compact Groups</entry>
<entry>-</entry>
<entry>99</entry>
<entry>-</entry>
<entry>Yes</entry>
<entry>No</entry>
</row>

</tbody>
</tgroup>
</table>
<note>
  <para>A potentially more up-to-date listing can be found in
    the <ulink url="https://protagon.space/catalogs/pages/catalogs.html">catalog
      repository documentation</ulink>.
  </para>
</note>
</para>

<para>
<indexterm><primary>Catalogs</primary>
<secondary>Star catalogs</secondary></indexterm>
The <guilabel>Stars</guilabel> section allows you to manage how stars are
displayed in &kstars;. You can choose to see the stars or not by checking the
<guilabel>Star catalogs</guilabel> checkbox. If you check it, then multiple
options will be enabled. Thus, you can set how many stars are drawn on the map
using the <guilabel>Star density:</guilabel> slider. You can also customize
&kstars; to toggle star name and <link linkend="ai-magnitude">magnitudes</link>.
Star names are drawn next to bright stars. To display labels of fainter stars,
increase the <guilabel>Label density:</guilabel> slider.
</para>

<para>
<indexterm><primary>Catalogs</primary>
<secondary>Deep-Sky Catalogs</secondary></indexterm>
Below the stars section, the <guilabel>Deep-Sky Objects</guilabel> section controls
the display of several non-stellar object catalogs. You can toggle the display of
Deep Sky Objects and control the display of their names and magnitudes. By default,
the list of deep-sky objects includes the Messier, NGC and IC catalogs.
Addons catalogs are available via the
<menuchoice><guimenu>Data</guimenu> <guimenuitem>Download New Data...</guimenuitem></menuchoice>
menu item where you can download catalogs provided by &kstars; team and the community through
the <ulink url="https://invent.kde.org/vboettcher/kstars-catalogs">catalog
packaging repository</ulink>. The <guilabel>DSO minimal zoom:</guilabel>
slider controls the minimal zoom level for which the
DSOs are shown. Increasing the minimal zoom level can lead to
performance improvements when panning the skymap zoomed-out.
The <guilabel>DSO cache percentage:</guilabel> slider regulates how
much of the DSO master catalog is being kept in memory. If you
experience memory issues with large catalogs, try lowering the
percentage. The <guilabel>Label density:</guilabel> slider controls
the perceived density of labels for the DSOs. If labels start to
overlap and the skymap begins to look too crowded, try tuning this
option. The <guilabel>Faint limit zoomed in/out:</guilabel> regulates up to which
magnitude objects are shown on the skymap (higher magnitude is
fainter). If <guilabel>Show objects of unknown magnitude</guilabel> is
ticked, objects of unknown magnitude are always shown.
</para>
<para>The following sections will detail how DSO catalogs work in
&kstars; and how they're managed.</para>

<sect2 id="catalog_general">
<title>The DSO Catalog Database</title>
<indexterm><primary>Deep-Sky Catalogs</primary>
<secondary>Database</secondary></indexterm>
<indexterm><primary>Deep-Sky Catalogs</primary>
  <secondary>Database System</secondary></indexterm>
<note>
  <para>
    This section aims at introducing the catalog database of &kstars; in
    simple but technical terms. It can be skipped without missing anything
    essential but helps understanding how to deal with and create (custom)
    catalogs.
  </para>
</note>
<para>
DSO catalogs  in &kstars; are  just SQL (sqlite3) database  tables. Each
catalog is represented by its own table which contains all its objects
and an entry in a catalog  metadata table. Additionally, catalogs may be
imported or exported from and into stand-alone database  files.
</para>

<para>
Each object has the usual properties like name and coordinates but
additionally features two IDs. The first ID is the unique identifier
for the specific object and is calculated by hashing all the object fields
along with the catalog id. Because objects can be contained in several
catalogs each object has an additional object id (OID) that identifies
the physical object and may be shared by several objects of different
catalogs.
</para>

<para>
To speed up object lookup all enabled catalogs are merged into a
master table. Each catalog has a priority number and if several
objects with the same OID occur the one from the catalog with the
highest priority is loaded. The objects from the master catalog are
then drawn on the sky and generally available in &kstars;.
</para>

<para>
Currently, deduplication (the assignment of OIDs) is only supported by
the tooling of
the <ulink url="https://invent.kde.org/vboettcher/kstars-catalogs">catalog
packaging repository</ulink>. The aim of this tool-chain is to
reproducibly build catalogs in a homogeneous environment. Every
catalog is
implemented <ulink url="https://invent.kde.org/vboettcher/kstars-catalogs/-/blob/master/catalogs/sharpless_2.py">
as a python module</ulink> and provides standard methods to acquire
data, parse it and find duplicates in other catalogs. All
downloadable catalogs are implemented this way. If you'd like to make
a catalog of your own available for &kstars;, it is recommended that you
implement it as a package in the repository. The tooling provided
there is so flexible, that it should work for you. For more
information on how to do that see
the <ulink url="https://protagon.space/catalogs/">catalog repository
documentation</ulink>. If you are not familiar with python programming
you can request the addition of a catalog by opening a ticket in the
repository or
contacting <ulink url="https://invent.kde.org/vboettcher/kstars-catalogs/-/project_members">the
maintainers</ulink>. &kstars; provides also provides means to create
custom catalogs by manually entering data or importing CSV tables, but
those are less flexible and offer no deduplication.
</para>
</sect2>
<sect2 id="catalog_gui">
<title>The Catalog Management &GUI;</title>
<indexterm><primary>Deep-Sky Catalogs</primary>
<secondary>GUI</secondary></indexterm>
<para>
The catalog management &GUI; is reached via the <menuchoice><guimenu>Data</guimenu>
<guimenuitem>Manage DSO Catalogs...</guimenuitem></menuchoice> menu item and is displayed
<link linkend="dso_manager">below</link>.

<screenshot>
<screeninfo>DSO Manager</screeninfo>
<mediaobject id="dso_manager">
  <imageobject>
    <imagedata fileref="dso_manager.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>The DSO catalog management interface.</phrase>
  </textobject>
  <caption>The DSO catalog management interface.</caption>
</mediaobject>
</screenshot>
</para>
<para>
On the left, a list of catalogs is displayed. In this list, you can
read off key catalog properties, including whether a catalog is
enabled, what its ID is and what its name
is. The <guilabel>Mutable</guilabel> column signifies whether the catalog
can be edited or not. Catalogs which have been downloaded from the
catalog repository via the <menuchoice><guimenu>Data</guimenu>
<guimenuitem>Download New Data...</guimenuitem></menuchoice> menu item are
usually immutable whereas user-created catalogs aren't. You can
always <guilabel>Clone</guilabel> a catalog to make it mutable.
</para>
<para>
The buttons in the upper right corner allow you to add catalogs to the
database.
</para>
<variablelist>
<varlistentry id="import">
<term><guibutton>Import Catalog...</guibutton></term>
<listitem>
  <para>Import a catalog in the <literal role="extension">.kscat</literal> format
  from a file.</para>
  <para>This is usually done to try out new versions of catalogs that
  haven't yet been picked up by the usual download server.</para>
</listitem>
</varlistentry>
</variablelist>
<para>
With the buttons in the lower right corner, you can add, remove, modify
and explore catalogs. Their actions always refer to the currently
selected catalog (the highlighted row on the left).

<variablelist>
<varlistentry>
<term><guibutton>Create Catalog...</guibutton></term>
<listitem>
  <para>Create a new catalog. See <xref linkend="create_catalog"/>.
  </para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Enable / Disable</guibutton></term>
<listitem>
  <para>Enable or disable a catalog.</para>
  <para>This is reflected in the skymap upon closing the
    catalog management &GUI;.</para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Remove</guibutton></term>
<listitem>
  <para>Remove a catalog from the catalog database.</para>
  <para>This is reflected in the skymap upon closing the
    catalog management &GUI;.</para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Export...</guibutton></term>
<listitem>
  <para>Export a catalog into a <literal role="extension">.kscat</literal> file.</para>
  <para>The resulting file can be imported with 
  <link linkend="import"><guibutton>Import Catalog...</guibutton></link> button.
  </para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Clone...</guibutton></term>
<listitem>
  <para>Make an exact copy of the catalog and insert it into the database.</para>
  <para>This is useful if you wish to make modifications to an
  immutable catalog.
    <note><para>Note however that this is not the recommended way to
    alter catalogs that are provided by
    the <ulink url="https://invent.kde.org/vboettcher/kstars-catalogs">catalog
    packaging repository</ulink> &ie; the catalogs downloaded via the
    <menuchoice><guimenu>Data</guimenu><guimenuitem>Download New
    Data...</guimenuitem></menuchoice> menu item.
    </para>
    </note>
  </para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Colors</guibutton></term>
<listitem>
  <para>Open the catalog color editor (See <xref linkend="catalog_colors"/>.).
  </para>
  <para>This will open a dialog which allows you to set the colors in
  which objects from the selected catalog will be displayed for each
  color scheme.
  </para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>More...</guibutton></term>
<listitem>
  <para>Open the catalog details dialog. (See <xref linkend="catalog_details"/>.)
  </para>
  <para>In there, you can see the contents of the catalog, as well as
  some more meta information. Amongst other things, you can also edit
  its contents (if it is mutable).
  </para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect2>

<sect2 id="create_catalog">
<title>Creating a new Catalog</title>
<screenshot>
<screeninfo>Catalog creation dialog</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="create_catalog.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Catalog creation dialog.</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
This dialog reached through the catalog management &GUI; (see
<xref linkend="catalog_gui"/>). The <guilabel>ID:</guilabel>
field will be automatically chosen but can be
changed. The <guilabel>Color:</guilabel> field configures in which
color the objects of the catalog will be displayed. All the other
values are optional or have sensible defaults. You can, of
course, change these values at a later point.
</para>

<para>Upon clicking <guilabel>Ok</guilabel> an empty catalog with the
  meta data entered into the dialog will be added to the database and
  can then be filled with
  objects. (See <xref linkend="catalog_details"/> and <xref linkend="csv_import"/>.)
</para>
</sect2>

<sect2 id="catalog_colors">
<title>Catalog Color Editor</title>
<indexterm><primary>Deep-Sky Catalogs</primary>
  <secondary>Catalog Color Editor</secondary></indexterm>

<screenshot>
<screeninfo>Catalog color editor</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="color_editor.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>The catalog color editor.</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
This dialog reached through the catalog management &GUI; (see
<xref linkend="catalog_gui"/>). Each button represents the color that
objects will be drawn in for a specific color scheme. Clicking on a
button will allow you to choose a color with a color picker. The
button colors are initialized with the default colors from the catalog
specification. The color "default" is the color which will be chosen
for the catalog if there is no color set for a color scheme.
</para>
</sect2>

<sect2 id="catalog_details">
<title>Catalog Details Dialog</title>
<indexterm><primary>Deep-Sky Catalogs</primary>
  <secondary>Catalog Details Dialog</secondary></indexterm>

<screenshot>
<screeninfo>Catalog details dialog</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="catalog_details.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>The catalog details dialog.</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
This dialog reached through the catalog management &GUI; (see
<xref linkend="catalog_gui"/>). In the top left corner, the catalog
metadata is being displayed. On the right, a table of all objects in
the catalog is being shown. The search line above the table filters
objects by name. Double-clicking a row opens the object details dialog
(see <xref linkend="tool-details"/>).
</para>
<para>
Selecting a row enables
the <guilabel>Object</guilabel> menu on the left.
Selecting multiple rows performs the single-object action for each
selected object.

<variablelist>
<varlistentry>
<term><guibutton>Edit...</guibutton></term>
<listitem>
  <para>Edit the catalog object. (See <xref linkend="add_object"/>).
  </para>
</listitem>
</varlistentry>

<varlistentry>
<term><guibutton>Remove</guibutton></term>
<listitem>
  <para>Removes the object from the catalog.
  </para>
</listitem>
</varlistentry>
</variablelist>
</para>

<para>
  Below the <guilabel>Object</guilabel> section, the general catalog
  options are situated.

<variablelist>
<varlistentry>
    <term><menuchoice>
        <guimenu>Edit Catalog Meta...</guimenu>
    </menuchoice></term>
    <listitem>
      <para>Edit the catalog metadata displayed in the top left. This
        opens the dialog described in <xref linkend="create_catalog"/>.
      </para>
    </listitem>
  </varlistentry>

  <varlistentry>
    <term><guibutton>Add Object...</guibutton></term>
    <listitem>
      <para>Add an object to the catalog. (See <xref linkend="add_object"/>.)
      </para>
    </listitem>
  </varlistentry>

  <varlistentry>
    <term><guibutton>Import CSV...</guibutton></term>
    <listitem>
      <para>Import objects from a tabular text format (csv, tsv,
        &etc;) into the catalog. (See <xref linkend="csv_import"/>.)
      </para>
    </listitem>
  </varlistentry>
</variablelist>
</para>
<sect3 id="add_object">
<title>Adding/Editing Objects</title>
<indexterm><primary>Deep-Sky Catalogs</primary>
  <secondary>Adding/Editing Objects</secondary></indexterm>

<screenshot>
  <screeninfo>Add/Edit DSO Dialog</screeninfo>
  <mediaobject>
    <imageobject>
      <imagedata fileref="add_object.png" format="PNG"/>
    </imageobject>
    <textobject>
      <phrase>Add/Edit DSO Dialog</phrase>
    </textobject>
  </mediaobject>
</screenshot>
<para>
  This dialog allows to create or edit a deep sky object
  (DSO). The <guilabel>Basics</guilabel> section contains fields that
  have to be filled in.
</para>

<variablelist>
  <varlistentry>
    <term><guilabel>Name:</guilabel></term>
    <listitem><para>The name of the object which will be displayed in the sky.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>Type:</guilabel></term>
    <listitem><para>The type of the object.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>RA / Dec (°, J2000):</guilabel></term>
    <listitem><para>The coordinates of the object in degrees and with respect to the J2000 epoch.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>Apparent magnitude:</guilabel></term>
    <listitem><para>The apparent magnitude of the object.</para></listitem>
  </varlistentry>
</variablelist>

<para>
  The <guilabel>Optional</guilabel> section contains data fields that
  are optional, is divided into two subsections. They are set to and can be left at their defaults.
</para>

<para>
  The <guilabel>Size Info in Arcminutes</guilabel> subsection. The object is modeled as an ellipse which is described by its major and minor axis.
</para>

<para>
  The <guilabel>Misc</guilabel> subsection.
</para>

<variablelist>
  <varlistentry>
    <term><guilabel>Long name:</guilabel></term>
    <listitem><para>A longer, more descriptive name.</para>
    <para>Usually, the long name is something like <quote>Andromeda Galaxy</quote> for the object M31. It can contain alternative designations and names in other catalogs as well.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>Catalog identifier:</guilabel></term>
    <listitem><para>A catalog internal identifier.</para>
    <para>For example the screenshot above, the object originates from the OpenNGC catalog where each row is identified by <quote>NGCXXXX</quote>.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>Flux:</guilabel></term>
    <listitem><para>The flux of the object. Only applies for radio sources.</para></listitem>
  </varlistentry>

  <varlistentry>
    <term><guilabel>Position angle (°):</guilabel></term>
    <listitem><para>If the object is extended, it must have some orientation in the sky. The position angle is the angle between its major axis and a straight line to the north pole.</para></listitem>
  </varlistentry>
</variablelist>

</sect3>
<sect3 id="csv_import">
<title>Importing CSV (and similar formats)</title>
<screenshot>
<screeninfo>Importing CSV Catalogs</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="csv_import.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Importing CSV Catalogs</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>The screenshot above shows the CSV import dialog in its default
  state. In the <guilabel>Input</guilabel> section, you can
  configure the csv parser. The <guilabel>Comment prefix:</guilabel> is
  the character that signals commented-out lines in the
  input. The <guilabel>Separator:</guilabel> should be adjusted to fit
  your input. Usually, it is <quote>,</quote> or <quote>;</quote> but other separators can
  occur. Finally, you can choose to skip a number of lines at the
  beginning of the file. <guibutton>Select/Read</guibutton> button lets you
  choose a csv file to read with the above configuration. After that,
  the dialog will look as in the screenshot below.
</para>
<screenshot>
<screeninfo>Importing CSV Catalogs, Populated</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="csv_import_populated.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Importing CSV Catalogs</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
In the top right you can choose whether coordinates are being
expressed in degrees or
hours/minutes/seconds. The <guilabel>Mapping</guilabel> section lets
you map columns in the CSV file to data fields in
&kstars;. Selecting <guilabel>Ignore</guilabel> assigns the default
value for this field. Entering your own text will use this as the
value for every object being read.  The <guilabel>Type
Mapping</guilabel> section maps strings to object types. You can add
and remove mappings by clicking <guilabel>+</guilabel>
or <guilabel>-</guilabel>.  When you're done mapping, you can test
your settings by clicking <guilabel>Preview</guilabel> to read the
first few objects from the csv. If you are satisfied you can
click <guilabel>OK</guilabel> to import the whole catalog or adjust
your settings and preview again. As a reference, a mapping for the
OpenNGC catalog is shown in the below screenshot.
</para>
<screenshot>
<screeninfo>Importing CSV Catalogs, OpenNGC</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="csv_openngc.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Importing CSV Catalogs</phrase>
  </textobject>
</mediaobject>
</screenshot>
</sect3>
</sect2>
</sect1>

<sect1 id="solar_system">
<title>Solar System</title>
<screenshot>
<screeninfo>Solar System Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="solarsystem_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Solar System Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Solar System page</secondary></indexterm>
In the <guilabel>Solar System</guilabel> page, you can specify whether
the Sun, Moon, planets, comets and asteroids are displayed, and
whether the major bodies are drawn as colored circles or actual images.
You can also toggle whether solar system bodies have name labels attached,
and control how many of the comets and asteroids get name labels.
There is an option to automatically attach a temporary <quote>orbit
trail</quote> whenever a solar system body is tracked, and another to
toggle whether the color of the orbit trail fades into the background
sky color.
</para>
</sect1>

<sect1 id="satellites">
<title>Satellites</title>
<screenshot>
<screeninfo>Satellites Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="satellites_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Satellites Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Satellites page</secondary></indexterm>
The <guilabel>Satellites</guilabel> page allows you to set the satellites view options. Firstly,
you can see or hide the satellites on the skymap using <guilabel>Show satellites</guilabel> checkbox
from the top <guilabel>View Options</guilabel> section. By default, satellites are drawn as small
light red filled circles with an optional dark red name label next to them. You can enable or disable
these labels by checking or not the <guilabel>Show labels</guilabel> checkbox. It is located below
the <guilabel>Show satellites</guilabel> checkbox, within the <guilabel>View Options</guilabel> section.
</para>
<para>
The colors of the dots representing satellites and their name labels can be easily customized using
the <guilabel>Colors</guilabel> page from the same <guilabel>Configure - &kstars;</guilabel> window.
In addition, satellites can be drawn just like regular stars by checking the <guilabel>Draw satellites
like stars</guilabel> checkbox. To display only the visible satellites from your current geographic location
and time, select <guilabel>Show only visible satellites</guilabel>.
</para>
<para>
&kstars; can draw artificial satellites from many predefined groups. Thus, you can select to display a particular
group, multiple groups or partially select subgroups. Under each group, a list of individual satellites is
presented. To select all satellites from a group, you need to check the group checkbox. You can also select
only the satellites of interest in each group.
The satellites orbital elements can be updated via the internet by pressing the <guibutton>Update TLEs</guibutton>
button. Another way for updating the satellites orbital elements is to use the <menuchoice><guimenu>Data</guimenu>
<guisubmenu>Updates</guisubmenu> <guimenuitem>Update Satellites Orbital Elements</guimenuitem></menuchoice> menu
item. If you know the name of a desired satellite then you can use the search satellites method that &kstars;
provides. You need to enter the name of satellite in the <guilabel>Search satellites</guilabel> text box and the
list will be reduced only to its best matches.
</para>
<para>
You can add new satellites to &kstars; default satellites set by editing the
<filename>kstars/data/satellites.dat</filename> file. As each line of this file is a group of
satellites, you need to add a new entry for your desired satellites group.
An entry should have the following format: <userinput>Group Name;local_filename;url</userinput>.
For example: <userinput>Iridium;iridium.tle;https://celestrak.com/NORAD/elements/iridium.txt</userinput>.
</para>
</sect1>

<sect1 id="supernovae">
<title>Supernovae</title>
<screenshot>
<screeninfo>Supernovae Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="supernovae_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Supernovae Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Supernovae page</secondary></indexterm>
The <guilabel>Supernovae</guilabel> page allows you to decide if the supernovae are displayed or not by checking
the <guilabel>Show supernovae</guilabel> checkbox. By default, supernovae are drawn as small light orange <quote>+</quote> mark.
As for satellites, the color of supernovae can be easily customized using the <guilabel>Colors</guilabel> page.
</para>
<para>
You can set the magnitude limit for showing a supernova as well as magnitude limit for supernova alerts using
the spin boxes control. The limiting magnitude is the faintest apparent magnitude of an skyobject that is
visible with the naked-eye or a telescope.
</para>
<para>
The list of recent supernovae can be updated via the <menuchoice><guimenu>Data</guimenu> 
<guisubmenu>Updates</guisubmenu> <guimenuitem>Update Recent Supernovae data</guimenuitem></menuchoice> menu item.
</para>
</sect1>

<sect1 id="guides">
<title>Guides</title>
<screenshot>
<screeninfo>Guides Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="guides_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Guides Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Guides page</secondary></indexterm>
The <guilabel>Guides</guilabel> page lets you toggle whether non-objects
are displayed (&ie;, constellation lines, constellation names, the
Milky Way contour, the <link linkend="ai-cequator">celestial
equator</link>, <link linkend="ai-ecliptic">the ecliptic</link>, <link
linkend="ai-horizon">the horizon line</link>, and the opaque ground).
You can also choose a sky culture, whether you would like to see Latin constellation
names, <acronym>IAU</acronym>-standard three-letter abbreviations, or
constellation names using your local language.
</para>
</sect1>

<sect1 id="terrain">
<title>Terrain</title>
<screenshot>
<screeninfo>Terrain Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="terrain_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Terrain Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Terrain page</secondary></indexterm>
The <guilabel>Terrain</guilabel> page lets you configure whether the terrain (landscape) image will be shown on the skymap.
</para>
<para>
The user is responsible for creating a partially-transparent image, that is overlayed onto the sky map. This image should have transparent regions that the user creates to let the skymap show through, and opaque regions representing the trees, buildings, the landscape around the telescope. There is a particular format required, and this is a significant effort. There are many resources on the web that explain how this is done for <ulink url="https://stellarium.org/landscapes.html">Stellarium</ulink>. The details of image creation are the same.
</para>
<para>
Initially, the user captures a full sphere equirectangular projection image from approximately the same point-of-view as his/her telescope. This kind of image can be captured with the Google Camera App, or the Google YouTube App on iPhone, or likely many other camera apps. The user then needs to edit the resulting image so that the sky is erased/transparent, and save it as a PNG. Finally, the user needs to determine where North is in the image, so it can eventually be aligned with the skymap. Once all that is done, the sky map can simulate the local sky view including the local terrain.
</para>
<para>
Once the image is created, it is possible to upload it via the <guilabel>Terrain</guilabel> page and configure the azimuth correction value (in degrees) that allows the user to rotate the view so north in the sky map is aligned with the north in the image.
</para>
<para>
Moreover, some speedup options can be configured to achieve the best user experience when rendering the terrain on the sky map.
</para>
<tip>
    <para>
        You can toggle the terrain overlay on and off using a keyboard shortcut <keycombo>&Ctrl;&Shift;<keycap>T</keycap></keycombo> and the <menuchoice><guimenu>View</guimenu><guimenuitem>Show Terrain</guimenuitem></menuchoice> menu item.
    </para>
</tip>
</sect1>

<sect1 id="imageOverlays">
<title>Image Overlays</title>
<screenshot>
<screeninfo>Image Overlays on SkyMap</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="imageOverlays2.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Image Overlays on SkyMap</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Image Overlays page</secondary></indexterm>
Image overlays are custom images (typically <literal role="extension">.jpg</literal>) that are rendered onto the
skymap over stars and other skymap items, but below the terrain. These images are added by you, the user, a sort
of personal sky catalog. If configured properly, these personal images can be displayed almost perfectly aligned
with other objects in the sky.
</para>
<screenshot>
<screeninfo>Image Overlays Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="imageOverlays1.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Image Overlays Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
The <guilabel>Image Overlays</guilabel> page lets you configure whether image overlays will be shown on the skymap,
and helps you add them to the system. The image at the start of this section shows the skymap with image overlays
enabled and some image overlays loaded.
</para>
<para>
Each time it starts up, &kstars; looks for new image overlay images in a special directory, parallel to the logs
directory, named <literal>imageOverlays</literal>. On Linux this can be found in
<filename class="directory">~/.local/share/kstars/imageOverlays</filename>. The exact location for your system can
be found by clicking the <guibutton>Overlay Directory</guibutton> button near the top of the
<guilabel>Image Overlays</guilabel> config page shown at the top of this section. To start, add your images to that
directory. Ideally, for performance reasons these aren't massive files, but probably images with widths 1000 or 2000
should be fine. To add additional images in the future, add them to the same directory and click the refresh button
or restart &kstars;. To remove overlays, remove them from the directory and click the refresh button or restart &kstars;.
</para>
<para>
Start &kstars; once you have images in the <literal>imageOverlays</literal> directory. If you then go to the
<guilabel>Image Overlays</guilabel> config page, you should see the new files listed in the table. The new images
will show their status as <guilabel>Unprocessed</guilabel>. Only images whose status is <guilabel>OK</guilabel>
are displayed on the SkyMap. That is because &kstars; needs to know the sky location, size, and orientation for
these images before it can display them. To change the status to <guilabel>OK</guilabel> you need to plate-solve
the images or add the required information manually--see below.
</para>
<para>
To prepare your images for display, you need to plate-solve the images (one time only). To do this, find an image
in the table, click on its filename, and then click <guibutton>Solve</guibutton> below the table.
The <guibutton>Solve</guibutton> button's label should switch to <guibutton>Cancel</guibutton> during the solve,
and then when completed successfully, the solved parameters are displayed in the table and the status is changed
to <guilabel>OK</guilabel>.  A successful plate-solve's information is stored in the user database so that solving
doesn't need to be repeated. The solved image should from then on appear in its proper position in the SkyMap. You
can plate-solve multiple images in a single operation by clicking on the first image's filename, then holding down
the &Shift; key and clicking on another filename. All the image files between the filenames should be selected.
Then clicking <guibutton>Solve</guibutton> will attempt to solve them all. However, &kstars; will not attempt to
plate-solve images whose status is <guilabel>OK</guilabel>, it will skip those images. (If you wish to re-plate-solve
images with status <guilabel>OK</guilabel>, then manually change their status to <guilabel>Unprocessed</guilabel> and
click <guibutton>Solve</guibutton>). It is possible that if you select several images, a few of them will not be
successfully solved.
</para>
<para>
Plate solving these images can sometimes be difficult. That is because at this point the system has no information as
to the scale or position to look, and thus it is a blind solve. To improve your chance for success, you can enter an
approximate RA/DEC center sky position into the <guilabel>RA</guilabel> and <guilabel>DEC</guilabel> columns for the
row you are trying to solve. You can also add an image scale, in arcseconds-per-pixel. You can add a default scale to
the right of the <guibutton>Solve</guibutton> button in the box labeled <guilabel>Default a-s/px</guilabel> so that
all solving attempts use this scale by default. You can also add a scale directly into the table-row-column, which
would override the default. You can choose which StellarSolver profile the solver uses (these profiles can be edited
in Ekos' <guilabel>Align</guilabel> tab). Finally, you can adjust the solver's <guilabel>Timeout</guilabel> in seconds.
</para>
<para>
If you have problematic images that won't solve, you can still display them by manually entering the values (that the
solver didn't find) into the table. They are the RA, DEC, arcsecond-per-pixel, orientation angle, and east-to-the-right
(or West-to-the-right) settings. Once you have done that, you can then change the status to <guilabel>OK</guilabel> and
&kstars; will save these values to the user database as if they had been automatically solved.
</para>
<para>
There are a few more controls on the <guilabel>Image Overlays</guilabel> settings page.
The <guilabel>Show image overlays</guilabel> checkbox at the top of the page enables or disables this feature--that is,
toggles whether any image overlays are display on the SkyMap or not.
</para>
<para>
The <guilabel>Maximum image dimension:</guilabel> spinbox allows you to vary the maximum image dimension used for images.
That is, if you place images that are, for example, 5000 pixels wide into the <literal>imageOverlays</literal> directory,
but this input box's value is 1000, then the 5000-pixel-images will be read in, but then downsampled to 1000-pixels-wide
before display. This is done to reduce the memory footprint and cpu usage of this feature. It would be more efficient to
add image files with the desired image width.
</para>
<para>
The <guilabel>Center SkyMap on selection</guilabel> checkbox allows you to easily navigate to the overlay images without
directly manipulating the SkyMap. With this enabled, you select a row in the overlay table (&ie;, by clicking on the
filename field) and the skymap is moved to that image if the image's status is <guilabel>OK</guilabel>. At that point
you can move from one image to the next with &Up; and &Down; arrow keyboard commands.
</para>
</sect1>

<sect1 id="colors">
<title>Colors</title>
<screenshot>
<screeninfo>Colors Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="colors_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Colors Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Colors page</secondary></indexterm>
<indexterm><primary>Color Schemes</primary>
<secondary>Customizing</secondary></indexterm>
The <guilabel>Colors</guilabel> page allows you to set the color scheme,
and to define custom color schemes.  The tab is split into two panels:
</para>
<para>
The left panel shows a list of all display items with adjustable
colors.  Click on any item to bring up a color selection window to
adjust its color.  Below the list is the <guilabel>Star color
mode:</guilabel> dropdown box.  By default, &kstars; draws stars with
a <link linkend="ai-colorandtemp">realistic color</link> tint according
to the spectral type of the star.  However, you may also choose to draw
the stars as solid white, black or red circles.  If you are using the
realistic star colors, you can set the saturation level of the star
colors with the <guilabel>Star color intensity:</guilabel> spinbox.
</para>
<para>
The right panel lists the defined color schemes.  There are four
predefined schemes: the <guilabel>Default Colors</guilabel> scheme,
<guilabel>Star Chart</guilabel>, which uses black stars on a white
background, <guilabel>Night Vision</guilabel>, which uses only shades
of red in order to protect dark-adapted vision, and <guilabel>Moonless
Night</guilabel>, a more realistic, dark theme.  Additionally,
you can save the current color settings as a custom scheme by clicking
the <guibutton>Save As...</guibutton> button.  It will prompt
you for a name for the new scheme, and then your scheme will appear in
the list in all future &kstars; sessions.  To remove a custom scheme,
simply highlight it in the list, and press the <guibutton>Remove</guibutton> button.
</para>
</sect1>

<sect1 id="fits-configure">
<title>FITS</title>
<screenshot>
<screeninfo>FITS Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="fits_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>FITS Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>FITS page</secondary></indexterm>
<para><abbrev>FITS</abbrev> (Flexible Image Transport System) is a popular open  standard for storage, transmission and processing of digital data. For the details, one is referred to the <ulink url="https://en.wikipedia.org/wiki/FITS">corresponding Wikipedia article</ulink>. This page allows you to configure presentation and processing of FITS data in &kstars;.
</para>
<para>
    The left panel is for configuring FITS viewer itself.
</para>
<para>
Check the <guilabel>Use FITS viewer</guilabel> item if you want automatically display received images in the FITS Viewer.
</para>
<para>The <guilabel>Single preview tab</guilabel> item is to display all captured FITS images in a single tab instead of multiple tabs
per image. The <guilabel>Single window capture</guilabel> item is to display captured FITS images from all cameras in a single FITS Viewer window
instead of a dedicated window to each camera. The <guilabel>Single window open</guilabel> item is to display opened FITS images in a single FITS Viewer window instead of a
dedicated window to each file and the <guilabel>Independent window</guilabel> item is to make FITS Viewer window independent from &kstars;.
</para>
<para>
The right panel lists processing options. The <guilabel>Auto stretch</guilabel> item is to always apply auto stretch to images in FITS Viewer, <guilabel>Limited resources mode</guilabel> is to enable limited resource mode to turn off any resource-intensive operations, namely: <guilabel>Auto debayer</guilabel> (bayered images will not be debayered; only grayscale images are shown), <guilabel>Auto WCS</guilabel> (World Coordinate System data
will not be processed; WCS maps sky coordinates to image coordinates;
equatorial grid lines, object identification, and telescope slew within an
image are disabled), and <guilabel>3D cube</guilabel> (RGB images will not be
processed; only grayscale images are shown). You can switch off some of these resource-greedy operations separately as well.
</para>
</sect1>

<sect1 id="indi_page">
<title>INDI</title>
<screenshot>
<screeninfo>INDI Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="indi_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>INDI Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>For detailed explanation of the options on the <guilabel>INDI</guilabel>
page see the <link linkend="indi-configure">Configure INDI</link> section.
</para>
</sect1>

<sect1 id="ekos-window">
<title>Ekos</title>
<screenshot>
<screeninfo>Ekos Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="ekos_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Ekos Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
Ekos is an astrophotography suite, a complete astrophotography solution that can control
all INDI devices including numerous telescopes, CCDs, DSLRs, focusers, filters, and a lot more.
Ekos supports highly accurate tracking using online and offline astrometry solver, autofocus
and autoguiding capabilities, and capture of single or multiple images using the powerful
built in sequence manager. For detailed explanation of <guilabel>Ekos</guilabel>,
see the <link linkend="ekos">Ekos section of this manual</link>.
</para>
</sect1>

<sect1 id="xplanet-configure">
<title>Xplanet</title>
<screenshot>
<screeninfo>Xplanet Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="xplanet_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Xplanet Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<ulink url="http://xplanet.sourceforge.net/">Xplanet</ulink> (should be installed separately) is
a solar system planet surface renderer. This page allows you to configure presentation and
processing of <application>Xplanet</application> data in &kstars;.
</para>
</sect1>

<sect1 id="advanced">
<title>Advanced</title>
<screenshot>
<screeninfo>Advanced Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="advanced_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Advanced Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Advanced page</secondary></indexterm>
The <guilabel>Advanced</guilabel> page provides fine-grained control
over the more subtle behaviors of &kstars;.
</para><para>
<indexterm><primary>Atmospheric Refraction</primary></indexterm>
The <guilabel>Correct for atmospheric refraction</guilabel> checkbox
controls whether the positions of objects are corrected for the effects
of the atmosphere.  Because the atmosphere is a spherical shell, light from
outer space is <quote>bent</quote> as it passes through the atmosphere to
our telescopes or eyes on the Earth's surface.  The effect is largest for
objects near the horizon, and actually changes the predicted rise or set
times of objects by a few minutes.  In fact, when you <quote>see</quote> a
sunset, the Sun's actual position is already well below the horizon;
atmospheric refraction makes it seem as if the Sun is still in the sky.
Note that atmospheric refraction is never applied if you are using
<guilabel>Equatorial coordinates</guilabel>.
</para><para>
<indexterm><primary>Animated Slewing</primary></indexterm>
The <guilabel>Use animated slewing</guilabel> checkbox controls how the
display changes when a new focus position is selected in the map.  By
default, you will see the sky drift or <quote>slew</quote> to the new
position; if you uncheck this option, then the display will instead
<quote>snap</quote> immediately to the new focus position.
</para><para>
<indexterm><primary>Objects in the Sky</primary>
<secondary>Labeling</secondary>
<tertiary>Automatic</tertiary>
</indexterm>
If the <guilabel>Attach label to centered object</guilabel> checkbox is
selected, then a name label will automatically be attached to an object
when it is being tracked by the program.  The label will be removed when
the object is no longer being tracked.  Note that you can also manually
attach a persistent name label to any object with its <link
linkend="popup-menu">popup menu</link>.
</para><para>
<indexterm><primary>Objects in the Sky</primary>
<secondary>Hiding</secondary></indexterm>
There are three situations when &kstars; must redraw the sky display very
rapidly: when a new focus position is selected (and <guilabel>Use
animated slewing</guilabel> is checked), when the sky is dragged with the
mouse, and when the time step is large.  In these situations, the positions
of all objects must be recomputed as rapidly as possible, which can put
a large load on the <abbrev>CPU</abbrev>.  If the <abbrev>CPU</abbrev>
cannot keep up with the demand, then the display will seem sluggish or jerky.
To mitigate this, &kstars; will hide certain objects during these rapid-redraw
situations, as long as the <guilabel>Hide objects while moving</guilabel>
checkbox is selected.  The timestep threshold above which objects will be
hidden is determined by the <guilabel>Also hide if time step larger
than:</guilabel> timestep-spinbox.  You can specify the objects that should
be hidden in the <guilabel>Configure Hidden Objects</guilabel> section.
</para>
</sect1>

<sect1 id="developer">
<title>Developer</title>
<screenshot>
<screeninfo>Developer Window</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="developer_page.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>Developer Window</phrase>
  </textobject>
</mediaobject>
</screenshot>
<para>
<indexterm><primary>Configure &kstars; window</primary>
<secondary>Developer page</secondary></indexterm>
The <guilabel>Developer</guilabel> page provides a few checkboxes that can help
debug issues with &kstars;. There are checkboxes for saving images
in logging directories that might help debug issues. Of course, saving images
can take up disk space and should be used judiciously.
</para><para>
  The images that can be saved are</para>
  <itemizedlist>
<listitem><para>
    all focus images,
</para></listitem>
<listitem><para>
    all guider images,
</para></listitem>
<listitem><para>
    all align images, and
</para></listitem>
<listitem><para>
    align images where the plate-solving failed.
</para></listitem>
  </itemizedlist><para>
    The images are all saved in folders parallel to the main
  logging directory. They are in folders named guide, autofocus, align, and align/failed.
</para>
</sect1>

<sect1 id="customize">
<title>Customizing the Display</title>

<para>
There are several ways to modify the display to your liking.</para>
<itemizedlist>
<listitem><para>
<indexterm><primary>Info Boxes</primary><secondary>Customizing</secondary></indexterm>
<indexterm><primary>Info Boxes</primary><secondary>Shading</secondary></indexterm>
Toggle whether the Info Boxes are drawn in the <menuchoice><guimenu>Settings</guimenu>
<guisubmenu>Info Boxes</guisubmenu></menuchoice> submenu.  In addition, you can
manipulate the three Info Boxes with the mouse.  Each box has additional lines of data
that are hidden by default. You can toggle whether these additional lines are visible
by double-clicking a box to <quote>shade</quote> it.  Also, you can reposition a box by
dragging it with the mouse.  When a box hits a window edge, it will
<quote>stick</quote> to the edge when the window is resized.
</para></listitem>
<listitem><para>
<indexterm><primary>Toolbars</primary><secondary>Customizing</secondary></indexterm>
Toggle whether the Toolbars are drawn in the <menuchoice><guimenu>Settings</guimenu>
<guisubmenu>Toolbars Shown</guisubmenu></menuchoice> submenu.  Like most &kde; toolbars,
they can also be dragged around and anchored on any window edge, or even detached from
the window completely if they are unlocked.
</para></listitem>
<listitem><para>
<indexterm><primary>Color Schemes</primary><secondary>Selecting</secondary></indexterm>
Select a different color scheme in the <menuchoice><guimenu>Settings</guimenu>
<guisubmenu>Color Schemes</guisubmenu></menuchoice> submenu.  There are four predefined
color schemes, and you can define your own in the
<link linkend="config"><guilabel>Configure - &kstars;</guilabel></link> window.
</para></listitem>
<listitem>
<para>
<indexterm><primary>Field-of-View Symbols</primary><secondary>Description</secondary></indexterm>
Choose an <quote>FOV Symbol</quote> using the
<menuchoice><guimenu>Settings</guimenu><guisubmenu>FOV Symbols</guisubmenu></menuchoice>
submenu.  <firstterm>FOV</firstterm> is an acronym for <quote>field-of-view</quote>.
An FOV symbol is drawn at the center of the window to indicate where the display
is pointing.  Different symbols have different angular sizes; you can use a symbol to show
what the view through a particular telescope would look like.  For example, if you choose
the <quote>7x35 Binoculars</quote> FOV symbol, then a circle is drawn on the display that is
9.2 degrees in diameter; this is the field-of-view for 7x35 binoculars.
</para>
<para>
<indexterm><primary>Field-of-View Symbols</primary><secondary>Customizing</secondary></indexterm>
You can define your own FOV symbols (or modify the existing symbols) using the
<guimenuitem>Edit FOV Symbols...</guimenuitem> menu item, which launches the FOV Editor:
</para>
<screenshot>
<screeninfo>Field-of-View Symbols Editor</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="fovdialog.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>FOV Symbol Editor</phrase>
  </textobject>
</mediaobject>
</screenshot>

<para>
The list of defined FOV symbols is displayed on the left.  On the right are buttons for
adding a new symbol, editing the highlighted symbol's properties, and removing the
highlighted symbol from the list.  Note that you can even modify or remove the four
predefined symbols (if you remove all symbols, the four defaults will be restored the
next time you start &kstars;).  Below these three buttons is a graphical preview display
showing the highlighted symbol from the list.  When the <guibutton>New...</guibutton> or
<guibutton>Edit...</guibutton> button is pressed, the <guilabel>New FOV Indicator</guilabel>
window is opened:
</para>

<screenshot>
<screeninfo>New Field-of-View Symbol</screeninfo>
<mediaobject>
  <imageobject>
    <imagedata fileref="newfov.png" format="PNG"/>
  </imageobject>
  <textobject>
    <phrase>New FOV Symbol</phrase>
  </textobject>
</mediaobject>
</screenshot>

<para>
<indexterm><primary>Field-of-View Symbols</primary><secondary>Defining New</secondary></indexterm>
This window lets you modify the four properties that define a FOV symbol: name, size,
shape, and color.  The angular size for the symbol can either be entered directly in the
<guilabel>Field of View</guilabel> edit box, or you can use the Eyepiece/Camera Tabs to
calculate the field-of-view angle, given parameters of your telescope/eyepiece or
telescope/camera setup.  The five available shapes are: Square, Circle, Crosshairs, Bullseye and Semitransparent circle.
Once you have specified all four parameters, press <guibutton>Ok</guibutton>,
and the symbol will appear in the list of defined symbols.  It will also be available
from the <menuchoice><guimenu>Settings</guimenu><guisubmenu>FOV Symbols</guisubmenu></menuchoice> submenu.
</para>
</listitem>
</itemizedlist>

</sect1>

<sect1 id="skymap_orientation">
  <title>Adjusting orientation of the sky map</title>
  <para>
    You can tweak various settings to make the orientation of the sky map match the view through your optical instrument.
  </para>
  <para>
    First, pick the coordinate system that matches your mount. For an equatorially mounted instrument, switch to the Equatorial Coordinate mode in the <guimenu>View</guimenu> menu or by pressing the <keycap>Space</keycap> key. The option to toggle the coordinate system should read <guilabel>Switch to Horizontal View (Horizontal Coordinates)</guilabel> when the current mode is Equatorial Coordinates. For an altazimuth-mounted instrument or naked-eye viewing, switch to Horizontal Coordinates, so that the option in the <guimenu>View</guimenu> menu reads <guilabel>Switch to Star Globe View (Equatorial Coordinates)</guilabel>. This sets the base coordinate system used to render the sky map, and also sets the reference for the orientation of the skymap: zenith or north.
  </para>
  <para>
    If your instrument is using an erecting prism, typically used on Schmidt-Cassegrain and refracting type telescopes, the view through the eyepiece will be mirrored horizontally. You can have the sky map match this by checking the <guilabel>Mirrored View</guilabel> option under the <guimenu>View</guimenu> menu, or using the key combination <keycombo>&Ctrl;&Shift;<keycap>M</keycap></keycombo>.
  </para>
  <para>
    Next, to rotate the sky map freely, you can hold down the &Shift; key and drag the mouse on the sky map. A temporary overlay will appear showing the direction of north and zenith at the point, and displaying the angle they make with the vertical in a counterclockwise sense. The orientations of zenith and north will update as you rotate the sky map. Letting go of &Shift; or the mouse button will stop the rotation operation. As you pan the sky map or focus it on different objects, the rotation you set is retained as an offset from the reference direction. The reference direction is north when using Equatorial Coordinates and zenith when using Horizontal Coordinates. As a reminder, the reference direction is solid and brighter in the temporary overlay. The temporary overlay also marks the East direction, which will be clockwise from north when mirrored and counter-clockwise when not mirrored. For the two common orientations of erect and inverted, the rotation can be set / reset using the <menuchoice><guimenu>View</guimenu><guisubmenu>Skymap Orientation</guisubmenu></menuchoice> submenu. Select <guilabel>North Down</guilabel> or <guilabel>Zenith Down</guilabel> as is applicable to set an orientation of 180 degrees.
  </para>
  <para>
    If you are visually observing through an eyepiece of an instrument, you may need to do some more correction. For the common case of a large Dobsonian telescope (or more generally a Newtonian design mounted on an altazimuth mount), an additional systematic correction is of help. This correction applies because we stand erect while using the telescope irrespective of the angle the telescope tube is making with the ground. So as we move the telescope in altitude, an additional correction depending on the altitude of the object needs to be applied to make the sky map match the view through the eyepiece where the observer is standing erect. This correction is enabled by choosing the appropriate "Erect observer correction" option in the <menuchoice><guimenu>View</guimenu><guisubmenu>Skymap Orientation</guisubmenu></menuchoice> submenu. The correction depends on which side the telescope's focuser is placed by the manufacturer. If when observing just above the horizon through the eyepiece, the sky is on the observer's right side (and the mirror to the left), pick the <guilabel>Erect observer correction, right-handed</guilabel> option. Similarly, if the sky is to the left of the observer, choose the <guilabel>Erect observer correct, left-handed</guilabel> option. This correction only makes sense in Horizontal Coordinate mode and is disabled when using equatorial coordinates.
  </para>
  <para>
    We now provide some examples of how to use these settings for various instruments:
    <itemizedlist>
      <listitem><para>Naked-eye observing: Choose Horizontal Coordinates and a <guilabel>Zenith Up</guilabel> orientation under <menuchoice><guimenu>View</guimenu><guisubmenu>Skymap Orientation</guisubmenu></menuchoice>.</para></listitem>
      <listitem><para>Camera on an equatorially mounted telescope: Choose Equatorial Coordinates and adjust the orientation of the sky map so that it matches your camera. As your mount points to different regions of the sky, the orientation should be rendered correctly.</para></listitem>
      <listitem><para>Using binoculars: Same settings as Naked-eye observing</para></listitem>
      <listitem><para>Eyepiece of an altazimuth Schmidt-Cassegrain telescope with an erecting prism: Under the <guimenu>View</guimenu> menu, choose <guilabel>Mirrored View</guilabel>, and under the <guisubmenu>Skymap Orientation</guisubmenu> sub-menu, choose <guilabel>Zenith Up</guilabel>. Finally, tweak the rotation manually to match the eyepiece view according to the angle you are using for your erecting prism.</para></listitem>
      <listitem><para>Using a RACI finder scope on an altazimuth mounted telescope, looking straight down into it: Same settings as Naked-eye observing, except you may need to tweak the orientation manually once if you have it mounted at an angle</para></listitem>
      <listitem><para>Using a RACI finder scope on an altazimuth mounted telescope, looking through it from the side: In addition to the aforementioned, enable Erect observer correction for the appropriate side.</para></listitem>
      <listitem><para>Using a straight-through (inverted view) finder scope on an altazimuth mounted telescope: Choose Horizontal Coordinates and a sky-map orientation of <guilabel>Zenith Down</guilabel> in <menuchoice><guimenu>View</guimenu><guisubmenu>Skymap Orientation</guisubmenu></menuchoice> submenu</para></listitem>
      <listitem><para>Eyepiece of a Dobsonian telescope: Choose Horizontal Coordinates, and in the <menuchoice><guimenu>View</guimenu><guisubmenu>Skymap Orientation</guisubmenu></menuchoice> submenu, select <guilabel>Zenith Down</guilabel> and enable the erect observer correction, picking the left/right handed option as is appropriate for your telescope. Then adjust the orientation manually once to match your telescope eyepiece view, and it should henceforth track it correctly.</para></listitem>
    </itemizedlist>
  </para>
  <para>
    It is typical in visual astronomy to use at least three different instruments: the unaided eye, a finder scope, and the main telescope. The orientations of these three will have different settings and will need frequent modification of all the aforementioned options. To make it easy to adjust these settings together, KStars provides the <guilabel>Views</guilabel> feature. This feature is accessible through the <menuchoice><guimenu>View</guimenu><guisubmenu>Views</guisubmenu></menuchoice> menu and the options contained therein. The <guilabel>Arbitrary</guilabel> view is not a real view, but the option that gets selected when the sky-map orientation is modified manually through the previously described options. The rest of the views are bona fide views. New views may be added, or the existing views may be edited, removed, or re-ordered using the <menuchoice><guimenu>View</guimenu><guisubmenu>Views</guisubmenu><guimenuitem>Edit Views...</guimenuitem></menuchoice> option. Choosing this brings up a window to manage the views:
  </para>
  <screenshot>
    <screeninfo>Dialog to manage sky map views</screeninfo>
    <mediaobject>
      <imageobject>
	<imagedata fileref="viewmanager.png" format="PNG"/>
      </imageobject>
      <textobject>
	<phrase>Manage Sky Map Views</phrase>
      </textobject>
    </mediaobject>
  </screenshot>
  <para>
    To remove a view, simply select the view from the list and delete it using the <guibutton>Remove</guibutton> button. To re-order the views, use the mouse to drag the view you wish to move and drop it at its destination in-between two other entries. To edit a view, select the view from the list and click <guibutton>Edit...</guibutton>. To create a new view, click the <guibutton>New...</guibutton> button. The <guibutton>Edit...</guibutton> and <guibutton>New...</guibutton> options bring up a view editor interface:
  </para>
  <screenshot>
    <screeninfo>Dialog to create a new view or edit an existing one</screeninfo>
    <mediaobject>
      <imageobject>
	<imagedata fileref="newview.png" format="PNG"/>
      </imageobject>
      <textobject>
	<phrase>Edit / Create View</phrase>
      </textobject>
    </mediaobject>
  </screenshot>

  <para>
  The <guilabel>Name</guilabel> field carries a unique name for the View. The <guilabel>Mount Type</guilabel> determines whether the reference direction used for orientation will be north or zenith. Typically, one would set this to the type of mount used for the telescope. However, when using refractors and Schmidt-Cassegrain Telescopes (SCTs) with a rotatable diagonal, the observer will have a tendency to re-orient the eyepiece for comfort so that the eyepiece remains at a fixed angle with respect to the zenith. For this reason, it makes sense to choose <guilabel>Altazimuth</guilabel> mounting even when the telescope is actually on an equatorial mount. Choose <guilabel>Equatorial</guilabel> mounting when the focuser will not be re-oriented, such as when using a camera on an equatorially mounted telescope.

  For Newtonian telescopes that invert (i.e. rotate by 180 degrees but do not change the handedness) of the view, pick the <guilabel>Inverted</guilabel> option. This is also the correct option for straight-through refractors and finder scopes. When using a erecting prism diagonal, the prism erects the inverted image by flipping it up-down. This results overall in a left-right mirrored image. Thus for telescopes that use an erecting prism, pick <guilabel>Mirrored</guilabel>. A special kind of prism called an Amici roof prism not only erects the image vertically, but it also prevents left-right mirroring of the image. Finder scopes incorporating such a diagonal are normally called "Right-Angle Correct Image" or RACI finder scopes. Such diagonals may also be used on refractors and SCTs. When using such a prism that produces a correct image, choose the <guilabel>Correct</guilabel> option. The <guilabel>Mirrored on the vertical axis</guilabel> option is not encountered in typical astronomical instruments, but is provided for completeness.

  Two more factors need to be considered: one is the angle of the eyepiece with respect to the reference direction (north / zenith), and the other is the orientation of the observer's head (and notion of the vertical) which we explained when describing the erect observer correction feature. These two aspects are configured using the single slider titled <guilabel>Eyepiece Angle</guilabel>. Two illustrations below the slider show the interpretation of this setting; on the left, as seen from the front as is more convenient for Newtonian telescopes, and on the right as is seen from the back, more convenient for refractors and Cassegrains. The observer naturally stands on the side that makes it more convenient to look through the eyepiece, so the erect observer correction is automatically adjusted accordingly. For eyepiece angles that are less than -1 degree on the slider, the <guilabel>Erect observer correction, right-handed</guilabel> option is applied. Similarly, for eyepiece angles that are greater than +1 degree, the <guilabel>Erect observer correction, left-handed</guilabel> is applied. At 0 degrees, no erect observer correction is applied. This correction is indicated by a silhouette of a person standing on the appropriate side of the telescope. In our convention, most mass-manufactured Dobsonians seem to have a correction around +45 degrees. Incidentally, this correction is also useful for finder scopes with diagonals.

  One may want to explicitly disable the erect observer correction even when the eyepiece angle is not zero. This is useful in case the view comes from a CCD camera that does not change angle with respect to the telescope body (unlike an observer's head), or if the display showing KStars' sky map is mounted on the telescope body itself. In this case the <guilabel>Display mounted on the telescope</guilabel> option can be checked. For the opposite effect, i.e. where the eyepiece angle is zero, but the observer is leaning to look through the eyepiece from one of the two sides, set the eyepiece angle to plus or minus 2 degrees to enable the erect observer correction; the minor difference will not be noticeable.

  Finally, one may want triggering of the view to also set the field-of-view of the sky map to some value, for example to set the FOV of a finder scope. In this case, the <guilabel>Also set the field of view</guilabel> check-box may be checked, and an approximate field-of-view to adjust may be specified. If this is not enabled, the zoom level of the sky map is not altered when this view is applied.
  </para>

</sect1>



&hips;

</chapter>
