You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find that I often require two things from the same assumption-checking code:
Fail the analysis if the assumptions are incorrect,
Separate out two data frames: (1) a dataframe of the rows with faulty assumptions (to remand to data collection) and (2) a data frame that passes the checks (for further data analysis).
Alternatively, get a single data frame with a column that indicates whether they passed the check.
I understand the original intention of engarde is to fail early, and it does provide some tools for (2), but there are two particular pain points:
Getting back to a data frame with and without errors is a little tough. In some cases, that's easy: verify_all returns a dataframe in AssertionError.args[1]. In others, it is less so: none_missing returns a list of (index, column) tuples, which all have to be passed to pandas.DataFrame.loc separately.
Engarde throws the first errors it encounters, which means that any other checks that might fail will only be discovered when this error is worked around.
Can engarde be used for my use case, or is that too far away from engarde's philosophy?
The text was updated successfully, but these errors were encountered:
Interesting... I hadn't considered 1. Do you have any proposed APIs to support splitting the pipeline in two? I'm not quite sure what it would look like...
I did hit pain point 2 when I was using engarde more. Not sure how best to handle it either.
sieve would have to catch all assertions, extract the indices of the rows that contain the error, and return a tuple of data frames. This might not make sense for all checks, but I think it makes sense for a lot of them?
I find that I often require two things from the same assumption-checking code:
Alternatively, get a single data frame with a column that indicates whether they passed the check.I understand the original intention of
engarde
is to fail early, and it does provide some tools for (2), but there are two particular pain points:verify_all
returns a dataframe inAssertionError.args[1]
. In others, it is less so:none_missing
returns a list of(index, column)
tuples, which all have to be passed topandas.DataFrame.loc
separately.Can
engarde
be used for my use case, or is that too far away fromengarde
's philosophy?The text was updated successfully, but these errors were encountered: