Seeking info/contact on UPP code routine which computes flight level/wind energy fields on MSL and AGL levels.

[gspetro-NOAA]

This question has been moved from the UFS community discussion forum. The original question appears here: https://github.com/orgs/ufs-community/discussions/38

From @jwraby:

I'm running an older version of the UPP V3.1.1 which has the capability to post-process SPE HUM, TMP, UGRD, VGRD, and other variables as flight level/wind energy fields on MSL and AGL levels. The routine is part of unipost and is briefly described/coded in the file "FDLVL.f". The UPP User's Guide for Version 3 discusses these fields in the "UPP Control File Overview" section. The field names are given in the "Fields produced by unipost" section. I'm interested in contacting a person who knows about this routine who might be able to answer questions about the code. Thanks.

[jwraby]

Hi Gillian. Where was the question moved to? Thanks.

[gspetro-NOAA]

Hi @jwraby ,

The question was moved here--you originally posted it in the ufs-community, which is a good place for general UFS questions, but UPP-specific questions will usually receive more attention directly in the UPP repository. I'm about to post a redirect in the original question. You just caught me in the middle of my responses/redirects. ;)

Best,
Gillian

[gspetro-NOAA]

Hi @jwraby ,

I believe @WenMeng-NOAA or @HuiyaChuang-NOAA may know best who to contact, but they are both out of the country currently. I will make sure they get back to you when they return. You can probably expect to hear something in about one week.

There is some scientific documentation for FDLVL.f available here, but it is for the most recent version of the UPP. Nonetheless, it may point you in the right direction while you are waiting. The scientific documentation comes from the source code, so you could also check what is available in the comments of the FDLVL.f file of UPP v3.0 if you haven't already.

You've mentioned in the past that you have certain constraints and need to use UPP v3.0 with WRF, but ultimately, support for WRF has ended, and the UPP team likely will not be able to provide much assistance with UPP v3.0 since it is such an old version. That said, I will see what I can find out! In the meantime, you might also want to check out the WRF/MPAS forum for your work.

Best,
Gillian Petro | User Support Team

[gspetro-NOAA]

Hi @jwraby,

I just wanted to check in and let you know that the UPP team suggests the WRF/MPAS forum as the best option for support for your work. Unfortunately, UPP developers cannot provide support for older versions of UPP (support significantly declines prior to v10.1.0), and support for UPP with WRF ended several years ago. You could reach out to developers listed in the FDLVL.f Program History Log (see documentation), but I cannot guarantee that you will get a response because their priorities lie with current and future operational code. It may be worth a try though if you're still stuck.

Best,
Gillian

[jwraby]

Hi Gillian - Thanks for following-up and providing the suggestion from the UPP team on the best option for obtaining support for the particular interest I have in the UPP. I'm still looking for a contact with knowledge on the UPP flight level/wind energy fields. I just registered at the WRF/MPAS forum and I posted my query there. R/ John From: Gillian Petro ***@***.***> Sent: Tuesday, February 27, 2024 11:02 AM To: NOAA-EMC/UPP ***@***.***> Cc: Raby, John W CIV USARMY DEVCOM ARL (USA) ***@***.***>; Mention ***@***.***> Subject: Re: [NOAA-EMC/UPP] Seeking info/contact on UPP code routine which computes flight level/wind energy fields on MSL and AGL levels. (Discussion #875) Hi @jwraby <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2Fjwraby&data=05%7C02%7Cjohn.w.raby2.civ%40army.mil%7C045fde053f6a4afce9e 308dc37bee09f%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C63844654016719182 8%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW wiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=4SVsCPC6av%2BPgLkn9yMNJ%2FgZTz9hwqy8v5UR cAR%2F5Sc%3D&reserved=0> , I just wanted to check in and let you know that the UPP team suggests the WRF/MPAS forum <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fforum.mm m.ucar.edu%2Fforums%2Fwrf-upp.133%2F&data=05%7C02%7Cjohn.w.raby2.civ%40army. mil%7C045fde053f6a4afce9e308dc37bee09f%7Cfae6d70f954b481192b60530d6f84c43%7C 0%7C0%7C638446540167191828%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qEx%2BaqPl%2Bzd fMh94NwXYKTI75dnth%2BUIUhD2%2B5nlYxE%3D&reserved=0> as the best option for support for your work. Unfortunately, UPP developers cannot provide support for older versions of UPP (support significantly declines prior to v10.1.0), and support for UPP with WRF ended several years ago. You could reach out to developers listed in the FDLVL.f Program History Log (see documentation <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fnoaa-emc .github.io%2FUPP%2FFDLVL_8f.html&data=05%7C02%7Cjohn.w.raby2.civ%40army.mil% 7C045fde053f6a4afce9e308dc37bee09f%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C 0%7C638446540167191828%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=awIc3QaIM83THtjU8D5 j3mF7%2FjfvVOQuMJ1TYYi0HPs%3D&reserved=0> ), but I cannot guarantee that you will get a response because their priorities lie with current and future operational code. It may be worth a try though if you're still stuck. Best, Gillian - Reply to this email directly, view it on GitHub <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2FNOAA-EMC%2FUPP%2Fdiscussions%2F875%23discussioncomment-8608894&data=05% 7C02%7Cjohn.w.raby2.civ%40army.mil%7C045fde053f6a4afce9e308dc37bee09f%7Cfae6 d70f954b481192b60530d6f84c43%7C0%7C0%7C638446540167191828%7CUnknown%7CTWFpbG Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0 %7C%7C%7C&sdata=RCPxmdZ%2FGPFgx5b8U8V1ARmk8RKh%2FLuIWd5ivXi%2FWI4%3D&reserve d=0> , or unsubscribe. You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AUX5FH4WKJHDXR5OC263UILYVYNP3A5CNFS M6AAAAABDMHU4NOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3T UL5UWJTQAQNOH4.gif> Message ID: ***@***.*** ***@***.***> >