Add to index, section labeling
parent
5b603689a6
commit
799d3f6e9a
|
@ -18,6 +18,7 @@ after it has been set up and configured.
|
|||
\section{Setup with \texttt{stvid}}
|
||||
\label{sec:stvid-setup}
|
||||
\index{stvid}\index{acquire}
|
||||
\index{virtualenv}
|
||||
Acquire data with \texttt{acquire.py} from \texttt{\gls{stvid}}.
|
||||
Enter \texttt{virtualenv}, if used:
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
|
||||
\section{Satellite Detection with stvid}
|
||||
\label{sec:satellite-detection}
|
||||
\index{detection}\index{stvid}\index{process.py}\index{Python}
|
||||
\index{detection}\index{stvid}\index{process}\index{Python}
|
||||
\index{FITS}
|
||||
|
||||
This is a description of \gls{satellite} detection processes.
|
||||
|
@ -21,9 +21,10 @@ Python script, if available, or the \texttt{process.py} script.
|
|||
|
||||
Note the \texttt{stvid} application's \texttt{process.py} and \texttt{process\_new.py}
|
||||
will perform both automated detection and identification of satellites.
|
||||
\index{identification}
|
||||
|
||||
\subsection{\texttt{process\_new.py} Usage}
|
||||
\index{process.py}
|
||||
\index{process}
|
||||
|
||||
This assumes you have installed \texttt{stvid} as shown in section \ref{sec:stvid-setup}.
|
||||
Adjust dated directory to actual directory name.
|
||||
|
@ -45,6 +46,7 @@ and new script are different.
|
|||
cd stvid/
|
||||
./process.py -c configuration.ini -d data/obs/20220825_1/020502/
|
||||
\end{minted}
|
||||
\index{stvid}\index{process}
|
||||
|
||||
|
||||
\begin{sidewaysfigure}[p!]
|
||||
|
@ -54,9 +56,11 @@ cd stvid/
|
|||
\index{stvid}\index{process}
|
||||
\end{sidewaysfigure}
|
||||
|
||||
\section{AstroImageJ}
|
||||
|
||||
|
||||
\section{AstroImageJ}
|
||||
\index{identify}\index{AstroImageJ}\index{FITS}
|
||||
|
||||
Analyze data with applications, such as \gls{AstroImageJ}.
|
||||
|
||||
\gls{FITS} files are commonly used in astronomy.%
|
||||
|
|
|
@ -413,3 +413,4 @@
|
|||
% PCB
|
||||
% HDL
|
||||
% constellations
|
||||
% fork
|
||||
|
|
|
@ -11,13 +11,16 @@
|
|||
|
||||
\section{Overview of Ground Stations}
|
||||
\label{sec:overview-groundstations}
|
||||
\index{ground station}
|
||||
\index{ground station}\index{SDR}\index{antenna}\index{camera}
|
||||
\index{receiver}\index{antenna}
|
||||
\Glspl{ground-station} are a setup of equipment such as computers, cameras,
|
||||
\glspl{SDR}, antennas, and receivers, located on Earth, observing space.
|
||||
|
||||
|
||||
\section{SatNOGS Ground Stations}
|
||||
\index{ground station}\index{Libre Space Foundation}
|
||||
\index{rotator}
|
||||
|
||||
The \gls{LSF} built the \gls{SatNOGS} network using distributed,
|
||||
volunteer-run, \gls{RF} \glspl{ground-station} using \glspl{SDR}, such as in
|
||||
figure \ref{fig:spacecruft-rotator}, page \pageref{fig:spacecruft-rotator}.%
|
||||
|
|
|
@ -23,6 +23,7 @@ Main hardware components in an optical ground station:
|
|||
\item Computer. \index{computer}
|
||||
\end{itemize}
|
||||
\end{mdframed}
|
||||
\index{lens}\index{camera}\index{embedded computer}
|
||||
|
||||
Other components:
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
|
@ -37,6 +38,8 @@ Other components:
|
|||
\item Internet, wifi or ethernet.
|
||||
\end{itemize}
|
||||
\end{mdframed}
|
||||
\index{ethernet}\index{USB}\index{enclosure}\index{power supply}
|
||||
\index{tripod}\index{mount}\index{wifi}
|
||||
|
||||
\section{Camera}
|
||||
\label{sec:hardware-camera}
|
||||
|
@ -47,7 +50,7 @@ Cameras being evaluated:
|
|||
\begin{itemize}
|
||||
\item The Imaging Source IMX174 based, monochrome. \index{The Imaging Source}\index{IMX174}
|
||||
\item ZWO ASI174MM, monochrome. \index{ZWO ASI}
|
||||
\item ZWO ASI1600MM Pro, monochrome.
|
||||
\item ZWO ASI1600MM Pro, monochrome. \index{ZWO ASI}
|
||||
\item \gls{DSLR} camera. \index{DSLR}
|
||||
\item PiCamera. \index{PiCamera}
|
||||
\end{itemize}
|
||||
|
@ -57,7 +60,7 @@ Cameras being evaluated:
|
|||
\parbox{\linewidth}{
|
||||
\textcolor{red}{NOTICE:} \\
|
||||
ZWO/ASI cameras require proprietary non-libre software on host computer and is not \gls{DFSG} compatible.
|
||||
\index{proprietary}
|
||||
\index{proprietary}\index{DFSG}
|
||||
}
|
||||
}
|
||||
|
||||
|
@ -79,22 +82,23 @@ Lenses being tested:
|
|||
|
||||
\section{Embedded Computer}
|
||||
\label{sec:hardware-computer}
|
||||
\index{hardware}\index{computer}
|
||||
Computers, such as Raspberry Pi, that can be used.
|
||||
\index{hardware}\index{embedded computer}
|
||||
Embedded computers, such as 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] --- ?
|
||||
\item [Raspberry Pi 4] --- ?
|
||||
\item [Raspberry Pi 3] --- ? \index{Raspberry Pi}
|
||||
\item [Raspberry Pi 4] --- ? \index{Raspberry Pi}
|
||||
\item [Intel NUC] --- ? \index{Intel}
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
|
||||
\subsection{Comparison}
|
||||
Comparing embedded computers for \gls{SatNOGS-Optical}.
|
||||
\index{embedded computer}
|
||||
|
||||
\begin{center}
|
||||
\begin{table}[ht]
|
||||
|
@ -116,9 +120,14 @@ Comparing embedded computers for \gls{SatNOGS-Optical}.
|
|||
\end{mdframed}
|
||||
\end{table}
|
||||
\end{center}
|
||||
\index{Odroid}\index{ARM64}\index{eMMC}
|
||||
|
||||
|
||||
\section{Example Optical Ground Station wtih Tracking}
|
||||
\label{sec:hardware-tracking-ground-station}
|
||||
\index{ground station}\index{mount}\index{tracking}
|
||||
\index{tripod}
|
||||
|
||||
This is an example of a tracking \gls{ground-station}.
|
||||
It is a prototype, so there are lots of mis-matched,
|
||||
overbuilt/underbuilt parts.
|
||||
|
@ -131,6 +140,7 @@ showing the Skywatcher telescope tracking mount,
|
|||
a Bosch \gls{PoE} camera enclosure,
|
||||
and through the glass the camera lens.
|
||||
\index{Skywatcher}\index{telescope}\index{mount}\index{Bosch}\index{PoE}\index{camera}
|
||||
\index{lens}
|
||||
In the background is a white antenna for \gls{GNSS} (\gls{GPS}) and a solar power setup.
|
||||
\index{GNSS}\index{GPS}\index{solar power}
|
||||
|
||||
|
@ -179,6 +189,7 @@ Figure
|
|||
shows the right side of the enclosure.
|
||||
Two mounting bolt access points can be seen on each end.
|
||||
These are unscrewed with a hex head tool (supplied) to open the enclosure.
|
||||
\index{enclosure}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -225,6 +236,9 @@ is:
|
|||
\item Assorted nuts, bolts, and washers for an ad-hoc standoff height.
|
||||
\end{itemize}
|
||||
\end{mdframed}
|
||||
\index{camera}\index{Kowa}\index{The Imaging Source}\index{Odroid}\index{Debian}
|
||||
\index{fan}\index{power cable}\index{mount plate}\index{Bosh}
|
||||
\index{ethernet cable}\index{PoE}\index{USB}\index{power cable}
|
||||
|
||||
\begin{sidewaysfigure}[p!]
|
||||
\begin{center}
|
||||
|
@ -249,7 +263,11 @@ See figure \ref{fig:video-enclosure-top}, page \pageref{fig:video-enclosure-top}
|
|||
\end{framed}
|
||||
\end{figure}
|
||||
|
||||
|
||||
\section{Future Designs}
|
||||
\index{RASA}\index{telescope}\index{astrograph}
|
||||
\index{rotator}\index{antenna}
|
||||
|
||||
There is some discussion of using much larger ``lenses'', such as
|
||||
a \gls{RASA} ``\gls{telescope}'' (See: \gls{astrograph}).
|
||||
The primary concern is the lack of \gls{satellite}
|
||||
|
|
|
@ -11,8 +11,9 @@
|
|||
|
||||
\section{Overview of Satellite Identification}
|
||||
\label{sec:overview-identify}
|
||||
\index{identification}
|
||||
\index{SIDLOC}
|
||||
\index{identification}\index{SIDLOC}\index{orbit}
|
||||
\index{SSA}
|
||||
|
||||
The \gls{LSF} is developing a project called \gls{SIDLOC},
|
||||
for \gls{satellite} identification and localization. With the
|
||||
addition of many more \glspl{satellite} in \gls{orbit} there is a growing need
|
||||
|
@ -21,6 +22,8 @@ for \gls{SSA}.
|
|||
|
||||
\section{\texttt{stvid}'s \texttt{process.py} for Identification}
|
||||
\label{sec:process-identify}
|
||||
\index{identify}\index{FITS}\index{stvid}\index{process}
|
||||
|
||||
The best tool for identifying \glspl{satellite} from \gls{FITS} files
|
||||
is the \texttt{process.py}
|
||||
script from \texttt{stvid}, available here:
|
||||
|
@ -33,7 +36,8 @@ My fork is here:
|
|||
|
||||
|
||||
\section{Identifying Satellites with \texttt{satid}}
|
||||
\index{satid}\index{sattools}
|
||||
\index{satid}\index{sattools}\index{identify}
|
||||
\index{C}\index{Giza}
|
||||
|
||||
The deprecated C application, \texttt{satid} from the \texttt{\gls{sattools}}
|
||||
package can help identify \glspl{satellite}.
|
||||
|
@ -60,6 +64,7 @@ My fork is here:
|
|||
|
||||
|
||||
\section{Identification with stvid}
|
||||
\index{identify}\index{stvid}
|
||||
See the Detection chapter for details on identification with stvid.
|
||||
The detection and identification steps are both done in one script.
|
||||
|
||||
|
|
|
@ -11,6 +11,7 @@
|
|||
|
||||
The SatNOGS Optical Unofficial Guide documents how to set up and run an
|
||||
\gls{optical-ground-station} for the \gls{LSF}'s \gls{SatNOGS} network.
|
||||
\index{ground station}
|
||||
|
||||
% https://network.satnogs.org/
|
||||
\begin{figure}[h!]
|
||||
|
@ -33,6 +34,7 @@ images of \glspl{satellite}. Hardware is reviewed, then software to run
|
|||
on it, with many options, including what is best. Finally,
|
||||
what to do with the data (idk!).
|
||||
The chapters that follow are listed below.
|
||||
\index{RF}
|
||||
|
||||
% Perhaps more LaTeXy ref XXX
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
|
@ -60,6 +62,9 @@ The chapters that follow are listed below.
|
|||
\item [Support] --- Where development is occurring and questions answered!
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{ground station}\index{process}\index{hardware}\index{software}
|
||||
\index{acquire}\index{solve}\index{detect}\index{indentify}\index{upload}
|
||||
\index{support}
|
||||
|
||||
|
||||
\section{Libre Space Foundation}
|
||||
|
@ -93,6 +98,7 @@ Select \gls{LSF} projects:
|
|||
|
||||
\section{SatNOGS Network}
|
||||
SatNOGS is the \gls{LSF}'s global network of \gls{satellite} ground stations.
|
||||
index{ground station}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -106,6 +112,7 @@ SatNOGS is the \gls{LSF}'s global network of \gls{satellite} ground stations.
|
|||
|
||||
|
||||
\section{Network Status}
|
||||
\index{RF}
|
||||
The SatNOGS \gls{RF} network has been running successfully for years.
|
||||
Adding an optical network is a new development. At present there
|
||||
are zero nodes on the network.
|
||||
|
@ -114,4 +121,5 @@ Some software already exists,
|
|||
some is being ported from \gls{C} to \gls{Python}, and other parts remain to be done.
|
||||
There is software available for acquiring optical data of \glspl{satellite}.
|
||||
There is no facility at present for pushing data back to the network.
|
||||
\index{C}\index{Python}
|
||||
|
||||
|
|
|
@ -9,14 +9,20 @@
|
|||
% International Public License (CC BY-SA 4.0) by Jeff Moe.
|
||||
%
|
||||
\section{SatNOGS Optical HOWTO}
|
||||
\label{sec:optical-howto}
|
||||
|
||||
\gls{SatNOGS-Optical} is the nascent distributed network of optical
|
||||
ground stations.
|
||||
|
||||
This chapter gives a top level review what is needed in terms of hardware and
|
||||
software to build an operating optical ground station.
|
||||
\index{hardware}\index{software}\index{ground station}
|
||||
|
||||
|
||||
\section{Toolchain}
|
||||
\label{sec:toolchain}
|
||||
\index{toolchain}
|
||||
|
||||
See below for a \gls{SatNOGS-Optical} Process Overview.%
|
||||
\footnote{\url{https://spacecruft.org/spacecruft/SNOPO}}
|
||||
See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
|
||||
|
@ -31,6 +37,7 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
|
|||
\item [Identify \glspl{satellite}] --- With \glspl{satellite} detected in the previous step, identify what they are. See \ref{sec:overview-identify}, page \pageref{sec:overview-identify}.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{hardware}\index{software}\index{acquire}\index{detect}\index{identify}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -42,6 +49,9 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
|
|||
\end{figure}
|
||||
|
||||
\section{Hardware}
|
||||
\label{sec:hardware}
|
||||
\index{hardware}
|
||||
|
||||
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}.
|
||||
|
@ -59,6 +69,7 @@ software used. Main categories:
|
|||
\item [Allsky cameras] --- Views of all, or nearly all of the sky.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{motion video}\index{still camera}\index{allsky}
|
||||
|
||||
Different types of equipment can be used in different categories.
|
||||
Some can be used in multiple setups, most just in one.
|
||||
|
@ -83,9 +94,12 @@ Examples of motion video camera sources that could be used:
|
|||
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
|
||||
is in very early development and not completely usable yet.
|
||||
\index{Python}
|
||||
|
||||
See the list below for still camera options:
|
||||
|
||||
|
@ -112,6 +126,7 @@ See the list below for still camera options:
|
|||
used with gphoto.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\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
|
||||
|
@ -148,4 +163,7 @@ There are also broader ``paths'' that need to be considered:
|
|||
usage.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{sattools}\index{Python}\index{C}\index{stvid}\index{motion video}
|
||||
\index{still camera}\index{allsky}\index{stphot}\index{allsky}
|
||||
\index{plate solver}
|
||||
|
||||
|
|
|
@ -11,11 +11,14 @@
|
|||
|
||||
\section{Overview of Satellites}
|
||||
\label{sec:overview-satellite}
|
||||
\index{satellite}
|
||||
\index{satellite}\index{RF}
|
||||
This chapter gives a brief overview of \glspl{satellite}, with particular
|
||||
antention to ones using amateur \gls{RF} bands.
|
||||
|
||||
\Glspl{artificial satellite} are rocks with modems.
|
||||
|
||||
\section{SatNOGS DB}
|
||||
\label{sec:satnogs-db}
|
||||
|
||||
The \gls{SatNOGS DB} is a database that lists \glspl{satellite},
|
||||
many of which can be tracked by ground station operators on the
|
||||
\gls{SatNOGS} network.
|
||||
|
@ -61,8 +64,11 @@ See the RamSat \gls{telemetry} dashboard.
|
|||
\end{figure}
|
||||
|
||||
\section{Libre Satellites}
|
||||
\label{sec:libre-satellites}
|
||||
|
||||
Below are \glspl{satellite} in \gls{orbit}, decayed, or designs on Earth that generally support the \gls{libre} way.
|
||||
Select \gls{libre} \glspl{satellite}:
|
||||
These are some select \gls{libre} \glspl{satellite}:
|
||||
\index{orbit}\index{decay}
|
||||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
|
@ -71,6 +77,7 @@ Select \gls{libre} \glspl{satellite}:
|
|||
\url{https://upsat.gr/}
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
\index{UPSat}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -86,7 +93,7 @@ Select \gls{libre} \glspl{satellite}:
|
|||
See figure \ref{fig:satnogs-obs-list-ramsat-web}, page \pageref{fig:satnogs-obs-list-ramsat-web}
|
||||
for a example list of observations of the RamSat \Gls{cubesat}.%
|
||||
\footnote{\url{https://network.satnogs.org/observations/?future=0&norad=48850&observer=&station=&start=&end=&transmitter_mode=&page=2}}
|
||||
\index{RamSat}\index{CubeSat}
|
||||
\index{RamSat}\index{CubeSat}\index{RF}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -101,6 +108,7 @@ for a example list of observations of the RamSat \Gls{cubesat}.%
|
|||
Individual \gls{RF} observations are uploaded to the SatNOGS network,
|
||||
as can be seen in the example observation of the RamSat by SatNOGS
|
||||
ground station ``2380 - Piszkesteto UHF'' run by volunteer bcsak (username).
|
||||
\index{RF}\index{RamSat}
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
@ -114,6 +122,11 @@ ground station ``2380 - Piszkesteto UHF'' run by volunteer bcsak (username).
|
|||
|
||||
|
||||
\section{Satellite Orbits}
|
||||
\label{sec:satellite-orbits}
|
||||
\index{orbit}\index{SGP}\index{SDP}\index{TLE}
|
||||
|
||||
Satellite \glspl{orbit}.
|
||||
See \gls{SGP} and \gls{SDP}.
|
||||
|
||||
See \gls{TLE}.
|
||||
|
||||
|
|
|
@ -10,6 +10,9 @@
|
|||
%
|
||||
|
||||
\section{Software Overview}
|
||||
\label{sec:software-overview}
|
||||
\index{software}
|
||||
|
||||
See \ref{fig:operation}, page \pageref{fig:operation}
|
||||
for a diagram with an overview of the software process.
|
||||
|
||||
|
@ -37,7 +40,7 @@ HOWTO set up and configure a \gls{SatNOGS-Optical} \gls{ground-station}.
|
|||
|
||||
Setup an embedded computer, such as an Odroid N2, with \gls{Debian} stable
|
||||
(11/Bullseye) or testing (Bookworm).
|
||||
\index{computer}\index{Odroid}\index{Debian}
|
||||
\index{embedded computer}\index{Odroid}\index{Debian}
|
||||
|
||||
See each repository for latest documentation.
|
||||
|
||||
|
@ -54,7 +57,7 @@ sudo apt install python3-virtualenv python3-pip python3-dev \
|
|||
\end{minted}
|
||||
|
||||
Next, install the \texttt{\gls{hough3d-code}} dependency.
|
||||
\index{hough3d}
|
||||
\index{hough3d-code}
|
||||
|
||||
\begin{minted}{sh}
|
||||
git clone https://gitlab.com/pierros/hough3d-code
|
||||
|
@ -79,7 +82,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} repository or the cbassa one.
|
||||
\index{stvid}
|
||||
\index{stvid}\index{Python}
|
||||
|
||||
\begin{minted}{sh}
|
||||
cd ../
|
||||
|
@ -89,7 +92,7 @@ git clone https://spacecruft.org/spacecruft/stvid
|
|||
\end{minted}
|
||||
|
||||
Optionally, set up a \gls{Python} virtual environment:
|
||||
\index{Python}
|
||||
\index{Python}\index{virtualenv}
|
||||
|
||||
\begin{minted}{sh}
|
||||
cd stvid
|
||||
|
@ -117,13 +120,14 @@ pip install --upgrade --ignore-installed numpy
|
|||
\gls{Debian} in bug \texttt{\#941466} changed the name of the
|
||||
\texttt{sextractor} dependency to \texttt{source-extractor},
|
||||
so a symlink is needed for now:
|
||||
\index{Debian}
|
||||
\index{Debian}\index{Source Extractor}
|
||||
|
||||
\begin{minted}{sh}
|
||||
sudo ln -s /usr/bin/source-extractor /usr/local/bin/sextractor
|
||||
\end{minted}
|
||||
|
||||
\section{Configure}
|
||||
\section{Configure Software}
|
||||
\label{sec:software-configure}
|
||||
Configure the embedded computer.
|
||||
|
||||
\begin{minted}{sh}
|
||||
|
@ -164,6 +168,7 @@ mkdir -p ./data/obs ./data/tle ./data/results
|
|||
|
||||
The \texttt{ST\_DATADIR} variable is still used, from \texttt{sattools}.
|
||||
Maybe set all these in \texttt{\~/.bashrc} (suit to fit directory setup):
|
||||
\index{bashrc}
|
||||
|
||||
\begin{minted}{sh}
|
||||
export ST_DATADIR=$HOME/sattools
|
||||
|
@ -171,11 +176,11 @@ export ST_TLEDIR=$HOME/TLE
|
|||
export ST_OBSDIR=$HOME/satobs
|
||||
export ST_LOGIN="identity=foo@no:pass"
|
||||
\end{minted}
|
||||
\index{sattools}
|
||||
\index{sattools}\index{TLE}
|
||||
|
||||
Set \texttt{astrometry.net} to run in parallel, assuming you have enough RAM:
|
||||
(This doesn't appear to work? Breaks?).
|
||||
\index{astrometry}
|
||||
\index{astrometry.net}
|
||||
|
||||
\begin{minted}{sh}
|
||||
sudo vim /etc/astrometry.cfg
|
||||
|
@ -185,6 +190,9 @@ inparallel
|
|||
|
||||
|
||||
\section{skymap}
|
||||
\label{sec:skymap}
|
||||
\index{skymap}\index{orbit}\index{sattools}
|
||||
|
||||
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
|
||||
|
@ -212,7 +220,7 @@ My fork:
|
|||
\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.
|
||||
\index{proprietary}
|
||||
\index{proprietary}\index{DFSG}\index{pgplot}
|
||||
}
|
||||
}
|
||||
|
||||
|
@ -221,6 +229,7 @@ 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
|
||||
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}
|
||||
|
||||
\begin{minted}{sh}
|
||||
# Install dependencies
|
||||
|
@ -251,6 +260,7 @@ sudo make uninstall
|
|||
\end{minted}
|
||||
|
||||
See below for \gls{skymap} (fork) usage:
|
||||
\index{TLE}
|
||||
|
||||
\begin{minted}{sh}
|
||||
tleupdate
|
||||
|
|
|
@ -11,7 +11,8 @@
|
|||
|
||||
\section{Plate Solver}
|
||||
\label{sec:plate-solver}
|
||||
\index{plate solver}
|
||||
\index{plate solver}\index{FITS}
|
||||
|
||||
A ``plate solver'' will take an image of stars and detect the time and place
|
||||
of the picture. There are two main steps:
|
||||
|
||||
|
@ -48,7 +49,9 @@ See below for a list of plate solvers that can be used.
|
|||
|
||||
|
||||
\section{Source Extractor}
|
||||
\label{sec:Source Extractor}
|
||||
\index{Source Extractor}
|
||||
|
||||
\texttt{Source Extractor}, formerly \texttt{SExtractor} and some other names,
|
||||
is an application to extract stars from images. The software has been
|
||||
widely used for many years.
|
||||
|
@ -84,22 +87,33 @@ a plate of stars that has been extracted from \texttt{Source Extractor}. XXX
|
|||
}
|
||||
|
||||
|
||||
\section{Star Databases}
|
||||
\index{star database}
|
||||
To use a plate solver, you will need star databases. They can get large.
|
||||
The \texttt{stvid} application includes a basic star database.
|
||||
\section{Star Catalogues}
|
||||
\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.
|
||||
XXX The \texttt{4200} series is also recommended.
|
||||
|
||||
|
||||
\section{World Coordinate System}
|
||||
\label{sec:wcs}
|
||||
\index{WCS}
|
||||
|
||||
\gls{WCS} info. XXX
|
||||
|
||||
|
||||
\section{SIP}
|
||||
\label{sec:sip}
|
||||
\index{SIP}
|
||||
|
||||
\gls{SIP} info. XXX
|
||||
|
||||
|
||||
\section{Plate Solving with \texttt{stvid}}
|
||||
\label{sec:plate-solving-stvid}
|
||||
\index{plate solver}\index{stvid}\index{process}
|
||||
|
||||
Use the \texttt{process.py} scripts described in section \ref{sec:plate-solver},
|
||||
page \pageref{sec:plate-solver}, to solve plates
|
||||
with \texttt{stvid}.
|
||||
|
|
|
@ -10,7 +10,9 @@
|
|||
%
|
||||
|
||||
\section{Upload Data}
|
||||
\label{sec:upload}
|
||||
\index{upload}
|
||||
|
||||
Push.
|
||||
The \gls{SatNOGS} network isn't ready for optical data yet.
|
||||
|
||||
|
|
Loading…
Reference in New Issue