This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hello, I am not familiar with CMAQ or the CCTM model, so I cannot provide any information specific to that. The error you're seeing suggests that the data being written is too large for the size of the dimensions which have been specified (indicated by error -57). You might try contacting the maintainers of CMAQ to see if they can provide any insight into the model or what might be causing this to happen. I'm sorry I can't provide any immediately useful information, but without knowledge of the CCTM model I can only speculate as to why it is trying to write excess data, and I have no insight into changing the behavior to fix this issue. Have a good day, -Ward > Hello, I asked this question before but didn't get any reply. I tried to > run the CMAQ (version 5.1) CCTM model agin. This time I used Netcdf - > 3.6.3. Good thing thing is, this time the whole program run for 4 hours > even got the messege, 'Program completed successfully' but in the log file > I found a error titled 'NCVGT: : NetCDF: Start+count exceeds dimension bound > netCDF error number -57 > Starting time not on file' > > and lot of warning titled 'WARNING in subroutine OPEN3 > File not available.' > > I have attached my log file. Any suggestion on this? Is this error > significant? should I care about this error? Thank you. > > Ticket Details =================== Ticket ID: MSH-339899 Department: Support netCDF Priority: Urgent Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.