I have 2 files for an activity.
File 1 (Zwift fit) the chest strap HR data is zero from the start until ~50% of the way through the activity, this file also contains "GPS" and power data.
File 2 has a start time a little later than file 1 and has wrist strap HR data only past the end time of File 1.
When I load the files the HR data in file 1 is not seen as a stream in the page where you control the combination of the files BUT the HR data is shown if I use the EDIT POINTS button and I can edit the data. The HR data is zero until the real data starts ~50% of the way through the file.
I want to combine the files using the HR data from File 2 up to the time where HR data is available in File 1, I thought I'd be able to do this by cutting up the files but I can't find a way to export the 2nd half of file 1 with its HR data intact, I need this to be able to combine with a 1st 50% combined file (which I'm sure I can make) .
any tricks I need to use ?
Thanks
Mike
combine files where stream data is zero at start of one file
Re: combine files where stream data is zero at start of one file
ugly workaround ... export file 1 to TCX. Use notepad++ to search replace zero value HR data with 10bpm data. Then when importing this doctored file 1 into gotoes tool the HR stream is seen and i can cut up the 2 files and recombine as i want. Many steps but gets the job done.
Mike
Mike
Re: combine files where stream data is zero at start of one file
Mike -
Thanks for the comment and for the work around. For future users, I'm going to explain a bit how the tool works so they can have an easier work-around in this situation.
The tool only reads the first 1500 points to determine if a value is present. So, if all of the first 1500 heart rate values are zero, then the tool decides that the user doesn't have any heart rate data. In general, I think it is safe to assume that this is true. The reason I limit this is to speed up the tool.. but since I wrote that code, I upgraded to a more expensive and faster server, so MAYBE we ca get rid of that limitation.
Anyway, to get the heart rate checkbox (or any other field for that matter), you simply need to give the first field an appropriate value. So rather than do a find and replace, you could have just edited the first field to be a heart rate of 60, and then been done. This applies for power, cadence, etc.
Once you do that, you should not have to do the splicing. The tool should automatically do that for you. The tool knows that it is impossible for a human to have a heart rate less than 20, so as it iterates through each point, it discards any values less than 20. Instead, it substitutes the "last known good value". Assuming the values for your two devices matched, this would make for a nice clean-and-easy fix - without having to dice and splice.
Thanks for the comment and for the work around. For future users, I'm going to explain a bit how the tool works so they can have an easier work-around in this situation.
The tool only reads the first 1500 points to determine if a value is present. So, if all of the first 1500 heart rate values are zero, then the tool decides that the user doesn't have any heart rate data. In general, I think it is safe to assume that this is true. The reason I limit this is to speed up the tool.. but since I wrote that code, I upgraded to a more expensive and faster server, so MAYBE we ca get rid of that limitation.
Anyway, to get the heart rate checkbox (or any other field for that matter), you simply need to give the first field an appropriate value. So rather than do a find and replace, you could have just edited the first field to be a heart rate of 60, and then been done. This applies for power, cadence, etc.
Once you do that, you should not have to do the splicing. The tool should automatically do that for you. The tool knows that it is impossible for a human to have a heart rate less than 20, so as it iterates through each point, it discards any values less than 20. Instead, it substitutes the "last known good value". Assuming the values for your two devices matched, this would make for a nice clean-and-easy fix - without having to dice and splice.