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

Validation procedure for code/model changes #1708

Closed
apiology opened this issue Dec 21, 2022 · 2 comments
Closed

Validation procedure for code/model changes #1708

apiology opened this issue Dec 21, 2022 · 2 comments
Assignees
Labels
Good first issue Issues that make good first tickets for new contributors. p1 important skill: backend engineering testing type: enhancement New feature or request

Comments

@apiology
Copy link
Member

From #1626:

A validation procedure will also be very helpful, to characterize the impact of changes made by folks like me who didn’t write the original code and model. I don’t know exactly what this looks like yet, but something pragmatic we can build on is better than nothing.

Perhaps a few key location+scenarios for microCOVIDs could be evaluated before and after and shown to the developer?

@apiology apiology added type: enhancement New feature or request p1 important skill: backend engineering Good first issue Issues that make good first tickets for new contributors. testing labels Dec 21, 2022
@zack112358
Copy link
Contributor

Can't assign it to myself, but I am working on this one starting Monday.

@zack112358
Copy link
Contributor

fixed in #1772

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good first issue Issues that make good first tickets for new contributors. p1 important skill: backend engineering testing type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants