-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add support for new point_weight_flag to the Point-Stat and Ensemble-Stat tools #2279
Comments
Related to Voroni Tesselations in MET #2661 |
Given time remaining in this beta, time remaining for this project's completion and associated funding, it seems like now is a good time to coordinate with the UK Met Office POCs and determine how much can be done to consider this issue closed. I will reach out to the necessary contacts later today. The remaining material will be captured for future work and future funding sources. |
Task checklist:
|
…id names and corresponding weights.
@georgemccabe and @j-opatz, I initially wrote this issue up to let the Any feedback on this detail? |
…mble-Stat config file and tweaking whitespace.
…config class. Also remove sue unneeded wgt_dp argument for the add_point_obs() functions. Plan to add logic to set the point weights only AFTER all the observations have been collected for each verification task.
@JohnHalleyGotway your new direction, keeping |
…it_point_weight.xml unit test to run Point-Stat on scalar and probability inputs weighting the stations by their elevation. Still need to add Ensemble-Stat calls.
@j-opatz note that I added a sanity check in the code. If
I suppose it's possible that a user could specify multiple station ID masks, request weighting, but only have weights defined for one or two of the masks, but not all of them. In that case, they might not want to see this warning. Should I keep it as a warning or switch to a debug log message? |
Describe the New Feature
The MET Grid-Stat tool supports a configuration option named grid_weight_flag to define weights for computing statistics aggregated over multiple grid points. The grid weighting is based on the area each grid point represents, giving larger weight to grid boxes with larger areas.
This task is to develop a method for weighting the aggregation of point observations. And the same basic motivation applies, wanting to avoid overemphasizing areas with dense observations, and underemphasizing areas with sparse observations.
Consider also whether
point_weight_flag
should be added to Stat-Analysis jobs when aggregating MPR lines to compute partial sums, contingency tables, and statistics.This request originally arose when aggregating SEEPS for individual stations into a spatial summary. The UK Met Office defines weights for that aggregation based on the spatial density of those stations. However, those weights are pre-defined and static since the stations they use are consistent run-to-run.
Recommend that when implementing this in MET, the weights NOT be static, in general. Instead, dynamically compute them for each verification task based on the location of the observations being processed.. The number and location of point observations can change dramatically run-to-run based on the masking region, variable, and data source. That being said, re-defining them in each run would likely be slower. Recommend that when specifying a
mask.sid
list of station id's we provide an option to define a fixed station weight.The tasks for this issue include:
point_weight_flag
configuration option for each verification task in Point-Stat and Ensemble-Stat with a default value ofNONE
, meaning apply a weight of 1 to all points.point_weight_flag
equal toDENSITY
to define the weights on the fly based on station location.mask.sid
is set to a file and station names are read from that file, add an option for a raw weight to be specified for that station (perhapsSID(weight)
with a numeric weight?). When aggregating across multiple stations, note that the true weight should be computed as the raw station weight divided by the sum of the weights of all points.Acceptance Testing
List input data types and sources.
Describe tests required for new functionality.
Time Estimate
1 week.
Sub-Issues
Consider breaking the new feature down into sub-issues.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Split between MetOffice and NOAA R2O keys.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
point_weight_flag
option.New Feature Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Linked issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
The text was updated successfully, but these errors were encountered: