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
Right now we can do prediction (i.e., design matrix generation) by specifying a set of data values ({"x": 1, "y": 2}). But for some purposes, like generating all pairwise categorical significance tests ("is the value of my linear predictor significantly different at a == a1 than it is at a == a2?"), it would be nice to be able to write this in terms of factor values ("is the value of my linear predictor significantly different when the C(...) factor is on level a1 compared to when it's on level a2?", without having to grovel through the AST of the factor's python code to figure out which data variables are being accessed. In particular, this would be expressed at the same representational level as factor-level metadata (see #61).
So we should have a version of predict that takes a set of specifications for factor values, and goes from there.
The text was updated successfully, but these errors were encountered:
Right now we can do prediction (i.e., design matrix generation) by specifying a set of data values (
{"x": 1, "y": 2}
). But for some purposes, like generating all pairwise categorical significance tests ("is the value of my linear predictor significantly different ata == a1
than it is ata == a2
?"), it would be nice to be able to write this in terms of factor values ("is the value of my linear predictor significantly different when theC(...)
factor is on levela1
compared to when it's on levela2
?", without having to grovel through the AST of the factor's python code to figure out which data variables are being accessed. In particular, this would be expressed at the same representational level as factor-level metadata (see #61).So we should have a version of predict that takes a set of specifications for factor values, and goes from there.
The text was updated successfully, but these errors were encountered: