Open epag opened 3 weeks ago
Original Redmine Comment Author Name: Hank (Hank) Original Date: 2019-05-15T17:09:47Z
James,
If you receive word from CBRFC that they would like this sooner rather than later, please feel free to bump this to an Urgent priority and assign it to the current development release. CB has been given access to the WRES Deployment Platform and were pointed to the instructions and examples. I would love for them to use WRES for this activity, but they may choose not to due to the headaches of having to move data from AWIPS to the WRES Deployment Platform.
Thanks for writing this ticket,
Hank
Original Redmine Comment Author Name: James (James) Original Date: 2019-05-15T17:19:18Z
Right. It was partly to give you (and others) a heads up, partly to express a desire to move all evaluation efforts to WRES, partly to express a real requirement for WRES.
Whatever we can do to get RFCs with live evaluation requirements (and existing accounts on WRES) over to the WRES as soon a practicable, I support that.
Author Name: James (James) Original Redmine Issue: 63987, https://vlab.noaa.gov/redmine/issues/63987 Original Date: 2019-05-15
Expected behavior:
Given a requirement to evaluate long-range forecasts that are produced by CBRFC and archived in a particular flavor of CSV, when I consider the options available to help evaluate those forecasts, then I want to choose WRES rather than EVS.
( Which could mean choosing WRES, and then enhancing WRES, but for now they are using EVS ).
Actual behavior:
Reported in #53457. Format example in #53457-7.
Implementation notes:
I've been asked to work on this for the EVS, but I would prefer to work on this for the WRES.
Given that the EVS and WRES have very different concepts of reading, the implementation for EVS is unlikely to be transferable to the WRES.