weight based peak performances not calculated if they precede first athlete weight entry

[MrSpock77]

I have imported data for several athletes from another computer. All activities appear to have been imported correctly as far as I can tell, but I have noticed that peak performances are not calculated for activities created before April 2022. Peak performances for the full time range may look like this on the source device:

The older peaks from 2018 are missing on the destination computer:

When looking at the actual activities on the destination computer, the chilis are still visible:

The issue seems to be related to the first registered date in the user’s weight history. I became a Sauce user in April 2022, so for many of the athletes I follow, their weight was first recorded by Sauce at that time:

On the source computer, peak performances were calculated for activities before that date, even though the weight was not known or manually registered by me. However, the import algorithm appears to depend on a weight recording in order to calculate peak performances. I suggest that Sauce use the oldest known weight value in this case as well.

[mayfield]

Hi,

The two things that would cause this are, data streams being unavailable (if the sync is in progress or never finished before exporting/importing). And if the local peaks calculations didn't complete or got corrupted/stale somehow. It's rare but can happen. I'd first try clicking the yellow "reload" icon in the sync panel. This will force a recompute of all the local peaks data for all the streams it has.

If that doesn't bring up the expected peaks values, I'd check that the streams are actually there by forcing a full activity scan. Disable the account (uncheck the enabled box in the sync panel) then Re-enable it. This will rescan all the activities and download any streams it doesn't already have.

[MrSpock77]

Hi, Justin.

I have made sure that there was no synchronization in progress during export/import. The sync log had “Sync completed” as the last line.

I do not think random corruption is the cause. This issue is present for all 22 athletes I have imported. The imported *.sbinz files are 3.5 GB in total. Most of the athletes had a long history of activities before I started using Sauce in 2022.

I have followed your recommendation by performing both a recomputation (yellow reload icon) and a full activity scan (disable/enable), but there was no difference. I can confirm that the “Activity Sync” summary widget shows the exact same number of activities on both the source and destination. The Training Load chart shows data for the full time period on the destination, while the Peak Performances chart has a clear break at the time corresponding to the first registered weight.

I believe you should be able to reproduce this on your end by editing the weight history of any athlete and then export/import.

Thank you,

Johan

[mayfield]

Maybe I misunderstood, is this just for w/kg peaks and is coupled with the start date of the first weight entry? As in, if you set the first weight entry to 1970, does everything work as expected?

[MrSpock77]

Yes, that is true. Peak Power was correct; only Peak Power (W/kg) was missing. I added a weight entry dated 1970-01-02, and that did the trick. I will do the same for the remaining athletes. I conclude that Sauce is able to calculate W/kg for older activities during a normal setup, but that this data is lost after import without this workaround.

[mayfield]

Okay thanks for the info and report. I'll update the title to reflect.