mirror of
https://github.com/meshtastic/firmware.git
synced 2026-01-17 15:27:29 +00:00
beb268ff25
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides.
I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop.
I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say.
This reverts commit 0d11331d18.
29 lines
1.2 KiB
C++
29 lines
1.2 KiB
C++
#pragma once
|
|
|
|
#include "configuration.h"
|
|
|
|
// Encapsulates code responsible for the timing of GPS updates
|
|
class GPSUpdateScheduling
|
|
{
|
|
public:
|
|
// Marks the time of these events, for calculation use
|
|
void informSearching();
|
|
void informGotLock(); // Predicted lock-time is recalculated here
|
|
|
|
void reset(); // Reset the prediction - after GPS::disable() / GPS::enable()
|
|
bool isUpdateDue(); // Is it time to begin searching for a GPS position?
|
|
bool searchedTooLong(); // Have we been searching for too long?
|
|
|
|
uint32_t msUntilNextSearch(); // How long until we need to begin searching for a GPS? Info provided to GPS hardware for sleep
|
|
uint32_t elapsedSearchMs(); // How long have we been searching so far?
|
|
uint32_t predictedSearchDurationMs(); // How long do we expect to spend searching for a lock?
|
|
|
|
private:
|
|
void updateLockTimePrediction(); // Called from informGotLock
|
|
uint32_t searchStartedMs = 0;
|
|
uint32_t searchEndedMs = 0;
|
|
uint32_t searchCount = 0;
|
|
uint32_t predictedMsToGetLock = 0;
|
|
|
|
const float weighting = 0.2; // Controls exponential smoothing of lock-times prediction. 20% weighting of "latest lock-time".
|
|
}; |