Update code and plots #24
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updating the study. This requires the package I've been developing to (re)use CRAN data, but I think it is worth it. I think it is more accurate, faster, easier to reuse and maintain.
Now the packages being archived are older:
I could explore if this is it due to longer notice to maintainers (I think Kurt extended the default notice to 3 weeks) or something else (CRAN cookbook?). We could check packages that were at risk of being archived and see if they submitted earlier or were archived (I recorded packages at risk till 2 months ago)
PS: I haven't used internal CRAN data, but we told Kurt that we would report back with our findings.