# Benchmark case for CMAQ 5.3.2 fails

**URL:** <https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035>\
**Category:** Run Time Errors and Issues\
**Created:** [January 28, 2021, 6:07pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035 "2021-01-28T18:07:42Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![msospedra](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@msospedra](https://forum.cmascenter.org/u/msospedra)\
**Post date:** [January 28, 2021, 6:07pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/1 "2021-01-28T18:07:42Z")

</div>

CMAQ is failing when is trying to create the CONC file when we try to run the benchmark case. We are able to run CMAQ5.3.2 for a different set of input files and domain, but somehow it crashes with the benchmark run script. Any ideas? (attached is the log file)

```
 >>--->> WARNING in subroutine OPEN3
 File not available.
 Could not open CTM_CONC_1 for update - try to open new

 Conc File Header Description:
    Concentration file output
    From CMAQ model dyn alloc version CTM
    Set of variables (possibly) reduced from CGRID
    For next scenario continuation runs,
    use the "one-step" CGRID file
    Layer 1 to 1
 
 Value for IOAPI_CHECK_HEADERS: N returning FALSE
 Value for IOAPI_OFFSET_64: YES returning TRUE
 Value for USR_DFLAT_LVL not defined; returning default: 9
 Value for COMPRESS_NC not defined;returning default: TRUE
 Value for IOAPI_CFMETA not defined;returning default: FALSE
 Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
 Error creating netCDF file
 netCDF error number -36 processing file "CTM_CONC_1"
 NetCDF: Invalid argument
 NetCDF: Invalid argument
 /pln6/MCS/CMAQ5.3.2/CMAQ-master/data/output_CCTM/CCTM_CONC_v532_cb6_intel_Bench_2016_12SE1_20160701.nc

 *** ERROR ABORT in subroutine OPCONC on PE 000          
 Could not open CTM_CONC_1

```

PM3EXIT: DTBUF 0:00:00 July 1, 2016  
Date and time 0:00:00 July 1, 2016 (2016183:000000)

[CTM\_LOG\_000.v532\_cb6\_intel\_Bench\_2016\_12SE1\_20160701.txt](https://forum.cmascenter.org/uploads/short-url/3CpPx9IjKG7OxhY1YJ7PHqmxeAU.txt) (35.4 KB)

---

<div class="post-metadata">

**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 28, 2021, 6:19pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/2 "2021-01-28T18:19:06Z")

</div>

What version of netCDF and IOAPI are you using? Did you compile netCDF with large file support?  
[https://www.unidata.ucar.edu/software/netcdf/faq-lfs.html](https://www.unidata.ucar.edu/software/netcdf/faq-lfs.html)

---

<div class="post-metadata">

**Author:** ![msospedra](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@msospedra](https://forum.cmascenter.org/u/msospedra)\
**Post date:** [January 28, 2021, 7:04pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/3 "2021-01-28T19:04:56Z")

</div>

Hi Chris,

Thanks for your reply.

These are the versions of iopai and netcdf that we are using:

```
ioapi-3.2: $Id: init3.F90 98 2018-04-05 14:35:07Z coats $                            
 Version with PARMS3.EXT/PARAMETER::MXVARS3= 2048                                     
 netCDF version 4.3.3.1 of Dec 4 2020 14:51:57 $   

```

Do you know how I can enable large file support? from the link you sent it seems to imply that there is no special compiler flag needed for Large File Support:

_ **Do I need to use special compiler flags to compile and link my applications that use netCDF with Large File Support?** _

_No, except that 32-bit applications should link with a 32-bit version of the library and 64-bit applications should link with a 64-bit library, similarly to use of other libraries that can support either a 32-bit or 64-bit model of computation._

---

<div class="post-metadata">

**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\
**Post date:** [January 28, 2021, 8:47pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/4 "2021-01-28T20:47:25Z")

</div>

Since netCDF 3.3 (IIRC), large file support has been automatic. You don’t need special compile flags, etc. for that.

---

<div class="post-metadata">

**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\
**Post date:** [January 29, 2021, 2:39am UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/5 "2021-01-29T02:39:01Z")

</div>

This may be off topic, but I don’t recognize the following two environment variables listed in your log file along with the other IOAPI environment variables like IOAPI\_OFFSET\_64 (indeed set to T), IOAPI\_CFMETA, etc.

> [@msospedra](#):
>
> ```auto
> Value for USR_DFLAT_LVL not defined; returning default: 9
> Value for COMPRESS_NC not defined;returning default: TRUE
> 
> ```

I was not aware that IOAPI supports netCDF internal compression which these two variables seem to refer to.

A look at netcdf.h suggests that netCDF error number -36 refers to the following

> #define NC\_EINVAL (-36) /\*\*\< Invalid Argument \*/

which may point to an error when netCDF functions are called from within IOAPI, but that shouldn’t happen unless modifications were made to IOAPI.

Again, I’m probably on the wrong track here, so apologies in advance if this is indeed the case.

---

<div class="post-metadata">

**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 29, 2021, 5:26pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/6 "2021-01-29T17:26:08Z")

</div>

You say that you are able to get CMAQv5.3.2 to run using a different domain and input files. How is that domain different?

---

<div class="post-metadata">

**Author:** ![msospedra](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@msospedra](https://forum.cmascenter.org/u/msospedra)\
**Post date:** [January 29, 2021, 5:52pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/7 "2021-01-29T17:52:25Z")

</div>

Thank you all for your help.

As Christian noticed, it turns out that we are using a modified version of IOAPI that allows for reading/writing netcdf4 files. We were able to run CMAQ5.3.2 with our 4km-by-4km grid Southern California domain with the saprc07tc\_ae6\_aq mechanism without any issues, so I don’t exactly understand why it wasn’t working with the benchmark case.

We set the following variables in the run script and that fixed the issue:

setenv IOAPI\_OFFSET\_64 NO  
setenv HDF5\_USE\_FILE\_LOCKING FALSE

Again, this is for a **modified** IOAPI version based on version 3.2, so I hope this doesn’t confuse other people into using these settings.

Thanks again for your time!

Marc

---

<div class="post-metadata">

**Author:** ![rajmal](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@rajmal](https://forum.cmascenter.org/u/rajmal)\
**Post date:** [September 13, 2024, 8:10am UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/8 "2024-09-13T08:10:17Z")

</div>

Dear All,

I am attempting to run CMAQv5.4. I am also getting similar kind of error. following is the error message comping at the end of log file. Please suggest a suitable solution / reasons if any. Thank you in advance.

Conc File Header Description:  
Concentration file output  
From CMAQ model dyn alloc version CTM  
Set of variables (possibly) reduced from CGRID  
For next scenario continuation runs,  
use the “one-step” CGRID file  
Layer 1 to 1

```
 Value for IOAPI_CHECK_HEADERS not defined;returning default: FALSE
 Value for IOAPI_OFFSET_64: YES returning TRUE
 Value for IOAPI_CFMETA not defined;returning default: FALSE
 Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_CMAQMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_SMOKEMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
 Value for IOAPI_TEXTMETA not defined; returning defaultval ': 'NONE'
 Error creating netCDF file
 netCDF error number -35 processing file "CTM_CONC_1"
 NetCDF: File exists && NC_NOCLOBBER
 NetCDF: File exists && NC_NOCLOBBER

```

---

<div class="post-metadata">

**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\
**Post date:** [September 13, 2024, 10:46am UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/9 "2024-09-13T10:46:53Z")

</div>

CMAQ insists on trying to open files in mode `FSNEW` (if the file already exists, fail; else create according to the supplied file-definition) rather than FSUNKNOWN (if the file already exists, check its consistency with the supplied file-definition; else create according to the supplied file-definition), wrongly IMNHO.

So you must delete already-existing CTM\_CONC\_1 (etc) files before the start of a run.

---

<div class="post-metadata">

**Author:** ![lizadams](https://avatars.discourse-cdn.com/v4/letter/l/49beb7/32.png) [@lizadams](https://forum.cmascenter.org/u/lizadams)\
**Post date:** [September 24, 2024, 1:18pm UTC](https://forum.cmascenter.org/t/benchmark-case-for-cmaq-5-3-2-fails/2035/10 "2024-09-24T13:18:49Z")

</div>


