Small text changes throughout
Jeff Moe
parent
6f421622c8
commit
23ef000497
|
|
@ -12,7 +12,7 @@
|
|||
\section{Overview of Operation}
|
||||
\label{sec:overview-operation}
|
||||
\index{operation}
|
||||
HOWTO run a \gls{SatNOGS-Optical} \gls{ground-station},
|
||||
Below shows how to run a SatNOGS Optical \gls{ground-station},
|
||||
after it has been set up and configured.
|
||||
|
||||
\section{Setup with \texttt{stvid}}
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@
|
|||
{FITS}{FITS}{Flexible Image Transport System}
|
||||
|
||||
\newacronym[
|
||||
description={Software-defined radio is a radio communication system where components that have been traditionally implemented in analog hardware (e.g. mixers, filters, amplifiers, modulators/demodulators, detectors, etc.) are instead implemented by means of software on a personal computer or embedded system.%
|
||||
description={Software-defined radio is a radio communication system where components that have been traditionally implemented in analog hardware (e.g. mixers, filters, amplifiers, modulators/demodulators, detectors, etc.) are instead implemented by means of software on a personal computer or embedded system. SDRs are used in \gls{SatNOGS} \glspl{ground-station}.%
|
||||
\footnote{\cite{Wiki22:softwdefinradiowikipfreeencyc}}
|
||||
}]
|
||||
{SDR}{SDR}{Software-defined radio}
|
||||
|
|
@ -103,7 +103,7 @@
|
|||
{NASA}{NASA}{National Aeronautics and Space Administration}
|
||||
|
||||
\newacronym[
|
||||
description={open-source hardware consists of physical artifacts of technology designed and offered by the open-design movement. Both \gls{FOSS} and open-source hardware are created by the open-source culture movement and apply a like concept to a variety of components. It is sometimes, thus, referred to as \gls{FOSH}. The term usually means that information about the hardware is easily discerned so that others can make it -- coupling it closely to the maker movement. Hardware design (i.e. mechanical drawings, schematics, bills of material, PCB layout data, HDL source code and integrated circuit layout data), in addition to the software that drives the hardware, are all released under free/libre terms. The original sharer gains feedback and potentially improvements on the design from the \gls{FOSH} community. There is now significant evidence that such sharing can drive a high return on investment for the scientific community. It is not enough to merely use an open-source license; an open source product or project will follow open source principles, such as modular design and community collaboration.%
|
||||
description={open-source hardware consists of physical artifacts of technology designed and offered by the open-design movement. Both \gls{FOSS} and open-source hardware are created by the open-source culture movement and apply a like concept to a variety of components. It is sometimes, thus, referred to as \gls{FOSH}. The term usually means that information about the hardware is easily discerned so that others can make it---coupling it closely to the maker movement. Hardware design (i.e. mechanical drawings, schematics, bills of material, PCB layout data, HDL source code and integrated circuit layout data), in addition to the software that drives the hardware, are all released under free/libre terms. The original sharer gains feedback and potentially improvements on the design from the \gls{FOSH} community. There is now significant evidence that such sharing can drive a high return on investment for the scientific community. It is not enough to merely use an open-source license; an open source product or project will follow open source principles, such as modular design and community collaboration.%
|
||||
\footnote{\cite{enwiki:Open-source-hardware}}
|
||||
}]
|
||||
{OSH}{OSH}{open-source hardware}
|
||||
|
|
@ -235,6 +235,12 @@
|
|||
description={a setup of equipment such as computers, cameras, \glspl{SDR}, antennas, and receivers, located on Earth, observing space.
|
||||
}}
|
||||
|
||||
\newglossaryentry{SatNOGS-Optical}
|
||||
{ name={SatNOGS Optical},
|
||||
description={is a project by the \gls{LSF} to add optical ground stations to the SatNOGS network.%
|
||||
\footnote{\url{https://satnogs.org/}}
|
||||
}}
|
||||
|
||||
\newglossaryentry{SatNOGS DB}
|
||||
{ name={SatNOGS DB},
|
||||
description={is an effort to create an hollistic, unified, global database for all artificial objects in space (\glspl{satellite} and spacecrafts). Users can view and export the data, contribute to it, or connect applications using an API. It is part of the \gls{SatNOGS} project.%
|
||||
|
|
@ -252,11 +258,6 @@
|
|||
description={a ground station using optical equipment (cameras) instead of antennas.
|
||||
}}
|
||||
|
||||
\newglossaryentry{SatNOGS-Optical}
|
||||
{ name={SatNOGS Optical},
|
||||
description={Project by the \gls{LSF} to expand the \gls{SatNOGS} network to add \glspl{optical-ground-station}.
|
||||
}}
|
||||
|
||||
\newglossaryentry{antenna}
|
||||
{ name={antenna},
|
||||
description={the interface between radio waves propagating through space and electric currents moving in metal conductors, used with a transmitter or receiver.%
|
||||
|
|
@ -395,9 +396,7 @@
|
|||
% IMX174
|
||||
% OpenCV
|
||||
% MIPI
|
||||
% FOV
|
||||
% f stop etc.
|
||||
% INDI
|
||||
% Kstars
|
||||
% ekos
|
||||
% gphoto
|
||||
|
|
@ -406,3 +405,11 @@
|
|||
% SatNOGS Optical
|
||||
% ASM
|
||||
% allsky
|
||||
% V4L
|
||||
% Pi/Raspberry Pi
|
||||
% appropriate technology
|
||||
% Lagrange point
|
||||
% LEO, GEO etc
|
||||
% PCB
|
||||
% HDL
|
||||
% constellations
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Cameras being tested:
|
|||
\fbox{
|
||||
\parbox{\linewidth}{
|
||||
\textcolor{red}{NOTICE:} \\
|
||||
ZWO/ASI cameras require proprietary non-libre software on host computer.
|
||||
ZWO/ASI cameras require proprietary non-libre software on host computer and is not \gls{DFSG} compatible.
|
||||
\index{proprietary}
|
||||
}
|
||||
}
|
||||
|
|
@ -69,6 +69,9 @@ Cameras being tested:
|
|||
\section{Lenses}
|
||||
\label{sec:hardware-lenses}
|
||||
\index{lens}
|
||||
For lenses, the faster the better.
|
||||
F1.2 works well.
|
||||
F1.8 is the maxmimum recommended.
|
||||
|
||||
Lenses being tested:
|
||||
|
||||
|
|
@ -123,7 +126,7 @@ Comparing embedded computers for \gls{SatNOGS-Optical}.
|
|||
\end{table}
|
||||
\end{center}
|
||||
|
||||
\section{Example Tracking Ground Station}
|
||||
\section{Example Optical Ground Station wtih Tracking}
|
||||
\label{sec:hardware-tracking-ground-station}
|
||||
This is an example of a tracking \gls{ground-station}.
|
||||
It is a prototype, so there are lots of mis-matched,
|
||||
|
|
@ -258,8 +261,8 @@ See figure \ref{fig:video-enclosure-top}, page \pageref{fig:video-enclosure-top}
|
|||
\end{figure}
|
||||
|
||||
\section{Future Designs}
|
||||
There is some discussion of using much large ``lenses'', such as
|
||||
\gls{RASA} ``\gls{telescope}'' (See: \gls{astrograph}).
|
||||
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}
|
||||
tracking mounts, because \gls{telescope} mounts are generally too slow,
|
||||
and need to leap-frog the \gls{satellite}. \Glspl{rotator} used for \glspl{antenna}
|
||||
|
|
|
|||
|
|
@ -354,11 +354,11 @@ leftmargin=1cm,rightmargin=1cm
|
|||
% Comment out a line to not render that chapter
|
||||
\chapterconf{Satellites}{Satellites}{Artificial Satellites in Space}
|
||||
\chapterconf{Ground_Stations}{Ground Stations}{Looking up from Earth}
|
||||
\chapterconf{SatNOGS_Optical}{Toolchain and Pipeline}{Make Old Photons Useful Again}
|
||||
\chapterconf{SatNOGS_Optical}{Toolchain and Pipeline}{Make Old Photons Count}
|
||||
\chapterconf{Hardware}{Hardware}{Design and Set Up Equipment}
|
||||
\chapterconf{Software}{Software}{Satellite Applications on Earth}
|
||||
\chapterconf{Acquire}{Acquire}{Twinkle, Twinkle, Little Starlink}
|
||||
\chapterconf{Solve}{Solve}{Place from Pixels}
|
||||
\chapterconf{Acquire}{Acquire Data}{Twinkle, Twinkle, Little Starlink}
|
||||
\chapterconf{Solve}{Plate Solvers}{Place from Pixels}
|
||||
\chapterconf{Detect}{Detect}{Find Satellites}
|
||||
\chapterconf{Identify}{Identify}{More Than Just Old Rocket Bodies}
|
||||
\chapterconf{Upload}{Upload}{Send Data to the SatNOGS Network}
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ software to build an operating optical ground station.
|
|||
|
||||
|
||||
\section{Toolchain}
|
||||
\gls{SatNOGS-Optical} Process Overview.%
|
||||
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.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
|
|||
\item [Hardware] --- Hardware, such as cameras and computers, 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 need to be processed by a \gls{plate-solver}. See \ref{sec:plate-solver}, page \pageref{sec:plate-solver}.
|
||||
\item [\Gls{plate-solver}] --- Acquired data samples in \gls{FITS} files need to be processed by a \gls{plate-solver}. See \ref{sec:plate-solver}, page \pageref{sec:plate-solver}.
|
||||
\item [Detect \glspl{satellite}] --- Using \glspl{TLE} and the ``solved'' plates, detect \glspl{satellite}. See \ref{sec:satellite-detection}, page \pageref{sec:satellite-detection}.
|
||||
\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}
|
||||
|
|
@ -44,11 +44,11 @@ See figure \ref{fig:snopo}, page \pageref{fig:snopo}, described below.
|
|||
\section{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 \ref{sec:hardware-overview}, page \pageref{sec:hardware-overview}.
|
||||
Below is discussed camera options, for details on computers and other parts,
|
||||
also see the Hardware chapter.
|
||||
can be see in section \ref{sec:hardware-overview}, page \pageref{sec:hardware-overview}.
|
||||
Discussed below are camera options, for details on computers and other parts,
|
||||
also see hardware in section \ref{sec:hardware-overview}, page \pageref{sec:hardware-overview}
|
||||
|
||||
For the purposes here, are three main categories of hardware. Depending which
|
||||
For the purposes here, there are three main categories of hardware. Depending which
|
||||
category of equipment is selected, it impacts everything else, such as the
|
||||
software used. Main categories:
|
||||
|
||||
|
|
@ -75,11 +75,11 @@ Examples of motion video camera sources that could be used:
|
|||
\item [UVC/Video4Linux2] --- ``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 bright environments.
|
||||
\item [OpenCV] --- Devices that work with OpenCV can be used.
|
||||
satellites, however, as most are designed for brighter environments.
|
||||
\item [OpenCV] --- Devices that work with OpenCV can be used, same as 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 are also compatible with the Pi
|
||||
Recommended. Many non-Raspberry Pi devices, such as Odroid are also compatible with the Pi
|
||||
MIPI interface.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
|
|
@ -92,7 +92,7 @@ See the list below for still camera options:
|
|||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [\Glspl{telescope}] --- Can definitely take images of \glspl{satellite}.
|
||||
Not the best tool at present, as it isn't well integrated into the toolchain.
|
||||
Not the best tool at present, as it isn't well integrated into the \gls{SatNOGS-Optical} toolchain.
|
||||
The \gls{FOV} is generally too small. The mounts are optimized for
|
||||
different types of tracking than satellites. This is changing, and longer
|
||||
term could be well-supported. Using \gls{RASA} style \glspl{astrograph}
|
||||
|
|
@ -144,7 +144,7 @@ There are also broader ``paths'' that need to be considered:
|
|||
The difficulty with all sky cameras is the \gls{plate-solver} isn't
|
||||
written to use images from the ``fish-eye'' view of an all sky camera.
|
||||
\item [Other] --- There are many other satellite and telescope software
|
||||
packges freely available on the Internet. Many could be adapted for
|
||||
packges freely available on the Internet. Perhaps some could be adapted for
|
||||
usage.
|
||||
\end{description}
|
||||
\end{mdframed}
|
||||
|
|
|
|||
|
|
@ -17,7 +17,8 @@
|
|||
|
||||
\section{SatNOGS DB}
|
||||
The \gls{SatNOGS DB} is a database that lists \glspl{satellite},
|
||||
many of which can be tracked by network operators.
|
||||
many of which can be tracked by ground station operators on the
|
||||
\gls{SatNOGS} network.
|
||||
|
||||
\begin{figure}[h!]
|
||||
\begin{framed}
|
||||
|
|
@ -60,12 +61,12 @@ See the RamSat \gls{telemetry} dashboard.
|
|||
\end{figure}
|
||||
|
||||
\section{Libre Satellites}
|
||||
\Glspl{satellite} in \gls{orbit}, decayed, or designs on Earth that generally support the \gls{libre} way.
|
||||
Below are \glspl{satellite} in \gls{orbit}, decayed, or designs on Earth that generally support the \gls{libre} way.
|
||||
Select \gls{libre} \glspl{satellite}:
|
||||
|
||||
\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
|
||||
\begin{description}
|
||||
\item [UPSat] --- First \gls{libre} \gls{OSH} and software \gls{satellite} in the world.
|
||||
\item [UPSat] --- First \gls{libre} \gls{OSH} and \gls{OSS} \gls{satellite} in the world.
|
||||
Created by the \gls{LSF}. \\
|
||||
\url{https://upsat.gr/}
|
||||
\end{description}
|
||||
|
|
@ -82,7 +83,7 @@ Select \gls{libre} \glspl{satellite}:
|
|||
\end{figure}
|
||||
|
||||
\Gls{RF} Observations can be scheduled on the SatNOGS network.
|
||||
See \ref{fig:satnogs-obs-list-ramsat-web}, page \pageref{fig:satnogs-obs-list-ramsat-web}
|
||||
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}
|
||||
|
|
|
|||
|
|
@ -211,7 +211,7 @@ My fork:
|
|||
\fbox{
|
||||
\parbox{\linewidth}{
|
||||
\textcolor{red}{NOTICE:} \\
|
||||
The main upstream sattools package requires non-\gls{libre} \texttt{pgplot} on host computer.
|
||||
The main upstream sattools package requires non-\gls{libre} \texttt{pgplot} on host computer which is not \gls{DFSG} compatible.
|
||||
\index{proprietary}
|
||||
}
|
||||
}
|
||||
|
|
@ -219,21 +219,27 @@ My fork:
|
|||
|
||||
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.
|
||||
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.
|
||||
|
||||
\begin{minted}{sh}
|
||||
# Install dependencies
|
||||
sudo apt install giza-dev git make dos2unix source-extractor wcslib-dev \
|
||||
libgsl-dev gfortran libpng-dev libx11-dev libjpeg-dev libexif-dev
|
||||
|
||||
# Clone repo
|
||||
git clone https://spacecruft.org/spacecruft/sattools
|
||||
# Or use upstream (needs more steps)
|
||||
git clone https://gitub.com/cbassa/sattools
|
||||
|
||||
cd sattools/
|
||||
|
||||
# Build
|
||||
make
|
||||
|
||||
# Install
|
||||
sudo make install
|
||||
|
||||
# To clean
|
||||
# Clean
|
||||
make clean
|
||||
|
||||
# To rebuild
|
||||
|
|
@ -244,15 +250,14 @@ make
|
|||
sudo make uninstall
|
||||
\end{minted}
|
||||
|
||||
See below for \gls{skymap} usage:
|
||||
See below for \gls{skymap} (fork) usage:
|
||||
|
||||
\begin{minted}{sh}
|
||||
cd bin/
|
||||
./tleupdate
|
||||
tleupdate
|
||||
|
||||
# set config in ~/.bashrc XXX
|
||||
|
||||
./skymap --help
|
||||
skymap --help
|
||||
Usage: skymap [OPTION]
|
||||
Visualize satellites on a map of the sky.
|
||||
|
||||
|
|
|
|||
|
|
@ -95,7 +95,12 @@ XXX The \texttt{4200} series is also recommended.
|
|||
\gls{WCS} info. XXX
|
||||
|
||||
|
||||
\section{SIP}
|
||||
\gls{SIP} info. XXX
|
||||
|
||||
|
||||
\section{Plate Solving with \texttt{stvid}}
|
||||
Use the \texttt{process.py} scripts described at XXX to solve plates
|
||||
Use the \texttt{process.py} scripts described in section \ref{sec:plate-solver},
|
||||
page \pageref{sec:plate-solver}, to solve plates
|
||||
with \texttt{stvid}.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue