Skip to content

Unify the epi_lag and epi_ahead functions #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dajmcdon opened this issue May 20, 2022 · 8 comments
Closed

Unify the epi_lag and epi_ahead functions #22

dajmcdon opened this issue May 20, 2022 · 8 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@dajmcdon
Copy link
Contributor

These are basically the same. Try to remove as much extraneous repetition as possible (say by dispatching to common underlying functions).

@dajmcdon dajmcdon added the good first issue Good for newcomers label May 20, 2022
@dajmcdon dajmcdon assigned dajmcdon and kenmawer and unassigned dajmcdon May 20, 2022
kenmawer referenced this issue in kenmawer/epipredict May 25, 2022
Issue #22 of uniting lag and ahead functions.
@kenmawer
Copy link
Contributor

Currently on my fork, I'm having an error here. I wilk continue work on it tomorrow.
example-recipe errors
e

@dajmcdon
Copy link
Contributor Author

I cannot reproduce your error locally. Can you describe how you are running the script? What R/package versions you're using?

@kenmawer
Copy link
Contributor

kenmawer commented May 26, 2022

I cannot reproduce your error locally. Can you describe how you are running the script? What R/package versions you're using?

On the example recipe, I run this with Ctrl+Shift+R (can also do Ctrl+A then Ctrl+R).

R version 4.1.1

tidyverse 1.3.1

covidcast 0.4.2

delphi.epidata 1.0.0

epiprocess 1.0.0

tidymodels 0.2.0

Note that I am getting the error with the code shown on my kenmawer/epipredict. I haven't tried it out with cmu-delphi/epipredict yet despite it differing from mine due to the inclusion of epi_shift.

It is saved in step_epi_lag (will be refactored to step_epi_shift once the code runs properly).

@dajmcdon
Copy link
Contributor Author

dajmcdon commented May 26, 2022

Have you loaded epipredict? (with devtools::load_all()) Note: the function epi_shift() is never called by that example script. (It is used in other, unrelated parts of the package.)

@kenmawer
Copy link
Contributor

Have you loaded epipredict? (with devtools::load_all()) Note: the function epi_shift() is never called by that example script. (It is used in other, unrelated parts of the package.)

Yes, I have. I think we should discuss this issue in detail as I followed all your steps but I still get this error, implying I may have done something else wrong.

@dajmcdon dajmcdon changed the title On epi_recipes branch: unify the epi_lag and epi_ahead functions Unify the epi_lag and epi_ahead functions May 30, 2022
@kenmawer
Copy link
Contributor

kenmawer commented Jun 1, 2022

I finished this. I am suggesting there be something done about insertion of negative values (which I utilized for tests), such as a warning.

kenmawer added a commit that referenced this issue Jun 7, 2022
@kenmawer
Copy link
Contributor

kenmawer commented Jun 18, 2022

Just a note: I still need to work on improving documentation for this, as the documentation is not quite right, which I didn't quite notice until recently.

@dajmcdon
Copy link
Contributor Author

Closed by #77

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants