BoatCoach mixed file reports strange summary

Sander Roosendaal reporter

marked as minor

2016-12-01T21:04:29+00:00

Sander Roosendaal reporter

Attached are two files, the original BC file for a 3x10'x5'r workout and a modified file for the same workout. The modified file has an "m" appended to the file name. Notice in the original file, in the workTime column at row 707, workTime ceases to tick up while restTime in the adjacent column continues to unwind. All I did was highlight the last two good workTime values and drag them down until I get the value (in this case) of 15:00 which should occur in the row where restTime goes to zero (+/-). Did the same thing for each of the three work pieces.

2016-12-06T21:09:33+00:00

Sander Roosendaal reporter

attached boatcoach_2016-12-06__08-52-42.csv
attached boatcoach_2016-12-06__08-52-42m.csv

Mike's files

2016-12-06T21:11:30+00:00

Sander Roosendaal reporter

Mike: BoatCoach again. The two files I sent you in the message below were for a PM5 interval workout that the CSV parser and/or the interval editor were not handling very well. You had asked what modification I had made to the CSV file to get it to (mostly) work.

Back then, workouts set up as single time on the PM5 were working OK but they are having some problems now also. After editing intervals, the average pace and power values in the workout summary on the edit page are way out of whack. Again I found a way to edit the CSV file which has (mostly) fixed the problem and I thought I'd add it to the above report.

Two files are attached. The one with the "m" appending the file name is the modified file. The workout was 1:15:00 single time with 5' splits which I rowed as 3x20'/5'. The first rest period begins at 20:00' workTime. Looking at the lastsplitDistance column in the original file, notice that the CSV dutifully reports the last split distance as 1183 (row 1190). The CSV should continue to report 1183 until the next 5' split begins but, at 21:07 mark, when I stopped rowing, the CSV incorrectly assumes that the 5' split is over and begins reporting 128 in the lastsplitDistance column. My fix was to copy 1183 down to the end of that 5' (rest) split. I did that for the second "rest" split too. In the last rest split I didn't stop rowing so the CSV file correctly reported the lastsplitDistance and no correction was necessary. The modified file worked OK when uploaded giving correct pace and power values.

Anyway I offer this in the hope that it will help to solve the issues with BoatCoach CSV files whenever you get to them in the grand scheme of things. Amongst our group it is just me using BC but, if they really are "the #1 app for rowing...", we can expect more customers using BC. For me, until I can get Painsled to work on this bloody PM5v2, BC is the next best thing.