The full featured file just got updated to version 1.5.
Changes:
1.5 ----- Accepts blank values for RHR and/or HRV while keeping correct averages. If too much data is missing, a watermark is indicated over the chart. That’s if more then 2 days out of the last 7 are missing or more then 9 out of the last 28. You will still get results but be notified by the watermark.
Just headup. I downloaded the file today , follow the instructions and looks good so far.
O little bit confunsing , abour workbook and updated workbook, which one i need to do the changes , but i think i do the right way.
Thanks so much
PS. if was possible how i can import just the sheet of IiThlete HRV , to another workbook and make work when “Refresh All” , without need to import others sheets ( i already have a bulk worbook, with a Dashboard , and graphs with my HRV , Tonnage , Volume , Food etc… )
Stumbled across and edge case today (and running the MacOS version, which I haven’t updated in a while so it may be fixed or irrelevant to others), which may be less relevant in the Northern Hemisphere winter/off-season.
The activities for 1Jan23, were being processed as 2023-01, as the logic in they YEAR() and ISOWEEK() functions are based on different things, found a good explanation about ISOWEEK()s first Thursday of the year start, and how to code for year here excel - week number and year combination - Stack Overflow
And the resulting code if anyone else needs/want it is swapping Activities “A”
is swapping
IF(B2="","",IF(ISOWEEKNUM(C2)<10,YEAR(C2)&"-0"&ISOWEEKNUM(C2),YEAR(C2)&"-"&ISOWEEKNUM(C2)))
with
=IF(B2="","",IF(ISOWEEKNUM(C2)<10,YEAR(C2+3-WEEKDAY(C2,3))&"-0"&ISOWEEKNUM(C2),YEAR(C2+3-WEEKDAY(C2,3))&"-"&ISOWEEKNUM(C2)))
2023-04
I really love the way WeekNum is used in this simplifies date/week handling so much, but the edge case caught me out.
Next fun, this year is one of the rarities that has 53 (iso)weeks…
Thanks for that. The weeknum function is my contribution to some of the work done on the various Excel files. My workaround (on my version) uses the IF function; when the week number is greater than 52, the new year and week 01 is then used.
As the HRV data is now managed using the app through MATLAB, the Excel file support has all but ended.
I still use the Excel file, but as mine works, I haven’t been look to improve on it.
Sorry, I typo’d my original.
The IF idea failed for me because 1Jan2023, showed up as 2023-52 originally, it’s in the second half of the 52nd week, but of 2022 calendar, so since week and year come from different maths, edge cases are tricky…
Just putting it here for reference, in case anyone else comes across similar.
The formula I use, is as follows:
=IF(G25="","",IF(YEAR(A25)<>YEAR(A26),YEAR(A26)&"-"&ISOWEEKNUM(activities[@[start_date_local]]),IFERROR(IF(activities[@[start_date_local]]="","",IF(C25<10,YEAR(activities[@[start_date_local]])&"-0"&C25,YEAR(activities[@[start_date_local]])&"-"&C25)),"")))
I need to give a public shout-out to @William_Barnes for the work he has put into the spreadsheet
“[Next Activity_icu v1 (shared)”. I’ve been using it for a month or so and going by its recommendations for “Next Activity” and I’ve been able to set many personal record wattage versus time numbers. The Next Activity workouts give me a choice on what I want to do the next day e.g.: FTP TTE, or CP TTE, or VO2Max, or just Z2.
Since I don’t think it’s earlier in this thread, here’s a stable link to the folder where the latest version (v2.3 currently) can be copied from for anyone else interested.
Copied the file in the link from (Training guidance tools using the API - #22 by Gerald) in google sheets, entered the info, and ran the import data script, but getting an error message saying " Exception: Request failed for https://intervals.icu returned code 403. Truncated server response: {“status”:403,“error”:“Access denied”}"
Hi all,
I’ve been using Excel version of Intervals_API_Tools_Office365_v1.6 but the data stopped refreshing at the end of March 2024. Excel throws [Expression error] The column “rampRate” of the table wasn’t found. Has anybody had the same issue? How can it be fixed?
thanks for this! I did search for the issue on the forum but didn’t find the thread you referred to. I can confirm that simply removing "Columns=38, " from the source query step in v1.6 solves the issue.
I do not get error messages when I open the file. I get this popup about security two times:
I check the box two times and save.
Then I get this error two times:
I hit OK two times
I enter my Athlete ID (no copy paste, real typing
I go to data and hit refresh, this error pops up:
No web access dialogue is showing up.
UPDATE:
OK f**k me I did it, dont mind my language . Its a simple and stupid mistake. The user name has to be “API_KEY” and NOT the api-key itself . That did the trick… Thx for replying and making me look through everything a second time
I started planning an ATP this weekend for my prep / road to LEL 2025. Everything works neatly, at least the planning ;). I found a tiny thing: the calendar weeks continue counting upwards over new years eve, instead of starting by 1 or 2 in the new year. The formula is “=Y9+1”. It should instead use the month, or the date as counting reference and not the previous number, no?
Depending on the system used, and the start day for the week (Sunday or Monday) the week number will change. I use ISOWEEKNUM instead of weeknum, then having to use 0 or 1 in the formula.
You could use the formula year and isoweeknum to ensure that you’re using the correct weeks. Here is an example of the weeks only (incl. allowing for double values in each week):