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

Move model-output transform function to its own repository #68

Closed
5 tasks done
bsweger opened this issue Apr 9, 2024 · 0 comments · Fixed by hubverse-org/hubverse-transform#1
Closed
5 tasks done
Assignees
Labels
cloud work related to cloud-enabled hubs

Comments

@bsweger
Copy link
Collaborator

bsweger commented Apr 9, 2024

Background

As part of exploring the possibility of AWS event notifications -> AWS lambda function for converting incoming model-output data to parquet format (#52), there is some MVP code for the python-based data transformation function. It's currently in a branch of the hubverse-infrastructure repo.

Work needed for this issue

Move the hubverse-transforms Python module from hubverse-infrastructure to its own repository so that it can be deployed as a Hubverse AWS lambda function or used by non-hubverse-cloud hubs who want to perform transformations to their model-output data.

Definition of done:

  • The model-output transformation Python module is in a standalone repo in the Infectious-Disease-Modeling-Hubs GitHub organization
  • The module can be pip installed from the GitHub repo
  • The module is code checked (linter, types, tests) via CI
  • The new repository has branch protections that prevent updating main without a PR and require successful checks
  • The README describes how to set up the project locally
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud work related to cloud-enabled hubs
Projects
Development

Successfully merging a pull request may close this issue.

1 participant