Turns out there was no problem with the MoCompleteness summary metric, but with how I was trying to set it in my example.
I did however fix a lingering inconsistency with how the kwargs metrics for completeness were handled between the two different versions of completeness summaries (over time and over H).
I also actually put in a small fix that I had done to update the RunComparison class a while ago.
Turns out there was no problem with the MoCompleteness summary metric, but with how I was trying to set it in my example.
I did however fix a lingering inconsistency with how the kwargs metrics for completeness were handled between the two different versions of completeness summaries (over time and over H).
I also actually put in a small fix that I had done to update the RunComparison class a while ago.