https://github.com/jorgepiloto/tfg
My bachelor thesis in aerospace engineering
https://github.com/jorgepiloto/tfg
aerospace astrodynamics kepler lambert orbital-mechanics
Last synced: 7 months ago
JSON representation
My bachelor thesis in aerospace engineering
- Host: GitHub
- URL: https://github.com/jorgepiloto/tfg
- Owner: jorgepiloto
- Created: 2021-07-06T07:43:41.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-09-06T18:55:23.000Z (about 4 years ago)
- Last Synced: 2025-01-25T21:11:26.419Z (9 months ago)
- Topics: aerospace, astrodynamics, kepler, lambert, orbital-mechanics
- Language: TeX
- Homepage:
- Size: 3.9 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Lambert's problem algorithms
A CRITICAL REVIEW
What is this project about?
---------------------------
This repository holds all the different files required to compile my original
work named *Lambert's problem algorithms: a critical review*, were a deep
comparison between modern routines for solving this classic astrodynamics
problem is presented to the reader.
About project structure
-----------------------
The project is divided into different directories, each one devoted to store a
particular type of information:
```
.
├── asy
├── bib
├── bin
├── dat
├── fig
│ └── static
├── main.tex
├── Makefile
├── README.md
├── src
└── tex
```
Within the `asy/` folder, all the scripts used for building the Asymptote based
figures are located. Their output will be temporary stored in the `fig/`
directory and removed after the PDF file has been successfully compiled. Notice
that the `static/` sub-directory holds figures which are not supposed to be
deleted after the cleaning process has been executed.
Regarding `bib/`, `src/` and `tex/` locations, they host all necessary style,
bibliography and work content files. The `main.tex` file is the one used to
control the rest of LaTeX files.
The `bin/` and `dat/` directories is where all binaries and databases used by
them are saved.
Finally the `Makefile` is where all auxiliary rules for automation are
described.
Required dependencies for building the project
----------------------------------------------
Several programs are required to compile the project. The versions listed here
are the ones originally used to build all files. It might be possible that with
newer version, some of tools presented in the following lines are not able to
produce expected results.
**latexindent: a tool for formatting LaTeX files**
```
3.8.3, 2020-11-06
```
**XeLaTeX: the LaTeX engine used to compile the files**
```
XeTeX 3.14159265-2.6-0.999992 (TeX Live 2020/Arch Linux)
kpathsea version 6.3.2
Compiled with ICU version 68.2; using 68.2
Compiled with zlib version 1.2.11; using 1.2.11
Compiled with FreeType2 version 2.10.4; using 2.10.4
Compiled with Graphite2 version 1.3.14; using 1.3.14
Compiled with HarfBuzz version 2.7.4; using 2.7.4
Compiled with libpng version 1.6.37; using 1.6.37
Compiled with poppler version 21.02.0
Compiled with fontconfig version 2.13.91; using 2.13.91
```
**biber: it is used for building the project bibliography**
```
biber version: 2.15
```
**pdfTeX: the program used to render the output PDF file**
```
pdfTeX 3.14159265-2.6-1.40.21 (TeX Live 2020/Arch Linux)
kpathsea version 6.3.2
Compiled with libpng 1.6.37; using libpng 1.6.37
Compiled with zlib 1.2.11; using zlib 1.2.11
Compiled with poppler version 21.02.0
```
**asymptote: it is used for building all technical figures and drawings**
```
Asymptote version 2.69 [(C) 2004 Andy Hammerlindl, John C. Bowman, Tom Prince]
```
**ghostscript: the tool acting as PostScript interpreter, related with
drawings**
```
GPL Ghostscript 9.53.3 (2020-10-01)
```
**Python: the programming language under which binaries are implemented**
```
Python: 3.8.5
```
**make: an utomatition for simplifying project building process**
```
GNU Make 4.3
Built x86_64-pc-linux-gnu
```
How to build the report
-----------------------
After installing all the different dependencies, you can start by building a
clean Python environment by running:
```
python -m venv .venv
```
which can be activated via `source .venv/bin/activate`. After that, install all
the required libraries listed in the `bin/requirements.txt` using:
```
pip install -r bin/requirements.txt
```
Finally, you simply need to execute the following rule to obtain the rendered
PDF:
```
make pdf
```