jatkinson1000 / archerycalculator Goto Github PK

It would be nice to add handicap tables with finer measurements and extended ranges.

How do I handle rounding intermediate values compared to the current inverse approach which gets an 'exact' value?

Depends on issue in archeryutils repo, but Vegas 300 round should use full face for classifications.

As a result the interfavce here needs extending to support Vegas 300 and Vegas 300 triple face.

Add support for clout once it is supported by archeryutils.

Need to set up tooling to handle the new indoor classifications being developed in archeryutils.

@mjtamlyn requested the addition of a Metric-122 20 round for use in the Wallingford Castle club shoots.

This should be fairly straightforward. Couple of points to consider however:

• It will be easiest to add this as a custom round
• However, it might be useful to incorporate it into some other functionalities (classifications by event?) and group in the same family as other Metric-122 rounds
• But we need to be sure it doesn't appear in classification tables and is flagged as unofficial for HC/classification purposes
• Are there any other rounds that could also be added at the same time? - Metric 122-80 20?

To make these changes we need to:

• Add the round in the archeryutils package
• Add any necessary functionality in archerycalculator to blacklist from certain operations etc.

It would be good if there was an option to calculate handicap tables for various schemes, not just the new AGB.
This would be useful as currently there is no decent resource available for AA2 tables online.

Currently only generic Red, Blue, and White courses.
Consider a distinction between Marked/Unmarked/Mixed, and adding the WA Yellow Peg rounds.

Requires:

• Add rounds to archeryutils
• Update archeryutils to process classification scores for the rounds
• Update classification tables to show the 3 types of rounds
• Update the tables by event to show 3 types of rounds
• Tests?

Currently the calculator returns values oiutside the 0-150 range when appropriate.

Should we enforce these to be either 0 or null?

Alternatively should we add a warning if a handicap outside this range is returned?

Add Asiatic bow as an option to the inputs.

Details in Archery GB Rules of Shooting.

Using the term 'app' and 'application' in metadata will boost search rankings.

Support new field classifications that are in development for ArcheryGB.

Add continuous Integration:

• black
• pylint
• mypy

Currently you are required to put in a round and a score for rounds comparisons.

It would be nice if this could be done just with a handicap instead as an alternative option.