Don't assume order and length is the same between observed and predicted features #3250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Combining diffs D68274239 & D68294872:
1 - D68274239 - [analysis] Don't assume order is the same in observed and predicted features
This is causing only 3 of 14 arms to show on an experiment. We're still assuming that within an observation the order of the metric names matches the order of the corresponding data.
2 - D68294872 - [analysis] Don't assume observed and predicted metrics are the same length
Comment from here:
In N6432597 I encounter a
StopIteration
error when rebased on D68274239. I believe this is becausepredicted.metric_names
is quite a bit longer thanobserved.data.metric_names
and so there's a chance thatnever finds the metric it needs and throws the
StopIteration
error.Differential Revision: D68336952