Elaboration of subtasks in the further ORC implementation. Added details in wiki/planning/orc.md .

This commit is contained in:
Daniel Lisunkin committed 2019-07-25 15:05:34 +02:00
1 parent 4b3d035b8c
commit 485ee60c4f
1 file changed
+31 -3
+31 -3
View File
@@ -30,6 +30,16 @@ The next step is to extend the properties of an ORCPerformanceCurveLeg to not on
After the functionality for the different course possibilities is added, there needs to be a system which takes on the difficulty between automatically deciding/proposing the course information from the tracked legs and giving the race officer the opportunity to overwrite the proposed information with his own evaluation.
This problem should be resolved by the usage of the RaceLog and by the usage of an adapter pattern to match the information given from a TrackedRace to the ORCPerformanceCurveCourse.
For this purpose there are the following subtasks:
- [ ] UML for this concept
- [ ] create RaceLogEvent for TWA/Length information per Leg. This task additionally consists out of some design decisions regarding the revokability of events.
- [ ] create RaceLogEventAnalyzer for this Event
- [ ] implement logic to get TWA/Length from a TrackedLeg
- [ ] implement logic wether to use information from RaceLog or automatic generated from TrackedLeg
- [ ] implement Listener on RaceLog
- [ ] implement Listener on Adapter, so the Ranking Metric get's the signal to recalculate
Future:
The next challenge will be to use the RegattaLog (and maybe also RaceLog) to define the used RankingMetric for a Race. It's not common but there are some races which mix the used RankingMetrics during a regatta. It can be Windward/Leeward with TripleNumbers on some inshore races and constructed course on a coastal.
Scratchbook:
@@ -39,18 +49,36 @@ Scratchbook:
---
## Certificate Management
[tbd]
We want to provide the possibility to change the ORCCertificate per Race (even if this is a corner case and the racing rules don't allow such flexibility). The currently (in this race) used certificates are managed by the ORCPerformanceCurveRankingMetric. The matching of competitor/boat to a certificate will happen via the admin console and
currently it will be set provisionally for the whole regatta. The RankingMetric will load this matching and eventual
updates from racelog upon creation (a RankingMetric is created per TrackedRace). Of course, there should be an opportunity to update the matching, as long as the RankingMetric lives.
From this point the Ranking Metric can choose to create PerformanceCurves to new Courses when it decides that it's
necessary.
- [ ] UML for this concept
- [ ] RegattaLogEvent to Match Competitor to available Certificate (transport the Certificate Object directly)
- [ ] RegattaLog Analyzer
- [ ] RaceLog for Update? Or a RegattaLogEvent as an update, if a certificate change for a competitor
- [ ] APIs for RankingMetric
- [ ] Saving the Certificates in the MongoDB in case of restart (-> Serialization)
Scratchbook:
- MGMT, DB, PC, TripleN, ToT
- CompetitorAndBoatStore
- BoatStore
- RMS Importer
- Long Series (Mittwochsregatta, change of Certificate/Rating Number) new Certificate/Race??
- Long Series (Mittwochsregatta, change of Certificate/Rating Number) new Certificate/Race??
- Serializing/Deserializing, saving certificates to the MongoDB
---
## Ranking Metric
[tbd]
So the main responsibility of the RankingMetric is the calculation of the current ranking based on the tracking information. From this ranking the next step is to calculate the time deltas based on the scratch boat.
For us the easiest way is to use the boat farthest ahead as the scratch boat. For now we will only support this scratch
boat, on the long run we need to support the automatic decision of the scratch boat based on the GPH or a manual
decision of the user.
- [ ] Certificate Management
- [ ] Calculation Parts **[tbd]**
Scratchbook:
- Differences in corrected time do apply on the boat farthest ahead