vo2_max() and workload column option

[Scott-S-Hannah]

Hi Felipe,

It's me again... haha.

I was just trialing the new vo2_max() function and was wondering whether you would consider adding an option to use a pre-defined workload column? The work_rate_magic option is fantastic but I already have workrate column produced by the gas analyser.

p.s. your GitHub links on your packagedown site are leading to a 404 page. I think there's an M missing from your GitHub account name 🤦‍♂️

Thanks,
Scott

[fmmattioni]

Hey Scott!

Thanks a lot for trying it out! Have you tried setting the work_rate_column argument in the read_data() function? Then you can set work_rate_magic to FALSE and that should do the trick. Let me know if it doesn't work.

I am going to update pkgdown, I hadn't noticed that before! Thank you!

[Scott-S-Hannah]

Hey Felipe,

Thanks for the quick reply. Unfortunately, setting the work_rate_column in the read_data() function doesn't seem to change how the vo2_max() call works.

I suppose if the read_data() function renamed my Power column when importing to "work_rate", then the vo2_max() function would produce peak power estimate. Another option might be to let users define their work_rate column like you have done with heart rate and rer etc.

perform_max <- function(.data,
                        vo2_column = "VO2",
                        vo2_relative_column = NULL,
                        heart_rate_column = NULL,
                        rer_column = NULL,
                        work_rate_column = NULL,
                        average_method = c("bin", "rolling"),
                        average_length = 30,
                        plot = TRUE,
                        verbose = TRUE) {

  if (!is.null(work_rate_column))
    if (! work_rate_column %in% colnames(.data))
      stop(glue::glue("It looks like the column {work_rate_column} does not exist."),
           call. = FALSE)
  
  out <- dplyr::tibble(POpeak = ifelse(
    is.null(work_rate_column),
    as.integer(max(data_normalized[["work_rate"]])),
    as.interger(max(data_normalized[[work_rate_column]]))
  ))
  
}

Might this work?

Thanks again, Felipe. You'll be pleased to know whippr is getting some good use in my thesis 😁.

[fmmattioni]

Oh, I see what the problem is.. I initially had an argument to specify the work rate column in perfom_max(), but ended up removing it to force it to be defined in read_data(). What I forgot to do is to rename the column you pass into read_data() as work_rate. I will push a fix.

It is great to hear that you are using it in your thesis!! If you have any suggestions, feel free to open a discussion in the Discussion tab! I am always looking for ways to improve the package.

[fmmattioni]

Hey Scott, I have just created a PR: #7

Could you give it a try?

You can install it with: remotes::install_github("fmmattioni/whippr#7")

[Scott-S-Hannah]

Works a treat, Felipe. Thanks 🙌

[fmmattioni]

Thanks a lot for reporting it, Scott!