文件列表:

Procfile (56, 2023-02-15)
raidradar.py (26138, 2023-02-15)
requirements-dev.in (25, 2023-02-15)
requirements-dev.txt (2466, 2023-02-15)
requirements.in (52, 2023-02-15)
requirements.txt (1424, 2023-02-15)
runtime.txt (14, 2023-02-15)
setup.cfg (151, 2023-02-15)
static (0, 2023-02-15)
static\idea_inactive_trawler.png (38137, 2023-02-15)
static\normalize.css (6138, 2023-02-15)
static\sakura-earthly.css (3353, 2023-02-15)
static\sakura-solarized-dark.css (3381, 2023-02-15)
static\sakura-vader.css (3381, 2023-02-15)
static\sample_table.png (59282, 2023-02-15)
static\skeleton.css (11452, 2023-02-15)
static\styledsample.png (28661, 2023-02-15)

# ogame raid radar a python dash app to visualize inactive players in a universe for https://ogame.org --- ## Demo Get an interactive plot with all inactive players on a server and get highlighted the ones near to your departure planet.  Look through the list and find the most lucrative targets to attack (highest economy score). Get all values exported as a `csv` file by hitting the `export` button.  ## usage The app can be used after the usual steps of - getting the code, - creating a virtualenv and activating it to protect your system python env, - installing the required third party packages and - finally, starting the app ```bash git clone cd raidradar virtualenv -p python3.7 venv . ./venv/bin/activate pip install -r requirements.txt python raidradar.py ``` ## How is it done? First forget about Newton, heliocentric view, or physics in general. The idea here is to get a visualisation logic. Imagine: - All `planets` exist around a fictional `center of the universe (x = 0, y = 0)`. - The `galaxy` and `solar system` are represented by an angle. - The distance (radius) of a planet from the core of the universe represents the planets position in a `solar system`. Here is the math behind it: ``` z = r * e^(i * phi) phi = f(galaxy, system) = (galaxy - 1) * galaxy_increment + (system - 1) * system_increment + shift_to_yaxis x = Re(z) y = Im(z) z = x + iy z = r(cos(phi) + i * sin(phi)) ``` `galaxy_increment` and `system_increment` depend on the galaxies in the universe and systems in a galaxy. Essentially, these constants are just there to ensure that our planets are spread equally and only between `0` in `2pi` (pi like 3.1415) The plot would start at `y = 0` (representing in-game coordinates of 1:1:1) and continue counter clockwise. That works if you spent too much time with graphs. Let's make it more intuitive by introducing `shift_to_yaxis`. Now the plot starts at `x = 0`. Usually `r` would be calculated: ``` r = |z| = sqrt(x^2 + y^2) ``` In that scenario `r` would form the spiral form. Which is not what we want. Instead, we set `r = 1` - for now - and get our preliminary `x` and `y` values ``` r = 1 x = Re(z) = cos(phi) y = Im(z) = sin(phi) ``` `galaxies` and the `solar system` are represented by an angle `phi`. We could use `r` to represent the `slot` in the `solar system` such that `slot = 5` would translates to fifth planet in the respective `solar system`. An empirical constant `minimum_distance` and `planet_increment` is set to ensure that all elements (i.e. planets) are spread out across the plot without overlapping each other. ``` r(planet_slot) = f(planet_slot) = planet_increment * planet_slot + minimum_distance ``` The final ready to plot coordinates for a cartesian plot can than be obtained with: ``` x = r(planet_slot) * cos(phi(galaxy, system)) y = r(planet_slot) * sin(phi(galaxy, system)) ``` The plot is running counter clockwise which non-intuitive for non-math people. To match it with an intuitive clock pattern **the `x-axis` is reversed**. > Note We never actually touched complex numbers but borrowed the concept of > the complex plain to visualize complex numbers! ## Constraints 1. I created this app mostly for my self to learn more about dash table elements. Note that the project uses a global variable `UNIVERSE_FIGURE`. That means that the app will break with multiple users. It's possible to have multiple users by using a session caches see (https://dash.plotly.com/sharing-data-between-callbacks). 2. The universe to plot is hardcoded (`universe_id=162, community='en'`). `dcc.Location` could be used to route to an app for each universe running on the `ogame` servers. But the global `UNIVERSE_FIGURE` needs to be removed to achieve that. 3. To reduce `http` calls I used `requests_cache`. You could remove the initialisation of it, or set an expiry matching the update frequencies of the XML files. ## Resources https://paletton.com to get excellent color suggestions to match the CSS theme which is already optimized by great people. https://github.com/oxalorg/sakura for a drop in css https://github.com/erkandem/ogame-stats client package for ogame game statistics

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：