Skip to content

compactify changes including adding a vignette #118

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
wants to merge 87 commits into from

Conversation

kenmawer
Copy link
Contributor

The vignette describes compactify, taken out from the archive vignette originally. It also describes how the use of compactify can save time for operations such as as_of. Note that the runtimes are not hard-coded, meaning that the time it takes may differ from one run of the code to another.

Note that once complete, the archive vignette should have a link to compactify in it so a user can find the information they need by clicking "See more" or something of the like.

admin and others added 30 commits May 10, 2022 16:53
Merge branch 'main' into epi_slide-error_message

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Merge branch 'main' into epi_slide-error_message
Merge branch 'main' into epi_slide-error_message
…tatement

Merge branch 'main' into epi-archive-print
@brookslogan
Copy link
Contributor

Closes #111. Note this comment if it is still applicable to this PR.

kenmawer added a commit to dajmcdon/epiprocess that referenced this pull request Jun 29, 2022
Merge branch 'km-compactify_time' into km-compactify_rectify

# Conflicts:
#	DESCRIPTION
#	data-raw/archive_cases_dv.R
@kenmawer kenmawer closed this Jun 29, 2022
@kenmawer kenmawer changed the title Created a separate vignette to describe compactify, as well as its indirect ability to save time compactify changes including adding a vignette Jun 29, 2022
@brookslogan
Copy link
Contributor

Were all the changes that were in this PR incorporated into #101?

@dajmcdon
Copy link
Contributor

dajmcdon commented Jul 8, 2022

I think that's right. @ken and I went through these together to decide which to keep.

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

Successfully merging this pull request may close these issues.

4 participants