jkgoodrich

I am allotting time for a full manual inspection of all release files to go along with the automated sanity checks that we have. It would be good to open...

Do we have a way to automatically update this each month, or do we only update when someone needs the newer version? We should also make sure this version is...

OK, that makes sense, then this doesn't impact v3.1 release at all really. I don't think those plots will change much and we used other metrics for evaluation as well.

Would be good to add in general stats. See epic https://github.com/broadinstitute/gnomad_production/issues/151

Thank you @PoisonAlien and @sabrinacamp2 It looks like this error was fixed with [this](https://github.com/broadinstitute/gnomad_methods/commit/38cb480b9e6cee75197ebeb7b06ccdb9e12f8dc7) commit, so this should be resolved in the newest gnomad_methods release. However, as described in this...

The newest release [v0.6.4](https://github.com/broadinstitute/gnomad_methods/releases/tag/v0.6.4) has fixed the `assign_population_pcs` function so that it still works with the code in the blog post. Closing the issue since I think this is now...