Calculating heat load in RealtimeData via static variables?

[Jonathan Savage]

I am adding a calculation of heat load, the cumulative impact of heat stress, to GC. I want to display this value in a DialWindow, just like real time data. 

My current implementation uses static variables, accumulating the load based on the passage of time. It's a bit ugly, but I couldn't see a way that's less ugly and more complex. 

(Note the formula for heat load is different to the CORE calculation and only a rough approximation as CORE's heat load is propitiatory.)

define HEATLOAD_OFFSET 0.9596

#define HEATLOAD_MULT 35.92

#define HEATLOAD_EXP 1.324

//heat load persists across sessions

double RealtimeData::heatLoad = 0;

qint64 RealtimeData::heatLoadMSec = 0;

//Skin temp passed but not used elsewhere

void RealtimeData::setCoreTemp(double core, double skin, double heatStrain) {

    this->coreTemp = core;

    this->skinTemp = skin;

    //heatStrain = 3.5;

    this->heatStrain = heatStrain;

    //(HSI-AOC_Off)^AOC_EXP*TIME/AOC_Mult

    QDateTime currentTime = QDateTime::currentDateTimeUtc();

    qint64 msecEpoc = currentTime.toMSecsSinceEpoch();

    if(this->heatLoadMSec != 0)

    {

        qint64 deltaMSec = msecEpoc - this->heatLoadMSec;

        double deltamin = deltaMSec / (1000.0 * 60.0); //msec to minutes

        double newLoad = pow(heatStrain-HEATLOAD_OFFSET, HEATLOAD_EXP) * deltamin / HEATLOAD_MULT;

        if(newLoad > 0)

            this->heatLoad += newLoad;

        if(this->heatLoad >= 10.0)

            this->heatLoad = 10.0;

    }

    this->heatLoadMSec = msecEpoc;

}

(For my personal usage, I can just restart GC each day to reset the heat load, but I'll probably add logic to check the local date and reset each day.) 

Jonathan 

[Ale Martinez]

It seems a bad idea, previous sessions can even belong to a different athlete.

[Jonathan Savage]

Is there a better place to calculate heat load? The simple alternative would be to reset when the timer starts. 

[Ale Martinez]

El martes, 8 de julio de 2025 a la(s) 4:06:01 a.m. UTC-3, Jonathan Savage escribió:

Is there a better place to calculate heat load? The simple alternative would be to reset when the timer starts. 

Derived real time metrics are computed in DialWindow itself in current code, there you can find several examples. 

[Jonathan Savage]

Thanks - that's a much better solution.