# MCIP problem when processing WRF3.9.1 output and benchmark **URL:** \ **Category:** MCIP\ **Tags:** admin\ **Created:** [January 4, 2020, 12:53pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215 "2020-01-04T12:53:27Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [January 4, 2020, 12:53pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/1 "2020-01-04T12:53:27Z")
Dear all, I have successfully compiled the MCIP5.1 and MCIP5.0 in CMAQ5.3.1 and CMAQ5.3 version. But when I tried to run the MCIP5.0 for processing the benchmark data and WRF3.9.1 output, there are errors reported below: * * * \*\*\* SUBROUTINE: SETUP \*\*\* ERROR OPENING WRF NETCDF FILE \*\*\* FILE = /GFPS8p/xyyang/wk/CMAQ-5.3/2016\_12SE1/met/wrfv3.8/subset\_wrfout\_d01\_2016-07-01\_00:00:00 \*\*\* NCF: Invalid argument * * * ``` *** ERROR ABORT in subroutine SETUP ABNORMAL TERMINATION IN SETUP Date and time 0:00:00 July 1, 2016 (2016183:000000) ``` Error running mcip ``` I am so curious about the specific error for such problem. I can process the same wrfout by using MCIP4.5 version in CMAQ5.2.1. ``` @tlspero @lizadams @bbaek @hogrefe.christian @cgnolte @fliu Kindly help me, please. Regards, Ryan ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [January 4, 2020, 12:57pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/2 "2020-01-04T12:57:34Z")
[run\_mcip.csh](https://forum.cmascenter.org/uploads/short-url/gXiGYQXgnN4hhjDMel2c7QervQ1.csh) (18.8 KB) [ncdump.txt](https://forum.cmascenter.org/uploads/short-url/bnEgrbBDllvwBN2A8xYnqJTXYxc.txt) (39.4 KB) Please find the run script and ncdump file for wrfout here. Note: I tried to use the MCIP5.1 and MCIP5.0 to process the benchmark wrf data and my own wrf3.9.1 output. But they all didn’t work. ---
**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\ **Post date:** [January 4, 2020, 10:10pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/3 "2020-01-04T22:10:26Z")
What version of netCDF are you using? ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [January 5, 2020, 3:51am UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/4 "2020-01-05T03:51:47Z")
Hi Chris, I use the netcdf4.1.3. Thanks! Kai ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [January 5, 2020, 1:30pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/5 "2020-01-05T13:30:45Z")
@tlspero @lizadams@cgnolte Please help me. Thanks ! ---
**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\ **Post date:** [January 5, 2020, 10:20pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/6 "2020-01-05T22:20:21Z")
Ryan, I don’t know what the problem is. That version of netCDF is quite old (from 2011). Did you use the same compiler (and version) in compiling MCIP as was used in compiling the library? When you use ncdump to view the header of the file, are you sure it is the same version of netcdf as you used for compilation? ---
**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\ **Post date:** [January 8, 2020, 10:22pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/7 "2020-01-08T22:22:59Z")
Basically, netCDF and _ncdump_ version should **never** be a problem; the format is well defined and all of the libraries (and _ncdump_s) use the same format. The only problems that may happen are “going backwards” – large-model files generated netCDF-3 or later will not be readable by netCDF-2; HDF based files from netCDF-4 or later will not be readable by netCDF-3 or earlier; however, these are exceptional situations that you have to “work at” to get yourself into. ---
**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\ **Post date:** [January 9, 2020, 1:26pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/8 "2020-01-09T13:26:26Z")
@cjcoats: I agree this should not be happening. That’s why it is perplexing. ``` use NETCDF rcode = nf90_open (file_mm(1), nf90_nowrite, cdfid) IF ( rcode == nf90_noerr ) THEN ! successfully opened NetCDF file; assume WRF ELSE ! error opening file as NetCDF [output error message] END IF ``` @Ryan is getting the error condition in the ELSE block. Any other suggestions of what could be going wrong? ---
**Author:** ![tlspero](https://avatars.discourse-cdn.com/v4/letter/t/bb73d2/32.png) [@tlspero](https://forum.cmascenter.org/u/tlspero)\ **Post date:** [January 9, 2020, 2:05pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/9 "2020-01-09T14:05:22Z")
@Ryan – Please check the path to the wrfout file, as you specified it in your script. In particular, should “GFPS8p” be “GPFS8p”? –Tanya ---
**Author:** ![Ryan](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@Ryan](https://forum.cmascenter.org/u/Ryan)\ **Post date:** [January 9, 2020, 8:06pm UTC](https://forum.cmascenter.org/t/mcip-problem-when-processing-wrf3-9-1-output-and-benchmark/1215/10 "2020-01-09T20:06:47Z")
Hi Tanya, I am pretty sure that the path to the wrfout file is correct. And I have solved this error by updating the MCIP to version5.1 (But I still have no idea what caused the error). @cgnolte Thanks a lot for your help, Chris. I really appreciate it. Regards, Ryan