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

Be more cautious with model-related artifacts #7

Open
lgessler opened this issue Oct 18, 2020 · 0 comments
Open

Be more cautious with model-related artifacts #7

lgessler opened this issue Oct 18, 2020 · 0 comments

Comments

@lgessler
Copy link
Collaborator

The problem: There are many places where we used serialized representations of parameters or other model-related information.

Why it's a problem: Often these are stored in a binary format (e.g. a pickle) that may be volatile with respect to platform, Python version, or dependency version.

Proposed solution: At minimum, these kinds of serialized representations should make explicit the assumptions they're making about platform and versions. This could mean:

  • (prerequisite) explicitly indicate python and package versions for any given release of the AMALGUM pipeline
    • I'll be doing this soon with a conda env.yml file
  • Adding AMALGUM version numbers to serialized model files stored on corpling.uis.georgetown.edu
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

No branches or pull requests

1 participant