Maximum activity duration (storage space)

isazi

@thanasis you can sync activities with SA also if you don’t have internet connection.

thanasis

@isazi said in Maximum activity duration (storage space):

@thanasis you can sync activities with SA also if you don’t have internet connection.

Thanks @isazi , shall I assume that for the rest is as I mention?
so saving them (stop it ,save, synchronise) on a daily basis?

but on the merging of the parts?

freeheeler

@thanasis
I wonder why you want to have one activity if a multi day activity is done on different days with dinner and sleep in between? Don’t get me wrong, everyone has his/her own process and philosophy.
personally I would record day by day and if you want to look at your entire track, load all relevant activities into quantified-self.io and merge them.

Likarnik

@freeheeler there is a difference between for example Moab 240 and Marathon Des Sables. Moab 240 - one activity, Marathon Des Sables - six activities Btw, I’m far for competing in those races, just an example how I would like to have them stored

DMytro

@freeheeler I bet 200k in one go looks more impressive in SA than 4x50km haha.
But apart from that I think at such severe level of tiredness one may as well forget to finish/start an activity, so it’s more for a peace of mind I suppose.

isazi

@thanasis you would need to export the FIT files and stitch them together somewhere else, then import them back in SA.

Likarnik

@isazi and lose data by design
https://forum.suunto.com/topic/8404/original-suunto-fit-file-loses-too-many-stuff/4?_=1672998761998

freeheeler

@Likarnik
I am aware for this topic for races. But when I go on a skitour for multiple days and it is not a race, personally I don’t see a reason why multiple days should be one activity… maybe what @DMytro says
I know people who record the commute there and back in one activity… but in between there is 10h of being at work again: philosophy question

isazi

@freeheeler I am with you here. If I wanted to do a race of this kind, I would like to have a single activity. But my usual multi-day activity is climbing/hiking/mountaineering and I consider it a collection of daily activities, because I eat and sleep in between

Likarnik

@isazi @freeheeler I agree with you on multi day trips, but as far as I understand, @MKPotts is talking about races

@freeheeler philosophy question? Maybe we should include ski touring/backcountry skiing/skimo in here

isazi

@Likarnik yes, and for that unfortunately we cannot go more than ~70 hours apparently. Future watches may be different in this regard.

freeheeler

@Likarnik
you’re right @MKPotts asked for that, but I was more focusing on the request from @thanasis , since the request from @MKPotts is not solved, but at least answered

… skitouring… well, priority number one is: we desperately need snow, everything else is priority number 2 or 3
I use skitouring for telemark skitours and snowboard tours (no splitboard) and I’m fine with that. The activity basically is the same: sweating heavily uphills and grinning from one ear to the other on the downhill

DMytro

@isazi should we start an s9ppp thread already? XD

MKPotts

@Likarnik said in Maximum activity duration (storage space):

@isazi @freeheeler I agree with you on multi day trips, but as far as I understand, @MKPotts is talking about races

Yes, I was talking only about races. If doing a multiday trip (e.g. backpacking, I can’t ski!), I’d want it as separate activities. So agree with all the comments.
Also agree there are workarounds for long races - saving, syncing, merging later etc - but they have downsides (especially when you’re sleep-deprived!).
I know very little about the design limitations and trade-offs with watches, file management etc, so would be interested to know why activity storage is still even a consideration on modern devices. Is the fit file size in SA indicative of storage needed on the device? If so, then looking at file sizes for some of my 12-24hr races, suggests a 120hr activity would only be about 10MB. Is that more challenging than it sounds?

isazi

@MKPotts it is challenging only in the way that current Suunto watches have very little storage available, so nothing can be done with current models I’m afraid.

Brad_Olwin

@MKPotts I used an Epix 2 for 8 months and had similar experiences but nothing as long as you have done. I sold my Epix 2.

Brad_Olwin

@MKPotts So a couple questions. I have had the same problems in the past. I ran Fat Dog in Canada (200k) when Ambit 3 Peak was the current watch and wanted data in 1s mode. It took 40h to finish. I split my run into 2 events. My main repository for data is TrainingPeaks so combining the files in TP worked fine. I just left these as two files in MC, now SA.

Do you use SA as your primary analysis tool?
If not I agree with @herlas on this and we should be able to import large fit files.

I am going to raise this with Suunto as I am considering doing a 320k or longer next year. Personally, the watch should not be limited, I could accept reduced HR sampling or no HR for a 120 race to record as one file. Current watches should handle that. I suspect it boils down to costs……

DMytro

@Brad_Olwin I also wonder if such things affect battery life, since during the prolonged recording the file is ‘open i.e. constantly being fed the data’, so I suppose keeping larger files ‘active’ puts more strain on memory and processing power thus also affecting the battery.
This is just my guess as sb who never had a CS class and also I can’t guess how the energy consumption scales with increasing activity duration (hard to imagine the effect being exponential tho).

MKPotts

@Brad_Olwin
When I’m doing more structured training I use TP (premium) as my primary tool for planning and analysis. At other times I’ll mainly use SA. I didn’t know I could combine fit files within TP, that’s helpful to know, thank you. I also send data to Strava but only for connecting with friends, I don’t find their analysis tools any use.
With splitting races into multiple files, the main reason I want to avoid it is because it’s something else to do/forget/mess up at checkpoints, when there’s already so many things to try to do efficiently (especially in winter).
I had/have an A3P but never went longer than 13hrs with it, so didn’t run into memory issues. But I know you could change the recording interval. Maybe reintroducing the option to do that in the S9 watches - e.g. still acquiring data every second for navigation but only writing to the file every 5sec - would be a way to extend run time without hardware changes.
Regardless, the S9 watches are still the best fit for my needs/priorities, so I’ll stick with them unless/until a better option comes along.

Brad_Olwin

@MKPotts You cannot combine within TP but after combining no data is lost upon TP import.