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 mean, shouldn't this be expected behavior? If you narrow down to time values starting at the first version, you get the "actual" revision behavior.
I suppose we could have a flag that triggers ignoring the time to the very first revision.
brookslogan
changed the title
revision_summary() outputs high/nonrepresentative time-to-semistable estimates when there's an (API) outagerevision_summary() outputs high/nonrepresentative time-to-semistable estimates when there's a rare outage
Dec 13, 2024
Well, it surprised me I guess. Not a great experience having to filter & reconvert, maybe better when we have a direct filter method.
And this + datetime versions + out-of-sync fetching challenges the underlying assumption of convenience that we have the entire history from (-Inf, versions_end]. One alternative would be replacing versions_end with a vector versions_observed (1 entry per snapshot recorded). Not sure if this would make the flag above easier to implement.
Based on this experience, I'd hope we'd default the flag to TRUE. I'd guess the mechanism for ignoring the first version would involve filtering time values somehow, though the simple way to filter time values would bias things a little bit towards lower reporting latency than was actually the case, since if we just exclude time values <= archive$DT[version == min(version), max(time_value)] then at the starting versions the minimum lag would be 0. Debiasing there seems like it might be a pain to do, but it may be fine to do without.
brookslogan
changed the title
revision_summary() outputs high/nonrepresentative time-to-semistable estimates when there's a rare outagerevision_summary() outputs high/nonrepresentative time-to-semistable estimates from initial report
Dec 13, 2024
E.g., on NSSP.
Created on 2024-12-12 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: