Page 1 of 1
Ergdata concept logs correction
Posted: May 10th, 2024, 5:08 pm
by Moogles
I've just completed a row.
4x8min 2min rest @1:58/500m or so.
When I finished the 4 intervals a got up and left without stopping session. When I came back it was at intervals.
I ended session then.
The erg logbook shows the session as an 8x4 session with only the 4 intervals shown.
But the total time, average stroke rate, pace seem to be using the longer data (including the 0 data intervals).
Same goes for session data on logs.concept2.
Any way to manually fix this?
Re: Ergdata concept logs correction
Posted: May 19th, 2024, 3:46 pm
by HornetMaX
I don't think you can fix this easily. You may be able to do that by downloading the per-stroke data, manually fix it and reupload it as new session (you'll probably lose the verification).
Side note: unless I'm wrong, ErgData doesn't allow you to define the number of intervals.
I suspect that this is to allow a variable number of intervals but I do find that decision very weird: I would much prefer an input data field where you can put the desired number of intervals (which is probably the most common use case) or "undefined".
Re: Ergdata concept logs correction
Posted: May 19th, 2024, 4:42 pm
by Sakly
HornetMaX wrote: ↑May 19th, 2024, 3:46 pm
I don't think you can fix this easily. You may be able to do that by downloading the per-stroke data, manually fix it and reupload it as new session (you'll probably lose the verification).
Side note: unless I'm wrong, ErgData doesn't allow you to define the number of intervals.
I suspect that this is to allow a variable number of intervals but I do find that decision very weird: I would much prefer an input data field where you can put the desired number of intervals (which is probably the most common use case) or "undefined".
As a workaround you could use variable intervals and program the number of (same) intervals you want to do. Ergdata will stop, when number is reached.
Re: Ergdata concept logs correction
Posted: May 19th, 2024, 5:20 pm
by HornetMaX
Sakly wrote: ↑May 19th, 2024, 4:42 pm
HornetMaX wrote: ↑May 19th, 2024, 3:46 pm
I don't think you can fix this easily. You may be able to do that by downloading the per-stroke data, manually fix it and reupload it as new session (you'll probably lose the verification).
Side note: unless I'm wrong, ErgData doesn't allow you to define the number of intervals.
I suspect that this is to allow a variable number of intervals but I do find that decision very weird: I would much prefer an input data field where you can put the desired number of intervals (which is probably the most common use case) or "undefined".
As a workaround you could use variable intervals and program the number of (same) intervals you want to do. Ergdata will stop, when number is reached.
Smart workaround indeed.
Re: Ergdata concept logs correction
Posted: May 21st, 2024, 6:21 pm
by Moogles
Thank you both. I don't need the specific data. Ill delete the bad session and upload a similar one.
This only happens by the way for constant intervals in units of time. Units of distance seem to be ok.
I'll use the variable in future alright. Nice way to do it, thanks
Re: Ergdata concept logs correction
Posted: May 22nd, 2024, 1:19 am
by jamesg
When I finished the 4 intervals I got up and left without stopping session. When I came back it was at intervals.
That's how Intervals works in PM. Stop it when you want it to, otherwise it continues to 50. If you use a Rerow, it stops at the same number.
This can be handy, since you can let it run to max 50 intervals, save, recall and use whenever you like to any smaller number, without reprogramming that type of interval.