-
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
Enhance TC-Pairs consensus logic to compute the spread of the location, wind speed, and pressure. #2036
Comments
Mentioned in the gap analysis for EVS version 1.0 on 9/7/22. |
Hi Seth,
I prefer the first one: NUM_MEMBERS.
While you are outputting TRACK_SPREAD, MSLP_SPREAD, MAX_WIND_SPREAD,
NUM_MEMBERS, please also include:
TRACK_MEAN (LAT_MEAN; LON_MEAN), MSLP_MEAN, MAX_WIND_MEAN in the same stat
file.
Thanks,
Jiayi
…On Mon, Oct 10, 2022 at 3:48 PM Seth Linden ***@***.***> wrote:
@KathrynNewman <https://github.com/KathrynNewman> yep sounds good, ywa
the track-spread is being output in nautical miles now.
@JiayiPeng-NOAA <https://github.com/JiayiPeng-NOAA> we can certainly add
a new output column to the TCMPR stat line type that shows the number of
ensemble members. What do you think we should call it?
NUM_MEMBERS?
or
CONS_MEMBERS?
or
SPREAD_MEMBERS?
Open to suggestions?
—
Reply to this email directly, view it on GitHub
<#2036 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRTVNPOJS4527REUDFX5YDWCRXI5ANCNFSM5NNGSS2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@JiayiPeng-NOAA sounds good. I think we may already be producing some of that output for the "consensus" model (TRACK_MEAN (LAT_MEAN; LON_MEAN), MSLP_MEAN, MAX_WIND_MEAN). But if we are not, I can certainly add those variables. I will also add output for NUM_MEMBERS. Thanks! |
Hi Seth,
While you are calculating ensemble spread, you have all the ensemble mean
data (Mean_LAT, Mean_LON, Mean_SLP and Mean_WindSpeed).
Please output these variables in one file, which will help for further
statistical analysis.
Thanks,
Jiayi
…On Mon, Oct 10, 2022 at 6:55 PM Seth Linden ***@***.***> wrote:
@JiayiPeng-NOAA <https://github.com/JiayiPeng-NOAA> sounds good. I think
we may already be producing some of that output for the "consensus" model
(TRACK_MEAN (LAT_MEAN; LON_MEAN), MSLP_MEAN, MAX_WIND_MEAN). But if we are
not, I can certainly add those variables. I will also add output for
NUM_MEMBERS. Thanks!
—
Reply to this email directly, view it on GitHub
<#2036 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRTVNPM6VY4BIDVY3TSVVTWCSNFTANCNFSM5NNGSS2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…orked compute_gc_dist_stdev() to compute track-spread and dist-mean. Re-organized. Cleaned up. SL ci-skip-all
…S TRACK_SPREAD DIST_MEAN MSLP_SPREAD MAX_WIND_SPREAD. SL ci-skip-all
…S TRACK_SPREAD DIST_MEAN MSLP_SPREAD MAX_WIND_SPREAD. SL ci-skip-all
…e type: NUM_MEMBERS, TRACK_SPREAD, DIST_MEAN, MSLP_SPREAD, MAX_WIND_SPREAD. Also updated some wording for the consensus section related to this. SL
…f the consensus track variables. SL
…new consensus variables into the track-point object. SL ci-skip-all
…ter which points the bdeck after the loop. Also update with newly generated Makefile.in files from seneca.
…function from a header file.
Received feedback from @JiayiPeng-NOAA on 11/14/2022 recommending that we rename the 5 new TCMPR output columns as follows. Note that I swapped the order of TRACK_SPREAD and TRACK_STDEV below to group all the STDEV columns together:
I confirmed and approved these changes with @KathrynNewman. Reopening this issue to handle this renaming. |
…RACK_STDEV, MSLP_STDEV, and MAX_WIND_STDEV.
Describe the Enhancement
This enhancement request initially arose via METplus discussions in dtcenter/METplus#1341.
The METplus team met with NOAA/EMC on 2/2/2022 to discuss this issue and this GitHub issue is the result. Here are the steps:
Please see attached slides from the 2/2/2022 meeting:
J.Peng_discussion_20220202_new.pdf
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.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
27703542
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement 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: