Does this allow to merge Tymewear ventilation data into an existing activity in I.icu? I.e. through the upload of the merged streams.csv?
What does not work for you?
AFAICT the Tymewear dashboard merge fundamentally works. However, it does ignore many streams, starting from L/R PM balance… Is that what you are referring to?
In my case, Tymeware data is included in the FIT file from Edge, but not Calibre data.
I assumed he is using a TymeWear app that produces a FIT file and wants to merge it with the one from his watch—probably a watch that doesn’t receive ventilation data from Tymeware.
With a small modification, my script would allow the merge of two i.icu streams.csv files: one generated from the watch’s FIT file and the other from the TymeWear app’s FIT file. The result would be a merged file ready for upload to i.icu, keeping all icu.streams and custom streams. Prerequisite: The files must share a common data stream (such as heart rate or power) in addition to the timestamp for the merge to be possible."
I’ve actually got the fit file merging to work well on Tymewear now if I only pair the breathing monitor to the app, and all other data from the external device / platform. Previously I was getting data gaps or no data at all from the secondary device/platform.
1 Like
I’m still having a nightmare with this. The Tymewear merging is a bit of a mess - for example for running activities pace is messed up, I now have a 5km PB of under 10 minutes.
Is there a format that you can upload to intervals.icu that isn’t FIT, which can still container all of the data streams? CSV?
If so that might be easier as an output format than trying to encode everything back to FIT format.
~
Did you get anywhere with this? Note they wouldn’t have a common field other than timestamp.
Only possible if both clock timestamps are synchronized, precise and accurate.
Can you share by PM the two files you want to merge, i can give node.js a try.
Unfortunately, I haven’t received a reply to my private message regarding the two FIT files.
Sorry I missed your message. Files sent now.
@pepe have also DM’d 2 examples files.
I completed the intervals–intervals streams.CSV merger. The merger output is ready for a final check and pruning before upload. Be sure to have the placeholder “Custom Streams” before upload. This is the simplest process, using David’s trusted FIT-file parsing. There is no need to recreate the entire FIT-file decode→ parse → JSON → merge → re-encode process. Sent you the files.
The primary and secondary data sources (e.g., the Tymeware app) have inconsistent start and end times. The secondary source data quality is very poor, with numerous gaps. Please investigate the root cause of these gaps. Perhaps phone power or background app settings.
However, the script is able to align and synchronize the data. The process uses only the recorded data and performs no interpolation
2 Likes
Would it be an option to put this on GitHub/similar?
When I have time, I will enhance it
1 Like
Thank you.
I’ve built a karoo extension for tymewear data.
1 Like