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
James: Please adjust the title and description accordingly.
As reported in #382, I added sampling uncertainty to an event detection evaluation wherein the time to peak error was computed. As a user, I expect that, when I ask for sampling uncertainty in an evaluation that includes time to peak error, I'll see a plot of time to peak errors that includes whiskers. Either that, or, if the WRES does not support sampling uncertainty whiskers for the plot, then the plot will be identical to the results for an equivalent evaluation with no sampling uncertainty.
That was not the case here: the plot of time to peak error against earliest valid time did not include whiskers and was not the same. Example plots are in this comment. Note that James responded in three comments that followed that comment indicating that this would be another ticket and not necessarily related to event detection.
The declaration to use to reproduce this results is below. Just comment out the sampling_uncertainty component to get a "before" result. As always, the data backing this evaluation is in the VLab Redmine Large Data Sets Google Drive folder.
If any more information is needed, let me know. Thanks,
I used the declaration in the Description without event detection in staging. I think I confirmed that this issue has nothing to do with event detection. Here are the results using the declaration without event detection or sampling uncertainty:
This evaluation, as declared, does not lend itself to time to peak error computations because I include no reference date window and its just a single time series for both observed and predicted. At least, I think that's why its just 0.
Here are the results with sampling uncertainty:
As a user, when adding sampling_uncertainty, I expect either whiskers to be added to the plot OR I expect the same result (indicating sampling_uncertainty is not supported). Instead, I get a different result, and, as a user, that's surprising me. If there is a reasonable expectation, that's fine, I just need to know what that is.
James: Please adjust the title and description accordingly.
As reported in #382, I added sampling uncertainty to an event detection evaluation wherein the time to peak error was computed. As a user, I expect that, when I ask for sampling uncertainty in an evaluation that includes time to peak error, I'll see a plot of time to peak errors that includes whiskers. Either that, or, if the WRES does not support sampling uncertainty whiskers for the plot, then the plot will be identical to the results for an equivalent evaluation with no sampling uncertainty.
That was not the case here: the plot of time to peak error against earliest valid time did not include whiskers and was not the same. Example plots are in this comment. Note that James responded in three comments that followed that comment indicating that this would be another ticket and not necessarily related to event detection.
The declaration to use to reproduce this results is below. Just comment out the
sampling_uncertainty
component to get a "before" result. As always, the data backing this evaluation is in the VLab Redmine Large Data Sets Google Drive folder.If any more information is needed, let me know. Thanks,
Hank
==========
The text was updated successfully, but these errors were encountered: