spacecruft
/
SNOUG
1
0
Fork 1
Code Packages Releases 14 Activity

Fix glossary words with spaces in name

glossary
Jeff Moe 2022-09-05 23:48:35 -06:00
parent f095b0ba15
commit 5f211905e2
10 changed files with 74 additions and 83 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/Glossary.bib
View File

@ -227,7 +227,7 @@
@entry{plate-solver,
name = {plate solver},
description = {is software implementing a technique used in astronomy and applied on celestial images. Solving an image is finding match between the imaged stars and a \gls{star catalogue}. The solution is a math model describing the corresponding astronomical position of each image pixel. The position of reference catalogue stars has to be known to a high accuracy so an astrometric reference catalogue is used. The image solution contains a reference point, often the image centre, image scale, image orientation and in some cases an image distortion model. With the astrometric solution it is possible to: 1) Calculate the celestial coordinates of any object on the image. 2) Synchronize the telescope mount or satellite pointing position to the center of the image taken. Astrometric solving programs extract the star x,y positions from the celestial image, groups them in three-star triangles or four-star quads. Then it calculates for each group a geometric hash code based on the distance and/or angles between the stars in the group. It then compares the resulting hash codes with the hash codes created from catalogue stars to find a match. If it finds sufficient statistically reliable matches, it can calculate transformation factors. There are several conventions to model the transformation from image pixel location to the corresponding celestial coordinates. The simplest linear model is called the \gls{WCS}. A more advanced convention is \gls{SIP} describing the transformation in polynomials to cope with non-linear geometric distortion in the celestial image, mainly caused by the optics.%
description = {is software implementing a technique used in astronomy and applied on celestial images. Solving an image is finding match between the imaged stars and a \gls{star-catalogue}. The solution is a math model describing the corresponding astronomical position of each image pixel. The position of reference catalogue stars has to be known to a high accuracy so an astrometric reference catalogue is used. The image solution contains a reference point, often the image centre, image scale, image orientation and in some cases an image distortion model. With the astrometric solution it is possible to: 1) Calculate the celestial coordinates of any object on the image. 2) Synchronize the telescope mount or satellite pointing position to the center of the image taken. Astrometric solving programs extract the star x,y positions from the celestial image, groups them in three-star triangles or four-star quads. Then it calculates for each group a geometric hash code based on the distance and/or angles between the stars in the group. It then compares the resulting hash codes with the hash codes created from catalogue stars to find a match. If it finds sufficient statistically reliable matches, it can calculate transformation factors. There are several conventions to model the transformation from image pixel location to the corresponding celestial coordinates. The simplest linear model is called the \gls{WCS}. A more advanced convention is \gls{SIP} describing the transformation in polynomials to cope with non-linear geometric distortion in the celestial image, mainly caused by the optics.%
\footnote{\cite{enwiki:Astrometric-solving}}
}
}
@ -290,21 +290,21 @@
@entry{star-catalogue,
name = {star catalogue},
description = {is an \gls{astronomical catalogue} that lists stars. In astronomy, many stars are referred to simply by catalogue numbers. There are a great many different \glspl{star catalogue} which have been produced for different purposes over the years. Most modern catalogues are available in electronic format and can be freely downloaded from space agencies' data centres. The largest is being compiled from the spacecraft Gaia and thus far has over a billion stars. Completeness and accuracy are described by the faintest limiting magnitude and the accuracy of the positions.%
description = {is an \gls{astronomical-catalogue} that lists stars. In astronomy, many stars are referred to simply by catalogue numbers. There are a great many different star catalogue which have been produced for different purposes over the years. Most modern catalogues are available in electronic format and can be freely downloaded from space agencies' data centres. The largest is being compiled from the spacecraft Gaia and thus far has over a billion stars. Completeness and accuracy are described by the faintest limiting magnitude and the accuracy of the positions.%
\footnote{\cite{enwiki:Star_catalogue}}
}
}
@entry{sky-chart,
name = {sky chart},
description = {or star chart or star map, also called or sky map, is a map of the night sky. Astronomers divide these into grids to use them more easily. They are used to identify and locate constellations and astronomical objects such as stars, nebulae, and galaxies. They have been used for human navigation since time immemorial. Note that a sky chart differs from an \gls{astronomical catalogue}, which is a listing or tabulation of astronomical objects for a particular purpose.%
description = {or star chart or star map, also called or sky map, is a map of the night sky. Astronomers divide these into grids to use them more easily. They are used to identify and locate constellations and astronomical objects such as stars, nebulae, and galaxies. They have been used for human navigation since time immemorial. Note that a sky chart differs from an \gls{astronomical-catalogue}, which is a listing or tabulation of astronomical objects for a particular purpose.%
\footnote{\cite{enwiki:Star_chart}}
}
}
@entry{astronomical-catalogue,
name = {astronomical catalogue},
description = {is a list or tabulation of astronomical objects, typically grouped together because they share a common type, morphology, origin, means of detection, or method of discovery. The oldest and largest are \glspl{star catalogue}. Hundreds have been published, including general ones and special ones for such items as infrared stars, variable stars, giant stars, multiple star systems, and star clusters. Since the late 20th century catalogs are increasingly often compiled by computers from an automated survey, and published as computer files rather than on paper.%
description = {is a list or tabulation of astronomical objects, typically grouped together because they share a common type, morphology, origin, means of detection, or method of discovery. The oldest and largest are \glspl{star-catalogue}. Hundreds have been published, including general ones and special ones for such items as infrared stars, variable stars, giant stars, multiple star systems, and star clusters. Since the late 20th century catalogs are increasingly often compiled by computers from an automated survey, and published as computer files rather than on paper.%
\footnote{\cite{enwiki:Astronomical_catalog}}
}
}

2
src/Ground_Stations.tex
View File

@ -13,7 +13,7 @@
\label{sec:overview-groundstations}
\index{ground station}\index{SDR}\index{antenna}\index{camera}
\index{receiver}\index{embedded system}
\Glspl{ground-station} are a setup of equipment such as \glspl{embedded system}, cameras,
\Glspl{ground-station} are a setup of equipment such as \glspl{embedded-system}, cameras,
\glspl{SDR}, \glspl{antenna}, and receivers, located on Earth, observing space.

29
src/Hardware.tex
View File

@ -20,10 +20,10 @@ Main hardware components in an optical \gls{ground-station}:
\begin{itemize}
\item Lens. \index{lens}
\item Camera. \index{camera}
\item \Gls{embedded system} (computer). \index{embedded system}
\item \Gls{embedded-system} (computer).
\end{itemize}
\end{mdframed}
\index{lens}\index{camera}\index{embedded system}
\index{lens}\index{camera}
Other components:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
@ -83,23 +83,21 @@ Lenses being tested:
\section{Embedded System}
\label{sec:hardware-computer}
\index{hardware}\index{embedded system}
\Glspl{embedded system}, such as \gls{Raspberry Pi}, that can be used.
\index{Raspberry Pi}
\index{hardware}
\Glspl{embedded-system}, such as \gls{Raspberry-Pi}, that can be used.
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Odroid N2] --- Confirmed working. \index{Odroid}
\item [Odroid M1] --- Testing.
\item [\gls{Raspberry Pi} 3] --- ? \index{Raspberry Pi}
\item [\gls{Raspberry Pi} 4] --- ? \index{Raspberry Pi}
\item [\gls{Raspberry-Pi} 3] --- ?
\item [\gls{Raspberry-Pi} 4] --- ?
\item [Intel \gls{NUC}] --- ? \index{Intel}
\end{description}
\end{mdframed}
\subsection{Embedded Systems Comparison}
Comparing \glspl{embedded system} for \gls{SatNOGS-Optical}.
\index{embedded system}
Comparing \glspl{embedded-system} for \gls{SatNOGS-Optical}.
\begin{center}
\begin{table}[ht]
@ -287,7 +285,7 @@ Tripod and similar options include:
\begin{description}
\item [No mount] --- Quick and dirty, just hang the camera out somewhere sitting on something.
\item [Small tripod] --- There are small desk tripods than can be used with lighter
setups, such as used with a \gls{Raspberry Pi} PiCamera.\index{tripod}
setups, such as used with a \gls{Raspberry-Pi} PiCamera.\index{tripod}
\item [Photography Tripod] --- Using a common camera tripod, of which there is a wide
variety, from light to heavy.\index{tripod}
\item [\Gls{telescope} Tripod] --- Similar to photography tripods, but typically heavier weight.\index{tripod}\index{telescope}
@ -333,12 +331,12 @@ Tracking mount options to consider include:
\item [\gls{INDI} \Gls{telescope} Mounts] --- A wide variety of other \gls{INDI} compatible \gls{telescope} mounts.
\item [Yaesu G-5500] --- Antenna \gls{rotator}.
\item [hamlib] --- Other hamlib compatible \glspl{rotator}.
\item [\gls{Teledyne FLIR} PTU-5] --- High Performance \gls{PTZ} Unit designed for security cameras (untested, no drivers?).
\item [\gls{Teledyne-FLIR} PTU-5] --- High Performance \gls{PTZ} Unit designed for security cameras (untested, no drivers?).
\item [Misc \gls{PTZ}] --- Other security camera \gls{PTZ} mounts.
\end{description}
\end{mdframed}
\index{track}\index{mount}\index{Sky-Watcher}\index{INDI}\index{Celestron}
\index{Yaesu}\index{rotator}\index{hamlib}\index{FLIR}\index{PTZ}
\index{Yaesu}\index{rotator}\index{hamlib}\index{PTZ}
\index{iOptron}
Tracking mounts aren't widely used, but there is support for them in
@ -353,13 +351,13 @@ For tracking, there a few different ways to track:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Static] --- No tracking, just point at one place in the sky.
Generates \glspl{star trail}.\index{star trail}
Generates \glspl{star-trail}.
Generates satellite trails.
\item [Sidereal tracking] --- Tracks stars.
Generates stars as points.
Generates satellite trails.
\item [Satellite tracking] --- Tracks satellites.
Generates \glspl{star trail}.
Generates \glspl{star-trail}.
Generates satellites as points or potentially larger images
of the satellite structure.
\end{description}
@ -433,9 +431,8 @@ speed will be too slow for satellite tracking.
Variable speed tracking (XXX phrase?) is needed for tracking satellites if
the goal is to keep the satellite in the (near) center of the image frame
and leave \glspl{star trail}. The speed the mount moves needs to be calculated
and leave \glspl{star-trail}. The speed the mount moves needs to be calculated
based upon a recent orbit calcuation, such as from a \gls{TLE}.
\index{star trail}
There are highly skilled amateur astronomers that have captured detailed
pictures of artificial satellites, such as the \gls{ISS} and astronauts doing

8
src/Identify.tex
View File

@ -90,7 +90,7 @@ See the following subsections for example output from \gls{stvid}.
\index{unidentified}\index{identify}\index{FITS}\index{stvid}
When \gls{stvid} runs the \texttt{process.py} (or new) script and
it encounters a satellite it cannot identify, it gives it the
\gls{NORAD ID} \texttt{90000}. If more unidentified satellites are
\gls{NORAD-ID} \texttt{90000}. If more unidentified satellites are
detected in the same image, each detection is incremented by one.
See figure \ref{fig:stvid-unidentified}, page \pageref{fig:stvid-unidentified},
@ -99,7 +99,7 @@ One is on the left, the other two on the right, next to each other.
See figures \ref{fig:stvid-unidentified-90000}, \ref{fig:stvid-unidentified-90001}, and \ref{fig:stvid-unidentified-90002}, pages \pageref{fig:stvid-unidentified-90000}, \pageref{fig:stvid-unidentified-90001}, and \pageref{fig:stvid-unidentified-90002},
to see an example of \texttt{stvid} labelling three identified satellites
with \glspl{NORAD ID} \texttt{90000}, \texttt{90001}, \texttt{90002}.
with \glspl{NORAD-ID} \texttt{90000}, \texttt{90001}, \texttt{90002}.
\begin{sidewaysfigure}[p!]
\includegraphics[keepaspectratio=true,height=1.00\textheight,width=1.00\textwidth,angle=0]{id-new-sats/2022-08-23T11:18:12.531.fits.png}
@ -180,9 +180,9 @@ This, and similar issues, can be addressed by checking:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{itemize}
\item Recent \glspl{TLE} on both the processing workstation and the
\gls{embedded system}.\index{TLE}
\gls{embedded-system}.\index{TLE}
\item Correct, \gls{NTP} (or better) synchronized time on on the processing
workstation and the \gls{embedded system}.
workstation and the \gls{embedded-system}.
\item Correct latitude, longitude, and altitude are set in configuration
files, typically based on \gls{GNSS} readings.
\index{latitude}\index{longitude}\index{altitude}\index{GNSS}

4
src/Introduction.tex
View File

@ -53,8 +53,8 @@ The chapters that follow are listed below.
\item [Solve] --- Pictures of stars reveal the time and location of
the photo. Plate solvers reviewed.\index{plate solver}
\item [Detect] --- The plate solver says where the photo is,
now detect if are there moving trails that aren't \glspl{star trail} that could
be \glspl{satellite}.\index{star trail}
now detect if are there moving trails that aren't \glspl{star-trail} that could
be \glspl{satellite}.
\item [Identify] --- With time, location, \gls{satellite} detection, \glspl{TLE}
are overlaid and compared with detected \glspl{satellite}.\index{identify}
\Gls{satellite} identification by computers and humans.

10
src/SatNOGS_Optical.tex
View File

@ -29,7 +29,7 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Hardware] --- Hardware, such as cameras and \glspl{embedded system}, is to be selected and set up.
\item [Hardware] --- Hardware, such as cameras and \glspl{embedded-system}, is to be selected and set up.
\item [Software] --- The best currently available software is to be downloaded, installed, and configured.
\item [Acquire] --- Data samples, typically in the form of \gls{FITS} file photographs, need to be acquired by running a camera outside at night taking pictures of the sky.
\item [\Gls{plate-solver}] --- Acquired data samples in \gls{FITS} files need to be processed by a \gls{plate-solver}. See section \ref{sec:plate-solver}, page \pageref{sec:plate-solver}.
@ -58,7 +58,7 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
Discussed in this section are some of the hardware options to be
explored. More explicit instructions of a particular hardware installation
can be see in section \ref{sec:hardware-overview}, page \pageref{sec:hardware-overview}.
Discussed below are camera options, for details on \glspl{embedded system} and other parts,
Discussed below are camera options, for details on \glspl{embedded-system} and other parts,
also see hardware in section \ref{sec:hardware-overview}, page \pageref{sec:hardware-overview}
\index{embedded system}\index{camera}
@ -94,13 +94,13 @@ Examples of motion video camera sources that could be used:
satellites, however, as most are designed for brighter environments.
\item [\gls{OpenCV}] --- cameras that work with \gls{OpenCV} can be used, same as \gls{UVC}.
To work well, they need to be sensitive.
\item [\gls{Raspberry Pi}] --- The PiCamera can be used. A good lower cost option.
Recommended. Many non-\gls{Raspberry Pi} devices, such as Odroid are also compatible with the Pi
\item [\gls{Raspberry-Pi}] --- The PiCamera can be used. A good lower cost option.
Recommended. Many non-\gls{Raspberry-Pi} devices, such as Odroid are also compatible with the Pi
\gls{MIPI} interface.
\end{description}
\end{mdframed}
\index{The Imaging Source}\index{ZWO ASI}\index{UVC}\index{V4L2}\index{OpenCV}
\index{Raspberry Pi}\index{Odroid}\index{MIPI}\index{DFSG}\index{MIPI}
\index{Odroid}\index{MIPI}\index{DFSG}
Still cameras can also be used productively. The current \gls{Python} \gls{toolchain}
is in very early development and not completely usable yet.

