1<chapter id="faq">
2<title
3>Questions and Answers</title>
4&reporting.bugs; &updating.documentation; <qandaset id="faqlist">
5
6<qandaentry>
7<question>
8<para
9>What is the &kstars; Icon?</para>
10</question>
11<answer>
12<para
13>The <guiicon
14>&kstars; Icon</guiicon
15> is a sextant, a handheld telescope which was used by navigators on sailing ships back when the stars were important for navigation. By carefully reckoning the positions of the stars, the navigator could get an accurate estimate of the ship's current <link linkend="ai-geocoords"
16>longitude and latitude</link
17>. </para>
18</answer>
19</qandaentry>
20
21<qandaentry>
22<question>
23<para
24>What do the different symbols for deep-sky objects mean?</para>
25</question>
26<answer>
27<para
28>The symbol indicates the object type: <itemizedlist>
29<listitem
30><para
31>dotted circle: Open Cluster</para
32></listitem>
33<listitem
34><para
35>cross-in-circle: Globular Cluster</para
36></listitem>
37<listitem
38><para
39>box: Gaseous Nebula</para
40></listitem>
41<listitem
42><para
43>diamond: Supernova Remnant</para
44></listitem>
45<listitem
46><para
47>circle with outer lines: Planetary Nebula</para
48></listitem>
49<listitem
50><para
51>ellipse: Galaxy</para
52></listitem>
53</itemizedlist>
54</para>
55</answer>
56</qandaentry>
57
58<qandaentry>
59<question>
60<para
61>What do the different colours of Deep-sky objects mean?</para>
62</question>
63<answer>
64<para
65>Generally, the different colours indicate to which catalogue the object belongs (Messier, NGC or IC). However, some objects have a different colour which indicates that there are extra images available in the <link linkend="popup-menu"
66>popup menu</link
67> (the default <quote
68>extras</quote
69> colour is red). </para>
70</answer>
71</qandaentry>
72
73<qandaentry>
74<question>
75<para
76>Why are there so many more U.S. cities than in other countries? Is it a conspiracy? </para>
77</question>
78<answer>
79<para
80>It may be a conspiracy, but &kstars; is not involved! We were unable to find a single longitude/latitude database that covers the globe equitably. We are currently working on adding many more non-U.S. cities to the database. We have already received city lists from users in Norway, Italy and Korea. If you can contribute to this effort, please let us know. </para>
81</answer>
82</qandaentry>
83
84<qandaentry>
85<question>
86<para
87>Why can I not display the ground when using Equatorial Coordinates</para>
88</question>
89<answer>
90<para
91>The short answer is, this is a temporary limitation. There is a problem when constructing the filled polygon that represents the ground when in Equatorial mode. However, it does not make too much sense to draw the ground in equatorial coordinates, which is why this fix has been given a low priority. </para>
92</answer>
93</qandaentry>
94
95<qandaentry>
96<question>
97<para
98>Why do some objects disappear when I am scrolling the display? </para>
99</question>
100<answer>
101<para
102>When the display is in motion, &kstars; must recompute the screen coordinates of every object in its database, which involves some pretty heavy trigonometry. When scrolling the display (either with the arrow keys or by dragging with the mouse), the display may become slow and jerky, because the computer is having trouble keeping up. By excluding many of the objects, the computational load is greatly reduced, which allows for smoother scrolling. You can turn off this feature in the <guilabel
103>Configure &kstars;</guilabel
104> window, and you can also configure which objects get hidden. </para>
105</answer>
106</qandaentry>
107
108<qandaentry>
109<question>
110<para
111>I do not understand all the terms used in &kstars;. Where can I learn more about the astronomy behind the program?</para>
112</question>
113<answer>
114<para
115>The &kstars; Handbook includes the <link linkend="astroinfo"
116>AstroInfo Project</link
117>; a series of short, hyperlinked articles about astronomical topics that can be explored and illustrated with &kstars;. AstroInfo is a community effort, like GNUpedia or Everything2. If you'd like to contribute to AstroInfo, please join our mailing list: <email
118>kstars-info@lists.sourceforge.net</email
119>. </para>
120</answer>
121</qandaentry>
122
123<qandaentry>
124<question>
125<para
126>How accurate/precise is &kstars;?</para>
127</question>
128<answer>
129<para
130>&kstars; is pretty accurate, but it is not (yet) as precise as it can possibly be. The problem with high-precision calculations is that you start having to deal with a large number of complicating factors. If you are not a professional astronomer, you will probably never have a problem with its accuracy or precision. </para>
131<para
132>Here is a list of some of the complicating factors which limit the program's precision: <itemizedlist
133> <listitem>
134<para
135>Planet positions are only accurate for dates within 4000 years or so of the current epoch. The planet positions are predicted using a Fourier-like analysis of their orbits, as observed over the past few centuries. We learnt in school that planets follow simple elliptical orbits around the Sun, but this is not strictly true. It would be true only if there was only one planet in the Solar system, and if the Sun and the planet were both point masses. As it is, the planets are constantly tugging on each other, perturbing the orbits slightly, and tidal effects also induce precessional wobbling. In fact, recent analysis suggests that the planets' orbits may not even be stable in the long term (i.e., millions or billions of years). As a rule of thumb, you can expect the position of a planet to be accurate to a few arcseconds between the dates -2000 and 6000. </para
136><para
137>Pluto is the exception to this; its position is perhaps ten times less precise than the positions of the other planets. Still, for dates near the present epoch, its position can be trusted to about an arcsecond. </para
138><para
139>The moon's position is the most difficult to predict to high precision. This is because its motion is quite perturbed by the Earth. Also, since it is so nearby, even minute effects that would be undetectable in more distant bodies are easily apparent in the moon. </para
140><para
141>The objects with the worst long-term precision in the program are the comets and asteroids. We use a very simplistic orbital model for the minor planets that does not include third-body perturbations. Therefore, their positions can only be trusted for dates near the present epoch. Even for the present epoch, one can expect positional errors among the minor planets of order 10 arcseconds or more. </para>
142</listitem>
143</itemizedlist>
144</para>
145</answer>
146</qandaentry>
147
148<qandaentry>
149<question>
150<para
151>Why do I have to download an improved NGC/IC catalogue and Messier object images? Why not just include them as part of the &kstars; distribution?</para>
152</question>
153<answer>
154<para
155>The author of the downloadable NGC/IC catalogue has released it with the restriction that it may not be used commercially. For most &kstars; users, this is not a problem. However, it is technically against the &kstars; license (the <acronym
156>GPL</acronym
157>) to restrict usage in this way. We removed the Messier object images from the standard distribution for two reasons: to simply reduce the size of &kstars;, and also because of similar licensing concerns with a couple of the images. The inline images are significantly compressed to a very low quality from their original form, so I doubt there is a real copyright concern, but I did obtain explicit permission from the images' authors to use the few images for which there was any question about it (see <filename
158>README.images</filename
159>). Still, just to be absolutely safe, I removed them from the standard distribution, and marked the download archive as being "free for non-commercial use". </para>
160</answer>
161</qandaentry>
162
163<qandaentry>
164<question>
165<para
166>I am really enjoying the beautiful images I have downloaded through &kstars;! I would like to share them with the world; can I publish a calendar featuring these images (or are there any usage restrictions on the images)?</para>
167</question>
168<answer>
169<para
170>It depends on the image, but many of the images restrict against commercial usage. The Image Viewer's statusbar will usually contain information about the image's copyright holder, and what usage restrictions apply. As a rule of thumb: anything published by NASA is in the public domain (including all HST images). For everything else, you can pretty safely assume that the images may not be used commercially without permission. When in doubt, contact the image's copyright holder directly. </para>
171</answer>
172</qandaentry>
173
174<qandaentry>
175<question>
176<para
177>Can I help contribute to future versions of &kstars;?</para>
178</question>
179<answer>
180<para
181>Yes, definitely! Introduce yourself on our mailing list: <email
182>kstars-devel@kde.org</email
183>. If you want to help with the coding, download the latest <ulink url="http://edu.kde.org/kstars/cvs.html"
184>CVS</ulink
185> version of the code and dive right in. There are several README files in the distribution that explain some of the code's subsystems. If you need ideas of what to work on, see the TODO file. You can submit patches to kstars-devel, and feel free to post any questions you have about the code there as well. </para
186><para
187>If you are not into coding, we can still use your help with i18n, docs, AstroInfo articles, URL links, bug reports and feature requests. </para>
188</answer>
189</qandaentry>
190
191</qandaset>
192</chapter>
193