I think I might have found the cause of the loss of my data. I seemed to lose all data once I fixed gaps in recording (in batch) on files that had a Duration metric override in them. Up until 2015 I used to override the "duration" of my activities with "time moving".
Once the gaps are fixed, you end up with an activity that has more data points than there are seconds in the duration of the activity. Could there be an issue where saving this editted activity is not possible in the latest development build?
In the files I uploaded a few posts ago, you can see the duration override in the original file and it disappears in the editted file.
-----
This is exactly what I did over the last few days:
1. I started with a bunch of activities , where some of them had gaps in recording that I wanted to remove
- from 2013 until May 2015 most of them contain GPS data and heartrate data, some are just metrics (distance, duration, ...)
- from May 2015 most of the activities contain power data as well.
Metric overrides were done previously:
- Added TSS and BikeScore for non power based activities
- I used to override Duration (workout_time in the JSON) as well before May 2015.
It seems I had 2 separate issues:
- The added comma when there were 2 metric overrides (i.e. TSS and BikeScore) (
Issue 1)
- A bigger issue where I lost all data once there also was an override of workout_time (
Issue 2)
2. As doing this per activity was very time-consuming, I wanted to resave all activities using the "set" function and apply the build-in "fix gaps in recording" processor when saving an activity.
When writing this, I realise I should have used the postprocess(x,y) function. Could this be a problem as well?
3. I added an integer data field called Force Save
4. Then I used the set function as a filter to change all activities: set(Force_Save,1,Date>"2017/01/01"....&&(Sport="Bike" or Sport="Run")).
5. I started doing this last Saturday for the period where I have power data (May 2015 untill today). There were about 80 bike activities that didn't contain power data. All of these 80 activities had 2 metric overrides (TSS and BikeScore)
- All files with power data loaded fine (if I remember correctly) and the gaps in recording were removed.
- For the non-power containing files (with metric overrides), there were a few with an obsolete comma in the JSON file. About 50 of the 80 non-power containing files got corrupted this way. After removing this comma manually, all data loaded fine.
6. Today I did the same for all other activities. All of them had 3 metric overrides (TSS, BikeScore and Duration). After applying the set function and saving the files, I lost all data on (I think) all of the activities where gaps in recording was fixed.
Today I went back to the previous build of August and followed the same procedure on a backup of my activities. All files saved correctly and gaps in recording were removed when present.
Kind regards,
Nigel