5
src/Satellites.tex
View File

@ -11,10 +11,9 @@
\section{Overview of Satellites}
\label{sec:overview-satellite}
\index{satellite}\index{RF}\index{amateur radio}
\index{satellite}\index{RF}
This chapter gives a brief overview of \glspl{satellite}, with particular
antention to ones using \gls{amateur radio} bands.
\index{amateur radio}
antention to ones using \gls{amateur-radio} bands.
\section{SatNOGS DB}

55
src/Software.tex
View File

@ -44,15 +44,14 @@ For a description of installation using \gls{Docker}, see
section \ref{sec:software-docker}, page \pageref{sec:software-docker}.
For a ``manual'' install, see immediately below.
Setup an \gls{embedded system}, such as a \gls{Raspberry Pi} or an Odroid N2,
Setup an \gls{embedded-system}, such as a \gls{Raspberry-Pi} or an Odroid N2,
with \gls{Debian} stable (11/Bullseye) or testing (Bookworm).
\index{embedded system}\index{Odroid}\index{Debian}
\index{Raspberry Pi}
\index{Odroid}\index{Debian}
See each \gls{software repository} for latest documentation.
See each \gls{software-repository} for latest documentation.
\index{repository}
Install dependencies from the \gls{Debian} \gls{software repository}:
Install dependencies from the \gls{Debian} \gls{software-repository}:
\begin{minted}{sh}
sudo apt update
@ -78,7 +77,7 @@ sudo cp -p hough3dlines /usr/local/bin/hough3dlines
\index{hough3dlines}
Install \texttt{\gls{satpredict}} from using either the cbassa or spacecruft
\gls{software repository}.
\gls{software-repository}.
\index{satpredict}\index{repository}
\begin{minted}{sh}
@ -93,7 +92,7 @@ sudo make install
Now install \texttt{stvid}, the main acquisition and processing
application. It is written in \gls{Python}. Either use the spacecruft
\texttt{git} \gls{software repository} or the cbassa one.
\texttt{git} \gls{software-repository} or the cbassa one.
\index{stvid}\index{Python}\index{acquire}
\begin{minted}{sh}
@ -140,8 +139,7 @@ sudo ln -s /usr/bin/source-extractor /usr/local/bin/sextractor
\section{Configure Software}
\label{sec:software-configure}
Configure the \gls{embedded system}.
\index{embedded system}
Configure the \gls{embedded-system}.
\begin{minted}{sh}
cd stvid/
@ -343,16 +341,16 @@ Software that can be used with \gls{telescope} tracking mounts:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [\gls{INDI}] --- Main client/server used by other applications.
\item [\gls{KStars}] --- \Glspl{sky chart}, \gls{INDI} control.
\item [\gls{KStars}] --- \Glspl{sky-chart}, \gls{INDI} control.
\item [Ekos] --- Application used within \gls{KStars} for remote control
of \glspl{telescope} and related hardware via \gls{INDI}.
\item [Stellarium] --- \Glspl{sky chart}, has \gls{INDI} plugin.
\item [Stellarium] --- \Glspl{sky-chart}, has \gls{INDI} plugin.
\item [Other \gls{INDI}] --- Many more applications work with \gls{INDI}.
\item [INDIGO] --- Positions itself as a next-generation \gls{INDI} (?).
\end{description}
\end{mdframed}
\index{telescope}\index{INDI}\index{KStars}\index{Ekos}\index{Stellarium}
\index{INDIGO}\index{sky chart}
\index{INDIGO}
Using \gls{INDI} with \gls{KStars} and Ekos on a Sky-Watcher or \gls{Celestron}
\gls{telescope} mount is a known working solution.
@ -362,9 +360,9 @@ Using \gls{INDI} with \gls{KStars} and Ekos on a Sky-Watcher or \gls{Celestron}
\subsection{Antenna Tracking Software}
At present, for the \gls{SatNOGS} network \gls{RF} \glspl{ground-station},
hamlib is typically used for tracking, if directional \glspl{antenna} are
used. Hamlib was originally created for \gls{amateur radio} equipment, but has
used. Hamlib was originally created for \gls{amateur-radio} equipment, but has
expanded to control many more devices.
\index{hamlib}\index{antenna}\index{RF}\index{amateur radio}
\index{hamlib}\index{antenna}\index{RF}
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
@ -409,7 +407,7 @@ regional systems.
\index{USA}\index{Europe}\index{Russia}\index{China}
A basic, widely available \gls{COTS} \gls{USB} \gls{GNSS} device
with a basic (or no!) \gls{antenna} plugged into the \gls{embedded system}
with a basic (or no!) \gls{antenna} plugged into the \gls{embedded-system}
can get time and location accurate enough for the
purposes here. See various U-Blox devices, for example.
\index{COTS}\index{USB}\index{U-Blox}
@ -594,7 +592,7 @@ Sidereal is the ``standard'' tracking mode of \glspl{telescope}.
\gls{KStars} is the ``main'' application, but it depends on other key parts.
\gls{INDI} is the protocol that \gls{KStars} uses for \gls{telescope} control.
\gls{INDI} itself is a collection of applications.
While \gls{KStars} has the main \gls{sky chart} and Ekos is launched within it,
While \gls{KStars} has the main \gls{sky-chart} and Ekos is launched within it,
the actual mount control is done with the Ekos application.
While it may sound complex, all of this is set up pretty easily in
\gls{Debian}.
@ -606,14 +604,14 @@ sudo apt update
sudo apt install kstars indi-bin indi-eqmod indi-gpsd
\end{minted}
\gls{KStars} has a \gls{sky chart}, as can be see in figure \ref{fig:kstars-skychart},
\gls{KStars} has a \gls{sky-chart}, as can be see in figure \ref{fig:kstars-skychart},
page \pageref{fig:kstars-skychart}.
When mount control is functioning, a location on the \gls{sky chart}, such as a star,
When mount control is functioning, a location on the \gls{sky-chart}, such as a star,
can be clicked on and the mount will \gls{GoTo} that location and optionally track it.
Using this, a \gls{telescope} mount can be used to easily point the camera at a location
and track it to observe \glspl{telescope}. It should also provide a superior \gls{FITS} file
for extracting data than using a static mount (XXX made up).
\index{KStars}\index{sky chart}\index{GoTo}\index{mount}\index{track}
\index{KStars}\index{sky-chart}\index{GoTo}\index{mount}\index{track}
\index{camera}
To use a \gls{telescope} tracking mount for use with \texttt{stvid}, the following steps need to be performed in
@ -632,7 +630,7 @@ An overview of steps:
(e.g. \texttt{date}).
See section \ref{sec:software-ntp}, page \pageref{sec:software-ntp}.
\item Run camera configuration script (e.g. \texttt{v4l2-ctl} commands).
\item Start \texttt{indiserver} on the \gls{embedded system}, using scripts to
\item Start \texttt{indiserver} on the \gls{embedded-system}, using scripts to
include a camera (such as \texttt{indi\_v4l2\_ccd}.
\item Start \gls{KStars} on the workstation.
\item Launch Ekos within \gls{KStars}, under \texttt{Tools}.
@ -640,7 +638,7 @@ An overview of steps:
and \texttt{\gls{V4L2}} for the \gls{CCD}, which will work with The Imaging Source
camera used in this example. Alternatively, the ZWO ASI could be used with a similar configuration.
\item The Ekos configuration should also be set to use the remote \texttt{indiserver}
\gls{IP} address of the embedded system \gls{USB} connected to the Sky-Watcher mount.
\gls{IP} address of the \gls{embedded-system} \gls{USB} connected to the Sky-Watcher mount.
\item Hit the start button to start Ekos/\gls{INDI}.
\item On the screen that pops up, confirm all the tabs are good.
\item Check the last configuration tab for the camera, it often
@ -654,19 +652,19 @@ An overview of steps:
\item If everything is tracking happily, good.
\item If not, do all the alignment steps.
\item When alignment is good and tracking is accurate, stop Ekos and close it.
\item Stop the \texttt{indiserver} running on the \gls{embedded system}.
\item Start the \texttt{indiserver} on the \gls{embedded system},
\item Stop the \texttt{indiserver} running on the \gls{embedded-system}.
\item Start the \texttt{indiserver} on the \gls{embedded-system},
but without using a camera (e.g. remove \texttt{indi\_v4l2\_ccd}.
\item Select the \gls{INDI} configuration with a remote \texttt{indiserver},
the \gls{EQ} Mount, and the Simulated \gls{CCD}.
\item Hit start in Ekos to get \gls{INDI} connections going.
\item Confirm all is ok in hardware tabs, then hit close.
\item Now in the \gls{KStars} \gls{sky chart} window there is
\item Now in the \gls{KStars} \gls{sky-chart} window there is
control of the mount without interfering with the camera.
\item Start \texttt{stvid}. See XXX for more info.
\item When done capturing that part of the sky with \texttt{stvid},
stop \texttt{stvid}
\item Go to the \gls{KStars} \gls{sky chart} and right-click
\item Go to the \gls{KStars} \gls{sky-chart} and right-click
on the new location, and \gls{slew} to it.
\item Start \texttt{stvid} again, pointing at the new location.
\item Repeat the last few steps each time a new sky location is desired.
@ -675,13 +673,13 @@ An overview of steps:
\index{v4l2-ctl}\index{mount}\index{KStars}\index{telescope}\index{track}
\index{lsusb}\index{cgps}\index{GNSS}\index{NTP}\index{indiserver}
\index{Ekos}\index{Sky-Watcher}\index{V4L2}\index{The Imaging Source}
\index{stvid}\index{sky chart}
\index{stvid}
\begin{sidewaysfigure}[p!]
\begin{center}
\includegraphics[keepaspectratio=true,height=1.00\textheight,width=1.00\textwidth,angle=0]{kstars-skychart.png}
\caption{KStars sky chart, example screenshot.}
\index{KStars}\index{sky chart}
\index{KStars}
\label{fig:kstars-skychart}
\end{center}
\end{sidewaysfigure}
@ -704,10 +702,9 @@ An overview of steps:
\end{center}
\end{sidewaysfigure}
If the camera and mount are connected to the \gls{embedded system} OK, it will
If the camera and mount are connected to the \gls{embedded-system} OK, it will
look like below, in this case with The Imaging Source camera and Sky-Watcher
mount:
\index{embedded system}
\begin{minted}{sh}
jebba@odroid-01:~$ lsusb

8
src/Solve.tex
View File

@ -20,7 +20,7 @@ of the picture. There are two main steps:
\begin{enumerate}
\item Extract stars from an image, such as a \gls{FITS} file generated by \texttt{stvid}.
\item ``Solve'' the image of the stars in the image against vast databases in a
\gls{star catalogue}.
\gls{star-catalogue}.
\index{stvid}\index{FITS}
\end{enumerate}
\end{mdframed}
@ -92,10 +92,10 @@ a plate of stars that has been extracted from \texttt{Source Extractor}. XXX
\section{Star Catalogues}
\label{sec:star-catalogues}
\index{star catalogue}\index{plate solver}\index{stvid}
\index{star-catalogue}\index{plate solver}\index{stvid}
To use a \gls{plate-solver}, you will need \glspl{star catalogue}. They can get large.
The \texttt{stvid} application includes a basic \gls{star catalogue}.
To use a \gls{plate-solver}, you will need \glspl{star-catalogue}. They can get large.
The \texttt{stvid} application includes a basic \gls{star-catalogue}.
XXX The \texttt{4200} index series is also recommended.

28
src/Upload.tex
View File

@ -153,9 +153,8 @@ The main blue line is slightly offset from where the satellite is calculated to
appear.
The blue line forms a small \texttt{L} shape.
The smaller segment indicates the area where the satellite may pass.
Next to the small segment line is the \gls{NORAD ID} for the satellite.
Next to the small segment line is the \gls{NORAD-ID} for the satellite.
If it is unknown, it will be given the number \texttt{90000} or larger.
\index{NORAD ID}
\begin{figure}[h!]
\begin{center}
@ -169,11 +168,11 @@ If it is unknown, it will be given the number \texttt{90000} or larger.
\subsection{\texttt{catalog.png} catalog PNG Files}
\index{FITS}\index{PNG}\index{stvid}\index{NORAD ID}
\index{FITS}\index{PNG}\index{stvid}
\index{detect}\index{identify}
When \texttt{stvid} identifies a satellite, it creates a new \gls{PNG} file for each
satellite detected in the image. A file name example follows, with satellite
\gls{NORAD ID} 48473 identified, also shown in figure
\gls{NORAD-ID} 48473 identified, also shown in figure
\ref{fig:stvid-png-48473-catalog}, page \pageref{fig:stvid-png-48473-catalog}.
\texttt{2022-08-23T04:16:26.633\_48473\_catalog.png}
@ -183,13 +182,13 @@ satellite detected in the image. A file name example follows, with satellite
\includegraphics[keepaspectratio=true,height=0.85\textheight,width=0.85\textwidth,angle=0]{stvid/data/2022-08-23T04:16:26.633_48473_catalog.png}
\caption{\texttt{stvid} PNG of the satellite trail of NORAD ID 48473 identified in red.}
\label{fig:stvid-png-48473-catalog}
\index{stvid}\index{PNG}\index{FITS}\index{NORAD ID}
\index{stvid}\index{PNG}\index{FITS}
\end{center}
\end{figure}
\index{stvid}\index{identify}\index{PNG}
If multiple satellites are detected in the image, they will each get a \gls{PNG} file.
For the example image, a satellite with \gls{NORAD ID} 52718 was also identified.
For the example image, a satellite with \gls{NORAD-ID} 52718 was also identified.
The file name is:
\texttt{2022-08-23T04:16:26.633\_52718\_catalog.png}
@ -199,18 +198,18 @@ The file name is:
\includegraphics[keepaspectratio=true,height=0.85\textheight,width=0.85\textwidth,angle=0]{stvid/data/2022-08-23T04:16:26.633_52718_catalog.png}
\caption{\texttt{stvid} PNG of the satellite trail of NORAD ID 52718 identified in red.}
\label{fig:stvid-png-52718-catalog}
\index{stvid}\index{PNG}\index{FITS}\index{NORAD ID}\index{identify}
\index{stvid}\index{PNG}\index{FITS}\index{identify}
\end{center}
\end{figure}
\subsection{\texttt{unid.png} Unidentified PNG Files}
\index{FITS}\index{PNG}\index{stvid}\index{NORAD ID}
\index{FITS}\index{PNG}\index{stvid}
\index{unidentified}
As shown previously, \texttt{stvid} will create a new \gls{PNG} with a
red line when it identifies a satellite.
When \texttt{stvid} finds a trail it can't identify in the
\gls{TLE} catalogs, it gives it a \gls{NORAD ID} starting with \texttt{90000},
\gls{TLE} catalogs, it gives it a \gls{NORAD-ID} starting with \texttt{90000},
incrementing by one.
See figure \ref{fig:stvid-png-90000-unid}, page \pageref{fig:stvid-png-90000-unid},
for an example of \texttt{stvid} marking an unidentified trail red.
@ -223,7 +222,7 @@ do the same with an unidentified satellite trail.
\includegraphics[keepaspectratio=true,height=0.85\textheight,width=0.85\textwidth,angle=0]{stvid/data/2022-08-23T04:16:26.633_90000_unid.png}
\caption{\texttt{stvid} PNG of an unidentified trail in red.}
\label{fig:stvid-png-90000-unid}
\index{stvid}\index{PNG}\index{FITS}\index{NORAD ID}
\index{stvid}\index{PNG}\index{FITS}
\end{center}
\end{figure}
@ -246,18 +245,17 @@ Note, there is no \texttt{.dat} file created corresponding to the
\texttt{2022-08-23T04:16:26.633.fits.png} file, since it doesn't show
detected trails.
The \texttt{.dat} file contents look like this, for \gls{NORAD ID} 48473:
\index{NORAD ID}
The \texttt{.dat} file contents look like this, for \gls{NORAD-ID} 48473:
\begin{minted}{sh}
48473 21 040AX 9999 G 20220823041631625 17 25 1533406+483563 37 S
\end{minted}
XXX This is the IOD ? XXX
The first field is the \gls{NORAD ID}. The fourth field looks like COSPAR. XXX
The first field is the \gls{NORAD-ID}. The fourth field looks like COSPAR. XXX
Large number starting with 2022 is date and time stamp.
The \texttt{.dat} file contents look like this, for \gls{NORAD ID} 52718:
The \texttt{.dat} file contents look like this, for \gls{NORAD-ID} 52718:
\index{.dat}
\begin{minted}{sh}
@ -323,7 +321,7 @@ satno,cospar,mjd,ra,dec,state,tlefile,age
32706,08010A ,59814.17811171,169.564400,+50.077336,sunlit,/data/tle/inttles.tle,0.624
...
\end{minted}
\index{.csv}\index{NORAD ID}\index{COSPAR}\index{TLE}
\index{.csv}\index{COSPAR}\index{TLE}
\subsubsection{\texttt{stvid} \texttt{threshold.csv} Files}