Having issues running UPP V3.0

[jwraby]

I just compiled and am running UPP V3.0 on an HPC using an input single hour netdf wrfout file produced by WRF-CHEM V3.8. The output GRIB file WRFPRS_d03.27 contains the expected output fields which I specified in the wrf_cntrl.parm file (pressure and hybrid level output), but no diagnostic (SHELTER) level output. I checked the wrf_cntrl.parm file to confirm that the first bit is 1 for the SHELTER level output. The log file (unipost_d03.27.out) has the following error:
At line 134 of file MDL2AGL.f
Fortran runtime error: Index '-1' of dimension 2 of array 'lvls' below lower bound of 1
Error termination. Backtrace:
#0 0x83ea60 in mdl2agl_
at /p/home/jraby/UPPV3.0/src/unipost/MDL2AGL.f:134
#1 0x718c70 in process_
at /p/home/jraby/UPPV3.0/src/unipost/PROCESS.f:95
#2 0x7f2c94 in wrfpost
at /p/home/jraby/UPPV3.0/src/unipost/WRFPOST.f:793
#3 0x7f41f6 in main
at /p/home/jraby/UPPV3.0/src/unipost/WRFPOST.f:134

In another test, I used the same UPP version and input a wrfout file produced by WRF V4.1. This WRF run was configured to use the newer hybrid mass sigma-pressure coordinate rather than the traditional sigma terrain following coordinate. It also uses vertical nesting. There are also model levels which are below 10 meters AGL in this configuration. This wrfout file is subhourly (15-min interval) with a forecast valid time given in the filename and the startdate given by dumping the file to text and looking for START_DATE. The lead time in hours is 11 based on the difference between the startdate and the date/time of the filename The run has an immediate error and the unipost_d01.11.out file has one error as follows:
"error opening /p/home/jraby/UPPV3.0/wrfprd/wrfout_d01_2022-07-05_23:00:00".

Updated information: Today I was able to resolve the error: "error opening /p/home/jraby/UPPV3.0/wrfprd/wrfout_d01_2022-07-05_23:00:00", by converting the wrfout file from netCDF-4 to 64-bit offset. The UPP is still unable to complete the run and has new errors.
From the unipost_d01.11.out file it shows that it can open/read the wrfout file which means that it can read it in 64-bit offset format.
But there are new errors:
Error reading T from /p/home/jraby/UPPV3.0/wrfprd/wrfout_d01_2022-07-05_23:00:00
ndim = 3
end_index(1) 250
end_index(2) 250
end_index(3) 60

There are similar worded errors for U, V, W, QVAPOR, and P_HYD.

There is also another error at the end of the log file as follows:
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.

Backtrace for this error:
#0 0x2aaaabc6c3ff in ???
#1 0x2aaaab5100cc in ???
#2 0x57b644 in initpost_
at /p/home/jraby/UPPV3.0/src/unipost/INITPOST.f:434
#3 0x7f200c in wrfpost
at /p/home/jraby/UPPV3.0/src/unipost/WRFPOST.f:687
#4 0x7f41f6 in main
at /p/home/jraby/UPPV3.0/src/unipost/WRFPOST.f:134
./run_unipost_minutes: line 406: 281950: ${RUN_COMMAND} > unipost_${domain}.${fhr}.out 2>&1

Is there an explanation for the inconsistent results obtained with the two wrfout files? Any troubleshooting assistance for the specific errors described would also be appreciated.

[laurenfrederick]

Hi, @jwraby, thank you for your question! Since this is related to the UPP, I've copied it over to the UPP discussions forum (NOAA-EMC/UPP#752) so that you can get a more targeted response.

[jwraby]

Thanks for catching this and getting it into the right forum! R/ John From: laurenfrederick ***@***.***> Sent: Monday, July 31, 2023 12:30 PM To: ufs-community/EPIC-GST ***@***.***> Cc: Raby, John W CIV USARMY DEVCOM ARL (USA) ***@***.***>; Mention ***@***.***> Subject: [URL Verdict: Neutral][Non-DoD Source] Re: [ufs-community/EPIC-GST] Having issues running UPP V3.0 (Discussion #21) Hi, @jwraby <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2Fjwraby&data=05%7C01%7Cjohn.w.raby2.civ%40army.mil%7C80a03009cf674a31839 c08db91f433ab%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C63826425025882345 3%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rwD95goVb2UttJvZwvHadZx42AjirmJo%2FCn jVlqjVPo%3D&reserved=0> , thank you for your question! Since this is related to the UPP, I've copied it over to the UPP discussions forum (NOAA-EMC/UPP#752 <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2FNOAA-EMC%2FUPP%2Fdiscussions%2F752&data=05%7C01%7Cjohn.w.raby2.civ%40ar my.mil%7C80a03009cf674a31839c08db91f433ab%7Cfae6d70f954b481192b60530d6f84c43 %7C0%7C0%7C638264250258823453%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OxU1PBtJr npikwDF6jhoSuSVQbecCyulzlWh6vU7Eos%3D&reserved=0> ) so that you can get a more targeted response. - Reply to this email directly, view it on GitHub <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2Forgs%2Fufs-community%2Fdiscussions%2F21%23discussioncomment-6598128&dat a=05%7C01%7Cjohn.w.raby2.civ%40army.mil%7C80a03009cf674a31839c08db91f433ab%7 Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C638264250258823453%7CUnknown%7CT WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3 D%7C3000%7C%7C%7C&sdata=I%2F1RK0xtOPI%2BrD7j%2BQDEkDZAnMZxl9ZfsVwe1Ut7LRo%3D &reserved=0> , or unsubscribe <https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.c om%2Fnotifications%2Funsubscribe-auth%2FAUX5FH7IL5ILTP5FJYHFXHTXS72TBANCNFSM 6AAAAAA2RY5KCA&data=05%7C01%7Cjohn.w.raby2.civ%40army.mil%7C80a03009cf674a31 839c08db91f433ab%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C63826425025882 3453%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1 haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=FH9sVAFA5jcYxeKoDHYmMAdoRX3r8ZhDUF DSy4FZlcI%3D&reserved=0> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AUX5FHZNJAL4566I4P5XT43XS72TBA5CNFS M6AAAAAA2RY5KCCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3T UL5UWJTQAMSW7A.gif> Message ID: ***@***.*** ***@***.*** om> >