glidergeek / opensoar Goto Github PK

https://packaging.python.org/tutorials/distributing-packages/

does anyone have any clue on which basis seeyou makes this distinction?

ideas for achieving this (thanks to @roeles):

• manually crafting an IGC file and run that trough SeeYou. This can be done with aerofiles.
  hopefully it doesnt care about the security entry

moved from GliderGeek/PySoar#160:

For some reason some contest days analysis result in wrong task speeds for some some participants in the PySoar output.

For example:
https://www.soaringspot.com/en_gb/open-militaire-kampioenschappen-zweefvliegen-2019-terlet-2019/results/clubklasse/task-2-on-2019-06-06/daily
The E9 task speed is completely off, while the others all have correct values compared to the task speeds SoaringSpot.

Could be related to the other problem with incorrect distances? The problem here is that it's only for some (in this case just one) participant within the set of daily result IGC's.

both in setup.py and in requirements.txt

As noted in the PySoar repository ( GliderGeek/PySoar#121 ) a high logger interval (e.g. 1 sec) can disrupt thermal detection and result in unusable performance indicators.

E.g. check flight PB on https://www.soaringspot.com/en_gb/62th-hungarian-national-gliding-hajduszoboszlo-airport-2017/results/unknown/task-8-on-2017-07-14/daily

The igc_lib repo already has an approach implemented for this:
https://github.com/xiadz/igc_lib/blob/master/igc_lib.py#L978

On a different note would there be a benefit to reuse igc_lib or make the flight analysis 'pluggable'?

I am trying to create a personal website to be able to analyse flight or soaringspot result from everywhere using opensoar (and PySoar).
I am using Pythonanaywhere and the website should allow the extern request. Can you please tell me more about the request (which API is used) to download flights from soaringspot daily results ?

• add license

I've distilled this state diagram from your code, please check if this is roughly correct.

I don't really see a state transition from PossibleCruise to Climb. You do check the transition to Cruise (when 1km has been cruised), but I see no place where cruise is set to False

the html format has been changed

following files should be added:

include README.rst
include CHANGELOG
include LICENSE

When analyzing a recent competition day, I realized that pysoar/opensoar has a problem with keyhole sectors. When flying through the 500m cylinder, a valid turnpoint is detected. Flying outside the cylinder but within the 90-degree sector results in an invalid turnpoint.

You may find an example in this competition day:
https://www.soaringspot.com/en_gb/altmarkpokal-2023-stendal/results/standard/task-6-on-2023-07-07/daily

currently the test run over live urls. would be better if there are static html tests in the repo.
the live tests are best done by the end applications

the english variant will not parse correctly.

it seems that the english strepla sites displaces the date differently, leading to a break:

German:

English:

there can be a lot of reasons for a failed analysis. in order to enable more stable programs, the developer should have the possibility to skip failed analyses and have a list of the competitors for which the analysis failed.

https://dev.soaringspot.com/en_gb/53-hww/results/std/task-6-on-2019-06-01/daily

from https://www.strepla.de/, strepla and strepla scoring are no longer supported. the hosting site for the igc files is no longer live so the functionality to scrape the site no longer makes sense

the analysis can be kept in for a while for those who have the specific strepla files around

in the old travis-ci setup, deployment were automatically handled on tag

travis didn't work anymore, so i switched to github actions, but the deployment part is not yet implemented

currently the docs are hosted on readthedocs.

• it does not show the functions inside the modules (it locally does)
• documentation is very limited, should be expanded