Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the database schema to handle new columns added to the MET-11.0.0-beta1 output. #92

Closed
9 of 21 tasks
JohnHalleyGotway opened this issue Jun 15, 2022 · 2 comments · Fixed by #100
Closed
9 of 21 tasks
Assignees
Labels
METdataio: Load STAT Data priority: blocker Blocker requestor: METplus Team METplus Development Team required: FOR DEVELOPMENT RELEASE Required to be completed in the development release for the assigned project type: enhancement Improve something that it is currently doing
Milestone

Comments

@JohnHalleyGotway
Copy link
Contributor

JohnHalleyGotway commented Jun 15, 2022

Describe the Enhancement

Several new columns of "stat" output were added to the output of MET version 11.0.0-beta1. This issue is to update the database schema to handle these changes.

  • Issue Allow 2x2 HSS calculations to include user-defined EC values MET#2147:

    • Adds EC_VALUE to the end of the CTC line type
      • Value between 0.0 and 1.0 to indicate the expected correct rate
      • Fill existing CTC tables with a default EC_VALUE of 0.5
      • Only aggregate CTC tables where the EC_VALUE remains constant
    • Adds 4 new columns to the end of the CTS line type: HSS_EC HSS_EC_BCL HSS_EC_BCU EC_VALUE
      • HSS_EC is the Heidke Skill Score using the user-configurable expected correct rate. See details in Appendix C.
      • The _BCL and _BCU columns are the bootstrap CI limits.
      • The EC_VALUE is as described in the CTC column. Don't see a need to actually plot this.
  • Issue Add Anomaly Correlation Coefficient to VCNT Line Type MET#2022:

    • Adds 2 columns to the end of the VAL1L2 line type: FA_SPEED_BAR and OA_SPEED_BAR
      • These correspond to the VL1L2 line type's F_SPEED_BAR and O_SPEED_BAR columns but for the anomalies (F-C and O-C) instead
    • Adds 8 new columns to the end of the VCNT line type:
    • Centered Anomaly Correlation with normal and bootstrap CI's
      • ANOM_CORR, ANOM_CORR_NCL, ANOM_CORR_NCU, ANOM_CORR_BCL, ANOM_CORR_BCU
    • Uncentered Anomaly Correlation with bootstrap CI's
      • ANOM_CORR_UNCNTR ANOM_CORR_UNCNTR_BCL ANOM_CORR_UNCNTR_BCU

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.
No sub-issues needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Linked issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.
@JohnHalleyGotway JohnHalleyGotway added type: enhancement Improve something that it is currently doing alert: NEED ACCOUNT KEY Need to assign an account key to this issue priority: blocker Blocker requestor: METplus Team METplus Development Team required: FOR DEVELOPMENT RELEASE Required to be completed in the development release for the assigned project METdataio: Load STAT Data labels Jun 15, 2022
@JohnHalleyGotway JohnHalleyGotway added this to the METdatadb-2.0 milestone Jun 15, 2022
@JohnHalleyGotway
Copy link
Contributor Author

Please find some recent output from the nightly build of the develop branch posted here:
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/MET-11.0.0_data/NB20220706_MET_test_output.tar.gz

@venitahagerty
Copy link
Contributor

Updated the schema, and also the code to read and load the new columns.

@TatianaBurek TatianaBurek linked a pull request Jul 27, 2022 that will close this issue
13 tasks
@hankenstein2 hankenstein2 moved this from To Do to In Progress in METplus-Analysis-5.0-beta2 (08/03/22) Jul 27, 2022
venitahagerty added a commit that referenced this issue Aug 3, 2022
New columns added to the MET-11.0.0-beta1 output. Issue #92
Repository owner moved this from In Progress to Done in METplus-Analysis-5.0-beta2 (08/03/22) Aug 3, 2022
@jprestop jprestop removed the alert: NEED ACCOUNT KEY Need to assign an account key to this issue label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
METdataio: Load STAT Data priority: blocker Blocker requestor: METplus Team METplus Development Team required: FOR DEVELOPMENT RELEASE Required to be completed in the development release for the assigned project type: enhancement Improve something that it is currently doing
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants