Open alvv1986 opened 1 year ago
Hi,
I apologize for the late response. Yeah - this is a simple fix. @param run_slant was designed for running X-STILT with TCCON or EM27, but I forgot to modify the default main script. Please check out an upcoming commit on Nov 18, 2023, where I also fixed a bunch of minor bugs when working with TROPOMI CH4 (if daily xCH4 data was downloaded from SRON).
Thanks, Dien
Hi Dien,
Thank you for the feedback. I am testing the new model codes, but I am getting the following error:
Error in met_list$met_file_format : $ operator is invalid for atomic vectors Execution halted
In the new version of run_xstilt.r we have the following lines
met = c('gfs0p25', 'hrrr', 'wrf27km')[2] # choose met fields met_path = file.path(homedir, met) # path of met fields met_list = download.met.arl(timestr, nhrs, run_trajec, met_path, met)
meanwhile in the previous version, I set up the lines above as follows
met = '/users/anliduvi/X-STILT/inout/WRF' met_path = file.path(met, 'ARL') # path of met fields met_file_format = '%Y%m%d' # met file name convention n_met_min = 1
and was working fine for quick tests. I realized that the parameter 'n_met_min' is no longer included in the new version, despite being listed in the namelist section. Please could you provide any hints on how to solve this issue?. Since I have my own WRF outputs, I do not execute the 'download.met.arl' function; instead I instruct the code on the location of my met files. Is that right?
Thank you so much in advance
Angel
Hi Angel,
I truly apologize for the late response. Finally got more time into the model code. I made some recent fixes to the download.met.arl
, which should allow you to use your own met fields. If you are still interested in using the model, feel free to check out the latest version esp around lines https://github.com/uataq/X-STILT/blob/master/run_xstilt.r#L177-L181. Let me know if it helps.
Dien
Hi,
I am trying to run the code for CH4 but I am getting the error below related to the run_slant variable. This issue seems easy to fix according to some R forums; however, I would like to hear from you about how I can proceed with this.
Thank you
--- Obtaining TROPOMI CH4 info ---
find.tropomi(): HH is given, narrowing down TROPOMI files... found the data that match the criteria; see nc file: S5P_RPRO_L2CH4__20180515T104750_20180515T123118_03037_01_010202_20181215T102911.nc?A-userid=alvv1986&Expires=1691571358&Signature=O0FVHdm4LXAKUh5zdkpZW3uQ9o-SPOvwVgHaElCTJrVcnRjCUcUUUfES1ZpWHdzslfe~vibwesyovpUhO4ngQeBbwqOR6T47Xm7HHl find.tropomi(): Searching for the correct TROPOMI file...
Output dir - /users/anliduvi/X-STILT/inout/XSTILT_output/Aarhus/out2018051511/users/anliduvi/X-STILT/inout/WRF_TROPOMI/CH4 Obs file - /users/anliduvi/X-STILT/inout/TROPOMI/CH4/L2/S5P_RPRO_L2CH4__20180515T104750_20180515T123118_03037_01_010202_20181215T102911.nc?A-userid=alvv1986&Expires=1691571358&Signature=O0FVHdm4LXAKUh5zdkpZW3uQ9o-SPOvwVgHaElCTJrVcnRjCUcUUUfES1ZpWHdzslfe~vibwesyovpUhO4ngQeBbwqOR6T47Xm7HHl Error in if (run_slant) { : argument is of length zero In addition: Warning messages: 1: In CRS(proj4string(countriesSP)) : sf required for evolution_status==2L 2: Using 'fast' method. This can cause inaccuracies in time zones near boundaries away from populated ares. Use the 'accurate' method if accuracy is more important than speed.