run_create_omi.csh (4.7 KB)
Hello, everyone.
I’m having trouble creating the OMI file. Since the default OMI file for CMAQ v5.4 only provides data from 1979 to 2019. Considering that I need data for 2020, I am using /PREP/create_omi/scripts/run_create_omi.csh to create a new OMI file. However, when the script was executed, the OMI file for 2020 was not created. The script, log, and the List file have been uploaded. Thanks in advance for any advice and help.
run_create_omi.csh (4.7 KB)
toms_list.dat.txt (2.4 KB)
run_create_omi.log.txt (5.6 KB)
Do you have all of the input data downloaded? It appears that you have 12 datasets, but you should have 520 files.
cd TOMS_OMI_O3_column/2020
ls *.txt | wc
520 520 14040
Please rerun the following script and verify that all of the input datasets are downloaded.
./get_toms_data.q
Dear lizadams,
Thanks for your help. I apologise for uploading the wrong file. I double-checked and made sure I did have 520 files. However, after running run_create_omi.csh, I only get a normal file called ‘toms_list.dat’ and an empty file called ‘omi_full_2020.dat’. I notice that the log file alerts me to ‘Above errors found in OMI_FILE_LIST’, but I don’t know exactly what this error refers to. I would be grateful if you could give some advice. The script and log have been uploaded.
Thanks so much!
run_create_omi.csh.txt (4.7 KB)
toms_list.dat.txt (114.8 KB)
run_create_omi.log.txt (118.0 KB)
Please verify what version of CMAQ you are using, as these OMI scripts are under the CCTM/PREP directory.
Please follow the instructions available in this tutorial:
I believe this error indicates that you to clean up the input files as instructed.
Another solution is to download the OMI file for 2020 created by EPA available on the CMAS AWS s3 bucket:
https://2020platform.s3.amazonaws.com/index.html#2020platform/12US1/omi/
Liz
Dear lizadams,
Thank you so much! The version of CMAQ I’m using is v4.5.I’m sure the OMI scripts are under the CCTM/PREP directory.I’ve installed the OMI tool a few times as you suggested but the results are the same as before.The rest of CMAQ works fine and outputs reasonable results. Therefore, I am not going to go ahead and create the 2020 OMI file myself. I am going to use the files directly from your link. Thanks again for your help.
Haorui Wang
1 Like
I checked the upload toms_list.dat.txt. If the file is @whr’s toms_list.dat, the file should not have its first line because the line is equivalent to the run-script’s ls command listing the TOMS data files. I’m not uncertain why the run-script added the line to the file. You may try removing the set echo commands near line 9 and 18 in run_create_omi.csh.
Note that OMI_FILE_LIST is the environment variable used by the create_omi program to open and read the oms_list.dat file.
1 Like
Dear bhutzell,
Thank you very much for your help. Sorry for such a late reply, I have been testing based on your suggestions. According to your suggestions, I removed the set echo commands near line 9 and 18 in run_create_omi.csh. I am so happy because it works! However, after visualising it, I noticed that the ozone distribution seems to be wrong (The first figure is for the first day, i.e. 20190901; and the second figure is for the 300th day, i.e. 20200701). I only uploaded a partial screenshot as the full OMI file is too large. I thought that maybe I set the wrong NLAT_OMI and NLON_OMI. but after I changed NLAT_OMI and NLON_OMI several times, I found that the ozone distribution is always wrong. I am very confused. I will appreciate if you can give me some suggestions.
run_create_omi.csh.txt (4.7 KB)
toms_list.dat.txt (57.4 KB)
Haorui Wang
The odd patterns result because the satellite is missing observations at numerous latitude-longitude points across the globe on these days. The create_omi tool handles missing observations by using the last available observation at a location. However, previous observations are not available on the first day of data so the tool uses mean values over all the data files and the ozone column can shows more odd patterns. The polar regions suffer from long periods of missing observations because of polar night. Note that missing observation become more apparent when output files have a higher resolution over the latitude-longitude grid.
The create_omi tool allows seeing where observations are missing when the run-script option FULL_FILES equal T. The option produces output files at the data’s full resolution over latitude and longitude. The omi_full_YEAR.ncf file (YEAR equals 2020 in the case.) has a variable called O3_MISSING showing where observations are missing. It equals 1.0 for missing observations. Otherwise, the variable equals -1.0. The below plots give examples of O3_MISSING’s values.
3 Likes
Dear bhutzell,
Thank you very much for your help. It is so clear!
Haorui Wang
2024.9.4