ALLOW_MISSING_INPUTS Functionality in MET v12.0.0 and METplus v6.0.0 beta3 Testing #2528
-
I tested MET v12.0.0-beta3 and METplus v6.0.0-beta3 with the subseasonal component of EVS. To test missing input files for grid-to-obs (which was easier to test but grid-to-grid would be similar), I set POINT_STAT_ALLOW_MISSING_INPUTS = True and POINT_STAT_INPUT_THRESH = 0.8 in my PB2NC and Point_Stat config files. Removing 2 obs (prepbufr_nam) files yielded a successful run for all periods as this was in the 80% threshold...only WARNINGs were issued. However, removing 3 obs (prepbufr_nam) files yielded ERROR: George suggested to add an option to loop through the times and gather the pass/fail numbers, then skip running with a warning if the threshold is not met, otherwise loop through the times again and actually run the METplus tools. I think this might work if the word "WARNING" was replaced with something like "NOTE" or maybe "ATTENTION" to comply with NCO standards for operational code. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Hi Shannon, And thank you for bringing this effect to our attention. At the moment, George is out of the office and as he was the one who worked primarily on issue #2460 I'm going to defer to his direction on how to proceed with the fix. Will it cause any major negative effects to wait until his return to the office (April 11th) to pursue a fix, or do we need to get this patched up prior to that? |
Beta Was this translation helpful? Give feedback.
-
Hi John,
No worries, this can wait until George's return. This missing input
functionality is not an immediate requirement; it is something we have been
discussing in our telecon meetings that would be nice to have in the future
for our EVS code.
Thanks,
Shannon
…On Fri, Mar 29, 2024 at 12:09 PM j-opatz ***@***.***> wrote:
Hi Shannon,
And thank you for bringing this effect to our attention. At the moment,
George is out of the office and as he was the one who worked primarily on
issue #2460 <#2460> I'm going
to defer to his direction on how to proceed with the fix.
Will it cause any major negative effects to wait until his return to the
office (April 11th) to pursue a fix, or do we need to get this patched up
prior to that?
—
Reply to this email directly, view it on GitHub
<#2528 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP4MEUBH2WGKTF5XW5IERZLY2WG43AVCNFSM6AAAAABFNBLLBGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJTGUYDO>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Shannon Shields
SAIC at NOAA/NWS/NCEP/EMC
5830 University Research Ct. Rm 2180
College Park, MD 20740
***@***.***
|
Beta Was this translation helpful? Give feedback.
-
Shannon, I wanted to reach out again to communicate the status on our side. As you are probably already aware, we are waiting on funds to proceed with much of our work; as a result, we've had to put a temporary halt on most projects and issues that are not mission critical. Given this context, we'll have to hold off on any further development on this topic until funding is secured and priorities have been reassessed. I hope you understand this does not mean this issue is unimportant, and the METplus team wants to return to this issue when we are able and find you a more permanent fix than the current script solution you're using. |
Beta Was this translation helpful? Give feedback.
-
I totally understand the situation and appreciate the update. We can
continue discussion on this missing input functionality in the future.
Thank you John,
Shannon
…On Tue, Apr 16, 2024 at 2:45 PM j-opatz ***@***.***> wrote:
Shannon, I wanted to reach out again to communicate the status on our
side. As you are probably already aware, we are waiting on funds to proceed
with much of our work; as a result, we've had to put a temporary halt on
most projects and issues that are not mission critical.
Given this context, we'll have to hold off on any further development on
this topic until funding is secured and priorities have been reassessed. I
hope you understand this does not mean this issue is unimportant, and the
METplus team wants to return to this issue when we are able and find you a
more permanent fix than the current script solution you're using.
—
Reply to this email directly, view it on GitHub
<#2528 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP4MEUC2AE27NHNGQR7FR73Y5VWVRAVCNFSM6AAAAABFNBLLBGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCMZTHA3DE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Shannon Shields
SAIC at NOAA/NWS/NCEP/EMC
5830 University Research Ct. Rm 2180
College Park, MD 20740
***@***.***
|
Beta Was this translation helpful? Give feedback.
-
To follow up here, we discussed these details in the METplus/NOAA Telecon on 6/10/2024. The details of the enhancements are described in the GitHub issue comments. I am going to close this discussion and lock it to prevent future posts. @ShannonShields-NOAA, please continue any communication about this in GitHub issue #2524 or create a new discussion if appropriate. Thanks! |
Beta Was this translation helpful? Give feedback.
To follow up here, we discussed these details in the METplus/NOAA Telecon on 6/10/2024. The details of the enhancements are described in the GitHub issue comments.
I am going to close this discussion and lock it to prevent future posts. @ShannonShields-NOAA, please continue any communication about this in GitHub issue #2524 or create a new discussion if appropriate. Thanks!