kopia lustrzana https://github.com/projecthorus/chasemapper
Update readme and screenshot
rodzic
ccc98f6324
commit
672c5bad03
21
README.md
21
README.md
|
@ -1,6 +1,6 @@
|
||||||
# Project Horus - Browser-Based HAB Chase Map
|
# Project Horus - Browser-Based HAB Chase Map
|
||||||
|
|
||||||
**Note: This is a work-in-progress. Not all of the features below are functional.**
|
**Note: This is a work-in-progress. Features may be incomplete or non-functional!**
|
||||||
|
|
||||||
This folder contains code to display payload (and chase car!) position data in a web browser:
|
This folder contains code to display payload (and chase car!) position data in a web browser:
|
||||||
|
|
||||||
|
@ -13,20 +13,27 @@ You also need flask, and flask-socketio, which can be installed using pip:
|
||||||
$ sudo pip install flask flask-socketio
|
$ sudo pip install flask flask-socketio
|
||||||
```
|
```
|
||||||
|
|
||||||
|
You can then clone this repository with:
|
||||||
|
```
|
||||||
|
$ git clone https://github.com/projecthorus/chasemapper.git
|
||||||
|
```
|
||||||
|
|
||||||
## Configuration & Startup
|
## Configuration & Startup
|
||||||
Many settings are defined in horusmapper.cfg configuration file.
|
Many settings are defined in the horusmapper.cfg configuration file.
|
||||||
Create a copy of the example config file using
|
Create a copy of the example config file using
|
||||||
```
|
```
|
||||||
$ cp horusmapper.cfg.example horusmapper.cfg
|
$ cp horusmapper.cfg.example horusmapper.cfg
|
||||||
```
|
```
|
||||||
Edit this file with your preferred text editor. The config file contains descriptions of each setting.
|
Edit this file with your preferred text editor. The configuration file is fairly descriptive - you will need to set:
|
||||||
|
* At least one telemetry 'profile', which defines where payload and (optionally) car position telemetry data is sourced from.
|
||||||
|
* A default latitude and longitude for the map to centre on.
|
||||||
|
|
||||||
You can then start-up the horusmapper server with:
|
You can then start-up the horusmapper server with:
|
||||||
```
|
```
|
||||||
$ python horusmapper.py
|
$ python horusmapper.py
|
||||||
```
|
```
|
||||||
|
|
||||||
The server can be stopped with CTRL+C.
|
The server can be stopped with CTRL+C. Somes the server doesn't stop cleanly and may the process may need to be killed. (Sorry!)
|
||||||
|
|
||||||
|
|
||||||
## Live Predictions
|
## Live Predictions
|
||||||
|
@ -36,6 +43,8 @@ To do this you need cusf_predictor_wrapper and it's dependencies installed. Refe
|
||||||
|
|
||||||
Once compiled and installed, you will need to:
|
Once compiled and installed, you will need to:
|
||||||
* Copy the 'pred' binary into this directory. If using the Windows build, this will be `pred.exe`; under Linux/OSX, just `pred`.
|
* Copy the 'pred' binary into this directory. If using the Windows build, this will be `pred.exe`; under Linux/OSX, just `pred`.
|
||||||
* [Download wind data](https://github.com/darksidelemm/cusf_predictor_wrapper/#3-getting-wind-data) for your area of interest, and place the .dat files into the gfs subdirectory.
|
* Copy the 'get_wind_data.py' script from cusf_predictor_wrapper/apps into this directory.
|
||||||
|
|
||||||
Modify the horusmapper.cfg Predictor section settings as necessary to reflect the gfs and predictor binary locations, and set `[predictor] predictor_enabled = True`
|
You will then need to modify the horusmapper.cfg Predictor section setting as necessary to reflect the predictory binary location, the appropriate model_download command, and set `[predictor] predictor_enabled = True`
|
||||||
|
|
||||||
|
You can then click 'Download Model' in the web interface's setting tab to trigger a download of the latest GFS model data. Predictions will start automatically once a valid model is available.
|
Plik binarny nie jest wyświetlany.
Przed Szerokość: | Wysokość: | Rozmiar: 204 KiB Po Szerokość: | Wysokość: | Rozmiar: 291 KiB |
Ładowanie…
Reference in New Issue