Data Field
Athlevo Race Pro
개발자 AthlevoRacePro · v0.51
평점
5.0
리뷰
1
다운로드
1,000
가격
무료
설명
One screen, six values, three sizes - so you can read it at race pace: - NOW and PLAN - your current segment pace next to the pace the plan calls for - In the centre, in the largest font - your projected finish time - Every few seconds the projection swaps for VS TARGET, the gap to your goal time: green when you are on track, red when you are not - LEFT and REQUIRED - how many kilometres to the finish, and the pace you need to hold over them to make your target - Heart rate at the bottom Distance to the finish comes from a loaded course, not from an integrated GPS track. When you run without a course loaded, the field says so plainly at the top of the screen, because the projection is then a bit less precise. The field also accounts for the fact that nobody runs the certified line. Passing other runners and taking wide corners adds a few hundred metres over a half marathon. With the remaining distance and the projected finish in front of you, you know whether the goal is still within reach. After the race your activity carries one more value - heart-rate drift (cardiac decoupling). It tells you how the ratio of pace to heart rate changed between the first and second part of the run. - below 1% - the second half was clearly stronger; there was more in the tank - 1-5% - the race was paced well, on a solid aerobic base - 5-10% - something did not go to plan, but nothing alarming; the aerobic base could use some work - over 10% - the aerobic base needs serious work before your next race GETTING STARTED 1. Add the field to a data screen in your running profile. 2. In Garmin Connect open the app settings and fill in three fields: official distance, target time and plan. 3. Paste the plan the day before, not at the start line - and check that the watch has actually synced. SETTINGS Official distance - in metres, from the race rules. Marathon 42195, half marathon 21097, 10K 10000. Target time - written as HOURS:MINUTES:SECONDS, for example 1:25:00. Leave it empty to hide the gap to target. Plan - a list of segments as segment_end_in_metres:pace_in_seconds_per_km, with no spaces. The distance is measured from the start, so entries must increase; you never type a segment's beginning, because it is the previous one's end. Why the end of a segment and not its length? Because then the last number in the plan is the finish distance, and you can see at a glance whether the plan ends where the race does. It also helps when you write a plan by hand: "10K at 5:25, the rest at 5:18" is simply 10000:325,42195:318 - both numbers are ones you already know, with nothing to subtract. Course file length - usually not needed, the watch detects it. GPS correction - only used without a course loaded. If your watch reads 10.1 km after 10 km, enter -1.0. Light background - black text on white, for transflective screens in full sun. EXAMPLE: HALF MARATHON IN 1:25:00 Official distance: 21097 Target time: 1:25:00 Plan: 1000:246,2000:246,3000:245,4000:245,5000:245,6000:243,7000:243,8000:243,9000:242,10000:242,11000:242,12000:241,13000:241,14000:240,15000:240,16000:240,17000:239,18000:239,19000:239,20000:238,21000:238,21097:238 That is a negative split: first kilometre at 4:06, last at 3:58, averaging 4:02/km. The total lands exactly on 1:25:00. Prefer something simpler? Even pace for the whole distance is a single entry: 21097:242
리뷰
리뷰 기사가 곧 게시됩니다.