Closed michelleharrold closed 2 years ago
@michelleharrold Are you planning on merging this into the develop
branch in time for the release? I have an issue here (#751) where I'm tracking which PRs that are/have been going into develop
also need to be merged into the release branch (which has already been created). I can add this PR to the list if you like.
@gsketefian -- this PR is not intended for develop before the release. Eventually, we will get these features into develop, but for the time being they are for the ens_design_RRFS branch we are using for the DTC ensemble task.
@gsketefian -- this PR is not intended for develop before the release. Eventually, we will get these features into develop, but for the time being they are for the ens_design_RRFS branch we are using for the DTC ensemble task.
Ok, no worries then. Thanks.
DESCRIPTION OF CHANGES:
In METv10.1, the ensemble-stat tool has been split into two distinct tools: gen-ens-prod (new tool; creates ensemble products) and ensemble-stat (calculates ensemble stats). These changes break out the current functionality (solely using ensemble-stat) to use both gen-ens-prod and ensemble-stat.
In addition, functionality was added for the user to provide input and output locations for METplus verification via the config.sh.
Note, this PR is for the ens_design_RRFS branch.
TESTS CONDUCTED:
Ran test case (2019061500) with GFSv15.2 physics suite for a 3 member (SPPT) ensemble and compared baseline/current capability to new capability to show results are the same using the gen-ens-prod tool.
Ran a test case (2021053000) with 9-member RRFS ensemble data staged in a different directory than where the MET output was written to test MET INPUT/OUTPUT directory functionality. @willmayfield also ran a test with the 9-member RRFS ensemble data as a sanity check.
DEPENDENCIES:
None.
DOCUMENTATION:
When gen-ens-prod capability is included in develop, the documentation will be updated accordingly.
ISSUE (optional):
Related to issue #709 (eventually this will be merged into develop).
CONTRIBUTORS (optional):
@jwolff-ncar