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
Defining negative control methods is easy -- simply permuting the features, graph or PCA embedding should do the trick. To define the positive control, we'll need to take a look at how to define positive controls to target specific metrics.
This was already done in v1 -- we should look for the discussion on how this was tackled in the v1.
From what I can see the control methods are not organised in the same hierarchy that you listed here @rcannood, but I think it might be useful to do that, so we don't get confused with the naming. This will require reorganising the v1 code as well as the number of the control methods, unless we come up with a way to compute a method and process the different outputs (feature, embedding, graph) differently based on 1 outcome, complicating things.
The OpenProblems v1 repo has the following control methods:
The text was updated successfully, but these errors were encountered: