.. datafilter uses a context that was used to create it
which is fine until it is used in user metrics which
are global and shared across multiple contexts.
.. so now when evaluating a ride item we use the context
for the rideitem being evaluated not the context of
the data filter performing the evaluation
.. next couple of commits will need to look at the way
we use RideItem and RideFile when computing both
Ride and Interval metrics.
.. if you select e.g. the TriScore PMC in the Library chart
in Trends, the high/low curves get left behind because they
use the same name (Best_xxx).
.. ironically this was already worked around by creating a name
that included the symbol, but this was not used when adding to
the curve mapping.
- Code cleanup, removing deprecated code and refactoring
- Metrics translation is now done in a method for LTMSettings
- User defined metric name (uname) is translated if it matches english name
- User defined units (uunit) is only translated if it matches saved units
.. using the Holt-Winters double exponential smoothing to avoid
low on rising and high on falling data series.
.. works best with relatively noisy and contiguous data
.. no need to pass across weight since we maintain two
models; absolute and per kg already.
NOTE: this has highlighted a bug in the code related to
estimated w/kg bests for 2 and 3 parameter models
that will be fixed shortly.
.. to augment the existing vo2max estimate using peak 5m
data in a ridefile, this now adds it as an estimate from
the PD model estimate for 5m peak power.
This commit is adding a new class QwtIndPlotMarker that will enable us
to indend Labels. The usage is pretty much the same,
please look at the changes in LTMPlot.cpp to see what will
change for using the new class.
So far the functionality is implemented for horizontally written labels only.
This solves the issue of all Labels (e.g. Seasons and events in LTMPlot case)
being on one line and thus being unreadable.
Signed-off-by: Simon Egli (Silzo) <smn.egli@gmail.com>
... shift plot if start date is earlier than any Power Estimates exist
... enhance grouping (calculation of averages for month/years/all
grouping)
... adjust estimates calculation
... to calculate non-overlapping weeks data
... to not create any "infinite" data for weeks before the first Power
based actitivity exists
.. tile mode highlights on mouse over for a more
fluid feel, and better feedback
.. can customise the trend view charts background
.. fixed a SEGV on apply preset in chart setup
.. this is part of a set of updates to update the
standard setup to be more complete so the user
can pretty much run off a standard config.
.. LTM stress curves had the same symbol name and
so some were not deleted when the date range changed
leaving curves on the plot
.. we now set the best symbol for stress curves so we
have a unique name for each curve
.. does all labels etc and integrates in with the rest
of the LTM chart and CurveColors classes.
.. underMouse() seems weird when legend is updated, might need
to find a better way to work out if/which legend was clicked.
.. introduce concept of configChanged(what) to
pass details of what config has been changed
.. fixed zones changes to re-read after write
to correct the save twice to get changes to
zones bug.
.. next parts need to spot changes (part 2) and
then action appropriately (part 3)
.. removes across the code base
.. need to fixup RideFileCache and Lucene refresh
within the RideItem/RideCache framework, they will
NOT be refreshed at present
.. need to look at how charts get refreshed on data
changes now RideItem provides a more granular
mechanism (look for XXXREFRESH in code)
.. New Intervals code will definitely NOT compile
and needs to be redesigned/reimplemented to fit
in with the ride cache
