updates

2025-04-01 14:47:03 +02:00
parent bc107983a1
commit 52d7fd8385
2 changed files with 1 additions and 1 deletions
@@ -1,7 +1,7 @@
 \chapter{GUI}
 \label{sec:gui}

-The data used in this thesis was gathered with the help of the astroquery (\cite{astroquery}) python package. For this purpose, as well as displaying the downloaded data, a GUI application was created with the python package PyQt5 (\cite{pyqt5}). The GUI window for downloads can be seen in figure \ref{fig:download_new_star_data_gui}.\\
+During the first startup the GUI window (e.g. in figure \ref{fig:full_gui_normal_selection}) is nearly completely empty. Also an empty local database will be created with SQLite3 (\cite{sqlite}). To show lightcurves, first data needs to be downloaded. For that, the "Add" button has to be clicked. A new dialog window will show. It can be seen in figure \ref{fig:download_new_star_data_gui}. This GUI uses the astroquery (\cite{astroquery}) python package to fetch metadata and download fits files from MAST (\cite{mast}).\\
 The first step is to enter the identifier of the star(s). In case of multiple, they have to be seperated by a semicolon. Then the missions from which the data should be fetched can be selected. The supported missions are TESS and Kepler/K2. For Kepler and K2 short and/or long cadence can be selected. The differeces are described in section \ref{sec:intro:space_missions}. After the selection has been made, the fetch button needs to be pressed. The program will then request metadata matching the star identifier(s) and selected missions from the MAST archive. The found mission data is then displayed in the preview field. It can then be downloaded by pressing the "Ok" button. The program the proceeds to download the according fits-files. The filename and TESS sector or Kepler/K2 target table ID is appended to the previously fetched metadata and handed back to the main GUI.\\
 There a request to Simbad is made to fetch additional metadata. First the alternative identifiers are fetched from Simbad, which also has a MAIN\_ID attribute. This is to make sure we only have one entry in the local database per star and no duplicates. Afterwards additional data is fetched from Simbad (\cite{simbad}) like spectral type, radial velocity and distance. After the data is gathered, the main identifier, the alternative identifiers, spectral type, rotational velocity and distance (and their respective units) as well as the file path, source (TESS, Kepler or K2), and sector/target table id are saved into a local database using SQLite3 (\cite{sqlite}).