Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement a tidy eval version of sliding! Much more convenient, since we can do something like this:
instead of this:
Also, I refactored
pct_change()
andestimate_deriv()
were refactored so that they just operate on vectors, rather than onepi_df
objects, and they can be used insideepi_slide()
fluidly. This all closes #18.Separately, I also decided to go with the following naming scheme: any function which operates on an
epi_df
object starts withepi
. This followed a suggestion of @earowang. So we now have:epi_slide()
epi_cor()
epi_detect_outlr()
Working in R studio, a user can therefore type
epi_
, then tab, and they will readily see what functions the package offers to operate onepi_df
objects.Finally, I updated the landing page (
index.md
) to give an overview of what the package offers.