Skip to content
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

CivicPy cache wrapper for fetching relevant checkpoints #303

Open
jsstevenson opened this issue Mar 26, 2024 · 6 comments
Open

CivicPy cache wrapper for fetching relevant checkpoints #303

jsstevenson opened this issue Mar 26, 2024 · 6 comments
Labels
enhancement New feature or request priority:low Low priority

Comments

@jsstevenson
Copy link
Member

Idle thought while reviewing #302 -- given that our data pipeline is reliant on specific checkpoints of CivicPy data, it might be helpful to write a small function or two that fetches the cache pickle for a relevant date (eg when an analysis notebook or a test set was run) from a VICC S3 bucket and places it in the appropriate local file location. That way we can easily ensure that team members are working with the same data set, analyses are reproducible, etc.

@jsstevenson jsstevenson added enhancement New feature or request priority:low Low priority labels Mar 26, 2024
@jsstevenson jsstevenson changed the title CivicPy cache wrapper CivicPy cache wrapper for fetching relevant checkpoints Mar 26, 2024
@korikuzma
Copy link
Member

@jsstevenson The civicpy cache can be found in s3://vicc-metakb/civicpy/

@jsstevenson
Copy link
Member Author

Right, I'm thinking about a way to declare/ensure in code that you're using a specific date's checkpoint file. We could also just use bash calls in a jupyter notebook too of course.

@korikuzma
Copy link
Member

@jsstevenson Yes, I like that! Just thought I'd post the location for whoever grabs the issue (not sure if everyone on the MetaKB team knew we also stored the civicpy cache in this bucket)

@jsstevenson
Copy link
Member Author

@korikuzma sounds like a job for some documentation!

@korikuzma
Copy link
Member

@jsstevenson #198 (comment)

Copy link

This issue is stale because it has been open 45 days with no activity. Please make a comment for triaging or closing the issue.

@github-actions github-actions bot added the stale label May 11, 2024
@korikuzma korikuzma removed the stale label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:low Low priority
Projects
None yet
Development

No branches or pull requests

2 participants