Hi Darby,
in your last post, are you specifically asking for feedback on the error you appear to be encountering when running combine as part of your CMAQ post-processing, either stand-alone or incorporated into the AMETv1.5 pre_and_post script? When you say that things were working with the AMET1.4 script, this probably doesn’t refer to running combine, because based on Wyat’s comments above, running combine wasn’t integrated into the AMETv1.4 script.
Prior to running combine as part of the AMET1.5 script, did you ever successfully run combine stand-alone for your case? The error message you show, as well as the grid spacing implied by your file names, suggest that you’re running into the same issue you encountered last year:
Back then, you updated the error checking in the combine code to work for your case. If running combine as part of the AMETv1.5 script, you need to make sure that the AMET script points to the same combine executable you created back then and that (I think) worked for you offline. And as was the case back then, the error isn’t caused by the different number of layers in ACONC and METCRO3D, but rather by non-robust grid consistency checking in combine for “odd” grid resolutions like 1.333 km.