mirror of
https://github.com/eclipse-sailing-analytics/sailing-analytics.git
synced 2026-10-04 03:13:49 +00:00
added comment for Igtimi Resource class; fixed counting of wind fixes actually imported
This commit is contained in:
1 parent
76a1ae0a6f
commit
6956083ecd
2 files changed
+2
-3
No files matched your search
+1
-1
@@ -7,7 +7,7 @@ import com.sap.sailing.domain.igtimiadapter.datatypes.Type;
|
||||
* You can think of resources really as meta-info - identifying time blocks of data that have some meaning. For an
|
||||
* Igtimi device it's a power cycle. However data access is not forced to be "through" a resource. If you only wanted to
|
||||
* get data from a specific resource then of course you would just use the start and end time stamps in the request.
|
||||
* Resources are meant to be non-overlapping, which is why this works. Although this is not strictly enforced...
|
||||
* Resources are meant to be non-overlapping, although this is not strictly enforced.
|
||||
*
|
||||
* @author Axel Uhl (d043530)
|
||||
*
|
||||
|
||||
+1
-2
@@ -651,11 +651,10 @@ DynamicTrackedRace, GPSTrackListener<Competitor, GPSFixMoving> {
|
||||
&&
|
||||
(endOfTracking == null || endOfTracking.plus(TimingConstants.IS_LIVE_GRACE_PERIOD_IN_MILLIS).after(wind.getTimePoint()) ||
|
||||
(endOfRace != null && endOfRace.plus(TimingConstants.IS_LIVE_GRACE_PERIOD_IN_MILLIS).after(wind.getTimePoint())))) {
|
||||
getOrCreateWindTrack(windSource).add(wind);
|
||||
result = getOrCreateWindTrack(windSource).add(wind);
|
||||
updated(/* time point */null); // wind events shouldn't advance race time
|
||||
triggerManeuverCacheRecalculationForAllCompetitors();
|
||||
notifyListeners(wind, windSource);
|
||||
result = true;
|
||||
} else {
|
||||
result = false;
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user