I am using CMAQv5.4 to run DDM for a simulation but the program fails to generate the ASENS file the log files show the program is done successfully. I am using SAPRC07 and I have only one emission species in sensinput.dat for testing. The ASENS file is created but only has 11k which must be something wrong. Other than that, the simulation seems done successfully, ACONC, CONC and SENGRID are in normal size and the variables in them are reasonable. Looking forward to help.
It is unusual that the program completes and creates a SENGRID files, but not the ASENS files. Does SENGRID have reasonable values?
Another thing to check would be that your GRIDDED_BEIS actually has NO species values in it. Or run a different sensitivity parameter - maybe one to total NO like this (but with proper formatting):
Yes, I think SENGRID has reasonable values (not infinity or zero). And I had tried different options in seninput.dat, including single species (e.g., NO, SO) and all emissions. All test run come up with the same issue.
I have no idea why you are experiencing this, honestly. The last thing to check would be to see if you are removing the old output files completely and to check that you are writing into a completely clean and empty directory.
Not sure if it is correct, I tried to use medium memory IOAPI and still got the same error. I tried this modification and now the ASENS file seems successfully generated (regular size).
Hi Sergey,
I have got the same error when I run the latest CMAQ 5.4-HDDM(compiled in September 2023). I have limited the output species, used large IOAPI and online MEGAN.
Here’s my sensinput.dat and the error: sensinput.txt (424 Bytes)
>>--->> WARNING in subroutine WRITE3
Variable O3_ENO not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_ENO to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_2EN not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_2EN to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_EVA not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_EVA to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_2EA not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_2EA to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_EVB not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_EVB to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_2EB not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_2EB to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine WRITE3
Variable O3_ENV not in file: A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
>>--->> WARNING in subroutine PWRGRDD on PE 000
Could not write O3_ENV to file A_SENS_1
M3WARN: DTBUF 0:00:00 Sept. 20, 2021(2021263:000000)
And I tried to run CMAQ5.4 HDDM in the former version (compiled in March 2023) and output the normal ASENS file.
This looks like you have an previously created file that exists in your output directory and the code is trying to add to it. I would make sure that you are writing to a completely empty output directory as the first test.
Please, attach the rest of the log file. Or look for text similar to:
Could not open A_SENS_1 file for update - try to open new
Avg Sens File Header Description:
DDM3D Sensitivity file output
Averaged over the synchronization time steps