PCPCombine: FCST_PCP_COMBINE_INPUT_OPTIONS not being used? #2158
-
In the NAM, there are two "WEASD/Z0" variables
They different in
I'd like to use record 64, so in my METplus conf file I set FCST_PCP_COMBINE_INPUT_OPTIONS = GRIB2_pdt=0;. However, it doesn't look the PCPCombine is using this information because the command that ran was /apps/ops/para/libs/intel/19.1.3.304/met/11.0.1/bin/pcp_combine -v 2 -subtract /lfs/h1/ops/prod/com/nam/v4.2/nam.20230430/nam.t06z.awip1206.tm00.grib2 'name="WEASD"; level="Z0";' /lfs/h1/ops/prod/com/nam/v4.2/nam.20230430/nam.t06z.awip1200.tm00.grib2 'name="WEASD"; level="Z0";' -name "WEASD_A06" pcp_combine_nam_accum06hr_WEASD_init2023043006_fhr006.nc but I would have expected /apps/ops/para/libs/intel/19.1.3.304/met/11.0.1/bin/pcp_combine -v 2 -subtract /lfs/h1/ops/prod/com/nam/v4.2/nam.20230430/nam.t06z.awip1206.tm00.grib2 'name="WEASD"; level="Z0"; GRIB2_pdt=0;' /lfs/h1/ops/prod/com/nam/v4.2/nam.20230430/nam.t06z.awip1200.tm00.grib2 'name="WEASD"; level="Z0"; GRIB2_pdt=0;' -name WEASD_A06 pcp_combine_nam_accum06hr_WEASD_init2023043006_fhr006.nc |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi @malloryprow, I confirmed that I get the same behavior. It looks like there is a bug in the PCPCombine wrapper when running in -subtract mode. I created issue #2161 to track this fix. Do you need a bugfix to be applied to METplus 5.0? |
Beta Was this translation helpful? Give feedback.
I created PR #2162 for this fix on the develop branch. Could you review it when the tests finish running?