ERROR ABORT in subroutine M3WNDW

I/O API m3tools
1

Dear all,

I am trying to execute m3wndw to narrow the scope of my emission file.
I typed the following commands in the interactive window.

setenv INFILE $MYPATH/emis_2017244.ncf
setenv OUTFILE $MYPATH/out.ncf
m3wndw INFILE OUTFILE

Then I typed these options for response:

Enter starting date (YYYYDDD) for run [2017244] >> Using default 2017244
Enter starting time (HHMMSS) for run [0] >> Using default 0
Enter duration (HHMMSS) for run [240000] >> Using default 240000
Enter name for windowed grid [“WNDW_CN3GD_152X1”] >> Using default “WNDW_CN3GD_152X1”

Enter LOCOL [1] >> Using response 28
Enter HICOL [28] >> Using response 148
Enter LOROW [1] >> Using response 1
Enter HIROW [1] >> Using response 97

Finally, I got errors:

Value for IOAPI_OFFSET_64 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 variable
netCDF error number -59 processing file “OUTFILE”
NetCDF: Name contains illegal characters
*** ERROR ABORT in subroutine M3WNDW
Could not open output file OUTFILE
Date and time 0:00:00 Sept. 1, 2017 (2017244:000000)

Please let me know why this is wrong and how to fix it.

Here is the full log file.
m3wndw.txt (242.0 KB)

Best
Jin

2

Curious.

First of all, what is $MYPATH – is it a real path? …and how in the world did the log have
File name "$MYPATH/emis_2017244.ncf"
using $MYPATH instead of its value?
Where did $INFILE come from (what generated it? Is it a legitimate I/O API generated file?) and how in the world are we seeing all of its VNAMEs be blank? What is the output of ncdump -h $INFILE?

It would also be interesting to see the result of env | sort immediately before the m3wndw command…

3

For privacy, I changed my real path to $MYPATH. The absolute path I set for real use. I also changed my real path in the log file (I only changed it). You can ignore $MYPATH and take $MYPATH as /full_path_to_file. Sorry for the inconvenience.

Here is the ncdump -h output.
emis_2017244.ncf.txt (35.0 KB)

This is how the error is displayed on the terminal.

image
image882×575 12.1 KB

I got $INFILE from another group, so I want to modify the emission file for my own use.

4

It would seem to me that something is being corrupted in the executable, possibly by an inconsistent build: I note that the file-header says I/O API 3.0 whereas the m3wndw program-version is for 3.2 Possibly you should do a complete re-build, using a consistent I/O API library throughout.

5

Thanks for your reply.

I used ncatted to modify IOAPI_VERSION to "ioapi-3.2: $Id: init3.F90 185 2020-08-28 16:49:45Z coats $ ". I executed m3wndw again, and it worked!