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

Dab glossary words. Add to glossary, acronyms

glossary
Jeff Moe 2022-09-02 18:54:28 -06:00
parent 26b0ee22a1
commit 305e8b80e6
10 changed files with 327 additions and 136 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/Detect.tex
View File

@ -15,7 +15,7 @@
\index{FITS}
This is a description of \gls{satellite} detection processes.
To detect \gls{satellite} in a \gls{FITS} file using the stvid toolchain,
To detect \gls{satellite} in a \gls{FITS} file using the stvid \gls{toolchain},
run \texttt{process.py} or, if it exists, the \texttt{process\_new.py}
\gls{Python} script.

89
src/Glossary.tex
View File

@ -12,6 +12,12 @@
%%%%%%%%%%%
% ACRONYM %
%%%%%%%%%%%
\newacronym[
description={An operating system is system software that manages computer hardware, software resources, and provides common services for computer programs.%
\footnote{\cite{enwiki:Operating_system}}%
}]
{OS}{OS}{Operating System}
\newacronym[
description={Instrument Neutral Distributed Interface is a \gls{DCS} protocol to enable control, data acquisition and exchange among hardware devices and software front ends, emphasizing astronomical instrumentation.%
\footnote{\cite{enwiki:Instrument-Neutral-Distributed-Interface}}%
@ -180,6 +186,7 @@
\newacronym[description={Single board computer.}]{SBC}{SBC}{Single board computer}
\newacronym[description={Basic Input/Output System.}]{BIOS}{BIOS}{Basic Input/Output System}
\newacronym[description={open-source appropriate technology.}]{OSAT}{OSAT}{open-source appropriate technology}
\newacronym[description={Personal Computer.}]{PC}{PC}{Personal Computer}
% POSIX
% INDIGO
@ -323,7 +330,7 @@
\newglossaryentry{Linux}
{ name={Linux},
description={is a free and open-source, monolithic, modular, multitasking, Unix-like operating system kernel. It was originally authored in 1991 by Linus Torvalds for his i386-based PC, and it was soon adopted as the kernel for the \gls{GNU} operating system, which was written to be a free (libre) replacement for Unix.%
description={is a free and open-source, monolithic, modular, multitasking, \gls{Unix}-like operating system kernel. It was originally authored in 1991 by Linus Torvalds for his i386-based \gls{PC}, and it was soon adopted as the kernel for the \gls{GNU} operating system, which was written to be a free (\gls{libre}) replacement for \gls{Unix}.%
\footnote{\cite{Wiki22:linuxkernewikipfreeencyc}}
}}
@ -471,9 +478,9 @@
\footnote{\cite{enwiki:Star_catalogue}}
}}
\newglossaryentry{star chart}
{ name={star chart},
description={or star map, also called a sky chart 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 star chart differs from an astronomical catalog, which is a listing or tabulation of astronomical objects for a particular purpose.%
\newglossaryentry{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 star chart differs from an astronomical catalog, which is a listing or tabulation of astronomical objects for a particular purpose.%
\footnote{\cite{enwiki:Star_chart}}
}}
@ -485,7 +492,7 @@
\newglossaryentry{Unix}
{ name={Unix},
description={is a family of multitasking, multiuser computer operating systems that derive from the original AT&T Unix, whose development started in 1969 at the Bell Labs research center by Ken Thompson, Dennis Ritchie, and others.%
description={is a family of multitasking, multiuser computer operating systems that derive from the original AT\&T Unix, whose development started in 1969 at the Bell Labs research center by Ken Thompson, Dennis Ritchie, and others.%
\footnote{\cite{enwiki:Unix}}
}}
@ -519,6 +526,60 @@
\footnote{\cite{enwiki:Slewing}}
}}
\newglossaryentry{toolchain}
{ name={toolchain},
description={is a set of programming tools that is used to perform a complex software development task or to create a software product, which is typically another computer program or a set of related programs.%
\footnote{\cite{enwiki:Toolchain}}
}}
\newglossaryentry{pipeline}
{ name={pipeline},
description={is a set of data processing elements connected in series, where the output of one element is the input of the next one. The elements of a pipeline are often executed in parallel or in time-sliced fashion.%
\footnote{\cite{enwiki:Pipeline_computing}}
}}
\newglossaryentry{embedded system}
{ name={embedded system},
description={is a computer system---a combination of a computer processor, computer memory, and input/output peripheral devices---that has a dedicated function within a larger mechanical or electronic system. It is embedded as part of a complete device often including electrical or electronic hardware and mechanical parts. Because an embedded system typically controls physical operations of the machine that it is embedded within, it often has real-time computing constraints. Embedded systems control many devices in common use today. it was estimated that ninety-eight percent of all microprocessors manufactured were used in embedded systems.%
\footnote{\cite{enwiki:Embedded_system}}
}}
\newglossaryentry{star trail}
{ name={star trail},
description={is a type of photograph that uses long exposure times to capture diurnal circles, the apparent motion of stars in the night sky due to Earth's rotation. A star-trail photograph shows individual stars as streaks across the image, with longer exposures yielding longer arcs.%
\footnote{\cite{enwiki:Star_trail}}
}}
\newglossaryentry{satellite flare}
{ name={satellite flare},
description={is a satellite pass visible to the naked eye as a brief, bright ``flare''. It is caused by the reflection toward the Earth below of sunlight incident on satellite surfaces such as solar panels and antennas. Many satellites flare with magnitudes bright enough to see with the unaided eye, i.e. brighter than magnitude +6.5.%
\footnote{\cite{enwiki:Satellite_flare}}
}}
\newglossaryentry{photon}
{ name={photon},
description={is an elementary particle that is a quantum of the electromagnetic field, including electromagnetic radiation such as light and radio waves, and the force carrier for the electromagnetic force. Photons are massless, so they always move at the speed of light in vacuum, 299,792,458 meters/second.%
\footnote{\cite{enwiki:Photon}}
}}
\newglossaryentry{software repository}
{ name={software repository},
description={or repo for short, is a storage location for software packages. Often a table of contents is also stored, along with metadata. A software repository is typically managed by source control or repository managers. Package managers allow automatically installing and updating repositories (sometimes called "packages").%
\footnote{\cite{enwiki:Software_repository}}
}}
\newglossaryentry{upstream}
{ name={upstream},
description={refers to a direction toward the original authors or maintainers of software that is distributed as source code, and is a qualification of either a version (released by the original authors, based on their upstream source code), a bug or a patch.%
\footnote{\cite{enwiki:Upstream}}
}}
\newglossaryentry{daemon}
{ name={daemon},
description={a service in a \gls{Unix} \gls{OS}.%
\footnote{\cite{enwiki:Daemon}}
}}
% TO ADD
% stphot
% giza (pgplot?)
@ -547,3 +608,21 @@
% fork software, fork mount
% sidereal
% List of Software ?
% Sky-Watcher
% Intel
% Kowa
% Odroid
% List of Companies
% Yaesu
% git
% all commands run
% numpy
% stellarium
% Galileo
% U-blox
% systemd
% gpsmon
% cgps
% indiserver
% ntpd
% lsusb

2
src/Ground_Stations.tex
View File

@ -66,7 +66,7 @@ The \gls{LSF} is developing \gls{SatNOGS-Optical} to add
Prototype \glspl{optical-ground-station} are being developed. An example
setup, using a Sky-Watcher EQ6-R Pro telescope tripod and tracking mount,
\index{Sky-Watcher}\index{telescope}\index{tripod}\index{mount}\index{enclosure}
can be seen in Figure
can be seen in figure
\ref{fig:video-enclosure-mount-tripod}, page \pageref{fig:video-enclosure-mount-tripod}.
\begin{figure}[p!]

82
src/Hardware.tex
View File

@ -33,9 +33,9 @@ Other components:
\item Enclosure. \index{enclosure}
\item Power supply. \index{power supply}
\item Tripod. \index{tripod}
\item Manual or tracking mount. \index{mount}
\item Manual or tracking mount. \index{mount}\index{track}
\item Power source, grid or alternative.
\item Internet, wifi or ethernet.
\item Internet, wifi or ethernet.\index{ethernet}
\end{itemize}
\end{mdframed}
\index{ethernet}\index{USB}\index{enclosure}\index{power supply}
@ -59,7 +59,7 @@ Cameras being evaluated:
\fbox{
\parbox{\linewidth}{
\textcolor{red}{NOTICE:} \\
ZWO/ASI cameras require proprietary non-libre software on host computer and is not \gls{DFSG} compatible.
ZWO/ASI cameras require proprietary non-\gls{libre} software on host computer and is not \gls{DFSG} compatible.
\index{proprietary}\index{DFSG}
}
}
@ -83,21 +83,21 @@ Lenses being tested:
\section{Embedded Computer}
\label{sec:hardware-computer}
\index{hardware}\index{embedded computer}
Embedded computers, such as Raspberry Pi, that can be used.
\Glspl{embedded system}, such as \gls{Raspberry Pi}, that can be used.
\index{Raspberry Pi}
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Odroid N2] --- Confirmed working. \index{Odroid}
\item [Odroid M1] --- Testing.
\item [Raspberry Pi 3] --- ? \index{Raspberry Pi}
\item [Raspberry Pi 4] --- ? \index{Raspberry Pi}
\item [\gls{Raspberry Pi} 3] --- ? \index{Raspberry Pi}
\item [\gls{Raspberry Pi} 4] --- ? \index{Raspberry Pi}
\item [Intel \gls{NUC}] --- ? \index{Intel}
\end{description}
\end{mdframed}
\subsection{Comparison}
Comparing embedded computers for \gls{SatNOGS-Optical}.
Comparing \glspl{embedded system} for \gls{SatNOGS-Optical}.
\index{embedded computer}
\begin{center}
@ -114,7 +114,7 @@ Comparing embedded computers for \gls{SatNOGS-Optical}.
Odroid & M1 & ARM64 & 8 GB & Yes\\
\hline
\end{tabularx}
\caption{Comparison of embedded computers}
\caption{Comparison of embedded systems}
\label{compare-embed}
\end{center}
\end{mdframed}
@ -155,6 +155,7 @@ In the background is a white \gls{antenna} for \gls{GNSS} (\gls{GPS}) and a sola
The camera lens is protected by the enclosure glass, which is \gls{IP67} (XXX) rated.
See a close up of the front of the enclosure and camera lens in figure
\index{encloser}\index{lens}\index{IP67}
\ref{fig:video-enclosure-front}, page \pageref{fig:video-enclosure-front}.
\begin{figure}[h!]
@ -172,6 +173,7 @@ As seen in figure
\ref{fig:video-enclosure-left}, page \pageref{fig:video-enclosure-left},
the left side of the enclosure has a hinge for opening.
The bottom white component is part of the telescope mount.
\index{mount}\index{telescope}
\begin{figure}[h!]
\begin{framed}
@ -203,6 +205,7 @@ These are unscrewed with a hex head tool (supplied) to open the enclosure.
\end{figure}
The enclosure is opened from the right side, as shown in figure
\index{enclosure}
\ref{fig:video-enclosure-right}, page \pageref{fig:video-enclosure-right}.
\begin{sidewaysfigure}[p!]
@ -215,6 +218,7 @@ The enclosure is opened from the right side, as shown in figure
\end{sidewaysfigure}
Inside the camera enclosure, as shown in Figure
\index{enclosure}
\ref{fig:video-enclosure-top-open}, page \pageref{fig:video-enclosure-top-open},
is:
@ -231,7 +235,7 @@ is:
\item Ethernet cable, internal, short white (came with Bosch enclosure). \index{ethernet}
\item \gls{PoE} ethernet cable, external, plugged into \gls{PoE} switch for data and power. \index{PoE}
\item \gls{USB} 3 cable, internal, way too long, needs replacing, from Odroid to camera. XXX flat connector
\item \gls{USB} 3 cable, external, from Odroid to telescope mount. XXX large rectangle connector \index{USB}
\item \gls{USB} 3 cable, external, from Odroid to \gls{telescope} mount. XXX large rectangle connector \index{USB}
\item ``Custom'' 12\gls{V} \gls{DC} power cable from Bosch \gls{PoE} to Odroid.
\item Assorted nuts, bolts, and washers for an ad-hoc standoff height.
\end{itemize}
@ -250,6 +254,7 @@ is:
\end{sidewaysfigure}
The top of the enclosure shows weather protection and a sun visor.
\index{enclosure}
See figure \ref{fig:video-enclosure-top}, page \pageref{fig:video-enclosure-top}.
\begin{figure}[h!]
@ -281,13 +286,13 @@ 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 Raspberry Pi PiCamera.
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.
\item [Telescope Tripod] --- Similar to photography tripods, but typically heavier weight.
\item [Telescope Portable Pier] --- Similar to a telescope tripod, but much heavier, typically
with a larger center pier post. Still movable, and folds up similar to a photography tripod.
\item [Telescope Pier] --- A wide variety, such as making a roughly 1.5 meter permanent cement post.
variety, from light to heavy.\index{tripod}
\item [\Gls{telescope} Tripod] --- Similar to photography tripods, but typically heavier weight.\index{tripod}\index{telescope}
\item [\Gls{telescope} Portable Pier] --- Similar to a \gls{telescope} tripod, but much heavier, typically
with a larger center pier post. Still movable, and folds up similar to a photography tripod.\index{pier}\index{telescope}
\item [\Gls{telescope} Pier] --- A wide variety, such as making a roughly 1.5 meter permanent cement post.
\end{description}
\end{mdframed}
\index{pier}
@ -295,7 +300,7 @@ Tripod and similar options include:
\section{Mounts}
\label{sec:hardware-mounts}
\index{mount}\index{track}
\index{mount}\index{track}\index{tripod}
For mounts, there are two main types: tracking or static.
By the latter ``static'' mounts, it is meant that the
camera, the tripod, and the mount all stay motionless.
@ -317,17 +322,18 @@ Static mounting options include:
\index{camera}\index{mount}
Tracking mount options to consider include:
\index{mount}\index{track}
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Sky-Watcher EQ6-R Pro] --- Telescope mount using \gls{INDI}.
\item [Celestron] --- Wide variety of telescope mounts using \gls{INDI}.
\item [iOptron] --- Telescope mount with (untested) satellite tracking.
\item [INDI Telescope Mounts] --- A wide variety of other \gls{INDI} compatible telescope mounts.
\item [Sky-Watcher EQ6-R Pro] --- \Gls{telescope} mount using \gls{INDI}.
\item [\gls{Celestron}] --- Wide variety of \gls{telescope} mounts using \gls{INDI}.
\item [iOptron] --- \Gls{telescope} mount with (untested) satellite tracking.
\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 [FLIR PTU-5] --- High Performance Pan-Tilt Unit designed for security cameras (untested, no drivers?).
\item [Misc PTZ] --- Other security camera pan/tilt mounts.
\item [FLIR PTU-5] --- High Performance i\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}
@ -337,8 +343,8 @@ Tracking mount options to consider include:
Tracking mounts aren't widely used, but there is support for them in
\texttt{stvid} when acquiring data.
The tracking needs to be set up independently of \texttt{stvid}.
At present, I use KStars with Ekos to control a Sky-Watcher tracking
mount.
At present, I use \gls{KStars} with Ekos to control a Sky-Watcher EQ6-R Pro
tracking mount.
\index{KStars}\index{Ekos}\index{Sky-Watcher}\index{stvid}\index{track}
For tracking, there a few different ways to track:
@ -346,21 +352,22 @@ 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 star trails.
Generates \glspl{star trail}.\index{star trail}
Generates satellite trails.
\item [Sidereal tracking] --- Tracks stars.
Generates stars as points.
Generates satellite trails.
\item [Satellite tracking] --- Tracks satellites.
Generates stars as tracks.
Generates \glspl{star trail}.
Generates satellites as points or potentially larger images
of the satellite structure.
\end{description}
\end{mdframed}
\subsection{Sidereal Tracking Mounts}
\index{track}\index{Celestron}
Sidereal tracking (``telescope tracking'') is what \gls{COTS} tracking ``GOTO''
\glspl{telescope} from Celestron or Sky-Watcher do, for example. They track
\glspl{telescope} from \gls{Celestron} or Sky-Watcher do, for example. They track
the stars, countering the rotation of the Earth to keep the same view
of the sky in the camera's \gls{FOV}. Stars remain as points, even after multi-minute
or multi-hour imaging. This is what is used for ``pretty'' pictures
@ -386,8 +393,8 @@ tracking, but for our uses all three will be included under sidereal tracking.
To use a sidereal tracking mount for imaging satellites, the camera
must ``leap frog'' the satellite.
At present, my practice is to use a sidereal mount, point at a location with KStars,
start stvid. Then stop stvid, move to new location using KStars,
At present, my practice is to use a sidereal mount, point at a location with \gls{KStars},
start stvid. Then stop stvid, move to new location using \gls{KStars},
start stvid.
\index{track}\index{KStars}\index{stvid}
@ -408,24 +415,27 @@ It requires, such as:
\item [\gls{TLE}] --- Need to know the \glspl{satellite}' orbit (accurately!).
\item [Variable speed tracking] --- \Glspl{satellite} are moving at different
speeds above, the mount needs to be capable of that.
\item [Human guided] --- Some skilled amateurs track by hand.
\item [Alignment] --- On top of all the gear and software needed,
the equipment needs to be accurately aligned.
\end{description}
\end{mdframed}
\index{GNSS}\index{TLE}
\index{GNSS}\index{TLE}\index{orbit}
% Some skilled amateurs track by hand.
Most tracking equipment for \glspl{telescope},
cameras, and antennas usually has just a few speeds, such as a slewing speed
cameras, and \glspl{antenna} usually has just a few speeds, such as a \gls{slew} speed
and a sidereal star tracking speed. Sometimes there will be a few steps
of these speeds (e.g. slew speeds from 1-9), but not the finely tuned tracking
of these speeds (e.g. \gls{slew} speeds from 1-9), but not the finely tuned tracking
speeds needed to track a satellite. Oftentimes the telescope tracking maximum
speed will be too slow for satellite tracks.
\index{track}\index{telescope}
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 star trails. 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
@ -434,7 +444,7 @@ space walks, using hand guided telescopes with low cost \gls{CCD} imagers.
% XXX ref
There are few options for satellite tracking mounts.
Some new iOptron telescope mount firmware supports tracking
Some new iOptron telescope mount \gls{firmware} supports tracking
satellites. This has been largely untested so far, but at present
is likely the best option, if a satellite tracking mount is wanted.
\index{iOptron}\index{track}\index{mount}
@ -443,7 +453,7 @@ is likely the best option, if a satellite tracking mount is wanted.
\section{Future Designs}
\label{sec:hardware-future}
\index{RASA}\index{telescope}\index{astrograph}
\index{rotator}\index{antenna}
\index{rotator}\index{antenna}\index{track}
There is some discussion of using much larger ``lenses'', such as
a \gls{RASA} ``\gls{telescope}'' (See: \gls{astrograph}).

