Quick and dirty script to dump bioconda metrics from the anaconda.org API#4
Open
tomkinsc wants to merge 1 commit into
Open
Quick and dirty script to dump bioconda metrics from the anaconda.org API#4tomkinsc wants to merge 1 commit into
tomkinsc wants to merge 1 commit into
Conversation
… API Quick and dirty script to dump bioconda metrics from the anaconda.org API, meant to be executed under Python>=3.5.
Contributor
|
Thank you Chris! This should be useful indeed. I'll keep this PR open for now, and we will see if we cherry-pick or merge. |
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
2 participants
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.
Here are a couple quick and dirty scripts I had from a presentation earlier in the year; they dump bioconda metrics from the anaconda.org API, and are meant to be executed under Python>=3.5. Similar to what already exists in this repo, and thus not added to the Snakemake workflow. Here they are anyway in case they are helpful.
I thought it might be nice to show a histogram of the packages by download count (or downloads/day), to show the “long tail” of obscure packages, but the violin plots also show this.
Metrics example:
https://gist.github.com/tomkinsc/038703afcf85c5a790628e6a9a6f9af9