triage
triage copied to clipboard
dssg
General Purpose Risk Modeling and Prediction Toolkit for Policy and Social Good Problems
Pulling this out into an issue. Context from my earlier comment on the retrain-and-predict PR: We decided on using `matrix_type` in the first version of triage to handle different label...
This functionality might be good to make control the size of predictions table. Might also help in removing unwanted (buggy) runs altogether from the database.
See discussion associated with #835 We switched to `yaml.load` when upgrading `pyYAML` to 5.4; moving back to `full_load` would provide some security enhancements but require changing how we represent `as_of_time`...
In addition to logging to stdout/stderr when using the triage CLI, we should make it easier to ensure logs get captured to a file as well (although users could do...
lists should be lists dicts should be dicts. for example, ref_groups in bias audit config should be a dict so validator should check
It seems like a typical user would want to be able to run triage just from the pip installed version and the tutorial should probably support this, without requiring a...
For ease, Triage configures the testing module ( https://github.com/tk0miya/testing.postgresql ) using the easy method of re-instantiating the database each time. It advertises a way to cache it, potentially speeding up...
Maybe this should be a link? I thought I was reading the documentation... 
Looks like the documentation site interprets the underscores in the table names as subscripts: 
When specifying multiple feature groups with the same prefix, triage silently overwrites all of the resulting tables with the final table to be generated. This only returns an error after...
