Problem with Pace units

[Jose A.]

Not sure why but, V3.8 changed the pace units for swimming and running averages from min/km to km/h to me. I read the FAQ and user guides, but they seems to be obsolete, there is no checkbox to check where faq and guide say it must be

How can I do to get pace for swimming and running to min/km and keep the km/h for cylind?

[Ale Martinez]

El domingo, 18 de enero de 2026 a la(s) 9:22:44 a.m. UTC-3, Jose A. escribió:

Not sure why but, V3.8 changed the pace units for swimming and running averages from min/km to km/h to me. I read the FAQ and user guides, but they seems to be obsolete, there is no checkbox to check where faq and guide say it must be

How can I do to get pace for swimming and running to min/km and keep the km/h for cylind?

You can select units in https://github.com/GoldenCheetah/GoldenCheetah/wiki/UG_Preferences_General 

[Jose A.]

Yes, I have those checkboxes selected, but still kms/h in Averages and Pace tab...

[Ale Martinez]

El domingo, 18 de enero de 2026 a la(s) 2:43:20 p.m. UTC-3, Jose A. escribió:

Yes, I have those checkboxes selected, but still kms/h in Averages and Pace tab...

You should try to be more specific about the issue you are facing, attach some screen shots, and the involved scripts if there ones to get help then…

[Ale Martinez]

El domingo, 18 de enero de 2026 a la(s) 3:06:26 p.m. UTC-3, Ale Martinez escribió:

El domingo, 18 de enero de 2026 a la(s) 2:43:20 p.m. UTC-3, Jose A. escribió:

Yes, I have those checkboxes selected, but still kms/h in Averages and Pace tab…

You should try to be more specific about the issue you are facing, attach some screen shots, and the involved scripts if there ones to get help then…

BTW, you are using a pre-release, which is fine and appreciated if you are willing to collaborate with debugging, there is a thread created for that purpose and it would be useful to know if the problem is specific to this version going back to the release one.

OTOH, if you are pissed off because you found something unexpected and demanding your problem be diagnosed and fixed without much collaboration, perhaps you should consider staying with the release version.

[Jose A.]

Did it. Thanks

[Ale Martinez]

El lunes, 19 de enero de 2026 a la(s) 11:53:34 a.m. UTC-3, Jose A. escribió:

Did it. Thanks

Ok, now I see the images and I can understand your issue is one of understanding how GoldenCheetah works in any version, not just this one.

I updated the wiki to try to explain this better, see https://github.com/GoldenCheetah/GoldenCheetah/wiki/FAQ-RUNNING-&-SWIMMING#how-can-i-choose-pace-units-for-running-and-swimming, https://github.com/GoldenCheetah/GoldenCheetah/wiki/FAQ-RUNNING-&-SWIMMING#how-can-i-see-pace-in-activity-charts and https://github.com/GoldenCheetah/GoldenCheetah/wiki/FAQ-RUNNING-&-SWIMMING#how-can-i-see-pace-and-distance-in-cv-charts

To use View > Reset Layout on each view can be a good idea to have the latest charts, unless you have customized them already.

[Jose A.]

THANKS it's working now. I use linux version, works fine too.  Reseting layout solved the issue. But I still have the problem with the timers... This are the timers values of a short run I did tonight to test if it was fixed too, uploaded directly from my sportwatch to Strava. I pressed start when started to run and stop it when I stopped running.  No pauses, the timers in Strava show the same values as my sportwatch.

And this are the values from Golden Cheetah, for the same activity, synchronized from Strava. Is the same duration , but the time recording and time the moving values are higher. I wasn't 4 minutes stopped and recording.. as Golden Cheetah isn't using duration, the average pace is higher too than my sportwatch and Strava 

[Ale Martinez]

It's weird, what happens if you import the original file directly to GC?

If you attach the file I could give this a look. 

[Jose A.]

I'll try later. This is the original file of the testing activity  downloaded from Strava.

[Ale Martinez]

El lunes, 19 de enero de 2026 a la(s) 5:49:46 p.m. UTC-3, Jose A. escribió:

THANKS it's working now. I use linux version, works fine too.  Reseting layout solved the issue. But I still have the problem with the timers... This are the timers values of a short run I did tonight to test if it was fixed too, uploaded directly from my sportwatch to Strava. I pressed start when started to run and stop it when I stopped running.  No pauses, the timers in Strava show the same values as my sportwatch.

And this are the values from Golden Cheetah, for the same activity, synchronized from Strava. Is the same duration , but the time recording and time the moving values are higher. I wasn't 4 minutes stopped and recording.. as Golden Cheetah isn't using duration, the average pace is higher too than my sportwatch and Strava 

The problem is duplicate records for the same timestamp which you can find in Data > Raw Data checking for Anomalies, I tried removing them using the following Python DP to fix this:

[Jose A.]

The activity was recorded with a Samsung Galaxy watch 4, using the built-in Sansung Health app, that upload the activities to Strava. Strava show the right moving time and duration, so I'm not sure if the duplicated records are because of the watch, Samung Health app, or Strava. I'll try to get the samsung health file , if exists, maybe the data be in an internal database and not in separated files, to compare... THANKS.

[Jose A.]

I tried to find the watch file, but seems to be hidden or in a database. So, I tried importing the file downloaded from Strava to GC, and this result in different timers than the synchronized activity. i asked Strava if the downloaded activity files are different from the synchronized data... and samsung for the original file, to see he differences

[Ale Martinez]

I gave a cursory look at the file you attached and it looks like a mess, it is not something I would like to deal with and I don’t plan to invest more time on this.

If your simplest workflow is to sync from Strava and you can remove duplicates with the Python processor I posted above or a similar one configured to run automatically at import, perhaps it could be a reasonable compromise.

[Jose A.]

Yes, it's nothing you should fix. I sync bike activities from Strava to GC, and there was no problem, data is the same. It's something wrong with GC sync from Strava for the activities recorded with Galaxy watch 4 and Samsung health that happen from May 2025. All the run activities recorded with Galaxy watch before this date and sync from Strava to GC have right timers. All the running activities from this date, have the same timer error. Rest of actvities (swimm, cycling ) recorded with ciclocomputers (different brands/models) or swimming watches are all fine. So I asked Samsung and Strava, maybe something changed on May 2025. THANK YOU for your time and support, you put me in the right direction of the issue.