6
src/Introduction.tex
View File

@ -41,17 +41,17 @@ The chapters that follow are listed below.
\begin{description}
\item [\Glspl{satellite}] --- What are we looking at?
\item [Ground Stations] --- How Earth talks to \glspl{satellite} and back.
\item [Toolchain and Process] --- The big picture of what
\item [\Gls{toolchain} and Process] --- The big picture of what
hardware and software is needed to set up an optical ground station
for use on the distributed network.
\item [Hardware] --- Details on appropriate hardware configurations,
and example setups.
\item [Software] --- A look at the myriad software related to \glspl{satellite},
and what works best at present for SatNOGS Optical.
\item [Acquire] --- Convert photons to bits. Pointing a camera at the
\item [Acquire] --- Convert \glspl{photon} to bits. Pointing a camera at the
sky works.
\item [Solve] --- Pictures of stars reveal the time and location of
the photo. Plate solvers reviewed.
the photo. Plate solvers reviewed.\index{plate solver}
\item [Detect] --- The plate solver says where the photo is,
now detect if are there moving tracks that aren't stars that could
be \glspl{satellite}.

90
src/SNOUG.bib
View File

@ -488,4 +488,94 @@
year = {2021},
}
@Misc{enwiki:Toolchain,
author = {{Wikipedia contributors}},
title = {Toolchain --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Toolchain&oldid=1094527160}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:11:55},
year = {2022},
}
@Misc{enwiki:Pipeline_computing,
author = {{Wikipedia contributors}},
title = {Pipeline (computing) --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Pipeline_(computing)&oldid=1096885455}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:14:10},
year = {2022},
}
@Misc{enwiki:Embedded_system,
author = {{Wikipedia contributors}},
title = {Embedded system --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Embedded_system&oldid=1106874216}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:19:17},
year = {2022},
}
@Misc{enwiki:Star_trail,
author = {{Wikipedia contributors}},
title = {Star trail --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Star_trail&oldid=1075094531}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:30:14},
year = {2022},
}
@Misc{enwiki:Satellite_flare,
author = {{Wikipedia contributors}},
title = {Satellite flare --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Satellite_flare&oldid=1104678552}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:34:00},
year = {2022},
}
@Misc{enwiki:Photon,
author = {{Wikipedia contributors}},
title = {Photon --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Photon&oldid=1104709214}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:43:30},
year = {2022},
}
@Misc{enwiki:Software_repository,
author = {{Wikipedia contributors}},
title = {Software repository --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Software_repository&oldid=1081326130}},
note = {[Online; accessed 2-September-2022]},
modificationdate = {2022-09-02T17:55:58},
year = {2022},
}
@Misc{enwiki:Upstream,
author = {{Wikipedia contributors}},
title = {Upstream (software development) --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Upstream_(software_development)&oldid=1066370459}},
note = {[Online; accessed 3-September-2022]},
modificationdate = {2022-09-02T18:05:06},
year = {2022},
}
@Misc{enwiki:Daemon,
author = {{Wikipedia contributors}},
title = {Daimon (disambiguation) --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Daimon_(disambiguation)&oldid=1069803376}},
note = {[Online; accessed 3-September-2022]},
modificationdate = {2022-09-02T18:16:56},
year = {2022},
}
@Misc{enwiki:Operating_system,
author = {{Wikipedia contributors}},
title = {Operating system --- {Wikipedia}{,} The Free Encyclopedia},
howpublished = {\url{https://en.wikipedia.org/w/index.php?title=Operating_system&oldid=1104687084}},
note = {[Online; accessed 3-September-2022]},
modificationdate = {2022-09-02T18:19:06},
year = {2022},
}
@Comment{jabref-meta: databaseType:biblatex;}

25
src/SatNOGS_Optical.tex
View File

@ -38,6 +38,7 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
\end{description}
\end{mdframed}
\index{hardware}\index{software}\index{acquire}\index{detect}\index{identify}
\index{plate solver}
\begin{sidewaysfigure}[p!]
\begin{center}
@ -82,22 +83,22 @@ Examples of motion video camera sources that could be used:
\item [The Imaging Source Cameras based on IMX174] --- Known to work. Recommended.
High quality cameras, believed to be usable following \gls{DFSG}.
\item [ZWO ASI based on IMX174] --- Known to work. Not \gls{DFSG} compatible.
Uses proprietary SDK. Currently in prototype development.
Uses proprietary \gls{SDK}. Currently in prototype development.
\item [\gls{UVC}/\gls{V4L2}] --- ``Any'' video camera that works with the \gls{Linux} kernel.
Typically, the device will appear similar to \texttt{/dev/video0}. A camera
that works with the software isn't necessarily sensitive enough to detect
satellites, however, as most are designed for brighter environments.
\item [OpenCV] --- \gls{CV} devices (cameras) that work with OpenCV can be used, same as \gls{UVC}.
\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 [Raspberry Pi] --- The PiCamera can be used. A good lower cost option.
Recommended. Many non-Raspberry Pi devices, such as Odroid are also compatible with the Pi
MIPI interface.
\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}
Still cameras can also be used productively. The current \gls{Python} toolchain
Still cameras can also be used productively. The current \gls{Python} \gls{toolchain}
is in very early development and not completely usable yet.
\index{Python}
@ -116,17 +117,17 @@ See the list below for still camera options:
Cannot be used directly with the current developing \gls{SatNOGS} toolchain.
It is not seen as the future path forward as it isn't well optimized for
\gls{SatNOGS-Optical} usage. That said, it is very useful at present for
running a tracking mount with KStars and Ekos, for example,
running a tracking mount with \gls{KStars} and Ekos, for example,
in lieu of a better option. Camera software in the \gls{INDI} platform typically
produce image \gls{FITS} files.
\item [gphoto] --- The \gls{Linux} kernel recognizes many cameras that can be
used with gphoto tools and drivers, available in \gls{Debian}.
\item [\gls{gPhoto}] --- The \gls{Linux} kernel recognizes many cameras that can be
used with \gls{gPhoto} tools and drivers, available in \gls{Debian}.
This is the recommended option at present for still cameras.
\gls{DSLR} cameras, such as from major manufacturers Canon and Nikon, are
used with gphoto.
used with \gls{gPhoto}.
\end{description}
\end{mdframed}
\index{telescope}\index{INDI}\index{gphoto}\index{DSLR}
\index{telescope}\index{INDI}\index{gPhoto}\index{DSLR}
Considering the hardware options above, they need to be matched with
corresponding software. Not all options work (at all), and some cannot be
@ -151,7 +152,7 @@ There are also broader ``paths'' that need to be considered:
\gls{SatNOGS-Optical} project will likely use in the future
for still cameras.
It is in very early development, but can acquire data (take photos)
with gphoto-compatible cameras.
with \gls{gPhoto}-compatible cameras.
\item [\texttt{asm}] --- All Sky Monitor for taking pictures of all, or nearly all
of the sky, such as with a 150 or 180 degree view. The \texttt{asm}
application is in pre-development, but is in \gls{Python} and could be

5
src/Satellites.tex
View File

@ -13,7 +13,8 @@
\label{sec:overview-satellite}
\index{satellite}\index{RF}
This chapter gives a brief overview of \glspl{satellite}, with particular
antention to ones using amateur \gls{RF} bands.
antention to ones using \gls{amateur radio} bands.
\index{amateur radio}
\section{SatNOGS DB}
@ -106,7 +107,7 @@ for a example list of observations of the RamSat \Gls{cubesat}.%
\end{figure}
Individual \gls{RF} observations are uploaded to the SatNOGS network,
as can be seen in the example observation of the RamSat by SatNOGS
as can be seen in the example observation of the RamSat \gls{cubesat} by SatNOGS
ground station ``2380 - Piszkesteto \gls{UHF}'' run by volunteer bcsak (username).
\index{RF}\index{RamSat}\index{UHF}\index{bcsak}

147
src/Software.tex
View File

@ -39,13 +39,13 @@ for a diagram with an overview of the software process.
HOWTO set up and configure a \gls{SatNOGS-Optical} \gls{ground-station} prototype.
Note: the SatNOGS network is not yet ready for optical data.
Setup an embedded computer, such as an Odroid N2, with \gls{Debian} stable
(11/Bullseye) or testing (Bookworm).
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 computer}\index{Odroid}\index{Debian}
See each repository for latest documentation.
See each \gls{software repository} for latest documentation.
Install dependencies from \gls{Debian} repository:
Install dependencies from the \gls{Debian} \gls{software repository}:
\begin{minted}{sh}
sudo apt update
@ -67,7 +67,8 @@ make all
sudo cp -p hough3dlines /usr/local/bin/hough3dlines
\end{minted}
Install \texttt{\gls{satpredict}} from using either the cbassa or spacecruft repo.
Install \texttt{\gls{satpredict}} from using either the cbassa or spacecruft
\gls{software repository}.
\index{satpredict}
\begin{minted}{sh}
@ -82,8 +83,8 @@ 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} repository or the cbassa one.
\index{stvid}\index{Python}
\texttt{git} \gls{software repository} or the cbassa one.
\index{stvid}\index{Python}\index{acquire}
\begin{minted}{sh}
cd ../
@ -109,10 +110,10 @@ install fails.
pip install --upgrade numpy
pip install --upgrade -r requirements.txt
\end{minted}
\index{numpy}
\index{numpy}\index{PIP}
If the system \texttt{python3-numpy} conflicts, you could try installing
numpy in the virtualenv thusly:
numpy with \gls{PIP} in the virtualenv thusly:
\begin{minted}{sh}
pip install --upgrade --ignore-installed numpy
@ -129,7 +130,7 @@ sudo ln -s /usr/bin/source-extractor /usr/local/bin/sextractor
\section{Configure Software}
\label{sec:software-configure}
Configure the embedded computer.
Configure the \gls{embedded system}.
\begin{minted}{sh}
cd stvid/
@ -160,6 +161,7 @@ st-password = bar
# Path to source-extractor
sex_config = /usr/share/source-extractor/default.sex
\end{minted}
\index{Source Extractor}
Store downloads here:
@ -196,8 +198,8 @@ inparallel
Use \gls{skymap} for viewing \gls{satellite} \glspl{orbit} tracks
projected on a map of of the sky. Skymap is part of \gls{sattools}.
\Gls{skymap} isn't a required part of the toolchain, but it is useful
to see what \glspl{satellite} are visibile at a particular time and
\Gls{skymap} isn't a required part of the \gls{toolchain}, but it is useful
to see what \glspl{satellite} are visible at a particular time and
location.
Source:
@ -220,17 +222,17 @@ My fork:
\fbox{
\parbox{\linewidth}{
\textcolor{red}{NOTICE:} \\
The main upstream sattools package requires non-\gls{libre} \texttt{pgplot} on host computer which is not \gls{DFSG} compatible.
The main upstream \gls{sattools} package requires non-\gls{libre} \texttt{pgplot} on the host computer which is not \gls{DFSG} compatible.
\index{proprietary}\index{DFSG}\index{pgplot}
}
}
Described below is how to build and install my fork of \gls{sattools} to use
\gls{skymap} instead of upstream. Upstream requires non-libre software which
\gls{skymap} instead of upstream. \Gls{upstream} requires non-\gls{libre} software which
also happens to be very difficult for most users to compile. My fork uses the
Giza library which replaces pgplot. It is much easier to build.
\index{fork}\index{sattools}\index{skymap}\index{Giza}
\index{fork}\index{sattools}\index{skymap}\index{Giza}\index{pgplot}
\begin{minted}{sh}
# Install dependencies
@ -297,6 +299,7 @@ Visualize satellites on a map of the sky.
-B, --latitude manual site latitude (deg)
-H, --elevation manual site elevation (m)
\end{minted}
\index{TLE}
\section{Tracking Software}
@ -313,40 +316,41 @@ software:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [Telescope] --- Controlling \glspl{telescope} remotely.
\item [Antenna] --- Controlling \glspl{antenna} remotely with hamlib.
\item [\Glspl{telescope}] --- Controlling \glspl{telescope} remotely.
\item [\Glspl{antenna}] --- Controlling \glspl{antenna} remotely with hamlib.
\item [Cameras] --- Controlling \gls{PTZ} cameras remotely.
\end{description}
\end{mdframed}
\index{telescope}\index{antenna}
\index{telescope}\index{antenna}\index{hamlib}\index{PTZ}
\subsection{Telescope Tracking Software}
Software that can be used with telescope tracking mounts:
Software that can be used with \gls{telescope} tracking mounts:
\index{mount}\index{track}
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{description}
\item [\gls{INDI}] --- Main client/server used by other applications.
\item [KStars] --- Sky charts, \gls{INDI} control.
\item [Ekos] --- Application used within KStars for remote 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] --- Sky charts, 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{INDIGO}\index{sky charts}
Using \gls{INDI} with KStars and Ekos on a Sky-Watcher or Celestron
telescope mount is a known working solution.
Using \gls{INDI} with \gls{KStars} and Ekos on a Sky-Watcher or \gls{Celestron}
\gls{telescope} mount is a known working solution.
\index{Sky-Watcher}\index{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 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}
@ -356,13 +360,15 @@ expanded to control many more devices.
\end{description}
\end{mdframed}
I don't know of anyone prototying a satellite tracking mount with hamlib,
I don't know of anyone prototyping a satellite tracking mount with hamlib,
but it should be possible using the ``leap frog'' method, perhaps on the
same mount as existing \gls{SatNOGS} \glspl{antenna}. The mount may not
be steady enough.
\index{hamlib}\index{mount}\index{track}
\subsection{Camera Tracking Software}
\index{PTZ}
There are applications for using \gls{PTZ} control of cameras, such as used in
``security'' cameras.
@ -381,7 +387,7 @@ at present.
\index{GNSS}\index{GPS}\index{Galileo}\index{GLONASS}\index{Beidou}
\index{gpsd}
\gls{GNSS} is used for time synchornization and for (somewhat)
\gls{GNSS} is used for time synchronization and for (somewhat)
accurately determining the location of the observation.
\gls{GNSS} collectively includes the USA \gls{GPS}, Europe's Galileo,
@ -390,13 +396,13 @@ regional systems.
\index{GPS}\index{Galileo}\index{GLONASS}\index{Beidou}
A basic, widely available \gls{COTS} \gls{USB} \gls{GNSS} device
with a basic (or no!) \gls{antenna} plugged into the embedded
computer can get time and location accurate enough for the
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}
In \gls{Debian} \gls{GNSS} service with a \gls{USB} device can be provided
by the \texttt{gpsd} application.
by the \texttt{\gls{gpsd}} application.
\index{Debian}
\begin{minted}{sh}
@ -412,7 +418,7 @@ GPSD_OPTIONS="-Gn"
USBAUTO="false"
\end{minted}
This will start a \texttt{gpsd} daemon listening on all interfaces,
This will start a \texttt{\gls{gpsd}} \gls{daemon} listening on all interfaces,
so it can be used by other computers on the network (such as if
acquire and process are on different machines). Using the
device \texttt{/dev/ttyACM0} can be problematic if there are multiple
@ -423,7 +429,7 @@ used in that case:
DEVICES="/dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00"
\end{minted}
Even with \texttt{gpsd} configuration listening on all \glspl{IP},
Even with \texttt{\gls{gpsd}} configuration listening on all \glspl{IP},
don't think \texttt{systemd} won't do what it likes. So
you may have to do:
@ -431,7 +437,8 @@ you may have to do:
systemctl edit --full gpsd.socket
\end{minted}
And create a configuration like this (I have \gls{IPv6} disabled, in this case):
And create a \gls{gpsd} configuration like this (I have \gls{IPv6} disabled, in this case):
\index{gpsd}
\begin{minted}{sh}
[Unit]
@ -497,21 +504,21 @@ See below for sample output from \texttt{cgps}.
│ Grid Square: DN70jn26 ││GA 15 315 17.0 232.0 43.0 Y │
└───────────────────────────────────────────┘└More...──────────────────────────┘
\end{minted}
\index{cgps}
\index{cgps}\index{GPS}\index{gpsd}
\section{NTP}
\label{sec:software-ntp}
\index{NTP}
With all the above, time still needs to be configured.
Configuring \texttt{gpsd} isn't enough for correct system time.
Configuring \texttt{\gls{gpsd}} isn't enough for correct system time.
The main system on the Internet used for time synchronization is \gls{NTP}.
In \gls{Debian} there are a few options for \gls{NTP}.
The best is to use a hardware \gls{GNSS} (\gls{GPS}), with \gls{PPS} for improved
accuracy. The easiest is to just use \gls{NTP}.
\index{PPS}\index{Debian}\index{GNSS}
\index{PPS}\index{Debian}\index{GNSS}\index{GPS}
All systems in the chain need to have the correct time and
All systems in the \gls{pipeline} need to have the correct time and
location. It is best if they all pull from the same \gls{NTP}
server, or even better than best if they all run \gls{GNSS}
hardware with \gls{PPS} enabled.
@ -536,36 +543,37 @@ sudo ntpdate 192.168.1.1
sudo systemctl start ntp
\end{minted}
Go through each of the systems used in the toolchain and make
sure they all have accurate time or everything will be off.
Go through each of the systems used in the \gls{toolchain} and make
sure they all have accurate time or processing will be off.
\section{KStars}
\label{sec:software-kstars}
\index{software}\index{KStars}\index{Debian}
KStars is an application that has been used for years in the astronomy
\gls{KStars} is an application that has been used for years in the astronomy
community. It is well established, well supported and included in \gls{Debian}.
KStars has multiple uses for imaging \glspl{satellite}.
One main use is to control a telescope tracking mount, such as the
\gls{KStars} has multiple uses for imaging \glspl{satellite}.
One main use is to control a \gls{telescope} tracking mount, such as the
hardware described in section \ref{sec:hardware-mounts}, page \pageref{sec:hardware-mounts}.
\index{track}\index{mount}
For the purposes here, described below will be using KStars with a
For the purposes here, described below will be using \gls{KStars} with a
Sky-Watcher tracking mount with \gls{INDI} and Ekos.
See figure \ref{fig:video-enclosure-mount-tripod}, page \pageref{fig:video-enclosure-mount-tripod}
for a photo of the setup used with KStars below.
for a photo of the setup used with \gls{KStars} below.
The telescope mount will be used in sidereal tracking mode,
The \gls{telescope} mount will be used in sidereal tracking mode,
where the stars will appear as
``points'', and the \glspl{satellite} will appear as trails.
The mount is not used in a satellite tracking mode.
Sidereal is the ``standard'' tracking mode of \glspl{telescope}.
\index{Sky-Watcher}\index{INDI}\index{Ekos}
KStars is the ``main'' application, but it depends on other key parts.
\gls{INDI} is the protocol that KStars uses for \gls{telescope} control.
\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 KStars has the main 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}.
@ -577,18 +585,18 @@ sudo apt update
sudo apt install kstars indi-bin indi-eqmod indi-gpsd
\end{minted}
KStars has a 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 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 go to that location and optionally track it.
Using this, a telescope mount can be used to easily point the camera at a location
and track it to observe telescopes. It should also provide a superior \gls{FITS} file
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}
To use a telescope tracking mount for use with \texttt{stvid}, the following steps need to be performed in
To use a \gls{telescope} tracking mount for use with \texttt{stvid}, the following steps need to be performed in
roughly this order, assuming everything has been configured.
A brief overview of steps:
An overview of steps:
\index{stvid}
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
@ -598,18 +606,19 @@ A brief overview of steps:
\item Confirm all hardware looks ok (e.g. \texttt{lsusb}).
\item Confirm \gls{GNSS} time and location are ok (e.g. \texttt{cgps -u m}).
See section \ref{sec:software-gnss}, page \pageref{sec:software-gnss}.
\item Confirm time is correct on all systems in toolchain (e.g. \texttt{date}).
\item Confirm time is correct on all systems in the \gls{toolchain}
(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 embedded computer, 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 KStars on the workstation.
\item Launch Ekos within KStars, under \texttt{Tools}.
\item Start \gls{KStars} on the workstation.
\item Launch Ekos within \gls{KStars}, under \texttt{Tools}.
\item In Ekos, select a configuration with the \gls{EQ} Mount for the Sky-Watcher,
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 computer \gls{USB} connected to the Sky-Watcher mount.
\gls{IP} address of the embedded computer \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
@ -623,20 +632,20 @@ A brief 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 embedded computer.
\item Start the \texttt{indiserver} on the embedded computer, but without using a camera
(e.g. remove \texttt{indi\_v4l2\_ccd}.
\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 KStars sky chart window there is control of the mount without
interfering with the camera.
\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 KStars sky chart and right-click on the new location,
and slew to it.
\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.
\end{enumerate}
@ -673,7 +682,7 @@ A brief overview of steps:
\end{center}
\end{sidewaysfigure}
If the camera and mount are connected to the embedded computer 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:
@ -689,7 +698,7 @@ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note the \texttt{The Imaging Source Europe GmbH DMK 33UX174} device is the
camera and the
\texttt{Prolific Technology, Inc. USB-Serial Controller} is the telescope
\texttt{Prolific Technology, Inc. USB-Serial Controller} is the \gls{telescope}
mount. Other views of the devices:
\begin{minted}{sh}

15
src/Solve.tex
View File

@ -13,13 +13,14 @@
\label{sec:plate-solver}
\index{plate solver}\index{FITS}
A ``plate solver'' will take an image of stars and detect the time and place
A ``\gls{plate-solver}'' will take an image of stars and detect the time and place
of the picture. There are two main steps:
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\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 of star images.
\item ``Solve'' the image of the stars in the image against vast databases in a
\gls{star catalogue}.
\end{enumerate}
\end{mdframed}
@ -29,13 +30,13 @@ images (e.g. \gls{FITS}).
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{itemize}
\item Source Extractor.
\item KStars with ekos adds \texttt{Internal SEP}.
\item KStars with ekos adds \texttt{Builtin method for solver}.
\item \gls{KStars} with Ekos adds \texttt{Internal SEP}.
\item \gls{KStars} with Ekos adds \texttt{Builtin method for solver}.
\end{itemize}
\end{mdframed}
\index{Source Extractor}\index{KStars}\index{ekos}
See below for a list of plate solvers that can be used.
See below for a list of \glspl{plate-solver} that can be used.
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
\begin{itemize}
@ -91,8 +92,8 @@ a plate of stars that has been extracted from \texttt{Source Extractor}. XXX
\label{sec:star-catalogues}
\index{star catalogue}\index{plate solver}\index{stvid}
To use a plate solver, you will need star catalogues. They can get large.
The \texttt{stvid} application includes a basic 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.